fix: Set childReportID of the optimistic IOU report action

Details
When creating a money request, set the report action's childReportID to the optimistically created money request reportID.
Fixed Issues
$ https://github.com/Expensify/App/issues/33114
PROPOSAL: https://github.com/Expensify/App/issues/33114#issuecomment-1961778058
Tests
Same as QA
Offline tests
Same as QA
QA Steps
Test 1:

Go offline
Request money: repeat for each of the manual, scan, and distance requests;
Navigate to the newly created money request report
Verify it's showing the correct data
Go online
Verify the report doesn't disappear after the data is fetched from BE

Test 2:

Request money: scan request;
Quickly navigate to the newly created money request report while it's still loading
Verify the report doesn't disappear after the data is fetched from BE

Test 3:

Request money: distance request;
Quickly navigate to the newly created money request report while it's still loading
Verify the report doesn't disappear after the route is fetched from BE

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
https://github.com/Expensify/App/assets/12595293/41d1c124-8186-4ed7-81f7-b38ee095449a

Android: mWeb Chrome
https://github.com/Expensify/App/assets/12595293/a71d4c72-cff2-4bd8-8ab8-2de79bbdd4cc

iOS: Native
https://github.com/Expensify/App/assets/12595293/fa999c52-20cc-49ff-af8e-432faa571239

iOS: mWeb Safari
https://github.com/Expensify/App/assets/12595293/cba9bf1a-aae1-4f37-aa12-9e6bbf5efc8a

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/12595293/2a104b9f-1477-4aa6-a506-1a3a2ac4eee4

MacOS: Desktop
https://github.com/Expensify/App/assets/12595293/c3df3194-d540-4721-a826-a1d89d6a074e

I think we can release without it, but there's a BE fix pending: https://github.com/Expensify/App/issues/33114#issuecomment-1961940800

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

Maybe out of scope but there are various glitches as seen in this video:
https://github.com/Expensify/App/assets/108292595/0e694d3a-28c6-4e36-a527-7069b09f0be4

After online:

Here's full repro video: (manual request to new (non-Expensify) user in offline mode)

BUG: unavailable workspace on transaction detail header when create expense request offline

https://github.com/Expensify/App/assets/108292595/45ede4b1-dc2d-4a15-a591-fbc2457dd2e3

@paultsimura this is blocker.
Bug not fixed: split manual request with a single user from FAB
https://github.com/Expensify/App/assets/108292595/7f7307dd-595d-4b92-9c1b-4270f754ee5b

@paultsimura this is blocker.
Bug not fixed: split manual request with a single user from FAB

This one is BE as well, similar to the SendMoney.
@cead22 when creating a Split request and calling the SplitBillAndOpenReport API endpoint, we send the stringified splits among parameters. Each split will now contain the transactionThreadReportID and createdReportActionIDForThread that need to be handled on the BE – currently, the optimistic transaction thread is replaced with another from the BE response.
Here's the params example:
{
    "reportID": "1932415687405820",
    "amount": 2200,
    "splits": "[{\"email\":\"paultsimura@gmail.com\",\"accountID\":15528187,\"amount\":1100},{\"email\":\"paultsimura+qa@gmail.com\",\"accountID\":15528255,\"amount\":1100,\"iouReportID\":\"2941200419003018\",\"chatReportID\":\"1932415687405820\",\"transactionID\":\"7451263110636286127\",\"reportActionID\":\"4265162090444479673\",\"createdChatReportActionID\":\"3058872218140896575\",\"createdIOUReportActionID\":\"792942737366932173\",\"reportPreviewReportActionID\":\"7347533532549283559\",\"transactionThreadReportID\":\"5196953162708250\",\"createdReportActionIDForThread\":\"8302969548555128822\"}]",
    "currency": "PLN",
    "merchant": "(none)",
    "created": "2024-03-03 19:54:14.852",
    "comment": "",
    "category": "",
    "tag": "",
    "billable": false,
    "transactionID": "5684861019807192728",
    "reportActionID": "4158501737745037324",
    "policyID": "_FAKE_"
}

While it's BE issue, I found interesting thing (possible fix in FE).
I tried to create optimistic chat with same user in 2 devices. On 2nd device, after making online, optimistic reportID (wrong one) is automatically replaced with correct reportID.
Can't this be applied to optimistic transaction report as well?
https://github.com/Expensify/App/assets/108292595/fb063372-a58d-4f50-be76-d9146b23c13b

This looks like a workaround.
The original PR about passing the optimistic thread IDs to BE was intended to fix this very issue, it was just not fully implemented.

BUG: unavailable workspace on transaction detail header when create expense manual request offline. Same happens on split manual request with workspace

Found a fix, working on it...

@situchan I think after this PR this code won't be needed anymore 🤔
https://github.com/Expensify/App/blob/6c2abde357968c1d38730cd379b3fd654130e766/src/components/ReportActionItem/MoneyRequestAction.tsx#L94-L102
https://github.com/Expensify/App/blob/c2e24e1c8d4ba00c6f206508244224195d0a6591/src/pages/home/report/ContextMenu/ContextMenuActions.tsx#L213-L219

@situchan I think after this PR this code won't be needed anymore 🤔 It was used to create a thread if a moneyRequestPreview didn't have a child report. But now we are creating and setting it optimistically ever time,
https://github.com/Expensify/App/blob/6c2abde357968c1d38730cd379b3fd654130e766/src/components/ReportActionItem/MoneyRequestAction.tsx#L94-L102
https://github.com/Expensify/App/blob/c2e24e1c8d4ba00c6f206508244224195d0a6591/src/pages/home/report/ContextMenu/ContextMenuActions.tsx#L213-L219

They were added in #18760, #25429.
Agree cleanup after we make sure that childReportID in money request action is already coming from backend for any type of money requests.

Login same account on device A & B
Create money request in A
Navigate to transaction detail page in B

Login same account on device A & B
Create money request in A
Navigate to transaction detail page in B

Do you observe any bug with this? If so – could you please share the recording? I didn't notice anything suspicious

Login same account on device A & B
Create money request in A
Navigate to transaction detail page in B

Do you observe any bug with this? If so – could you please share the recording? I didn't notice anything suspicious

I just shared test case. If you confirm that no bug found on all types of requests, you can remove them as unnecessary codes. We don't wanna be affected by any possible regressions from code cleanup.

Now we should hold PR for BE fix of split, send cases, right?

Now we should hold PR for BE fix of split, send cases, right?

I'll let @cead22 decide here. This PR won't break the flow because the behavior we have with splits & send flow is already happening in Prod. But just to be sure the BE fix works well with this PR, we can hold.

If you confirm that no bug found on all types of requests, you can remove them as unnecessary codes. We don't wanna be affected by any possible regressions from code cleanup.

Tests well, both IOU & expense requests:
https://github.com/Expensify/App/assets/12595293/78711e40-d237-41e1-a159-75ea9708b398
https://github.com/Expensify/App/assets/12595293/3de721e3-b996-4f18-9a0a-bbee9a86ade5

BUG: unavailable workspace on transaction detail header when create expense manual request offline. Same happens on split manual request with workspace

Fixed ✔

@cead22 when creating a Split request and calling the SplitBillAndOpenReport API endpoint, we send the stringified splits among parameters. Each split will now contain the transactionThreadReportID and createdReportActionIDForThread that need to be handled on the BE – currently, the optimistic transaction thread is replaced with another from the BE response.

Thanks for letting me know, I'll make an issue for us to update the back end!

currently, the optimistic transaction thread is replaced with another from the BE response.

I made the issue, and we can wait for that fix to test this PR, but are you sure the backend replacing the value with a different one, and the issue isn't that we're not setting iouAction.childReportID in the client?
If the backend isn't returning a bad value, then things should work with the front end fix, because we'll navigate to the right report based on that front end value, right?

@cead22 I suppose you haven't made any changes on the BE side yet?
That's strange because I cannot reproduce now either SendMoney or Split bugs (with the changes from this PR) 🤔

@situchan, from my side the PR now tests well without extra BE changes pending.
Could you please re-test from your side as well?

are you sure the backend replacing the value with a different one, and the issue isn't that we're not setting iouAction.childReportID in the client?

@cead22, on the recording here, you can see that the optimistically created transaction thread was present initially (offline), but was replaced with a skeleton once the ReconnectToReport API response arrived upon coming back online.
In this PR I'm already setting the iouAction.childReportID, and the recording was made with the changes in place, so I wouldn't blame the absent iouAction.childReportID here.
Anyway, looks like this blocker was resolved – will just wait for @situchan to confirm.

I am blocked retesting this bug
Looks like regression from recent PR
https://github.com/Expensify/App/assets/108292595/50f2643a-11b5-4883-a735-9d999854fff5

I am blocked retesting this bug Looks like regression from recent PR
Screen.Recording.2024-03-05.at.8.53.30.PM.mov

I cannot reproduce – what is the precondition? Is it a new user you're trying to split with?

Same as https://github.com/Expensify/App/pull/37232#issuecomment-1975263308:

split manual request with a single user (non-Expensify) from FAB

@situchan the blocker was resolved, please re-test the failing scenario.
Just make sure to run npm ci on the branch – npm i did not get rid of the blocker for me.
https://github.com/Expensify/App/assets/12595293/7cb05168-99cc-4fe6-bbda-88ac9988651b

