Xenia Manager not running Arkham Origins config file

Installed Batman Arkham Origins to Xenia Manager (XM), adding launch_module = "SP.xex" to the config file. XM sees and runs the applicable title updates, but does not use the custom config file. The game won't run from default.xex and must be run from SP.xex, therefore the launch fails.
Steps to reproduce the behavior:

Run C:\Xenia\xenia_canary.exe <game path>\Content\0000000000000000\57520828\00004000\56B7A4470DB037981526DFD01E1F12E7 --launch_module="SP.xex" to show it works from the command line.

Edit C:\Xenia\config\Batman™ Arkham Origins.config.toml to include launch_module = "SP.xex". (removed TM for purposes of zip file)
Batman™ Arkham Origins config file

Click on game icon in Xenia Manager.

Xenia Manager log showing game launch was attempted

Game fails.

Canary log showing config file wasn't used running from default.xex

Expectations:
I expected the game to use the config file and launch it using SP.xex, similar to step 1 above, but from the logs it's evident it was launching default.xex instead. Unsure how else to get the game to run within Xenia Manager.
Other Observations:
This is not the only title that contains a title update and launch_module specification (e.g., Assassin's Creed IV), though it is the only such game that was ripped from disk. Initial install into Xenia Manager of Arkham Origins had a similar problem until I tricked it to launch SP.xex using the default config file during the install.
Screen captures and logs embedded within.

Just to be sure, can you increase draw resolution to 2 or 3 and then launch the game? Does it say in the title of Xenia window 2x2 or something similar?

@markjfine unrelated to the initial issue but i had a question, how exactly do you have all the pictures loading just fine? Many of my games only allow a blank disc image to be the icon for some reason.

@shazzaam7

Just to be sure, can you increase draw resolution to 2 or 3 and then launch the game? Does it say in the title of Xenia window 2x2 or something similar?

Chicken and egg issue here. I can set in the default configuration and it still fails, because it's not launching from the custom config telling it to launch SP.xex. I mean, I can set it to launch properly from the default config too, but then all of the other games will fail,  defeating the whole purpose of the per-game custom configs.

Also, I assume the game is a 2 disc game, correct?

Basically a 2-disk game, but XBox won't install the second disk. It's basically for multiplayer online, almost another game completely.

@markjfine unrelated to the initial issue but i had a question, how exactly do you have all the pictures loading just fine? Many of my games only allow a blank disc image to be the icon for some reason.

I did it manually. Found a good image to use either from XBox marketplace or something else, 'saved as' with the game name XM uses and an .ico extension, then moved it on top of the one in the Icons directory. In fact, sometimes the one found on Wikipedia or the other list are meh, so I replace it to make it look better.

Okay so here's what I gathered from my research so far.
The configuration file loads, but for some reason launch_module isn't (My guess is that it's one of those settings that is initialized before per-game configuration loads (Reference to what I'm talking about).
I also noticed your game is in 'Installed Game' format (00004000), so what you can do is extract it (Think Xenia VFS Dump Tool will work just fine) and in the extracted folder you will see 2 files (default.xex & SP.xex). You add SP.xex as the game and it will work just fine. I know this is a bypass and I'm sorry for that.
What I can do is add a detection to stuff like this so it can warn the user or even use the Xenia VFS Dump tool (since it's downloaded on first setup) to extract the game into the 'installed' format and then add the game that way.
If you have any further questions let me know.

Strange, but for '4' types (installed from disk) you could be right. I did have a problem adding the game to XM at first. Let me expand the game file and see if this works.

Interesting: Dumped the install file and edited installedGames.json to point to SP.xex... it worked. In fact, I think it's now using the title update that fixes the famous 'infinite fall' problem in NG+.
Also didn't realize that VFS Dump completely uncompresses the whole game, to include everything in the .dat directory. There was even a $SystemUpdate with a completely updated dash in there... wild stuff.
I may do this for all the '4' types, just to make sure those are reading the TUs as well.

Somewhat related, but as an FYI:
In VFS-dumping the other installed from disk games, I noticed that Xenia has a confusion problem with a registered symbol in the config file's name... I just edited them out of installedGames.json as well as the filenames in the config directory, and Xenia is happy again. May want to include a check for this when doing a game add.

Thank you for the FYI. I have fixed it in the 12567c7.


Release/2.0.0

About time this gets updated to 2.0 and then updates/fixes can be made to it.

Closing after discussion of enhancements needed for 2.0


Failed to calculate charging cost / energy for charging process

Hello,
I have recently setup Teslamate Agile and am using Home Assistant to track import costs of provider.
My particular provider has a plan where my electricity price drops to $0 between the hours of 12pm and 2pm Saturday and Sunday.
There is no API integration with this provide, so I have Home assistant just running a number helper to automate the price change in import costs from the provider.
The helper triggers on schedule and changes the price of import costs, all other services in HA that depend on this cost appear to be representing their data correctly, so I assume I have set that up right.
I have seen this on a few charges and it has cleared itself automatically in the past, but this one is not clearing and has now been overtaken by a newer charge that was calculated.
Attached is the charge id in question
data-1693143085068.csv
info: Microsoft.Hosting.Lifetime[0]
      Content root path: /app/
info: TeslaMateAgile.PriceHelper[0]
      Looking for finished charging processes with no cost set started less than 6 day(s) ago in the 'Home' geofence (id: 1)
info: TeslaMateAgile.PriceHelper[0]
      Calculating cost for charges 08/24/2023 23:43:53 UTC - 08/25/2023 03:19:42 UTC
info: TeslaMateAgile.PriceHelper[0]
      Phase correction: 2 -> 3
fail: TeslaMateAgile.PriceHelper[0]
      Failed to calculate charging cost / energy for charging process 65
      System.Exception: Charge calculation failed, pricing calculated for 628 / 629, likely missing price data
         at TeslaMateAgile.PriceHelper.CalculateChargeCost(IEnumerable`1 charges) in /src/TeslaMateAgile/Helpers/PriceHelper.cs:line 138
         at TeslaMateAgile.PriceHelper.Update() in /src/TeslaMateAgile/Helpers/PriceHelper.cs:line 74
info: TeslaMateAgile.PriceService[0]
      Waiting 14400 seconds until next update

This keeps repeating in the logs. Sadly I recreated the container without saving the old logs, but I am now up to charge process 66 and that one calculated fine.
While reading through closed issues, I saw that it was mentioned that the phase correction was not needed and to be removed, I have done that recently but has not fixes my issue. Here is my compose file
  teslamateagile:
    image: mattjeanes/teslamateagile:latest
    restart: always
    environment:
      - DATABASE_USER=teslamate
      - DATABASE_PASS=secret
      - DATABASE_NAME=teslamate
      - DATABASE_HOST=database
      - TeslaMate__UpdateIntervalSeconds=14400
      - TeslaMate__GeofenceId=1
      - TeslaMate__EnergyProvider=HomeAssistant
      - TeslaMate__LookbackDays=6
      #- TeslaMate__Phases=3 not required https://github.com/MattJeanes/TeslaMateAgile/issues/17
      - HomeAssistant__BaseUrl=<IP>
      - HomeAssistant__AccessToken=<TOKEN>
      - HomeAssistant__EntityId=input_number.re_import_price

Bonus question: Since I only charge every other day, I don't need this process checking every 5 minutes if a charge has completed, so have increased the update interval a little to an arbitrary time (4 hours) so it would only run 6 times a day.
My price only changes for 2 hours in a day, most charging sessions last 4-5 hours and the free energy period will usually be in the middle of the 4-5 hour session. Would the calculations be able to account for that without checking for charge events every 5 minutes?
Thanks

Hey, first of all many thanks for the detailed report - super appreciated!
Can I ask you to please run this call against the Home Assistant API and tell me the results?
POST <home-assistant-url>/api/history/period/2023-08-24T23:43:53Z?end_time=2023-08-25T03:19:42Z&filter_entity_id=input_number.re_import_price
Ensure you set the header Authorization: Bearer <home-assistant-token> as well!
What appears to be happening is when querying HA, the dates of the returned data don't line up with the charges in the CSV you sent me for some reason, as there is a matching step to designate all charges to a relevant price from the returned data. I suspect it may be a timezone related issue or perhaps something off by a second or minute etc.
For your bonus question, you can run it as infrequently as you like, but make sure your lookback days and HA history will work with what you set. In your particular scenario this would be fine because HA history would still be available which is where it gets the price data from, it doesn't really matter when it runs as long as the charge is within the lookback days and HA history is available for the date/time range 🙂

Sorry for the late reply, has been a busy few days and glad you liked the detail. I suffer from a lack of detail in reported problems at work every day so I know the struggle :)
Sure thing, here is the output of that get request
[[{"entity_id":"input_number.re_import_price","state":"0.2748","attributes":{"initial":null,"unit_of_measurement":"AUD/kWh","icon":"mdi:lightning-bolt","friendly_name":"red_energy_import_price"},"last_changed":"2023-08-24T23:43:53+00:00","last_updated":"2023-08-24T23:43:53+00:00"}]]

I suspected it may be time based thing, I do have my HA set to UTC+10 but I dont think I configured TMA to any timezone (not sure if its possible)
Thanks for the info on the bonus question, i'll back this off to run once a day then as I am only charging every other day. At first read of the doco it appeared that you may need to run this constantly to keep a running tally so I tried to space it out to the average of my charge sessions

Thank you! It looks like there was just one price of 0.2748 AUD/kWh for the duration of that charge, does that sound correct?
I'll run it through the debugger when I'm back home next week, I'm on holiday at the moment 🙂
If there's a particular section of the docs which implies TeslaMateAgile needs to run often to track charging within a charge session let me know and I'll try and reword it to be be clearer (or you could submit a PR of course!)

Hey @ObJuanK, I have now fixed this in v1.12.1 🙂
If you're interested, it was caused by the final price having the exact same time as the final charge entry, down to the millisecond. This combined with my usage of charge.Date < price.ValidTo instead of charge.Date <= price.ValidTo was the issue!
That charge you supplied worked out as 5.88 cost by the way in case the Home Assistant data has expired by now and you need to enter it manually.
Also I hope you don't mind, I have added your data to some unit tests to help prevent this issue re-occurring in future, but please let me know if this is an issue and you want me to remove it.

Hey Matt,
Thanks for looking into it and taking the time to reply on holidays.
Ive been on holidays myself but did not have the luxury of being anywhere with any form of reception, I guess thats a good thing 😄
I came home to find a myriad of failed calculations after my initial report, I have those logs if you are interested and can pull the data for those session if it helps you, just let me know.
But I pulled down v1.12.1 and when the container started it was able to calculate everything correctly as far back as HA could see, so looks like it did the trick! thank you 🙏
No issues with you using my data.
On the doco implying it needed to be run regularly: It was not anything specific and it could possibly be how I interpret things, but I inferred from context a little when reading the Required Environment Variables section.

The variable to check is in seconds, suggesting this can be configured to run near real time.
The example showing a default of 5 minutes,
The comment Check for completed charges without a set cost every x seconds to me, suggest you need to check for a completed charge regularly otherwise you'll miss it. Could be the every x seconds bit that did it for me.

What I think might help would be adding some subtext under Required Environment Variables with the explanation you provided me in your original reply.
Set the refresh value as in/frequent as you like. Ensure this does not exceed lookback days or HA data
I'd make a PR but I have not looked at how this works very much with other provides so can only offer my 2 cents on HA.
Thanks again and keep up the awesome work :)

Thank you, glad to hear it's all working for you now, and thanks for letting me use your data in the tests.
I've made a little commit here to change the wording and increase the example to an hour, hopefully this will make the purpose of it clearer: https://github.com/MattJeanes/TeslaMateAgile/commit/1ebe629644b318bf195856cf7f69c285617b1493
🙂


show all hoodie-account data in account template

This is a minor change.  But now basic feature set of hoodie-admin is done:
√ login as admin
√manage user accounts (add and remove account)
√ access user data

This looks good, thanks 👍
Right now we can only view accounts, we cannot change them. Also there are a few special properties in accounts. Here’s what I’d suggest to do next

Add username change feature
Add password change feature
Add password reset feature
Show profile properties as a table with key / value, value itself might be an object, so this could be nested. For example, there could be properties like profile.address.street. Allow to add / remove / change properties
Show roles (.roles) . Allow to add / remove roles. Roles is an array of strings. Roles are used for access management and feature flags (e.g. a "pro-plan" role after a user signed up for a paid plan)
List tokens (.tokens). Allow to remove tokens. Tokens are used for password reset, email confirmations, one-time logins, etc. They have an id, a type and an expiration date.

@gregor.
About item (4), I see 2 different approaches:
a) Firebase approach: create a tree (https://www.evernote.com/l/AZQ34mmVBppCQqyaN90MFID2Be5qZIVqbQkB/image.png)
b)Parse approach: a menu tree and tables
https://www.evernote.com/l/AZSLZVqPGLFD1Zhz9bQlz3CHn3LqZS-pyVEB/image.png
What have you imagined?

Thanks for doing the research, both parse and firebase are definitely projects we can learn from to make our admin dashboard great :)
We didn’t yet give a lot of thought on how to design the account edit forms. I think for now we would be good to have different sections for
# {username}

created: {createadAt}
signed up: {signedUpAt}
last update: {updatedAt}

[change username], [change password], [reset password], [delete account]

## Roles

list roles as bullet points, allow to add / remove

## Tokens

Show table of tokens with id, type, timestamp, expiration, and meta data. Allow to delete

## Profile

Show a table with key / value. For nested properties, we can simply do JSON for now and come up with something more sophisticated later?

This is long due... but I was wondering if what you mean is something like this:

When you click in the user, if opens details of profile.
I don't know about Roles and Tokens in Hoodie, though.

looks good to me :)


docs: examples for list filter

https://jinja.palletsprojects.com/en/2.11.x/templates/#list
Could someone please provide examples? Docs say: Convert the value into a list. If it was a string the returned list will be a list of characters.
What other value can be passed then?

Any iterable. It's equivalent to list(value) in Python.


toHaveToggleValue() fails with RN73

What happened?
A common matcher such as:
await expect(element(by.id('item.toggle'))).toHaveToggleValue(false);

seems to have stopped working when upgrading from RN 71 to 73. It introduces the following error:
Test Failed: Failed expectation: TOHAVEVALUE(value == “0”) WITH MATCHER(id == “item.toggle”)

What was the expected behaviour?
No response
Was it tested on latest Detox?

[X] I have tested this issue on the latest Detox release and it still reproduces.

Did your test throw out a timeout?

[ ] I have followed the instructions under Identifying which synchronization mechanism causes us to wait too much.

Help us reproduce this issue!
Should repro on any screen with a toggle coming from react-native-ui-lib.
In what environment did this happen?
Detox version:
React Native version:
Has Fabric (React Native's new rendering system) enabled: (yes/no)
Node version:
Device model:
iOS version:
macOS version:
Xcode version:
Test-runner (select one): jest / other
Detox logs
Detox logs
paste logs here!

Device logs
Device logs
paste your device.log here!

More data, please!
No response

Heavy debugging shows that for toggles based on non-switch components (as in react-native-ui-lib), rather, utilize RN's accessibility props, the issue is reproduced. For example:
      <TouchableOpacity {...this.getAccessibilityProps()} {...props} onPress={this.onPress}>
        {this.renderToggle()}
      </TouchableOpacity>

// where getAccessibilityProps is something like:
getAccessibilityProp() {
    return {
      accessible: true,
      accessibilityRole: 'switch',
      accessibilityState: {
        disabled,
        checked: value ? 'checked' : 'unchecked'
      },
      accessibilityValue: {
        text: value ? '1' : '0'
      }
    };

}

Starting RN73 (or 72), the native accessibility value is now determined based on both accessibilityValue and accessibilityRole. Up to RN71 it used to be set based on accessibilityValue alone. Namely, for a 'role=switch' and value=1`', this is the change that appears to have been introduced:
RN < 73:
iOS accessibility value = '1'

RN ≥ 73:
iOS accessibility value = 'switch, 1'

Workaround
Resort to jest-expecting based on getAttributes().value
Solution

(Best) accessibilityValue doesn't seem to be manipulated by RN when using the official RN Switch component. Need to have react-native-ui-lib either use it (instead of relying on a proprietary implementation) or at least better mimic what they are doing.
Adjust detox to compare either value=<accessibilityValue> or value=<accessibilityRole, accessibilityValue>

I see RN continues to break platform norms like crazy. 🤦♂
The accessibility value is used for things like VoiceOver. So I guess now RN has broken VoiceOver support because … reasons.

I see RN continues to break platform norms like crazy. 🤦♂
The accessibility value is used for things like VoiceOver. So I guess now RN has broken VoiceOver support because … reasons.

Leo! How have you been? 😄
This time, I wouldn't say it's actually RN itself, but rather more in the places where it is used unconventionally. We're currently to get things fixed via ui-lib.

Hello 🙂
If it’s a third party or internal framework, that’s fine. But if RN itself does it for all controls, that’s really bad.


Start trace with size > 1MB fails (err=87)

Hi Alex,
I was wondering why starting a trace with size > 1MB fails on my machine (Windows 10 Pro, Build 10.0.19043):
PS C:\Users\ipt\Desktop\Masterthesis\ipt> ./ipttool.exe --start 11488 3200000 0x0
/------------------------------------------\
|=== Windows 10 RS5 1809+ IPT Test Tool ===|
|===  Copyright (c) 2018 Alex Ionescu   ===|
|===    http://github.com/ionescu007    ===|
|===  http://www.windows-internals.com  ===|
\------------------------------------------/

[*] Size will be aligned to a power of 2
[+] Using size: 2097152 bytes
[+] Tracing Options:
           Match by: Any process
         Trace mode: User-mode only
     Timing packets: No  Packets
[-] Failed to start a trace (err=87)

However, specifying a size <= 1MB works:
PS C:\Users\ipt\Desktop\Masterthesis\ipt> ./ipttool.exe --start 11488 1600000 0x0
/------------------------------------------\
|=== Windows 10 RS5 1809+ IPT Test Tool ===|
|===  Copyright (c) 2018 Alex Ionescu   ===|
|===    http://github.com/ionescu007    ===|
|===  http://www.windows-internals.com  ===|
\------------------------------------------/

[*] Size will be aligned to a power of 2
[+] Using size: 1048576 bytes
[+] Tracing Options:
           Match by: Any process
         Trace mode: User-mode only
     Timing packets: No  Packets
[+] Trace for PID 11488 started

Regarding your soure code ( ipttool.c , libipt.h ) it should be possible to specifiy a range between 4KB and 128MB. I also checked CheckOption in ìpt.sys and it seems like specifying a range between 4KB - 128MB should be valid. Unfortunately, I do not have the time to debug the kernel driver.
Are you aware of this bug or do you have any idea what could be the reason for this?

Off the top of my head I would suggest looking at AllocateToPA and seeing
if that's what's failing. I think ipt.sys directly allocates a TOPA of the
size you specify, and depending on your CPU capabilities, there might be a
limit there.
Best regards,
Alex Ionescu
On Mon, Dec 6, 2021 at 8:48 AM Marcel @.***> wrote:

Hi Alex,
I was wondering why starting a trace with size > 1MB fails on my machine
(Windows 10 Pro, Build 10.0.19043):
PS C:\Users\ipt\Desktop\Masterthesis\ipt> ./ipttool.exe --start 11488 3200000 0x0
/------------------------------------------\
|=== Windows 10 RS5 1809+ IPT Test Tool ===|
|===  Copyright (c) 2018 Alex Ionescu   ===|
|===    http://github.com/ionescu007    ===|
|===  http://www.windows-internals.com  ===|
------------------------------------------/
[*] Size will be aligned to a power of 2
[+] Using size: 2097152 bytes
[+] Tracing Options:
       Match by: Any process

     Trace mode: User-mode only

 Timing packets: No  Packets

[-] Failed to start a trace (err=87)
However, specifying a size <= 1MB works:
PS C:\Users\ipt\Desktop\Masterthesis\ipt> ./ipttool.exe --start 11488 1600000 0x0
/------------------------------------------\
|=== Windows 10 RS5 1809+ IPT Test Tool ===|
|===  Copyright (c) 2018 Alex Ionescu   ===|
|===    http://github.com/ionescu007    ===|
|===  http://www.windows-internals.com  ===|
------------------------------------------/
[*] Size will be aligned to a power of 2
[+] Using size: 1048576 bytes
[+] Tracing Options:
       Match by: Any process

     Trace mode: User-mode only

 Timing packets: No  Packets

[+] Trace for PID 11488 started
Regarding your soure code ( ipttool.c
http://../blob/master/ipttool/ipttool.c#L40 , libipt.h
http://../blob/master/inc/libipt.h#L77 ) it should be possible to
specifiy a range between 4KB and 128MB. I also checked CheckOption in
ìpt.sys and it seems like specifying a range between 4KB - 128MB should
be valid. Unfortunately, I do not have the time to debug the kernel driver.
Are you aware of this bug or do you have any idea what could be the reason
for this?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ionescu007/winipt/issues/13, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABOEQ6B7CUZC2VSSA64B3QTUPS5MHANCNFSM5JOVMY7Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


DataProcessor objects with super() calls fail to pickle

DataProcessor objects that make super() calls fail to pickle. This is an issue in dill that was apparently resolved in a recent PR, but there has not been a new release of the package to incorporate this change.

As a workaround, you can do the following.
Original:
class DoubledPresetDataProcessor(PresetDataProcessor):
    """Processes a preset dataset, with no file I/O; doubles tensor values."""

    def get_raw_features_and_labels(self, dataset_path: str) -> \
            Tuple[Dict[str, np.ndarray], Dict[str, np.ndarray]]:
        """Returns doubled preset raw feature and label tensors.

        :param dataset_path: Unused
        :return: A 2-tuple of the features dictionary and labels dictionary,
            with matching keys and ordered tensors.
        """
        # This will cause a pickling error.
        features, labels = super().get_raw_features_and_labels(dataset_path)
        for name, tensor in features.items():
            features[name] = 2 * tensor
        return features, labels

Workaround:
class DoubledPresetDataProcessor(PresetDataProcessor):
    """Processes a preset dataset, with no file I/O; doubles tensor values."""

    def get_raw_features_and_labels(self, dataset_path: str) -> \
            Tuple[Dict[str, np.ndarray], Dict[str, np.ndarray]]:
        """Returns doubled preset raw feature and label tensors.

        :param dataset_path: Unused
        :return: A 2-tuple of the features dictionary and labels dictionary,
            with matching keys and ordered tensors.
        """
        # See #49 for why we can't use super().
        features, labels = PresetDataProcessor.get_raw_features_and_labels(
            self, dataset_path)
        for name, tensor in features.items():
            features[name] = 2 * tensor
        return features, labels


Typo "@rowcount_only"→"@rowcount_only"

https://docs.microsoft.com/en-us/sql/relational-databases/replication/validate-data-at-the-subscriber?view=sql-server-2017

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

This pull request is for the Live branch. We can't merge to Live. Would you resubmit your changes to the master branch? Thanks.

Hi @hyoshioka0128 , thank you so much for your contribution, and for making docs better! You've actually identified an issue in our docs - these parameters should be in code blocks, and if they are, there is no escape character necessary. I am updating all of these within a bulk update which will supersede this PR. As such, I will proceed with closing out this PR, but please feel free to reply should you need anything further.
Thanks!
Masha from the SQL Docs team


Update VPP not only in ligato but also in Contiv.

Coverage decreased (-0.05%) to 76.784% when pulling 8e34c69ceabaa1cc9439f81b382e18196b3432c5 on milanlenco:master into d03f13d616b8015334826d9a04d3f9d228387963 on contiv:master.


Add RedirectModel callback.

https://github.com/fchollet/keras/pull/8598 conditionally sets a model if it is not already set. After discussing with a colleague, this is a bit strange that a set function conditionally does or doesn't set something. This PR corrects that by adding a RedirectModel callback instead. This callback can be used to wrap another callback, while setting a different model when the training begins.
Example usage:
    model = keras.models.load_model('model.h5')
    model_checkpoint = ModelCheckpoint(filepath='snapshot.h5')
    parallel_model = multi_gpu_model(model, gpus=2)
    parallel_model.fit(X_train, Y_train, callbacks=[RedirectModel(model_checkpoint, model)])

this is a bit strange that a set function conditionally does or doesn't set something.

Yes, I would agree with that.
Regarding this new callback: why not simply have your original callback implement on_train_begin(), with self.model = your_model in it? Why would you need a new class to do it?

@fchollet that would work if you are implementing your own callback, or subclassing an existing one. This PR makes it so you can have this functionality without implementing your own callback classes.

I don't think this use case justifies an API change.

This PR makes it so you can have this functionality without implementing your own callback classes.

I think the solution will be to simply subclass an existing callback:

your_other_model = ...

class RedirectSomeCbk(SomeCbk):

    def on_train_begin(self, logs):
         self.callback.set_model(your_other_model)
         super(SomeCbk, self).on_train_begin(logs)

I will revert the previous PR to make it work (make set_model unconditional).


NE-1530: IngressController LB Subnet Selection in AWS

Allows users to specify subnets (i.e. Availability Zones) for IngressControllers using load balancers in AWS. Introduce
under the IngressControllerLBSubnetsAWS FeatureGate. Works for both CLB and NLBs.
Enhancement: https://github.com/openshift/enhancements/pull/1595
Epic: https://issues.redhat.com/browse/NE-705

/hold
EP is still under review and it's likely we will add a ingresses.config.openshift.io.spec.loadBalancer.platform.aws.subnets field as well.

Install failure
/test e2e-azure

Yikes, I messed up this rebase bad. Fixing.

An example failure from verify-crd-schema.  Is it in development?

error running generator schemacheck on group operator.openshift.io:
could not run schemacheck generator for group/version operator.openshift.io/v1:
error in operator/v1/zz_generated.crd-manifests/0000_50_ingress_00_ingresscontrollers-CustomNoUpgrade.crd.yaml: ListsMustHaveSSATags: crd/ingresscontrollers.operator.openshift.io version/v1 field/^.spec.namespaceSelector.matchExpressions must set x-kubernetes-list-type
error in operator/v1/zz_generated.crd-manifests/0000_50_ingress_00_ingresscontrollers-CustomNoUpgrade.crd.yaml: ListsMustHaveSSATags: crd/ingresscontrollers.operator.openshift.io version/v1 field/^.spec.namespaceSelector.matchExpressions[*].values must set x-kubernetes-list-type

/test verify-crd-schema

An example failure from verify-crd-schema. Is it in development?

error running generator schemacheck on group operator.openshift.io:
could not run schemacheck generator for group/version operator.openshift.io/v1:
error in operator/v1/zz_generated.crd-manifests/0000_50_ingress_00_ingresscontrollers-CustomNoUpgrade.crd.yaml: ListsMustHaveSSATags: crd/ingresscontrollers.operator.openshift.io version/v1 field/^.spec.namespaceSelector.matchExpressions must set x-kubernetes-list-type
error in operator/v1/zz_generated.crd-manifests/0000_50_ingress_00_ingresscontrollers-CustomNoUpgrade.crd.yaml: ListsMustHaveSSATags: crd/ingresscontrollers.operator.openshift.io version/v1 field/^.spec.namespaceSelector.matchExpressions[*].values must set x-kubernetes-list-type

/test verify-crd-schema

@candita I saw that too, but at the end of the logs is:
This verifier checks all files that have changed. In some cases you may have changed or renamed a file that already contained api violations, but you are not introducing a new violation. In such cases it is appropriate to /override the failing CI job.

And I reviewed the logs and don't see any issue with my added API. Instead, all of the errors are from existing fields. So I think I will require an override when the time comes to it.

/retest

No major concerns on my part, just a few comments/nits.
/lgtm

@gcs278 Just wanted to check you still wanted to merge this for 4.16 given the proximity to the branch cut, feel free to hold cancel if you're still wanting it in

Just to follow up on the PR: We are holding off until 4.17 opens to merge this.

/lgtm
/override ci/prow/verify-crd-schema
Ignoring existing failures being reported here, all SSA tags fixed so everything left is unfixable

/hold cancel
/retest

/retest

Cluster install failure and a seemingly unrelated test failure:
/retest

Unrelated failure
/retest

e2e-aws-serial-techpreview is permafailing now with:
[sig-api-machinery] API data in etcd should be stored at the correct location and version for all resources [Serial] [Suite:openshift/conformance/serial] expand_less	7s
{  fail [github.com/openshift/origin/test/extended/etcd/etcd_storage_path.go:534]: test failed:
no test data for resource.k8s.io/v1alpha2, Kind=ResourceClaimParameters.  Please add a test for your new type to etcdStorageData.
no test data for resource.k8s.io/v1alpha2, Kind=ResourceClassParameters.  Please add a test for your new type to etcdStorageData.
no test data for resource.k8s.io/v1alpha2, Kind=ResourceSlice.  Please add a test for your new type to etcdStorageData.
etcd data does not match the types we saw:
seen but not in etcd data:
[
	resource.k8s.io/v1alpha2, Resource=resourceclassparameters
	resource.k8s.io/v1alpha2, Resource=resourceslices
	resource.k8s.io/v1alpha2, Resource=resourceclaimparameters]
Ginkgo exit error 1: exit with code 1}

I see a bug was created https://issues.redhat.com/browse/OCPBUGS-34666 and https://github.com/openshift/kubernetes/pull/1984 is being tested as a fix.

https://github.com/openshift/origin/pull/28843 has merged. I believe this is intended to fix the techpreview e2e tests.
/hold cancel
/retest

@JoelSpeed could I get you to override ci/prow/verify-crd-schema once again?

@gcs278 Has something happened? There seem to be numerous SSA tag failures, I thought we had cleared all of those? Did a commit get dropped in a rebase?

@gcs278 Has something happened? There seem to be numerous SSA tag failures, I thought we had cleared all of those? Did a commit get dropped in a rebase?

I don't think anything changed since your first overrode, the errors are still the same. The SSA errors are from the same file I touched, but I didn't introduce them. Based on the output of the test, I thought overriding is acceptable:
This verifier checks all files that have changed. In some cases you may have changed or renamed a file that already contained api violations, but you are not introducing a new violation. In such cases it is appropriate to /override the failing CI job.

Do you want me to fix the existing SSA errors?

/retest

I had one nit that doesn't have to be changed if no other changes are needed, but I'll go on the record saying this is perplexing godoc due to the variety of validation methods and the fact they are separated in the godoc.
/lgtm

I'm not sure whether this PR is waiting for my /lgtm or is only blocked on #1917, but just in case—
/lgtm

/test verify-crd-schema

@JoelSpeed @Miciah @candita updated API per @JoelSpeed suggestion in slack. The subnets field has been moved from AWSLoadBalancerParameters to under AWSClassicLoadBalancerParameters and AWSNetworkLoadBalancerParameters.
Sorry about mixing the rebase in the recent force push (I usually to avoid that), but the changes are in the type_ingress.go diff and the Integration Tests diff

/lgtm
Feel free to cancel the hold if the network folks are happy now

/override ci/prow/verify-crd-schema

/lgtm
/unhold


3.3.2 isn't available on mavenCentral() like all the other versions

See https://mvnrepository.com/artifact/io.opentracing.contrib/opentracing-spring-jaeger-web-starter and https://search.maven.org/artifact/io.opentracing.contrib/opentracing-spring-jaeger-web-starter.
Could it have to do with the sunsetting of Bintray/JCenter?

That could very well be the case


Added Contributing Guidelines file type markdown.

@amanjaiman1 I have added the CONTRIBUTING.md file.
Please review it.

Final Reminder - Do Star the Repo.

@amanjaiman1 I have already created a PR and you have merged it also.


More work on APIs, demos and tests

I'm making a new PR so I can run the CI and make sure I don't screw it up. I would like to start thinking on merging this. I still need to solve some issues / complete the virtual command feature but I wanted to have your feedback now about. Besides that I think it's almost ready. See changes

@KnicKnic I'm ready to push this into ML. Since it has lots of new features / refactors I would like you to verify it before pushing. See changes: https://github.com/KnicKnic/WASM-ImageMagick/pull/28/files#diff-4ac32a78649ca5bdd8e0ba38b7006a1eR42

@cancerberoSgx so I did a few edits, but there are still some problems due to usage of require
The following line has an error in the produced magickApi.js
const Minimatch = require('minimatch');
error
Uncaught ReferenceError: require is not defined
Repro url https://knicknic.github.io/imagemagick/rotate/index.1.html

An update on this, I resume seeing the state of this branch but too much time have passed and I keep track of some features here. Although it builds and test correctly I'm afraid merging with main will have bad consequences since some features implemented here were also implemented  in master. Simply had too many features inside and too much time passed. I'm identifying features that could add value, and t I'm doing is identifying things that will add value, and for for each work on individual branches. The first one is adding support for text and fonts basically adding emscripten port for freetype. Next is pull a couple of features for  execute command syntax to support script-like strings little shell-like features so it's similar to scripts and easy to port them as a command.
I'm not seeng right now much more relevant features but I need to revisit,
@KnicKnic   please don't delete the branch since I will be pulling code from there to individual PRs.


feat: add base components 🧱

Description
This PR adds the foundational components to kickstart the project's design system, including the Button and the Card component. Additionally, I have introduced a reusable InnerBorder component to enhance the glass effect on the Card.
Changes:

Button Component:

Built on top of Pressable, with two variants:

One variant for handling Expo Router links.
Another for normal callbacks.

Card Component:

A styled container featuring:

A gradient background.
A shadow effect.
Glass effect, achieved using the reusable InnerBorder component.

Cross-platform Compatibility:

The components have been tested and work as expected on both mobile and web platforms.

Known Issue:
The LinearGradient component is currently unimplemented due to an issue that prevents the use of tailwind variables with it. A corresponding issue has been opened on the GluestackUI repository.

Hi @doranakan,
All of our components follow a well-implemented design system with standard best practices. You can explore the design files and guidelines here.
If you have any questions or need assistance with the design, feel free to start a discussion—we’re here to help!
Regarding your suggestions, we understand they are based on your specific use case. That’s why we provide copy-pastable patterns that allow users to easily customize them to suit their needs.
The discussion around using expo-linear-gradient might feel a bit biased since not everyone may choose to use it. Some users might already have react-native-skia installed and prefer to use that instead. You can check out more about react-native-skia gradients here.
While we've provided a recipe for expo-linear-gradient, we understand that we can't (and shouldn't) force users to follow a specific approach. We want to give developers the flexibility to choose what works best for their project.

All of our components follow a well-implemented design system with standard best practices. You can explore the design files and guidelines here.
If you have any questions or need assistance with the design, feel free to start a discussion—we’re here to help!
Regarding your suggestions, we understand they are based on your specific use case. That’s why we provide copy-pastable patterns that allow users to easily customize them to suit their needs.
The discussion around using expo-linear-gradient might feel a bit biased since not everyone may choose to use it. Some users might already have react-native-skia installed and prefer to use that instead. You can check out more about react-native-skia gradients here.
While we've provided a recipe for expo-linear-gradient, we understand that we can't (and shouldn't) force users to follow a specific approach. We want to give developers the flexibility to choose what works best for their project.

Thank you for the detailed response and the flexibility you’re aiming to provide with customizable patterns!
I agree with your point about allowing users to choose the approach that works best for their project, whether it’s expo-linear-gradient or react-native-skia. However, it seems like the issue with NativeWind colors would persist regardless of the method suggested, even with the custom patterns.
Do you have any recommendations on how we could manually select or override NativeWind colors at runtime? This would help developers like myself better adapt the components to specific needs, especially when custom runtime color management is required.
Looking forward to hearing your thoughts!

you can directly use token values.
Changing your LinearGradient to this will work on native device.

'use client';
import React from 'react';
import { tva } from '@gluestack-ui/nativewind-utils/tva';
import { LinearGradient as ExpoLinearGradient } from 'expo-linear-gradient';
import { cssInterop } from 'nativewind';

cssInterop(ExpoLinearGradient, {
  className: 'style',
});

const linearGradientStyle = tva({
  base: '',
});

export const LinearGradient = React.forwardRef(
  ({ className, from, to, ...props }: any, ref?: any) => {

    return (
      <ExpoLinearGradient
        {...props}
        colors={[from, to]}
        ref={ref}
      />
    );
  }
);

cssInterop(LinearGradient, {
  from:{
    target:"from",
    nativeStyleToProp:{
      color:true,
    }
  },
  to:{
    target:"to",
    nativeStyleToProp:{
      color:true,
    }
  }
});

 <LinearGradient
           className="w-full rounded-full items-center py-2"
            from="color-success-500"
            to="color-primary-600"
            start={[0, 1]}
            end={[1, 0]}
          />

for web you can have custom implementation with index.web.tsx with

For more info on cssInterop you can have look at https://www.nativewind.dev/v4/api/css-interop

you can directly use token values.
Changing your LinearGradient to this will work on native device.

'use client';
import React from 'react';
import { tva } from '@gluestack-ui/nativewind-utils/tva';
import { LinearGradient as ExpoLinearGradient } from 'expo-linear-gradient';
import { cssInterop } from 'nativewind';

cssInterop(ExpoLinearGradient, {
  className: 'style',
});

const linearGradientStyle = tva({
  base: '',
});

export const LinearGradient = React.forwardRef(
  ({ className, from, to, ...props }: any, ref?: any) => {

    return (
      <ExpoLinearGradient
        {...props}
        colors={[from, to]}
        ref={ref}
      />
    );
  }
);

cssInterop(LinearGradient, {
  from:{
    target:"from",
    nativeStyleToProp:{
      color:true,
    }
  },
  to:{
    target:"to",
    nativeStyleToProp:{
      color:true,
    }
  }
});

 <LinearGradient
           className="w-full rounded-full items-center py-2"
            from="color-success-500"
            to="color-primary-600"
            start={[0, 1]}
            end={[1, 0]}
          />

for web you can have custom implementation with index.web.tsx with

For more info on cssInterop you can have look at https://www.nativewind.dev/v4/api/css-interop

thanks @Viraj-10 for the suggestion. this way we are capable of display the linear gradient correctly with tailwind colors


DevContainer some calls all previous postCreateCommands

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.85.2 (Universal)
OS Version: MACOS 14.2.1 (23C71)

Steps to Reproduce:

Create a container
Add a postCreateCommand
Recreate the container
Change the postCreateCommand
Recreate the container again

Expectation
After creation, the container runs the last postCreateCommand command.
Reality
all the previous postCreateCommand are run one after the other.
I can see in the build logs that Running the postCreateCommand from devcontainer.json.... is printed several times with the different commands I had.
I can always reproduce it using the files below and this repo as base https://github.com/pulsejet/memories :
devcontainer.json
// For format details, see https://aka.ms/devcontainer.json. For config options, see the
// README at: https://github.com/devcontainers/templates/tree/main/src/alpine
{
  "name": "Nextcloud DevContainer",
  "dockerComposeFile": ["./docker-compose.yml"],
  "service": "nextcloud",
  "workspaceFolder": "/var/www/html/custom_apps/memories",
  // Features to add to the dev container. More info: https://containers.dev/features.
  "features": {},

  // Use 'forwardPorts' to make a list of ports inside the container available locally.
  // "forwardPorts": [],
 "postCreateCommand": "echo 'created'",
  // Configure tool-specific properties.
  "customizations": {
    "vscode": {
      "extensions": [
        "bmewburn.vscode-intelephense-client",
        "muuvmuuv.vscode-just-php-cs-fixer",
        "getpsalm.psalm-vscode-plugin",
        "esbenp.prettier-vscode",
        "Vue.volar",
        "Vue.vscode-typescript-vue-plugin"
      ],
      "settings": {
        "terminal.integrated.shell.linux": "/bin/bash"
        // Add any other VS Code settings you need for your project
      }
    }
  },

  // Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
  "remoteUser": "root"
}

docker-compose.ymal
name: 'nextcloud-with-memories'
services:
  nextcloud:
    build:
      context: .
      dockerfile: Dockerfile
    volumes:
      - ./custom_apps:/var/www/html/custom_apps
      - ./../:/var/www/html/custom_apps/memories
      - ./config:/var/www/html/config
    ports:
      - 9080:80
    image: nextcloud

Dockerfile
# Use the official Nextcloud image as the base image
FROM nextcloud

RUN echo "alias ll='ls -alF'" >> /etc/bash.bashrc
# Install Node.js 18 and npm
RUN curl -fsSL https://deb.nodesource.com/setup_18.x | bash - && \
  apt-get install -y nodejs && \
  rm -rf /var/lib/apt/lists/*

# Install Needed libs
# Install Git, wget, and PHP Composer
RUN apt-get update && \
  apt-get install -y git wget make unzip

# Install PHP Composer
RUN php -r "copy('https://getcomposer.org/installer', 'composer-setup.php');" && \
  php composer-setup.php --install-dir=/usr/local/bin --filename=composer  && \
  php -r "unlink('composer-setup.php');"

RUN composer global require "vimeo/psalm"

The image build is circular in your config: The Dockerfile starts from nextcloud and the docker-compose.yml tags the result as nextcloud. One of the two needs to change to a different name. Also see the output of docker history nextcloud which will show the Dockerfile's RUN statements applied multiple times.


error: unknown identifier 'resettingSynthInstanceCache' on Lean nightly with fresh package.

I'm getting this error output when building a brand new mostly blank package:
Building Qq.Macro error: > LEAN_PATH=./lake-packages/mathlib/build/lib:./lake-packages/Qq/build/lib:./lake-packages/aesop/build/lib:./build/lib:./lake-packages/std/build/lib LD_LIBRARY_PATH=/home/deb/.elan/toolchains/leanprover--lean4---nightly/lib:./lake-packages/Qq/build/lib /home/deb/.elan/toolchains/leanprover--lean4---nightly/bin/lean ./lake-packages/Qq/././Qq/Macro.lean -R ./lake-packages/Qq/./. -o ./lake-packages/Qq/build/lib/Qq/Macro.olean -i ./lake-packages/Qq/build/lib/Qq/Macro.ilean -c ./lake-packages/Qq/build/ir/Qq/Macro.c error: stdout: ./lake-packages/Qq/././Qq/Macro.lean:377:8: error: unknown identifier 'resettingSynthInstanceCache' error: external command ``/home/deb/.elan/toolchains/leanprover--lean4---nightly/bin/lean`` exited with code 1
Steps to get this error, for me:

Create new project with lake new package math
Add import Mathlib.Data.Real.Basic to Package.lean.
Update lean-toolchain to leanprover/lean4:nightly
Run elan update, lake update then lake build.

Update lean-toolchain to leanprover/lean4:nightly

You should never do that.  Please just copy lake-packages/mathlib/lean-toolchain to lean-toolchain.

Run elan update, lake update

You should not do that either.  And always copy lake-packages/mathlib/lean-toolchain to lean-toolchain after running lake update.  Only call lake update if you want a new mathlib version.


Question about GPU memory usage

First of all, congratulations on the excellent method you've proposed!
I'm curious about one detail, for the Argoverse2 dataset, what is the maximum number of 'n_token‘ that can be in the sft_layer? Also, does the repeat process cause excessive GPU memory usage? Was there any special consideration given to this aspect when designing the method?

@jkewang Sorry for the late reply. Actually, we won't set a limit for n_token, it basically depends on the complexity of the scenarios. Of course, you can set an upper bound and remove some elements that are not important based on some handcrafted rules. In my personal experiments, n_token varies from 100-250.
It indeed cost more GPU memory compared with the previous method since we modeled the all-to-all relationship between the instances in the RPE calculation. For Argo2, our experiment setup is 3090 (24G) x 8, batch_size=8 on each GPU, around 11 hours for 50 epochs, so I think (maybe) it is kind of "affordable" at present :). The good side for SIMPL (also for other methods based on relative scene encoding, such as QCNet, GoRela, etc.) is we only need to infer one time for all surrounding agents, which is different from those target-centric methods that need to conduct "normalize then predict" multiple times, and achieve good prediction accuracy as well. In practice, for agent-centric methods, we usually preprocess the surrounding context for each target, then send them to the network in a batch, which also costs a lot of memory. Besides, as you previously mentioned, we can set an upper bound for n_token, so the total memory usage will be bounded. I would personally think this is not a big issue, especially in the inference stage.
By the way, sorry for the Argo2 code, since I'm currently busy with some personal matters. I will try to clean the code and release it in the near future, hopefully within this month.


fix: cli handling of shadows fixed and shadow parser improved

Proposed changes
cli handling of shadows fixed and shadow parser improved:

offset of box-shadow | shadow are now based on borderWidths slice instead of spacings and sizes
Invalid values for shadows are now returned as they are passed

Types of changes

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)

Checklist

[x] I have read the CONTRIBUTING doc
[x] Lint and unit tests pass locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)
[x] Any dependent changes have been merged and published in downstream modules

Codecov Report

Merging #84 (fe37dae) into main (cb93138) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #84   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           69        69
  Lines          831       832    +1
  Branches       111       111
=========================================
+ Hits           831       832    +1

Impacted Files
Coverage Δ

packages/cli/src/constants/maps.ts
100.00% <ø> (ø)

packages/preset-default/src/base/borders.ts
100.00% <ø> (ø)

packages/cli/src/commands/build.ts
100.00% <100.00%> (ø)

packages/core/src/parsers/shadows.ts
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cb93138...fe37dae. Read the comment docs.


Rebuild for 0.8.14.

Description
Rebuild support/0.x so that the merge of pull request #906 is included in the build.
Even though it may not be ready for release, this allows other people to reference and test the support/0.x branch directly, using GitHub references in NPM's package.json.
Fixes Related issues

Related to issue #903 with a bugfix for IE.

Checklist

[X] I have read and understand the CONTRIBUTIONS.md file
[X] I have searched for and linked related issues
[ ] I have created test cases to ensure quick resolution of the PR is easier
[x] I am NOT targeting main branch
[ ] I did NOT include the dist folder in my PR

@json-schema-form/angular-schema-form-lead

The build fails with a version conflict on jQuery. This also happened in build 246465021.
I don't know if the support/0.x branch would build before, but when I built it I resolved it with jQuery. Maybe this resolution should be marked in bower.json?

Thanks @rhelgeby let me know after a little while if you think it is stable enough for a release :)

What about a release?

We use this version in production already and I suppose it's considered stable now.
I've forked and built my own version and reference my branch for this pull request directly: "angular-schema-form": "github:rhelgeby/angular-schema-form#build"
Warning: Don't rely on me to keep this branch or fork forever. I won't give notices of changes. It's better to have an official release and package in the NPM repository.

I have tested it and it works wonderful! Thank you!
The only problem was the way to use it. I had to use this variant:
"angular-schema-form": "git@github.com:rhelgeby/angular-schema-form.git#build"

This version should be in this repository as version 0.8.14.

Great. Even though I use this in production, again, remember that you use my fork on your own risk. I can't guarantee anything. If you want to ensure stability you could fork my clone and reference your own repository.
@Anthropic Could you make an official release for 0.8.14 when time permits? It's best if we all switch to an official version.

@rhelgeby I will, yes, glad it works for you all I will get onto it shortly, I'm recovering from surgery so there's been a slight delay in me getting to things as I am heavily medicated during recovery.

@rhelgeby
https://github.com/json-schema-form/angular-schema-form/releases/tag/v0.8.14
NPM is updated to 0.8.14 also.


Export from command line

Hi,
it would be really nice to be able to do exports directly from the command line. Like that, the add-on will become more versatile and can even be executed without a GUI (when using blender -b, see here)). That is especially helpful for GUI-less Blender operation, e.g., when working on a specific machine via SSH.
Personally, I would say that a Python script, which handles this and possibly allows options via a CLI, would be the easiest and best option. (I.e., usage would somehow look like this: blender somescene.blend -b --python new_exporter_script.py and could be wrapped further with a shell script.)
Thank you!

Hi,
This is already supported, as all blender operators are registered in the Blender Python API. In general, you can find the API handle of each operator/parameter in the Blender UI by enabling "Python tooltips" in the Blender preferences (Interface > Display). Hovering over any operator/parameter will then show you the associated handle in the API.
In the case of this addon, the operator to call to export from the blender API should be bpy.ops.export_scene.mitsuba2
The full signature is as follows:
bpy.ops.export_scene.mitsuba2(filepath="", check_existing=True, filter_glob="*.xml", use_selection=False, split_files=False, export_ids=False, ignore_background=True, axis_forward='-Z', axis_up='Y')
You can get those signatures in the Python interactive console inside of blender, by just entering the name of the operator.
Please let me know if this doesn't work for you.

Thanks for the quick reply!
I already tried a little bit to go in that direction, but then ran into issues (I think I got the filepath argument wrong)...
With your suggested signature, I was able to export scenes. But, on Windows, is very crucial to state your path with double backslashes (bpy.ops.export_scene.mitsuba2(filepath="D:\\myfolder\\mysubfolder\\myfile.xml", check_existing=True, [...])) instead of a single forward slash ("D:/myfolder/mysubfolder/myfile.xml"). If you work with single forward slashes, the first few parts of the XML (i.e., the Defaults, Camera and Rendering Parameters, Materials, and Emitters sections)  are created successfully, the it fails in the creation of the Shapes-block. It took me quite a while to figure out that the double backslashes fix this, because the error is so strange. I know why I usually use the pathlibmodule on Windows 😄
In case anyone runs into a similar problem, here is my traceback:
PS C:\> blender "D:/scenes/myscene/myscene.blend" -b --python-console
Blender 2.82 (sub 7) (hash 375c7dc4caf4 built 2020-03-12 15:41:08)
Read prefs: C:\Users\myuser\AppData\Roaming\Blender Foundation\Blender\2.82\config\userpref.blend
found bundled python: C:\Program Files\Blender Foundation\Blender 2.82\2.82\python
Read blend: D:/scenes/myscene/myscene.blend
Python 3.7.4 (default, Nov  1 2019, 13:23:36) [MSC v.1916 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
(InteractiveConsole)
>>>
>>> import bpy
>>> bpy.ops.export_scene.mitsuba2(filepath="D:/temp/from_commandline/myscene.xml", check_existing=True, use_selection=False, split_files=False, export_ids=False, ignore_background=True, axis_forward='-Z', axis_up='Y')
2022-05-02 11:05:00 INFO  main  [file_api.py:127] log(): Ignoring Blender's default background...
2022-05-02 11:05:00 INFO  main  [PluginManager] Loading plugin "plugins\blender.dll" ..
2022-05-02 11:05:00 INFO  main  [PluginManager] Loading plugin "plugins\diffuse.dll" ..
2022-05-02 11:05:00 INFO  main  [PluginManager] Loading plugin "plugins\uniform.dll" ..
2022-05-02 11:05:00 WARN  main  [BlenderMesh] Mesh Plane-Matte has no texture coordinates!
2022-05-02 11:05:00 INFO  main  [BlenderMesh] Plane-Matte: Removed 2 duplicates
2022-05-02 11:05:00 INFO  main  [Mesh] Writing mesh to "D:/temp/from_commandline\meshes\Plane-Matte.ply" ..
2022-05-02 11:05:00 INFO  main  [Mesh] "D:/temp/from_commandline\meshes\Plane-Matte.ply": wrote 2 faces, 4 vertices (120 B in 0ms)
2022-05-02 11:05:00 WARN  main  [file_api.py:127] log(): Light 'Point' has a non-zero soft shadow radius. It will be ignored.
2022-05-02 11:05:00 INFO  main  [PluginManager] Loading plugin "plugins\path.dll" ..
2022-05-02 11:05:00 INFO  main  [PluginManager] Loading plugin "plugins\ply.dll" ..
2022-05-02 11:05:00 INFO  main  [PluginManager] Loading plugin "plugins\perspective.dll" ..
2022-05-02 11:05:00 INFO  main  [PluginManager] Loading plugin "plugins\point.dll" ..
2022-05-02 11:05:00 INFO  main  [PluginManager] Loading plugin "plugins\independent.dll" ..
2022-05-02 11:05:00 INFO  main  [PluginManager] Loading plugin "plugins\hdrfilm.dll" ..
Error: Traceback (most recent call last):
  File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\scripts\addons\mitsuba2-blender\export.py", line 154, in execute
    self.export_ctx.write()
  File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\scripts\addons\mitsuba2-blender\file_api.py", line 104, in write
    self.xml_writer.process(self.scene_data)
  File "D:\mitsuba2\dist\python\mitsuba\python\xml.py", line 637, in process
    self.write_dict(self.scene_data[Files.MAIN])
  File "D:\mitsuba2\dist\python\mitsuba\python\xml.py", line 574, in write_dict
    self.write_dict(value)
  File "D:\mitsuba2\dist\python\mitsuba\python\xml.py", line 588, in write_dict
    value = self.format_path(value, self.current_tag())
  File "D:\mitsuba2\dist\python\mitsuba\python\xml.py", line 525, in format_path
    copy2(filepath, target_path)
  File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\python\lib\shutil.py", line 266, in copy2
    copyfile(src, dst, follow_symlinks=follow_symlinks)
  File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\python\lib\shutil.py", line 104, in copyfile
    raise SameFileError("{!r} and {!r} are the same file".format(src, dst))
shutil.SameFileError: 'D:\\temp\\from_commandline\\meshes\\Plane.ply' and 'D:/temp/from_commandline\\meshes\\Plane.ply' are the same file

location: C:\Program Files\Blender Foundation\Blender 2.82\2.82\scripts\modules\bpy\ops.py:201

Traceback (most recent call last):
  File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\scripts\addons\mitsuba2-blender\export.py", line 154, in execute
    self.export_ctx.write()
  File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\scripts\addons\mitsuba2-blender\file_api.py", line 104, in write
    self.xml_writer.process(self.scene_data)
  File "D:\mitsuba2\dist\python\mitsuba\python\xml.py", line 637, in process
    self.write_dict(self.scene_data[Files.MAIN])
  File "D:\mitsuba2\dist\python\mitsuba\python\xml.py", line 574, in write_dict
    self.write_dict(value)
  File "D:\mitsuba2\dist\python\mitsuba\python\xml.py", line 588, in write_dict
    value = self.format_path(value, self.current_tag())
  File "D:\mitsuba2\dist\python\mitsuba\python\xml.py", line 525, in format_path
    copy2(filepath, target_path)
  File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\python\lib\shutil.py", line 266, in copy2
    copyfile(src, dst, follow_symlinks=follow_symlinks)
  File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\python\lib\shutil.py", line 104, in copyfile
    raise SameFileError("{!r} and {!r} are the same file".format(src, dst))
shutil.SameFileError: 'D:\\temp\\from_commandline\\meshes\\Plane.ply' and 'D:/temp/from_commandline\\meshes\\Plane.ply' are the same file

location: C:\Program Files\Blender Foundation\Blender 2.82\2.82\scripts\modules\bpy\ops.py:201

location: C:\Program Files\Blender Foundation\Blender 2.82\2.82\scripts\modules\bpy\ops.py:201
Error: Traceback (most recent call last):
  File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\scripts\addons\mitsuba2-blender\export.py", line 154, in execute
    self.export_ctx.write()
  File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\scripts\addons\mitsuba2-blender\file_api.py", line 104, in write
    self.xml_writer.process(self.scene_data)
  File "D:\mitsuba2\dist\python\mitsuba\python\xml.py", line 637, in process
    self.write_dict(self.scene_data[Files.MAIN])
  File "D:\mitsuba2\dist\python\mitsuba\python\xml.py", line 574, in write_dict
    self.write_dict(value)
  File "D:\mitsuba2\dist\python\mitsuba\python\xml.py", line 588, in write_dict
    value = self.format_path(value, self.current_tag())
  File "D:\mitsuba2\dist\python\mitsuba\python\xml.py", line 525, in format_path
    copy2(filepath, target_path)
  File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\python\lib\shutil.py", line 266, in copy2
    copyfile(src, dst, follow_symlinks=folloTraceback (most recent call last):
  File "<console>", line 1, in <module>
  File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\scripts\modules\bpy\ops.py", line 201, in __call__
    ret = op_call(self.idname_py(), None, kw)
RuntimeError: Error: Traceback (most recent call last):
  File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\scripts\addons\mitsuba2-blender\export.py", line 154, in execute
    self.export_ctx.write()
  File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\scripts\addons\mitsuba2-blender\file_api.py", line 104, in write
    self.xml_writer.process(self.scene_data)
  File "D:\mitsuba2\dist\python\mitsuba\python\xml.py", line 637, in process
    self.write_dict(self.scene_data[Files.MAIN])
  File "D:\mitsuba2\dist\python\mitsuba\python\xml.py", line 574, in write_dict
    self.write_dict(value)
  File "D:\mitsuba2\dist\python\mitsuba\python\xml.py", line 588, in write_dict
    value = self.format_path(value, self.current_tag())
  File "D:\mitsuba2\dist\python\mitsuba\python\xml.py", line 525, in format_path
    copy2(filepath, target_path)
  File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\python\lib\shutil.py", line 266, in copy2
    copyfile(src, dst, follow_symlinks=follow_symlinks)
  File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\python\lib\shutil.py", line 104, in copyfile
    raise SameFileError("{!r} and {!r} are the same file".format(src, dst))
shutil.SameFileError: 'D:\\temp\\from_commandline\\meshes\\Plane.ply' and 'D:/temp/from_commandline\\meshes\\Plane.ply' are the same file

location: C:\Program Files\Blender Foundation\Blender 2.82\2.82\scripts\modules\bpy\ops.py:201

... truncated>>>

That brings me to two smaller issues:

The path needs to be set without the GUI. In the readme, it tells that

Point Path to Mitsuba 2's build directory. If the environment variable MITSUBA_DIR was set (cf. Mitsuba 2 install instructions), this field will automatically be filled with the path it contains.

I wasn't able to find the certain section. Just creating a new environment variable didn't seem to solve this.

Maybe, there should be a small section in the readme on how the add-on can be executed from the command line. If you don't want to dig into this right now, I could also write a few sentences about this and create a PR for the updated readme.

Update to point 1:
I dug into it and found the problem. The created environment variable (just named mitsuba_dir with mitsuba's build path) is read by the export.py-script. However, there are two processing issues under Windows:

The first issue is caused by this line:
for token in tokens.split(':'): (see here)
On Linux, where different entries of an environment variable are separated by colons (:), everything works fine. But on Windows, environment variables are separated by semicolons (;). So a path D:\mitsuba is splitted into the two parts D: and \mitsuba. Here needs to be distinguished between systems to get the correct seperator.
The second issue is caused by the default way of installation of Mitsuba2 on Windows, where the build directory and the mitsuba2 root directory are the same (caused by cmake -G "Visual Studio 16 2019" -A x64, see here). Therefore, the line path = os.path.join(token, 'build') (see here) is unnecessary. path should just be token.

Thanks for looking into this.
The code to use the environment variable ion Windows seems broken indeed, and support for it will likely be dropped in the next release. I recommend you instead set the path manually in your script by accessing directly the preferences of the addon:
C.preferences.addons['mitsuba2-blender'].preferences.mitsuba_path


change pf-utilization-chart to pf-utilization-trend-chart in containe…

change pf-utilization-chart to pf-utilization-trend-chart in containers dashboard.
there was a name change in the new PF version.
Before:

After(notice the donut is now aligned to the left):

@miq-bot add_label bug, ui, providers/containers
Please review @himdel @abonas
cc @simon3z

don't you need to change it here as well?

don't you need to change it here as well?

Good catch!

you might want to do a shareable file and include in both files, PRs such as this are quite evident why it would be a good idea to do it. less chance to forget, less need for copy paste.
see an example here https://github.com/ManageIQ/manageiq/pull/6985

Would be great to have the common code unified, but as for this PR, looks good :)
(Also, seems like pf-card, pf-select, pf-trends-chart and pf-aggregate-status-card all survived the 2->3 change, so hopefully we should get no more angular-patternfly surprises :) (I haven't checked patternfly itself though.))

Would be great to have the common code unified...
you might want to do a shareable file with common code and...

@himdel @abonas Moved dashboard haml to shared partial.

pls change the title to reflect what this PR does (2 changes now).
other than that - great!

@zeari please see @himdel comments above.  I missed them (screen didn't refresh), so please address them in a follow up PR.  Thx, Dan


Cohort Deletion Tracking as an event

Tracking Cohort Deletion!

Merged!
Thank you for your feedback @zqian and @jonespm


revise load parameters

PR types: Bug fixes
PR changes
deepspeech/models/deepspeech2.py 中import 的checkpoint修改
Describe
修改import的内容为checkpoint.py模块为checkpoint.py中的Checkpoint类，并修改deepspeech/models/deepspeech2.py的225行

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


[Proposal] Move to C# 10 for SDK development

Describe the proposal
Now that .NET 6 is the minimum target for the SDK, we can roll forward the C# language version to 10, which has some useful new features.

/assign


fix: cleanup cargo dependencies

Summary of changes

Changes introduced in this pull request:

implement ruby script for detecting unused cargo dependencies
update CI
cleanup cargo manifests

Reference issue to close (if applicable)

Closes https://github.com/ChainSafe/forest/issues/2413
Other information and links

Change checklist

[x] I have performed a self-review of my own code,
[x] I have made corresponding changes to the documentation,
[x] I have added tests that prove my fix is effective or that my feature works (if possible),
[x] I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

In general, does it make cargo-udeps obsolete, and if so can we get rid of it? I mean, if this script detects a superset of what cargo-udeps does then there's no point in keeping the latter in the CI.

I believe cargo-udeps is using a more formal way that invokes the compiler AST parser and re-uses the cargo manifest parser, I'm not confident about whether this simple script can fully replace it.


[feature] Add methods to compare moments

isBeforeMoment
isAfterMoment
isBetweenMoments

Current coverage is 99.41% (diff: 92.77%)

Merging #30 into master will decrease coverage by 0.22%

@@             master        #30   diff @@
==========================================
  Files            26         26
  Lines          2479       2562    +83
  Methods         873        890    +17
  Messages          0          0
  Branches         21         33    +12
==========================================
+ Hits           2470       2547    +77
- Misses            9         15     +6
  Partials          0          0

Powered by Codecov. Last update 367453c...2d0666b

Wow, great! Thank you @strictlyd! This is a nice feature.


Add documentation for implicit arguments

We should have some reference documentation for implicit arguments, which were added in #439.

Fixed in #450


Failed renewal still uppdates "renewal date"

My renewal failed. That may happen.
Problem is: Last thing that happened, even tho the renewal failed:
Renewal Scheduled IIS ******* (C:\inetpub\letsencrypt) Renew After 2017-07-27
So, eh. I fixed the problem. Tried to rerun the renewal.
But all it says now is:
Checking Renewals
Checking IIS ***** (C:\inetpub\letsencrypt) Renew After 2017-07-27
I would call this a bug?
Why would it update the renewal date (as I understand, it's a registrysetting), when the renewal fails?
How am I now supposed to fix this?
I see no --force flag...
Edit: Ok, so I managed to solve this by manually editing the date in the registry-setting, but I still think this is either a bug, or should be coupled with some sort of override parameter.

Hi!
Same issue, where did you update the reg?
Tore

HKEY_CURRENT_USER\Software\letsencrypt-win-simple\https://acme-v01.api.letsencrypt.org/\Renewals

+1

Some additional information: If you have multiple certs being renewed, and one succeeds and the other doesn't, then BOTH certificates get the registry values updated to the same renewal date.
This implies that the renewal date value is not coded to be per certificate either, as both were updated!
Expecting that the successful cert update registry key gets updated, and the failed cert registry key timestamp does not.

I have the same issue when my certificate expired on 2017-07-05 19:30PM.
Then, I try renew it same day at 20:00PM, I get the same result "Renew After 2017-07-05"
You can see that the renewal process is check the date but not time, even your certificate expired in evening but it is consider certificate expire end of the day (next day).
If you use of IIS, you can check certificate expiry time in Server Certificates.
I believe this is a bug or letsencrypt.exe have to allow us to renew one day in advance.

This issue has been fixed in version 1.9.4!


[scrcpy 2.0] v4l2 output is broken ("[h264 @ 0xHex] No start code is found")

[x] I have read the FAQ.
[x] I have searched in existing issues.

Environment

OS: Arch Linux
scrcpy version: 2.0
installation method: Arch community repository
device model: OnePlus 7 Pro
Android version: 10

Describe the bug
Small bit of context: I use scrcpy primarily as a way to use my device as a webcam in OBS.
In scrcpy 1.25, the v4l2 output works as expected in OBS, as well as other apps that use webcam on Linux through v4l2 (i.e. Discord)
In scrcpy 2.0, which the community repo just pushed as of a day ago, the v4l2 output seems to still be pushed as expected:
scrcpy --v4l2-sink=/dev/video0 --v4l2-buffer=300 --video-bit-rate=30M --max-fps=60 --lock-video-orientation=3 --crop=1440:2560:0:364 --video-codec=h264 -N -S -w --power-off-on-close
Detected device 64943115
scrcpy 2.0 <https://github.com/Genymobile/scrcpy>
INFO: No display and no recording: audio disabled
/usr/share/scrcpy/scrcpy-server: 1 file pushed, 0 skipped. 695.8 MB/s (52867 bytes in 0.000s)
[server] INFO: Device: OnePlus OnePlus 7 Pro (Android 10)
INFO: v4l2 sink started to device: /dev/video0
[server] INFO: Device screen turned off

...however, when I open OBS, the video capture element reserved for the scrcpy v4l2-loopback device is black. I notice that the video format dropdown has changed, from "Planar YUV 4:2:0" to "YU12 (emulated)" and there's a new format labeled "H.264". But selecting this doesn't change anything - in fact, the output seems to fail.
(truncated OBS tty output just to show the relevant symptom):
...
info: v4l2-input: Found device 'Dummy video device (0x0000)' at /dev/video0
info: v4l2-input: Found input 'loopback' (Index 0)
info: v4l2-input: Pixelformat: H.264 (available)
info: v4l2-input: Pixelformat: RGB3 (Emulated) (unavailable)
info: v4l2-input: Pixelformat: BGR3 (Emulated) (available)
info: v4l2-input: Pixelformat: YU12 (Emulated) (available)
info: v4l2-input: Pixelformat: YV12 (Emulated) (available)
info: v4l2-input: Stepwise and Continuous framesizes are currently hardcoded
info: v4l2-input: Stepwise and Continuous framerates are currently hardcoded
info: v4l2-input: Pixelformat: H.264 (available)
info: v4l2-input: Pixelformat: RGB3 (Emulated) (unavailable)
info: v4l2-input: Pixelformat: BGR3 (Emulated) (available)
info: v4l2-input: Pixelformat: YU12 (Emulated) (available)
info: v4l2-input: Pixelformat: YV12 (Emulated) (available)
info: v4l2-input: Stepwise and Continuous framesizes are currently hardcoded
info: v4l2-input: Stepwise and Continuous framerates are currently hardcoded
info: v4l2-input: Stepwise and Continuous framesizes are currently hardcoded
info: v4l2-input: Stepwise and Continuous framerates are currently hardcoded
info: v4l2-input: Stepwise and Continuous framerates are currently hardcoded
info: v4l2-input: Start capture from /dev/video0
info: v4l2-input: Input: 0
info: v4l2-input: Resolution: 2560x1440
info: v4l2-input: Pixelformat: H264
info: v4l2-input: Linesize: 0 Bytes
info: v4l2-input: Framerate: 30.00 fps
info: v4l2-input: Stepwise and Continuous framerates are currently hardcoded
info: v4l2-input: /dev/video0: select timeout set to 166666 (5x frame periods)
[h264 @ 0x7f6604012540] No start code is found.
[h264 @ 0x7f6604012540] Error splitting the input into NAL units.
error: v4l2-input: decoder: failed to send frame to codec
error: v4l2-input: failed to unpack jpeg or h264
info: v4l2-input: /dev/video0: Stopped capture after 0 frames
info: v4l2-input: Stepwise and Continuous framesizes are currently hardcoded
info: v4l2-input: Stepwise and Continuous framerates are currently hardcoded
info: v4l2-input: Start capture from /dev/video0
info: v4l2-input: Input: 0
error: v4l2-input: Unable to set format
error: v4l2-input: Initialization failed, errno: Invalid argument
info: v4l2-input: Stepwise and Continuous framerates are currently hardcoded
info: v4l2-input: Start capture from /dev/video0
info: v4l2-input: Input: 0
info: v4l2-input: Resolution: 2560x1440
info: v4l2-input: Pixelformat: H264
info: v4l2-input: Linesize: 0 Bytes
info: v4l2-input: Framerate: 30.00 fps
info: v4l2-input: /dev/video0: select timeout set to 166666 (5x frame periods)
[h264 @ 0x7f66040029c0] No start code is found.
[h264 @ 0x7f66040029c0] Error splitting the input into NAL units.
error: v4l2-input: decoder: failed to send frame to codec
error: v4l2-input: failed to unpack jpeg or h264
info: v4l2-input: /dev/video0: Stopped capture after 0 frames

This also affects Discord, which with scrcpy 2.0, shows that it recognizes the loopback device, but testing the camera shows nothing. (Discord does not output any useful console info.)
Reverting back to scrcpy 1.25 from the Arch Linux Archives allows the output to work as expected, in both OBS and Discord.
...
info: v4l2-input: Found device 'Dummy video device (0x0000)' at /dev/video0
info: v4l2-input: Found input 'loopback' (Index 0)
info: v4l2-input: Pixelformat: Planar YUV 4:2:0 (available)
info: v4l2-input: Pixelformat: RGB3 (Emulated) (unavailable)
info: v4l2-input: Pixelformat: BGR3 (Emulated) (available)
info: v4l2-input: Pixelformat: YV12 (Emulated) (available)
info: v4l2-input: Stepwise and Continuous framesizes are currently hardcoded
info: v4l2-input: Stepwise and Continuous framerates are currently hardcoded
info: v4l2-input: Pixelformat: Planar YUV 4:2:0 (available)
info: v4l2-input: Pixelformat: RGB3 (Emulated) (unavailable)
info: v4l2-input: Pixelformat: BGR3 (Emulated) (available)
info: v4l2-input: Pixelformat: YV12 (Emulated) (available)
info: v4l2-input: Stepwise and Continuous framesizes are currently hardcoded
info: v4l2-input: Stepwise and Continuous framerates are currently hardcoded
info: v4l2-input: Stepwise and Continuous framesizes are currently hardcoded
info: v4l2-input: Stepwise and Continuous framerates are currently hardcoded
info: v4l2-input: Stepwise and Continuous framerates are currently hardcoded
info: v4l2-input: Stepwise and Continuous framerates are currently hardcoded
info: v4l2-input: Start capture from /dev/video0
info: v4l2-input: Input: 0
info: v4l2-input: Resolution: 2560x1440
info: v4l2-input: Pixelformat: YU12
info: v4l2-input: Linesize: 2560 Bytes
info: v4l2-input: Framerate: 30.00 fps
info: v4l2-input: /dev/video0: select timeout set to 166666 (5x frame periods)

Thank you for your report.
Already fixed on master: https://github.com/Genymobile/scrcpy/issues/3795


Support remaining CWL draft-3 workflow features (resolves #712)

Resolves #712

Support complex scatter.
Support multiple sources on workflow steps.
Support valueFrom on workflow step input.

Passes CWL draft-3 conformance tests in local run.

Jenkins, test this please.

Cool, btw.

I don't think the test failures are related to this branch?

@tetron, I think so. I will take care of this and rerun the tests.

Jenkins, test this please.

Tests failed for unrelated reasons. Tracking that in https://github.com/BD2KGenomics/toil/issues/714.


Bump up kover version to 0.7.x

Current, we use 0.6.1
https://github.com/naver/spring-batch-plus/blob/9cfd63ccf4f45e697839aa259a8c076738ebe3c3/buildSrc/build.gradle.kts#L14
See also: Kover migration guide from 0.6.x to 0.7.4

even 0.8.0 is released
https://github.com/Kotlin/kotlinx-kover/releases/tag/v0.8.0


Add has method

This adds a has method to the cache. My code could just always perform a get, but I thought it might be nice to have this helper.

Codecov Report

Merging #2 into master will decrease coverage by 1.74%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master       #2      +/-   ##
==========================================
- Coverage   87.87%   86.13%   -1.75%
==========================================
  Files           3        3
  Lines          99      101       +2
  Branches       25       25
==========================================
  Hits           87       87
- Misses         12       14       +2

Impacted Files
Coverage Δ

src/AbortablePromiseCache.ts
84.61% <0%> (-2.23%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b168ec1...9f3e89e. Read the comment docs.

released on npm in abortable-promise-cache 1.1.0


python311Packages.python-engineio: 4.9.0 -> 4.9.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.python-engineio is: Python based Engine.IO client and server
meta.homepage for python311Packages.python-engineio is: https://github.com/miguelgrinberg/python-engineio/
meta.changelog for python311Packages.python-engineio is: https://github.com/miguelgrinberg/python-engineio/blob/v4.9.1/CHANGES.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.9.1 with grep in /nix/store/jh33ls3yzp2i37bflp2air50ffxf02f1-python3.11-python-engineio-4.9.1
found 4.9.1 in filename of file in /nix/store/jh33ls3yzp2i37bflp2air50ffxf02f1-python3.11-python-engineio-4.9.1

Rebuild report (if merged into master) (click to expand)

33 total rebuild path(s)

33 package rebuild(s)

First fifty rebuilds by attrpath

appdaemon
faraday-agent-dispatcher
gdbgui
home-assistant-component-tests.ambient_network
home-assistant-component-tests.ambient_station
home-assistant-component-tests.control4
onionshare
onionshare-gui
pgadmin4
pgadmin4-desktopmode
powerhub
python311Packages.aioambient
python311Packages.flask-socketio
python311Packages.pycontrol4
python311Packages.python-engineio
python311Packages.python-socketio
python311Packages.ripe-atlas-cousteau
python311Packages.sisyphus-control
python311Packages.tago
python311Packages.tagoio-sdk
python311Packages.uptime-kuma-api
python312Packages.aioambient
python312Packages.flask-socketio
python312Packages.pycontrol4
python312Packages.python-engineio
python312Packages.python-socketio
python312Packages.ripe-atlas-cousteau
python312Packages.sisyphus-control
python312Packages.tago
python312Packages.tagoio-sdk
python312Packages.uptime-kuma-api
ripe-atlas-tools

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/jh33ls3yzp2i37bflp2air50ffxf02f1-python3.11-python-engineio-4.9.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.python-engineio https://github.com/r-ryantm/nixpkgs/archive/2318c2311f7dfaf10fb8072dde65513c4709b2e2.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/2318c2311f7dfaf10fb8072dde65513c4709b2e2#python311Packages.python-engineio

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/jh33ls3yzp2i37bflp2air50ffxf02f1-python3.11-python-engineio-4.9.1
ls -la /nix/store/jh33ls3yzp2i37bflp2air50ffxf02f1-python3.11-python-engineio-4.9.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

61 packages built:

appdaemon
appdaemon.dist
faraday-agent-dispatcher
faraday-agent-dispatcher.dist
gdbgui
gdbgui.dist
home-assistant-component-tests.ambient_network
home-assistant-component-tests.ambient_station
home-assistant-component-tests.control4
onionshare
onionshare-gui
onionshare-gui.dist
onionshare.dist
pgadmin4
pgadmin4-desktopmode
pgadmin4-desktopmode.dist
pgadmin4.dist
powerhub
powerhub.dist
python311Packages.aioambient
python311Packages.aioambient.dist
python311Packages.flask-socketio
python311Packages.flask-socketio.dist
python311Packages.pycontrol4
python311Packages.pycontrol4.dist
python311Packages.python-engineio
python311Packages.python-engineio.dist
python311Packages.python-socketio
python311Packages.python-socketio.dist
python311Packages.ripe-atlas-cousteau
python311Packages.ripe-atlas-cousteau.dist
python311Packages.sisyphus-control
python311Packages.sisyphus-control.dist
python311Packages.tago
python311Packages.tago.dist
python311Packages.tagoio-sdk
python311Packages.tagoio-sdk.dist
python311Packages.uptime-kuma-api
python311Packages.uptime-kuma-api.dist
python312Packages.aioambient
python312Packages.aioambient.dist
python312Packages.flask-socketio
python312Packages.flask-socketio.dist
python312Packages.pycontrol4
python312Packages.pycontrol4.dist
python312Packages.python-engineio
python312Packages.python-engineio.dist
python312Packages.python-socketio
python312Packages.python-socketio.dist
python312Packages.ripe-atlas-cousteau
python312Packages.ripe-atlas-cousteau.dist
python312Packages.sisyphus-control
python312Packages.sisyphus-control.dist
python312Packages.tago
python312Packages.tago.dist
python312Packages.tagoio-sdk
python312Packages.tagoio-sdk.dist
python312Packages.uptime-kuma-api
python312Packages.uptime-kuma-api.dist
ripe-atlas-tools
ripe-atlas-tools.dist

Maintainer pings
cc @Mic92 for testing.

Result of nixpkgs-review pr 313010 run on x86_64-linux 1

61 packages built:

appdaemon
appdaemon.dist
faraday-agent-dispatcher
faraday-agent-dispatcher.dist
gdbgui
gdbgui.dist
home-assistant-component-tests.ambient_network
home-assistant-component-tests.ambient_station
home-assistant-component-tests.control4
onionshare
onionshare-gui
onionshare-gui.dist
onionshare.dist
pgadmin4
pgadmin4-desktopmode
pgadmin4-desktopmode.dist
pgadmin4.dist
powerhub
powerhub.dist
python311Packages.aioambient
python311Packages.aioambient.dist
python311Packages.flask-socketio
python311Packages.flask-socketio.dist
python311Packages.pycontrol4
python311Packages.pycontrol4.dist
python311Packages.python-engineio
python311Packages.python-engineio.dist
python311Packages.python-socketio
python311Packages.python-socketio.dist
python311Packages.ripe-atlas-cousteau
python311Packages.ripe-atlas-cousteau.dist
python311Packages.sisyphus-control
python311Packages.sisyphus-control.dist
python311Packages.tago
python311Packages.tago.dist
python311Packages.tagoio-sdk
python311Packages.tagoio-sdk.dist
python311Packages.uptime-kuma-api
python311Packages.uptime-kuma-api.dist
python312Packages.aioambient
python312Packages.aioambient.dist
python312Packages.flask-socketio
python312Packages.flask-socketio.dist
python312Packages.pycontrol4
python312Packages.pycontrol4.dist
python312Packages.python-engineio
python312Packages.python-engineio.dist
python312Packages.python-socketio
python312Packages.python-socketio.dist
python312Packages.ripe-atlas-cousteau
python312Packages.ripe-atlas-cousteau.dist
python312Packages.sisyphus-control
python312Packages.sisyphus-control.dist
python312Packages.tago
python312Packages.tago.dist
python312Packages.tagoio-sdk
python312Packages.tagoio-sdk.dist
python312Packages.uptime-kuma-api
python312Packages.uptime-kuma-api.dist
ripe-atlas-tools
ripe-atlas-tools.dist


metadata for cloudflare got updated

Prerequisites

[x] Ensure you have latest version of plugin installed
[x] Search for possible issue duplicates

Installation details

[2019.2.3] IDE version (Help->About->Copy to Clipboard)
[0.7.6] intellij-hcl plugin version (Settings->Plugins)
[0.12.7] Terraform version (terraform -v)

Terraform Configuration Files
// add mx records for user mail
resource "cloudflare_record" "mx" {
  for_each   = {
  for key, value in var.mx_records:
  value.target => value
  }
  zone_id    = cloudflare_zone.zone.id
  name       = each.value.prefix != "" ? each.value.prefix : cloudflare_zone.zone.zone
  type       = "MX"
  value      = each.key
  priority   = each.value.priority
  ttl        = 3600
  depends_on = [
    cloudflare_zone.zone]
}

Expected Behavior
The hcl definition should pass validation.
Actual Behavior
The syntaxhighlighting says `Missing required properties: domain" -> the metadata isn't up to date with the changes for the cloudflare provider v2.0: https://www.terraform.io/docs/providers/cloudflare/guides/version-2-upgrade.html

Thanks for reporting, will try to fix ASAP