Works now after removing node modules again and clearing caches

Split scan seems not working. To reproduce, click report preview quickly after scan success
https://github.com/Expensify/App/assets/108292595/005c882e-1d9e-4597-a37e-db4516d368ff

Test Result: (🟢: pass, 🔴: failed, 🟡: pending test)

Request
Manual
Manual (receipt)
Scan
Distance

IOU (from FAB)
🟢
🟡
🟢
New

Expense (from FAB)
🟢
🟡
🟢
🟢

Split with user (from FAB)
🟢
🟡
🔴
New

Split with workspace (from FAB)
🟡
🟡
🟡
🟡

Send (from FAB)
🟡
N/A
N/A
N/A

IOU (from chat)
🟡
🟡
🟡
New

Expense (from chat)
🟡
🟡
🟡
🟡

Split with user (from chat)
🟡
🟡
🟡
New

Split with workspace (from chat)
🟡
🟡
🟡
🟡

Send (from chat)
🟡
N/A
N/A
N/A

(I keep updating fields upon testing)

@paultsimura Let's split testing. Can you please test all above cases for existing contact (if you haven't tested)?
I will test non-existing contact cases.

@situchan I've confirmed that all manual requests work fine.
Managed reproduce the issue with scan splits, investigating now...

@cead22 there is a BE issue with the CompleteSplitBill API call: it doesn't set (and return) the childReportID of the IOU action that we're passing in params. Right after, in an OpenReport call to the BE, the childReportID comes with a different value. And the optimistically created report gets removed:
https://github.com/Expensify/App/assets/12595293/c2bbf52b-9cef-4037-a2d8-3e9f2dbd84d9
Could we get this fixed on the BE side? Seems like so far it's the only API endpoint that's blocking us (if we want to hold for the BE change).

Being many issues are held for this PR and already dragged a lot for past blockers, I suggest to merge without waiting BE fix.

Maybe out of scope but map preview not showing in split distance request:

Tests completed
Result: https://github.com/Expensify/App/pull/37232#issuecomment-1983648624

@cead22 while testing, I've noticed a (relatively unrelated) issue with the SendMoney flow – we don't properly pass the optimistic CREATED actions:
https://github.com/Expensify/App/assets/12595293/47e059c1-62ec-444b-93e8-a53e7eb0a0c1
But to fix it, we need another BE fix. Should we hold for it, or can we make it a separate issue?

@cead22 while testing, I've noticed a (relatively unrelated) issue with the SendMoney flow – we don't properly pass the optimistic CREATED actions:
Screen.Recording.2024-03-10.at.19.12.42-compressed.mp4
But to fix it, we need another BE fix. Should we hold for it, or can we make it a separate issue?

yes, I noticed that as well but that should not really block this PR to be merged

All checks passed and everything was green when I merged. This wasn't an emergency change

🚀 Deployed to staging by https://github.com/cead22 in version: 1.4.51-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/luacmartins in version: 1.4.51-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Bitflag enums should inherit from enum.IntFlag instead of enum.IntEnum

What is the feature you'd like to have?
Some of the types defined in binaryninja.enums act as bitflags instead of using sequential integers for variant values. From what I can tell, these are the SegmentFlag, SettingsScope, and PluginStatus enums. They should inherit from IntFlag instead of IntEnum.
Is your feature request related to a problem?
The IntFlag type implements bitwise operations on enums, which fits with the use case for bitflags. Whereas, performing bitwise ops on the IntEnum type produces integers, causing issues with type checking.
Additional Information:
The enum.IntFlag type was added in Python 3.6, but the minimum supported version is already 3.8.

Hmm good catch. This is slightly annoying to fix because the enums.py is a generated file from the binaryninjaapi.h We'd have to special case these particular enumerations in the api generator. Annoying that IntEnum doesn't support the required bitwise operations 🤔


Update joda-convert to 2.2.1

Updates org.joda:joda-convert from 1.9.2 to 2.2.1.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.joda", artifactId = "joda-convert" } ]

labels: semver-major

Codecov Report

Merging #323 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #323   +/-   ##
========================================
  Coverage    61.29%   61.29%
========================================
  Files           50       50
  Lines         1540     1540
  Branches        40       40
========================================
  Hits           944      944
  Misses         596      596

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 38d2219...d0e8da3. Read the comment docs.


.Net4.5.2 WPF applcation : Error CS7069 Reference to type 'IEnableLogger' claims it is defined in 'Splat', but it could not be found

See also #983
Bizarrely I've just had this issue again, but this time for a .Net 4.5.2 WPF application from VS2015 (14.0.25123.00 Update 2) running NuGet <IP_ADDRESS>0.
With a single WPF application project, I created a quick UI and then added Reactiveui which came in as 6.5.0, upon adding  myReactiveCommandObject.Subscribe(________)  I got the red wiggles with Reference to type 'IEnableLogger' claims it is defined in 'Splat', but it could not be found
Furthermore, I can resolve this by running  Install-Package Splat -DependencyVersion Highest which migrated Splat from 1.0.0 to 1.6.2
Package Manager Console Host Version <IP_ADDRESS>0

Type 'get-help NuGet' to see all available NuGet commands.

PM> Install-Package ReactiveUI -DependencyVersion Highest
Package 'ReactiveUI.6.5.0' already exists in project 'Hilt'
PM> Install-Package Splat -DependencyVersion Highest
Attempting to gather dependency information for package 'Splat.1.6.2' with respect to project 'Hilt', targeting '.NETFramework,Version=v4.5.2'
Attempting to resolve dependencies for package 'Splat.1.6.2' with DependencyBehavior 'Highest'
Resolving actions to install package 'Splat.1.6.2'
Resolved actions to install package 'Splat.1.6.2'
Removed package 'Splat.1.0.0' from 'packages.config'
Successfully uninstalled 'Splat.1.0.0' from Hilt
  GET https://www.nuget.org/api/v2/package/Splat/1.6.2
  OK https://www.nuget.org/api/v2/package/Splat/1.6.2 2343ms
Installing Splat 1.6.2.
Adding package 'Splat.1.6.2' to folder 'C:\Dev\Hilt\packages'
Added package 'Splat.1.6.2' to folder 'C:\Dev\Hilt\packages'
Added package 'Splat.1.6.2' to 'packages.config'
Successfully installed 'Splat 1.6.2' to Hilt
Removing package 'Splat.1.0.0' from folder 'C:\Dev\Hilt\packages'
Removed package 'Splat.1.0.0' from folder 'C:\Dev\Hilt\packages'
PM>

@alski Splat needs to be installed before ReactiveUI when using 6.5 currently. It's super annoying, v7 is just around the corner and has fixed this.

Looking forwards to v7 then :-)

Come join us in slack. :)
On Wed, 15 Jun 2016, 3:52 PM Al<EMAIL_ADDRESS>wrote:

Looking forwards to v7 then :-)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/reactiveui/ReactiveUI/issues/1120#issuecomment-226094599,
or mute the thread
https://github.com/notifications/unsubscribe/AAHxeUrMAk6v4l9zYZg9ZPblDHrrhdjqks5qL5M6gaJpZM4IywBS
.

Howdy we have pushed v6.5.1 to NuGet which resolves installation into portable class libraries that target Profile259. This release contains the exact same binaries as v6.5.0 but resolves a nuspec metadata version definition which was causing this problem.
.@ReactiveXUI v6.5.1 has been released. Resolves install into Profile259 ie UWP/XamForms. Same binaries as v6.5.0. pic.twitter.com/gBjxHQxsjZ— Geoffrey Huntley (@GeoffreyHuntley) August 17, 2016


Wrong 'type' gets populated in constraint if user chooses any other type than default.

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):

Create a cluster, navigate to dashboard, enable gatekeeper.
Create a constraint in edit form while changing the type.
View constraint in yaml form.

Result:
Constraint is created with the type which was appearing in constraint by default. In below example kind and and type are not same.
apiVersion: constraints.gatekeeper.sh/v1beta1
kind: K8sRequiredLabels
metadata:
  annotations:
    cattle.io/description: ""
  creationTimestamp: "2020-04-13T17:02:50Z"
  finalizers:
  - finalizers.gatekeeper.sh/constraint
  generation: 1
  name: test
  resourceVersion: "926363"
  selfLink: /apis/constraints.gatekeeper.sh/v1beta1/k8srequiredlabels/test
  uid: 7d3ce42f-b4ab-4e5b-93dd-270cb1c80c8f
spec:
  enforcementAction: deny
  match:
    excludedNamespaces: []
    kinds:
    - apiGroups:
      - ""
    labelSelector:
      matchExpressions: []
    namespaceSelector:
      matchExpressions: []
  parameters: {}
status:
  byPod:
  - enforced: true
    id: gatekeeper-controller-manager-76f7b99c4b-scrqs
    observedGeneration: 1
type: constraints.gatekeeper.sh.k8sallowedrepos

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.4.2
Installation option (single install/HA): Single

@codyrancher One thing I see in the above yaml file is that there is a type added type: constraints.gatekeeper.sh.k8sallowedrepos which is wrongly sent by the UI in the POST request while creating the constraint. Seems like an issue with toggling the "template" on the form

First I created a constraint using template "k8sallowedrepos"
It got created fine
Then I created another constraint and toggled the template to "k8srequiredlabels". But the data that is sent in the http POST by the UI still sent the "type" as "constraints.gatekeeper.sh.k8sallowedrepos"

{"type":"**constraints.gatekeeper.sh.k8sallowedrepos**","spec":{"parameters":{},"match":{"kinds":[{"apiGroups":[""]}],"excludedNamespaces":[],"labelSelector":{"matchExpressions":[]},"namespaceSelector":{"matchExpressions":[]}},"enforcementAction":"deny"},"metadata":{"name":"**label**","annotations":{"cattle.io/description":null}}}

Verified in latest master, type is getting populated as template selected while creating constraint.
Steps:

Click create constraint.
Change the template value and save.
Verified in yaml view. Type is getting updated as per template selected.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_4286c7cc-50d9-4516-811a-f6bb407c630d/pull/1 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target_4286c7cc-50d9-4516-811a-f6bb407c630d.git

Docs Build status updates of commit 54cb996:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://aka.ms/SiteHelp and include the error report for our team to troubleshoot

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Update readme.md

With 12GB of RAM the build was failing with Out of Memory and with 30GB Disk the build was failing with Out of Space.

We can probably include this info, but builds should be cached for x86_64
Did you doing a nixos-rebuild switch after adding substituters but before enabling any cosmic nixos options? (I need to make readme much clearer about that...)

The following process was used from readme.md:
"After rebuilding with that configuration to get the binary cache substituters set up, enable COSMIC"
Yes nixos-rebuild switch was used.

Yes nixos-rebuild switch was used.

As in you did nixos-rebuild switch and enabled services.desktopManager.cosmic.enable = true and then did a nixos-rebuild switch again, to enable COSMIC?

Yes

This is probably not the right place to discuss this, but I also added the cache to my flake.nix, ran nixos-rebuild switch, enabled the services, ran nixos-rebuild switch again, and had to build all the packages locally.
Is there something else we might have to enable or install like the cachix client?

This is probably not the right place to discuss this, but I also added the cache to my flake.nix, ran nixos-rebuild switch, enabled the services, ran nixos-rebuild switch again, and had to build all the packages locally.
Is there something else we might have to enable or install like the cachix client?

No, there is nothing else to do, and I'm not sure what's up with that. If you are still having to build packages locally, please open a new issue with information on what your nixos-unstable revision is and what architecture (e.g. x86_64-linux or aarch64-linux) you are using

I'll go ahead and merge this but adjust it further to clarify that the requirements are only necessary if building locally and that options like -j 1 and --cores 1 can help to reduce concurrent RAM usage


Undefined symbols for architecture x86_64

Hey, I'm getting the following error while building an React Native Expo App, all latest versions for iOS.
macos-14-arm64
Xcode 15.3
[RUN_FASTLANE] ❌  Undefined symbols for architecture x86_64
┌─ Symbol: _groth16_prover
└─ Referenced from: -[Rapidsnark groth16Prove:witnessData:proofBufferSize:publicBufferSize:errBufferSize:resolve:reject:] in react_native_rapidsnark[x86_64][3](Rapidsnark.o)
[RUN_FASTLANE]
❌  ld: symbol(s) not found for architecture x86_64
[RUN_FASTLANE]
❌  clang: error: linker command failed with exit code 1 (use -v to see invocation)

Hi,
Are you running local build or in Expo CI?

Hey @5eeman Both EAS build using Github Actions & Local EAS builds return the same error on 0.0.1-alpha.3
[RUN_FASTLANE] +---------------------------------------+
[RUN_FASTLANE] |           Build environment           |
[RUN_FASTLANE] +-------------+-------------------------+
[RUN_FASTLANE] | xcode_path  | /Applications/Xcode.app |
[RUN_FASTLANE] | gym_version | 2.217.0                 |
[RUN_FASTLANE] | sdk         | iPhoneOS17.4.sdk        |
[RUN_FASTLANE] +-------------+-------------------------+

Hi @anudit.
Currently we have  only arm64 build for IOS.
Can you try to build only for arm64 or for device?

In radpidsnark we have asm optimisation for mobiles devices. We have builds without optimisations specifically for simulator. As x86_64 required only for old intel devices it was not included in the library. On modern apple devices with arm architecture, already available simulators with arm64, and x86_64 is not reqired for local builds.

You can exclude architecture in the settings and it should work

For devices you will need arm anyway.
If there's a good reason to add x86_64 for simulators we can do it.

@demonsh I tried excluding it in the settings and Podfile but still hitting the Undefined symbols for architecture x86_64
installer.pods_project.targets.each do |target|
      target.build_configurations.each do |config|
        config.build_settings['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = 'x86_64'
      end
    end

I'll make a minimal repro of this.

Thanks @anudit. I'll take a look on it.

@anudit please, try using a version from fix/ios_sim_x64 branch.
I've updated ios sim libs with version with x86_64 support.

Thanks a lot @5eeman  @demonsh iOS Simulator builds work perfectly now on the fix/ios_sim_x64 branch.
[RUN_FASTLANE] › Generating debug Omnid » Omnid.app.dSYM
[RUN_FASTLANE] › Executing Omnid » Bundle React Native code and images
[RUN_FASTLANE] › Executing Omnid » [CP] Copy Pods Resources
[RUN_FASTLANE] › Executing Omnid » [CP] Embed Pods Frameworks
[RUN_FASTLANE] › Signing   Omnid » Omnid.app
[RUN_FASTLANE] › Creating  Omnid » Omnid.app
[RUN_FASTLANE] › Build Succeeded
[UPLOAD_APPLICATION_ARCHIVE] Application archives: /var/folders/lb/p46m2p597tg43_4nfbct5vjc0000gn/T/eas-build-local-nodejs/1fb83023-af03-450b-b689-292ae07e8d4d/build/ios/build/Build/Products/Debug-iphonesimulator/Omnid.app
[UPLOAD_APPLICATION_ARCHIVE] Uploading application archive...
[PREPARE_ARTIFACTS] Preparing artifacts
[PREPARE_ARTIFACTS] Writing artifacts to /Users/anudit/Documents/GitHub/omnidapp/app-ios.tar.gz

Build successful
You can find the build artifacts in /Users/anudit/Documents/GitHub/omnidapp/app-ios.tar.gz

@anudit just for my interest, how you are building witness?

Webview for now, switching to native c++ soon. Experimenting with https://github.com/0xPolygonID/witnesscalc & https://github.com/philsippl/circom-witness-rs
Not keen on adding an additional wasm runtime though we can link arkworks directly.

Thanks @anudit
We are using https://github.com/0xPolygonID/witnesscalc  in production for almost two years.
If you will succeed with https://github.com/philsippl/circom-witness-rs please share your experience. We are working on adding missing instructions to circom-witness-rs, but at the moment it is more experiments.

Fixed in 0.0.1-alpha.4


When I execute the 'python train_stage1.py' directive, I find a problem

Hi.  Your work is very good, thank you very much for releasing your code.
However, when I was running the 'python train_stage1.py' instruction, I found a problem and I hope you can help me solve it.
Thank you very much.

Traceback (most recent call last):
File "train_stage1.py", line 164, in
main()
File "train_stage1.py", line 157, in main
best_model = load_checkpoint(model, best_ckpt_fpath)
File "/home/test/RecNet/RecNet/utils.py", line 242, in load_checkpoint
checkpoint = torch.load(ckpt_fpath)
File "/home/test/RecNet/RecNet/.env/local/lib/python2.7/site-packages/torch/serialization.py", line 368, in load
return _load(f, map_location, pickle_module)
File "/home/test/RecNet/RecNet/.env/local/lib/python2.7/site-packages/torch/serialization.py", line 517, in _load
_check_seekable(f)
File "/home/test/RecNet/RecNet/.env/local/lib/python2.7/site-packages/torch/serialization.py", line 189, in _check_seekable
raise_err_msg(["seek", "tell"], e)
File "/home/test/RecNet/RecNet/.env/local/lib/python2.7/site-packages/torch/serialization.py", line 182, in raise_err_msg
raise type(e)(msg)
AttributeError: 'NoneType' object has no attribute 'seek'. You can only torch.load from a file that is seekable. Please pre-load the data into a buffer like io.BytesIO and try to load from it instead.

It seems that there was an error at the try block, but the full error message is not shown. I just removed the try block, as I think it is not that important functionality. So, can you run your code again and show me the error message?

First of all, thank you very much for helping me solve the above problem. When I made the modification as you suggested, another problem occurred after running 'python train_stage1.py 'again. I searched the Internet for many solutions, but none of them solved the problem. So again, I hope you can help me solve this problem.
Thank you very much.
Traceback (most recent call last):
File "train_stage1.py", line 156, in
main()
File "train_stage1.py", line 127, in main
C.reg_lambda, C.recon_lambda, C.gradient_clip)
File "/home/test/RecNet/RecNet/utils.py", line 52, in train
output, feats_recon = model(feats, captions, teacher_forcing_ratio)
File "/home/test/RecNet/RecNet/.env/local/lib/python2.7/site-packages/torch/nn/modules/module.py", line 489, in call
result = self.forward(*input, **kwargs)
File "/home/test/RecNet/RecNet/models/caption_generator.py", line 110, in forward
teacher_forcing_ratio)
File "/home/test/RecNet/RecNet/models/caption_generator.py", line 36, in forward_decoder
output, hidden, attn_weights = self.decoder(output.view(1, -1), hidden, feats)
File "/home/test/RecNet/RecNet/.env/local/lib/python2.7/site-packages/torch/nn/modules/module.py", line 489, in call
result = self.forward(*input, **kwargs)
File "/home/test/RecNet/RecNet/models/decoder.py", line 53, in forward
feats, attn_weights = self.attention(last_hidden, feats)
File "/home/test/RecNet/RecNet/.env/local/lib/python2.7/site-packages/torch/nn/modules/module.py", line 489, in call
result = self.forward(*input, **kwargs)
File "/home/test/RecNet/RecNet/models/temporal_attention.py", line 20, in forward
Uv = self.U(feats)
File "/home/test/RecNet/RecNet/.env/local/lib/python2.7/site-packages/torch/nn/modules/module.py", line 489, in call
result = self.forward(*input, **kwargs)
File "/home/test/RecNet/RecNet/.env/local/lib/python2.7/site-packages/torch/nn/modules/linear.py", line 67, in forward
return F.linear(input, self.weight, self.bias)
File "/home/test/RecNet/RecNet/.env/local/lib/python2.7/site-packages/torch/nn/functional.py", line 1354, in linear
output = input.matmul(weight.t())
RuntimeError: size mismatch, m1: [5600 x 25088], m2: [1536 x 256] at /pytorch/aten/src/THC/generic/THCTensorMathBlas.cu:266

I think the shape of the features is not the same as I expected. Can you check the shape of feats at models/temporal_attention.py? I think the shape of the feats tensor should be (200, 28, 1536) (where the 200 is the batch size, 28 is the number of sampled frames, and 1536 is the feature dimension).
FYI, if you wrap the error message with backticks (```), it is more readable, like below
Traceback (most recent call last):
File "train_stage1.py", line 156, in
main()
File "train_stage1.py", line 127, in main
C.reg_lambda, C.recon_lambda, C.gradient_clip)
File "/home/test/RecNet/RecNet/utils.py", line 52, in train
output, feats_recon = model(feats, captions, teacher_forcing_ratio)
...

I'm sorry, I can't understand you very well.I looked at the models/temporal_attention.py file, but all I saw were the parameters that called each other, not the actual values that were set.
For example:
import torch
import torch.nn as nn
import torch.nn.functional as F

class TemporalAttention(nn.Module):
    def __init__(self, hidden_size, feat_size, bottleneck_size):
        super(TemporalAttention, self).__init__()
        self.hidden_size = hidden_size
        self.feat_size = feat_size
        self.bottleneck_size = bottleneck_size

        self.W = nn.Linear(self.hidden_size, self.bottleneck_size, bias=False)
        self.U = nn.Linear(self.feat_size, self.bottleneck_size, bias=False)
        self.b = nn.Parameter(torch.ones(self.bottleneck_size), requires_grad=True)
        self.w = nn.Linear(self.bottleneck_size, 1, bias=False)

    def forward(self, hidden, feats):
        Wh = self.W(hidden)
        Uv = self.U(feats)
        Wh = Wh.unsqueeze(1).expand_as(Uv)
        energies = self.w(torch.tanh(Wh + Uv + self.b))
        weights = F.softmax(energies, dim=1)

        weighted_feats = feats * weights.expand_as(feats)
        attn_feats = weighted_feats.sum(dim=1)
        return attn_feats, weights

Can you provide me with your msvd_inceptionv4.hdf5 file?I was wondering if there was a problem with my extracted msvd_inceptionv4.hdf5 file.

What I meant was, check the dimension of feats so that it is (200, 28, 1536).
I'll upload the link for downloading `MSVD_InceptionV4.hdf5' soon.


N813 seems too broad in scope

Hi, currently N813 is raised even for cases such as
import netCDF4 as nc

which seem innocuous from the point of view of the rule: https://docs.astral.sh/ruff/rules/camelcase-imported-as-lowercase/
Would it make sense to restrict the applicability of this rule to cases where name.to_lowercase() == asname.to_lowercase()? I would be happy to send a PR if that was the case!

I'm a bit torn as this does match "upstream" (i.e. ,pep8-naming does flag with the same error), but I agree that this isn't a very helpful violation in practice.

this does match "upstream"

For me that means pep8-naming also implemented this in a suboptimal way—this violation shouldn't show up for module aliases imo.


Rebuild Rocky Linux 9 image with missing packages and newer cloud-init

New rocky-container-stackhpc element contains containerfile that installs 'Minimal Install' group which fixes missing packages like microcode_ctl and brings in new cloud-init from c9s that supports NetworkManager and fixes some interface renaming issues.

We did still see the race occurring on at least one node with cloud-init-23.1.1-12.el9.noarch.rpm and the NetworkManager cloud init renderer. I don't think we had the Minimal install group:
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    25 |                                                                                | 2023-10-31 14:43 | Install        |    2
    24 |                                                                                | 2023-10-31 14:43 | Removed        |    2 EE
    23 |                                                                                | 2023-10-31 14:43 | Install        |   19  <
    22 | install tree                                                                                | 2023-10-31 14:17 | Install        |    1 >
    21 |                                                                                | 2023-10-31 14:02 | Install        |    2
    20 |                                                                                | 2023-10-31 14:02 | Install        |    1 EE
    19 |                                                                                | 2023-10-31 14:02 | Install        |   13 EE
    18 |                                                                                | 2023-10-31 14:01 | Install        |    5
    17 |                                                                                | 2023-10-16 11:30 | Reason Change  |    1
    16 | -v -y install lvm2                                                                                | 2023-10-16 11:30 | Install        |    6 EE
    15 |                                                                                | 2023-10-16 11:30 | Reason Change  |    1
    14 | -v -y install cryptsetup                                                                                | 2023-10-16 11:30 | Install        |    1
    13 |                                                                                | 2023-10-16 11:30 | Reason Change  |    6
    12 | -v -y install grub2-tools grub2 efibootmgr grub2-efi-x64 grub2-efi-x64-modules shim-x64                                | 2023-10-16 11:29 | Install        |   47 EE
    11 |                                                                                | 2023-10-16 11:29 | Reason Change  |    9
    10 | -v -y install logrotate net-tools vim git less python3 NetworkManager-config-server linux-firmware cloud-utils-growpar | 2023-10-16 11:29 | Install        |   19 EE
     9 | -v -y remove linux-firmware-whence linux-firmware                                                                      | 2023-10-16 11:29 | Removed        |    2
     8 |                                                                                | 2023-10-16 11:29 | Reason Change  |   26
     7 | -v -y install dnf-plugins-core python3-libselinux traceroute python3-policycoreutils selinux-policy-targeted tcpdump a | 2023-10-16 11:28 | Install        |  132 EE
     6 | -y update                                                                                | 2023-10-16 11:28 | Upgrade        |   16
     5 |                                                                                | 2023-10-16 11:28 | Reason Change  |    1
     4 | -v -y install iscsi-initiator-utils                                                                                | 2023-10-16 11:28 | Install        |    3 EE
     3 |                                                                                | 2023-10-16 11:28 | Reason Change  |    2
     2 | -v -y install gettext python3-PyYAML                                                                                | 2023-10-16 11:28 | Install        |    2
     1 | install -y findutils util-linux sudo python3 NetworkManager https://mirror.stream.centos.org/9-stream/AppStream/x86_64 | 2023-10-10 15:59 | I, U           |   77 EE
Failed to store expired repos cache: [Errno 13] Permission denied: '/var/cache/dnf/expired_repos.json'
[stack@compute-12 ~]$

We did still see the race occurring on at least one node with cloud-init-23.1.1-12.el9.noarch.rpm and the NetworkManager cloud init renderer. I don't think we had the Minimal install group:
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    25 |                                                                                | 2023-10-31 14:43 | Install        |    2
    24 |                                                                                | 2023-10-31 14:43 | Removed        |    2 EE
    23 |                                                                                | 2023-10-31 14:43 | Install        |   19  <
    22 | install tree                                                                                | 2023-10-31 14:17 | Install        |    1 >
    21 |                                                                                | 2023-10-31 14:02 | Install        |    2
    20 |                                                                                | 2023-10-31 14:02 | Install        |    1 EE
    19 |                                                                                | 2023-10-31 14:02 | Install        |   13 EE
    18 |                                                                                | 2023-10-31 14:01 | Install        |    5
    17 |                                                                                | 2023-10-16 11:30 | Reason Change  |    1
    16 | -v -y install lvm2                                                                                | 2023-10-16 11:30 | Install        |    6 EE
    15 |                                                                                | 2023-10-16 11:30 | Reason Change  |    1
    14 | -v -y install cryptsetup                                                                                | 2023-10-16 11:30 | Install        |    1
    13 |                                                                                | 2023-10-16 11:30 | Reason Change  |    6
    12 | -v -y install grub2-tools grub2 efibootmgr grub2-efi-x64 grub2-efi-x64-modules shim-x64                                | 2023-10-16 11:29 | Install        |   47 EE
    11 |                                                                                | 2023-10-16 11:29 | Reason Change  |    9
    10 | -v -y install logrotate net-tools vim git less python3 NetworkManager-config-server linux-firmware cloud-utils-growpar | 2023-10-16 11:29 | Install        |   19 EE
     9 | -v -y remove linux-firmware-whence linux-firmware                                                                      | 2023-10-16 11:29 | Removed        |    2
     8 |                                                                                | 2023-10-16 11:29 | Reason Change  |   26
     7 | -v -y install dnf-plugins-core python3-libselinux traceroute python3-policycoreutils selinux-policy-targeted tcpdump a | 2023-10-16 11:28 | Install        |  132 EE
     6 | -y update                                                                                | 2023-10-16 11:28 | Upgrade        |   16
     5 |                                                                                | 2023-10-16 11:28 | Reason Change  |    1
     4 | -v -y install iscsi-initiator-utils                                                                                | 2023-10-16 11:28 | Install        |    3 EE
     3 |                                                                                | 2023-10-16 11:28 | Reason Change  |    2
     2 | -v -y install gettext python3-PyYAML                                                                                | 2023-10-16 11:28 | Install        |    2
     1 | install -y findutils util-linux sudo python3 NetworkManager https://mirror.stream.centos.org/9-stream/AppStream/x86_64 | 2023-10-10 15:59 | I, U           |   77 EE
Failed to store expired repos cache: [Errno 13] Permission denied: '/var/cache/dnf/expired_repos.json'
[stack@compute-12 ~]$

Minimal Install basically adds mainly microcode_ctl which adds CPU CVE mitigations (which was missing) - I'm not aware it fixes anything else.

We did still see the race occurring on at least one node with cloud-init-23.1.1-12.el9.noarch.rpm and the NetworkManager cloud init renderer. I don't think we had the Minimal install group:
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    25 |                                                                                | 2023-10-31 14:43 | Install        |    2
    24 |                                                                                | 2023-10-31 14:43 | Removed        |    2 EE
    23 |                                                                                | 2023-10-31 14:43 | Install        |   19  <
    22 | install tree                                                                                | 2023-10-31 14:17 | Install        |    1 >
    21 |                                                                                | 2023-10-31 14:02 | Install        |    2
    20 |                                                                                | 2023-10-31 14:02 | Install        |    1 EE
    19 |                                                                                | 2023-10-31 14:02 | Install        |   13 EE
    18 |                                                                                | 2023-10-31 14:01 | Install        |    5
    17 |                                                                                | 2023-10-16 11:30 | Reason Change  |    1
    16 | -v -y install lvm2                                                                                | 2023-10-16 11:30 | Install        |    6 EE
    15 |                                                                                | 2023-10-16 11:30 | Reason Change  |    1
    14 | -v -y install cryptsetup                                                                                | 2023-10-16 11:30 | Install        |    1
    13 |                                                                                | 2023-10-16 11:30 | Reason Change  |    6
    12 | -v -y install grub2-tools grub2 efibootmgr grub2-efi-x64 grub2-efi-x64-modules shim-x64                                | 2023-10-16 11:29 | Install        |   47 EE
    11 |                                                                                | 2023-10-16 11:29 | Reason Change  |    9
    10 | -v -y install logrotate net-tools vim git less python3 NetworkManager-config-server linux-firmware cloud-utils-growpar | 2023-10-16 11:29 | Install        |   19 EE
     9 | -v -y remove linux-firmware-whence linux-firmware                                                                      | 2023-10-16 11:29 | Removed        |    2
     8 |                                                                                | 2023-10-16 11:29 | Reason Change  |   26
     7 | -v -y install dnf-plugins-core python3-libselinux traceroute python3-policycoreutils selinux-policy-targeted tcpdump a | 2023-10-16 11:28 | Install        |  132 EE
     6 | -y update                                                                                | 2023-10-16 11:28 | Upgrade        |   16
     5 |                                                                                | 2023-10-16 11:28 | Reason Change  |    1
     4 | -v -y install iscsi-initiator-utils                                                                                | 2023-10-16 11:28 | Install        |    3 EE
     3 |                                                                                | 2023-10-16 11:28 | Reason Change  |    2
     2 | -v -y install gettext python3-PyYAML                                                                                | 2023-10-16 11:28 | Install        |    2
     1 | install -y findutils util-linux sudo python3 NetworkManager https://mirror.stream.centos.org/9-stream/AppStream/x86_64 | 2023-10-10 15:59 | I, U           |   77 EE
Failed to store expired repos cache: [Errno 13] Permission denied: '/var/cache/dnf/expired_repos.json'
[stack@compute-12 ~]$

Minimal Install basically adds mainly microcode_ctl which adds CPU CVE mitigations (which was missing) - I'm not aware it fixes anything else.

We only seemed to hit on one node, so seems much more reliable, but possibly doesn't 100% fix the issue. @Dawud can confirm.

Hey @jovial , I think you meant to mention somebody else, not me. Cheers!

Sorry about that @dawud, I think the intended target was @technowhizz


Separate ToSchema from PAB usage

Area
[X] Plutus Application Framework Related to the Plutus application backend (PAB), emulator, Plutus libraries
Describe the feature you'd like
ToSchema seems to be useful only for Playground, and provides support for user to input data in the web-interface.
Also PAB is useful on it's own in the headless-mode. When we can run servant server.
Often one or another data type can not be made instance of ToSchema, because it does not support Sum-types
(only sum of constants is supported right now0.
I wonder is it possible to create functional PAB in headless node without requirement for ToSchema instance for it's inputs.
If we are going to use it with cli-executable that can create JSON-values.
So is it possible to relax requirement of PAb from ToSchema down to ToJSON?
it can be super useful to create custom cli-executables.

Closing as solved in https://github.com/input-output-hk/plutus-apps/issues/212.


Add Python Template

Why shouldn't this generator have a Discord.py template?

 HA, I added it!


[Proposal] Make an official tech lead process

Description
Make an official tech-lead process.
Impact

This will give us transparency in how these leads are chosen, and what expectations are to get there.
Scope

Minimal, but will need community discussion and TOC approval.
TODO

[ ] TAG Environmental Sustainability lead representative:  All TAG Chairs/leads
[ ] Project leader(s):  @leonardpahlke
[ ] Project Members:  N/A
[ ] Fill in addition TODO items here so the project team and community can see progress!
[ X ] Scope
[ ] Deliverable(s):  Documentation added to TAG

This document already describes the process around becoming a TL: https://github.com/cncf/tag-env-sustainability/blob/main/governance/tech-lead-proposal-process.md
I opened a PR to make some small updates without changing the process or guidelines..: https://github.com/cncf/tag-env-sustainability/pull/121
This PR adds some guidelines on how to mature as a contributor inside the TAG: https://github.com/cncf/tag-env-sustainability/pull/124

Can be closed?


only run gateway conformance tests during nightly builds

/lgtm

/override "Generate some code!"
/override "style / suggester / yaml"
/override "style / suggester / github_actions"
/override "style / Golang"


spam issues

Hi,
I am receiving emails on my work inbox<EMAIL_ADDRESS>for this whole repo. Every issue filed, answered, PR, commit... everything lands in my inbox. It is driving me crazy.
I did never watch or star the repo. It started happening out of the blue.
My Github account does not even use this email as login. I have no idea on how and why this is happening.
Thank you for helping on this.
edit: clicking on the "unsubscribe" link of the email brings me to this repo, with that error.

I don't know if this would help but have you checked out this article on notifications:
https://help.github.com/en/articles/subscribing-to-and-unsubscribing-from-notifications

I am getting notifications for everything under this repo, without opting in notifications. I'll contact github, but I'd like to know: is there anything set on your org, like a mailing list or something like that?

I am not the owner of this repo so i can't say for sure, but I suspect there isn't.
When ever I get an email from Github there is always a unsubscribe link, have you tried that.

This is part of the issue description. The link does not work. The email address I am getting spammed at is not even my github email.

Yep, this is not an issue with the repo or the org. We are not sending emails to people about anything we do, let alone issues and PRs. It's probably an issue with Github or a 3rd-party app. Hope you can resolve this.
I'll keep this open for a little bit, post any information you get here and inform us if we can help in any way with this if it's some kind of configuration problem.

Sounds good. I already contacted github's support... crossing fingers. Thank you!

I'll close - it seems to be redirects from a former employee's email address. Thank you!


[doc] Modify from Job Name to Unique ID

Document says td_load> can use "Job name" instead of yml. However, "Job name" is not understandable and make a confuse. It would be said "Unique ID".
Refer: https://support.treasuredata.com/hc/en-us/articles/360001474328-Reference-an-Input-Data-Transfer#Configuring your Unique ID Incremental Data Transfer
And remove duplicated "td.last_job_id" item.

I mis-read td.last_job_id and td.last_job.id.... It would be better to re-write.

@kamikaseda thanks for fixing. As I took a look the impl. of td_load operator. At least the command name doesn't represent TD job name. You're correct. But, I think that "Unique ID" also will make users confused. According to the impl., that's the name of data transfer, former bulk_load_session. What do you think that we'd better to change "Unique ID" with the name of data transfer in both of Digdag doc and support doc?

@muga Naming rules is wholly Treasure Data internal issue. I think we should unify a name based on Treasure Data's official document for now.

@kamikaseda got it, thanks. I think that uniq id still make confising but, better than job name. let's merge it.


Generalise xla::Map to functions over arbitrary shapes

System information

TensorFlow version (you are using): 2.8
Are you willing to contribute it (Yes/No): No

Describe the feature and the current behavior/state.
Currently xla::Map only allow functions from shape [] to []. I'd like to use functions with arbitrary shapes. For example, apply a function with shapes [2, 3] -> [5] to a tensor [100, 4, 2, 3] to get a [100, 4, 5].
I've not yet thought about how it would work when mapping multiple input tensors at once.
Will this change the current api? How?
It would extend xla::Map, either internally, or as an overload. It's possible additional information would need to be passed to a more general implementation of map, in which an overload may be preferable to maintain backwards compatibility.
Who will benefit with this feature?
Anyone using XLA who'd like to apply a function over sections of a tensor. It would effectively be an alternative to (some portion of) broadcasting, allowing people to use functions that don't allow leading dimensions to tensors with leading dimensions.
It is particularly useful for me as I'm working with dependent types and adding leading dimensions is non-trivial (and verbose) in type signatures.
Any Other info.
It is already possible to do this by indexing into the tensor and iteratively applying the function to the contents, then concatenating the results, but I expect this is significantly slower than could be achieved within XLA. I have considered using xla::While for this but I still expect the slicing and concatenation would still come with a significant performance cost.

I have remembered that it may be possible to use xla::While with xla::Slice and xla::DynamicUpdateSlice, thus avoiding the concatenation at the end. I don't know if this would be performant.


Feature request: connect timeout

Request:

When connecting to ble device with peripheral uuid it would be nice to have a connect timeout that cancels the connect
For example, if connecting to BLE device and then device loses power the app gets stuck in the connecting state currently

Yes that could be nice. Could you make a PR?

@farfromrefug yeah, I'll try to get something out in a week


window.navigator.getGamepads() fails on Firefox and Edge when using ddc and breaks every Iterable used afterwards

EDIT: See https://github.com/dart-lang/sdk/issues/37190#issuecomment-499892026, getGamepads() ruins every iterable.
I have this code:
  final connectedGamepads = window.navigator.getGamepads();
  print(connectedGamepads.length);
  print(connectedGamepads.runtimeType);
  print(connectedGamepads);

which I compile using pub serve build_runner serve and using dartdevc as the compiler. When I open the page in Firefox, the following is logged (It does not matter if a gamepad is connected or not):
0 dart_sdk.js:18740:15
_GamepadList dart_sdk.js:18740:15
Error: dart_sdk.js:5844:7
    DartError dart_sdk.js:5844
    throw dart_sdk.js:4556
    castError dart_sdk.js:4516
    as dart_sdk.js:4856
    check_C dart_sdk.js:4036
    add dart_sdk.js:73426
    _isSubtypeOrLegacySubtype dart_sdk.js:4306
    _isSubtypeOrIgnorableCastFailure dart_sdk.js:4818
    as dart_sdk.js:4853
    check_C dart_sdk.js:4036
    add dart_sdk.js:73426
    _isSubtypeOrLegacySubtype dart_sdk.js:4306
    _isSubtypeOrIgnorableCastFailure dart_sdk.js:4818
    as dart_sdk.js:4853
    check_C dart_sdk.js:4036
    add dart_sdk.js:73426
    iterableToFullString dart_sdk.js:15270
    toString dart_sdk.js:9719
    str dart_sdk.js:4981
    print dart_sdk.js:41132
    main main.dart:9
    <anonymous> main.dart.bootstrap.js:237
    execCb require.js:1696
    check require.js:878
    enable require.js:1139
    bind require.js:134
    emit require.js:1189
    each require.js:59
    emit require.js:1188
    check require.js:938
    enable require.js:1139
    bind require.js:134
    emit require.js:1189
    each require.js:59
    emit require.js:1188
    check require.js:938
    enable require.js:1176
    init require.js:788
    callGetModule require.js:1203
    completeLoad require.js:1590
    onScriptLoad require.js:1717

When I set the breakpoint @DartError dart_sdk.js:5844 the following error message is passed to DartError: Expected a value of type 'Gamepad', but got one of type 'NativeJavaScriptObject
If I open the page with Chrome or use dart2js everything works fine and it prints an empty list for Firefox .
What I would expect:

code compiled with dartdevc should also work on Firefox (same for Edge)

Also, I am sure it did work at some point, because I've run this code successfully before (before May 21, so Dart 2.3.0 and Firefox 67). Going back to an older pubspeck.lock where it did work doesn't change anything, so it's probably dartdevc (maybe Firefox 68 returns something different than Firefox 67 that can't be mapped like before? It works in Chrome after all.).
OS: Windows 10
Browser: Firefox 68.0b7 (64-bit)
Dart: Dart VM version: 2.3.1 (Tue May 21 19:28:38 2019 +0200) on "windows_x64"

Okay, this one is driving me nuts. I've downgraded to Dart 2.3.0 and Firefox 67 and it still didn't run, but when I switched some lines of code, it suddenly run (even on current Dart 2.3.1 and Firefox 68 and Edge).
So, this code does not run on Firefox and Edge:
  print('getGamepads');
  final connectedGamepads = window.navigator.getGamepads();
  print('listen');
  window.on['gamepadconnected'].cast<GamepadEvent>().listen((event) {
    print(event.gamepad);
  });
  print('iterate');
  for (var i = 0; i < connectedGamepads.length; i++) {
    if (connectedGamepads[i] != null) {
      print(i);
    }
  }
  print('done');

and outputs:
getGamepads dart_sdk.js:18740:15
listen dart_sdk.js:18740:15
Error: dart_sdk.js:5844:7

but this code runs just fine on Chrome, Firefox and Edge (the only change is that I moved the getGamepads() line):
  print('listen');
  window.on['gamepadconnected'].cast<GamepadEvent>().listen((event) {
    print(event.gamepad);
  });
  print('getGamepads');
  final connectedGamepads = window.navigator.getGamepads();
  print('iterate');
  for (var i = 0; i < connectedGamepads.length; i++) {
    if (connectedGamepads[i] != null) {
      print(i);
    }
  }
  print('done');

and outputs:
listen dart_sdk.js:18740:15
getGamepads dart_sdk.js:18740:15
iterate dart_sdk.js:18740:15
done dart_sdk.js:18740:15

and even [object Gamepad] in all 3 browsers once I press a button. No NativeJavaScriptObject anywhere.
It's a simple fix in this example, but this "fix" doesn't work in my actual code (not yet at least), so I have no idea what's going on here. I haven't touched that part of my code since November 2018.

Okay, it's not me who is going nuts, it's window.navigator.getGamepads() that's gone totally bonkers in ddc on Firefox and Edge.
This simple program which doesn't even interact with the gamepads just fails spectacularly:
import 'dart:html';

void main() {
  window.navigator.getGamepads();
  print('add item');
  [].add(1);
  print('done');
}

It's the same exception as above with a similar stacktrace. Somehow getGamepads() turns all lists into lists of gamepads.
In the dart_sdk.js of the add method is this code:
add(value) {
  E._check(value);
  dart.throw(new core.UnsupportedError.new("Cannot add to immutable List."));
}

E is a type parameter and in this case it is Gamepad. As far as I can tell, everything that is Iterable is affected.

I believe that DDC (the development compiler) is only tested against Chrome. dart2js (the release mode compiler) is tested against the major evergreen browsers.
cc @vsmenon

Thanks for the simplified repro!
As @devoncarew said, we're only officially supporting (i.e., testing against) Chrome for ddc/debugging.  We plan to expand that eventually.
@terrylucas
I suspect the problem is here:
https://github.com/dart-lang/sdk/blob/master/tools/dom/templates/html/impl/impl_Navigator.darttemplate#L18
We're tagging the object/prototype as a GamepadList, but that type is probably Chrome only.  I bet it's just a regular JS Array in FF / Edge.

Using getGamepads() on chrome, I get a RangeError: Maximum call stack size exceeded with a large stack trace including:
    at dart.NullableType.new.as (http://localhost:54953/dart_sdk.js:6935:39)
    at FixedSizeListIterator.new.get current [as current] (http://localhost:54953/dart_sdk.js:111922:18)
    at JsIterator.next (http://localhost:54953/dart_sdk.js:6898:52)
    at Object._isInterfaceSubtype (http://localhost:54953/dart_sdk.js:6418:16)
    at Object._isSubtype (http://localhost:54953/dart_sdk.js:6309:16)
    at Object.isSubtypeOf (http://localhost:54953/dart_sdk.js:6214:29)
    at Object.instanceOf [as is] (http://localhost:54953/dart_sdk.js:5343:17)
    at Function.is_C [as is] (http://localhost:54953/dart_sdk.js:4970:51)
    at dart.NullableType.new.as (http://localhost:54953/dart_sdk.js:6935:39)
    at FixedSizeListIterator.new.get current [as current] (http://localhost:54953/dart_sdk.js:111922:18)
    at JsIterator.next (http://localhost:54953/dart_sdk.js:6898:52)
    at Object._isInterfaceSubtype (http://localhost:54953/dart_sdk.js:6418:16)
    at Object._isSubtype (http://localhost:54953/dart_sdk.js:6309:16)
    at Object.isSubtypeOf (http://localhost:54953/dart_sdk.js:6214:29)
    at Object.instanceOf [as is] (http://localhost:54953/dart_sdk.js:5343:17)

I got Expected a value of type 'Gamepad?', but got one of type 'Type' error in Chrome Version 116.0.5845.179 (Official Build) (64-bit) too...

As this works with package:web which is already beyond 1.0 and a replacement for dart:html I don't think this issue matters anymore, so I'm closing it.


p006 swift

a quick conversion of python p006 file

fyi this pr would be considerably shorter if my p005 was already in master

I'm still going through PRs and trying to solve them.
What I see here is that you are trying to commit multiple files, so I want to ask you to merge these files and keep it in a single file per video part - the same way as we are going in the book. I understand that some parts of the code are going to be duplicated and that's ok - this solves multiple problems. I hope that you understand :)
Thank you.
PS. If p.5 is made the same way, I'm going to leave a similar message there as well.

I think you will understand my intent when you look at #5. I am using a separate file, but just like the python code does.

The reason why we are using NNFS package, which is a package that you can just "pip install" and import is because of the book - we did not intend to explain how we are making these datasets, also this package does more than holds the dataset - ensures results repeatability and contains some tool for the book.
With this repository our goal is to keep whole lesson in a single file as well - of something cannot be imported, like NumPy, because it's not a well-known package from the repository (again NNFS does not count as it serves multiple purposes), it should be contained within the script itself. This way we can ensure backward compatibility (what if you change something and it breaks something in older lessons?), we avoid confusion (what to download to run the code), we don't have to worry if you stop committing to the repository and someone else takes it over, etc. There are a few more reasons, but to make it easy for us to maintain and for people to use, we agreed to the format that I asked you about. I understand why you split the code into separate files, I would normally do the same, but this repository needs to follow some rules.
Does this make sense?

Thank you!


Merge changes from Main into V2

This is a cherry pick of https://github.com/splunk/syntheticsclient/pull/15
Specifically to get that commit from main which needs to be in v2 for release.
v2 is now set as the default branch for this repo also.

Before the change?

cherry pick commit accidentally merged to main instead of v2

After the change?

adds behavior for lastrunat and lastrunstatus

Pull request checklist

[x] Acceptance Tests have been updated, run (make testacc), and pasted in this PR (for bug fixes / features)
[ ] Docs have been reviewed and added / updated if needed (for bug fixes / features)

Acceptance Test Output

Does this introduce a breaking change?

[ ] Yes
[x] No

@bchhay-splunk please check out this PR cherrypicking your commit for the lastRunAt and lastRunStatus properties.
Looks like just your changes but would love to have you give this PR a once over. 😄

This LGTM! Thanks for doing this.


AP evaluation

I think I did answer this. While you think it uses the same threshold 0.7, it actually does not, see thresholds here:
https://github.com/open-mmlab/OpenPCDet/blob/0642cf06d0fd84f50cc4c6c01ea28edbc72ea810/pcdet/datasets/kitti/kitti_object_eval_python/eval.py#L639
The "Car<EMAIL_ADDRESS>0.70, 0.70:" and "Car<EMAIL_ADDRESS>0.50, 0.50" lines do not apply to the 3d AP lines. It is confusing indeed.
I was tracking this issue since I realized they are not the same. But could you find what is the thresholds for car pedestrian and cyclist for 3d bb correctly?
Originally posted by @paland3 in https://github.com/open-mmlab/OpenPCDet/issues/432#issuecomment-894068655

Okey I tracked the issue and the following line calls eval_class for 3D bounding box metric.
https://github.com/open-mmlab/OpenPCDet/blob/0642cf06d0fd84f50cc4c6c01ea28edbc72ea810/pcdet/datasets/kitti/kitti_object_eval_python/eval.py#L612-L614
So if we just put the following if condition inside of eval_class function it gives us the thresholds used for 3D bounding boxes
for k, min_overlap in enumerate(min_overlaps[:, metric, m]):
if metric == 2:
print(current_class, min_overlap, difficulty)
The output of this print call is as following:

and it means
<EMAIL_ADDRESS>0.70 0.70
@0.50 0.50 0.50
Pedestrian @0.50 0.50 0.50
@0.25 0.25 0.25
Cyclist @0.50 0.50 0.50
@0.25 0.25 0.25
instead of the titles we have in log file for 2D bounding boxes
(
<EMAIL_ADDRESS>0.70 0.70
@0.70, 0.50, 0.50"
Pedestrian @0.50 0.50 0.50
@0.50 0.25 0.25
Cyclist @0.50 0.50 0.50
@0.50 0.25 0.25
)


Remove use of define_method

Hey @booch! Just saw your RailsConf talk and loved it, nice work!
I noticed the project uses define_method in a few places. Obviously that's a perfectly valid approach, but I think what it's trying to do can be accomplished without creating a closure. By and large, methods defined in the "normal" way are faster to invoke than ones created with define_method. What do you think?

Ooh, that looks interesting. I'll take a look at it ASAP.


ISPN-9538 Allow for segmentation to be configurable via Features

https://issues.jboss.org/browse/ISPN-9538

Yes, data-segmentation sounds good
On Thu, Sep 27, 2018 at 2:50 PM William Burns<EMAIL_ADDRESS>wrote:

@wburns commented on this pull request.
In core/src/main/java/org/infinispan/factories/DataContainerFactory.java
https://github.com/infinispan/infinispan/pull/6274#discussion_r220909408
:

@@ -34,6 +34,8 @@
public class DataContainerFactory extends AbstractNamedCacheComponentFactory implements
AutoInstantiableFactory {

private static final String SEGMENT_CONTAINER_FEATURE = "segmented-container";

Alright, thanks for the clarification. What do you think we want the
feature name to be then? Maybe data-segmentation? We can't really use
data container anymore.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/infinispan/infinispan/pull/6274#discussion_r220909408,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAX9Hm_M3hVERxK53La1upfxPmnx6rQzks5ufMmPgaJpZM4W5VMo
.

Added check in PersistenceManagerImpl class to throw exception if feature is disabled yet a segmented store is configured.

@wburns I added a unit test to cover unitary and test the features. let's see if CI works


Single line install script installs old version (0.12.3)

Please verify that this bug has NOT been raised before.

[X] I checked and didn't find a similar issue

Describe the bug*
Hi All,
I have installed Inventree this week but have noticed that the install script (and thus the apt repository) both point to 0.12.3. Im wondering if this is intended or if this has been missed in the latest releases.
Otherwise everything is great, really enjoying it and looking forward to getting into the API to integrate with our other processes. Great work guys!
Cheers
Tim
Steps to Reproduce

Install via single line installer
Notice version is 0.12.3 and UI says update available
Attempt to update via Apt
Cry

Expected behaviour
Expect the latest stable via Apt
Deployment Method

[ ] Docker
[ ] Bare metal

Version Information
0.12.3
Please verify if you can reproduce this bug on the demo site.

[ ] I can reproduce this bug on the demo site.

Relevant log output
No response

@timmyhadwen sorry for the delay, @matmair is the go-to on the installer and he's currently away. Have you had any further luck with this?

@timmyhadwen the latest available version of the stable package is 0.12.3 currently

Our stable CI seems to be breaking; I need to investigate that

Something happened with our docker builds too - 0.12.4 is missing from docker hub.
@matmair do you know if the packager is up and running again?

@SchrodingersGat it did not trigger, I had to do it by hand - 0.12.7 is released now.

Should work now again

Thanks heaps :) Working great now!


Why does the sum of probabilities returned exceed 100%?

In the Quick Test example of the picture of the dog, the probabilities returned are dog: 90.3%, pony: 15.9%.  Why don't the probabilities add up to 100%?  In some of my testing with two labels, I get back results like label1: 95%, label2: 95% - how is this possible?
Thanks,
Sohrab

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e898e972-43eb-601b-fc5c-1b0199315473
Version Independent ID: e8504165-4688-e91b-1ee3-3da10560e583
Content: Test and Retrain Your Model
Content Source: articles/cognitive-services/Custom-Vision-Service/test-your-model.md
Service: cognitive-services
GitHub Login: @anrothMSFT
Microsoft Alias: anroth

@scrampy Thanks for the feedback! We are currently investigating and will update you shortly.

@scrampy Hi, this is a mathmatical issue. Because the propabilities are represented the similarity between the sample photo and target photo, so the number you got for every target is not relative. You can use the data to judge which one is more similar. Thanks.

Hey @scrampy - wanted to provide some context here. Custom Vision Service currently by default builds "multilabel" classifiers. So there isn't a strict assumption that your photo being predicted contains either a dog OR a pony- instead the classifier returns the probability that your image contains a dog, and the probability that it contains a pony. This is nice property if you have photos that might contain both dogs and ponies!
If you are interested to lean more about "multiclass" vs "multilabel" classifiers and the techniques used to train each, there is some interesting content on the web about this. :)

@anrothMSFT Thank you for your explanation!
@scrampy We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Property with private or internal setter are not mapped

Describe the bug
Pubic property with private setter are not mapped even with IncludedMembers = MemberVisibility.All applied
Declaration code
https://dotnetfiddle.net/E4iGqY - reproduction
using System;
using Riok.Mapperly.Abstractions;

public class User(string emailAddress)
{
	public string EmailAddress { get; private set; } = emailAddress;
}

public record UserUpdateDto(string EmailAddress);

[Mapper(IncludedMembers = MemberVisibility.All)]
public static partial class UserMapper
{
	static partial void ApplyTo(this UserUpdateDto input, User user);

	public static void ApplyUpdates(this UserUpdateDto input, User user)
	{
		UserMapper.ApplyTo(input, user);
	}
}

public class Program
{
	public static void Main()
	{
		var user = new User("user@gmail.com");
		var updates = new UserUpdateDto("new-user@gmail.com");

		updates.ApplyUpdates(user);

		Console.WriteLine(user.EmailAddress); // still shows<EMAIL_ADDRESS>	}
}

Environment (please complete the following information):

Mapperly Version: 3.6.0
Nullable reference types: enabled
.NET Version: .NET 8.0
Target Framework: .NET 8.0
Compiler Version: 8.0

I cannot reproduce this locally and I'm not sure if .NET fiddle runs source generators correctly.
The following works as expected for me:
# in a new empty directory
dotnet new console
dotnet add package Riok.Mapperly -v 3.6.0
# replace content of Program.cs with provided content
dotnet run
# prints<EMAIL_ADDRESS>as expected...

Do these steps work for you? Can you reproduce the issue in Rider? in VS Code? in VS? on the terminal?

I cannot reproduce this locally and I'm not sure if .NET fiddle runs source generators correctly. The following works as expected for me:
# in a new empty directory
dotnet new console
dotnet add package Riok.Mapperly -v 3.6.0
# replace content of Program.cs with provided content
dotnet run
# prints<EMAIL_ADDRESS>as expected...

Do these steps work for you? Can you reproduce the issue in Rider? in VS Code? in VS? on the terminal?

Can confirm this worked, however the minimal reproduction is not complete, my bad. Here is a better one.
I experienced it when the object mapped is in a different project.
The generated code in Rider is:
// <auto-generated />
#nullable enable
public static partial class UserMapper
{
    [global::System.CodeDom.Compiler.GeneratedCode("Riok.Mapperly", "<IP_ADDRESS>")]
    static partial void ApplyTo(this global::UserUpdateDto input, global::User user)
    {
        user.SetEmailAddress(input.EmailAddress);
    }
}

[global::System.CodeDom.Compiler.GeneratedCode("Riok.Mapperly", "<IP_ADDRESS>")]
static file class UnsafeAccessor
{
    [global::System.CodeDom.Compiler.GeneratedCode("Riok.Mapperly", "<IP_ADDRESS>")]
    [global::System.Runtime.CompilerServices.UnsafeAccessor(global::System.Runtime.CompilerServices.UnsafeAccessorKind.Method, Name = "set_EmailAddress")]
    public static extern void SetEmailAddress(this global::User target, string value);
}

The generated code seems correct and is the exact same as when the class is contained in the same project. However, when running it, the changes are not applied.

Thanks for the update. It seems that PropertySymbol.IsReadOnly is true and Symbol.SetMethod is null. As soon as I find the time I'll investigate further why exactly this is the case (probably private members are just not visible to other compilation units?).

Pretty sure public string EmailAddress { get; private set; } = emailAddress; gets normalized from the compiler to:
private string <EmailAddress>k__BackingField;
public string EmailAddress => <EmailAddress>k__BackingField;

We may need to access the backing field directly in this case, instead of going through the setter...

Hello, any updates on this?

@7amou3 nope, feel free to contribute 😉


Mandelbrot.Canvas: Added tabular layout and viewport parameters + Demo: Computer algebra system

Added a tabular layout instead of the top-down layout the project had. Seperated labels from controls. Added helper functions to facilitate the construction of tables and added viewport parameters (complex plain bounds) instead of hardcoding them

New demo! a minimalistic computer algebra system (CAS) written in C#.
Demo: Here!
This demo consists of three main parts:

The expression language used for algebraic manipulations
A plotter to plot single variable (i.e. Func<double, double>) functions
A parser, which a partial port of Sprache, a monadic parser written in C#.

This example is only a demo to show what is possible. Alot of this code is work-in-progress and alot of functions are not supported for differentiation nor evaluation, for example: inverse and hyperbolic trigonometric functions.
For the parser I just copy-pasted from their repo and hoped it would work, it didn't :( as Bridge translator had a couple of problems with:

translating the docs (I disabled that from bridge.json)
translating generic anonymous types (I put [IgnoreGeneric] everywhere until it worked)

Putting all code in Live Bridge did not work as I could not disable translation of docs that were causing problems!

Hi @Zaid-Ajaj,
That is super cool and very impressive! Thank you!
We merged your PR. The new demo is accessible here also.


Link to weights is dead.

Hi @kuldeepbishnoi,
Thank you for such amazing work. I'm highly interested in implementing it, however the link to your weights is dead.
Would you please update it for us?
Regards.

Hello @kuldeepbishnoi ,
WE STILL WANT THE WEIGHTS SO CAN YOU PLEASE DO FOR US


cannot find -lcuda

Successfully install it but got this error when running the model.

You should use triton 2.1.0.

@tridao thanks for the prompt reply. upgraded triton to 2.1 but the error still persists.

You'll also need to run ldconfig before running the script so that it cna find cuda.so.

@tridao Still not able to get it work. I did the following step by step:

run ldconfig
install package from source python3 setup.py install

the error is same as above.

I run ldconfig before running the triton code. This is more of a triton issue. I'm not sure what else to fix.

I run ldconfig before running the triton code. This is more of a triton issue. I'm not sure what else to fix.

You can try:

Adding the following content to the .bashrc file:

export LIBRARY_PATH="/usr/local/cuda/lib64/stubs:$LIBRARY_PATH"

Sourcing the .bashrc file.

source .bashrc


Drop Block

Paper
Implement Drop Block proposed DropBlock: A regularization method for convolutional networks
TODOs

[x] develop the model in a scalable way (using *Block syntax and nn modules)
[x] draw the model on figma
[x] write doc
[x] test the model

Close by #199

Close by #199


Programmatically change routes

How do I change the route programmatically? I tried history.pushState - it changes the URL but doesn't load the view, meaning the app state never changes.
This one, pushPath('/about') (from redux-simple-router) doesn't do anything at all. Link on the other hand works great. Not sure if there is something specific needs to happen inside view or component in order to change the route. Thanks!

Interesting, that's definitely broken... might have to see if it's a bug with redux-simple-router? I'll look around when I get a chance.

Just as an example, I changed the increment button to:
<button className='btn btn-default'
  onClick={() => this.props.history.pushState(null, '/about')}>
  Increment
</button>

And it worked as expected. Further experimentation hasn't yielded any issues. Could you post a small code snippet that reproduces the problem?

Sure, below example is for sign in but I tried that for simple clicks as well. In my case I have to do some logic in handleSubmit before redirecting user to correct route. Thanks for your help!
import { createHistory } from 'history'
let history = createHistory()

handleSubmit (e) {
  if(login.auth) {
     history.pushState(null, '/about')
 }
}

<form className='login' onSubmit={this.handleSubmit.bind(this)}>
...
</form>

I don't think that will work because it's a new history instance. You'll want to use the history that's passed by react-router into your component's props (any component that lives at a route receives a history prop). Can you try doing this using this.props.history and see if it works?

Yes, that worked!!! thank you very much. All I needed was this.props, like this
static propTypes = {
    history: React.PropTypes.object
}

handleSubmit (e) {
  if(login.auth) {
     this.props.history.pushState(null, '/about')
 }
}

Cool, glad that fixed it!


Fix record validation in SeekableStreamIndexTaskRunner

Fix https://github.com/apache/incubator-druid/issues/7239.
In verifyInitialRecordAndSkipExclusivePartition(), currOffset is now used to verify the record offset. I also fixed a bug which uses the default compareTo method of SequenceOffsetType.  OrderedSequenceNumber should be used instead. I also changed SequenceOffsetType to not extend Comparable to prevent this problem in the future.

Oops, I noticed that the unit test for kinesis indexing is missing. I'll add it.


Add Icarus Verilog

Tool information

Tool name: Icarus Verilog
Add or update? Add
Desired version: latest
Approximate size: 6.5MB installed
If this is an add request:

Brief description of tool: Verilog Simulator
URL for tool's homepage: http://iverilog.icarus.com/

Virtual environments affected

[ ] macOS 10.15
[x] Ubuntu 16.04 LTS
[x] Ubuntu 18.04 LTS
[ ] Windows Server 2016 R2
[ ] Windows Server 2019

Can this tool be installed during the build?
Yes, tool can be installed using "apt install iverilog", install should take < 10 seconds

Thanks for the suggestion! Since this can be installed during the build and doesn't need to be pre-installed, we'd like to see more demand for this enhancement before adding it.


Implement ability to use custom renderers for attachments

Description
Implement ability to use custom renderers for attachments
Use case/motivation
No response
Related issues
No response
Confidential information

[X] I confirm that do not share any confidential information

No manual testing is possible now.


fix(capitalization): Capitalizing a button.

SUMMARY
Capitalizing the + Alert and + Report buttons.
Before:

After:

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

/testenv up

@yousoph asked for an env to test the capitalization

@rusackas I think @mistercrunch's test env command didn't work, can you try to do it? 🙏🏻

Hah, I merged it too quickly, sorry... not sure why ephemerals aren't working. I did test it though, as seen in the screenshots.
There is one remaining inconsistency, but it seemed relatively minor. It asks in one modal "Delete Alert?" or "Delete Report?" now. I can just make it so that these strings aren't reused variables, and just put them in the correct capitalization in the places they go.

Ha, it's on you now @rusackas 🤠

Maybe we're OK, depending on how our capitalization lawyers interpret this:

Where a product page is titled “Settings”, you refer to this in writing as follows: “Edit your personal information on the Settings page”.