[CP stag]Skip rendering IOU pay action for non-send money flow if the user needs to enable wallet or add bank account

Details

Follow up to https://github.com/Expensify/App/pull/30079 coming from https://expensify.slack.com/archives/C07J32337/p1697844844307529?thread_ts=1697843073.603539&cid=C07J32337
For money request flow we create two IOU actions on the iou report. One is of type create and the other of type pay. So let's see how these actions are rendered on the frontend if the payee is on silver wallet(aka we add the isWaitingOnBankAccount status to the iou report).

IOU create action -> We use this to render a preview.
ReimbursementQueued action -> To show a system message that the payee needs to enable the wallet and show the enable wallet button.
IOU pay action -> This doesn't fall in any if block under the ReportActionItem component as a result else block gets executed for this and we render another system message asking user to add their bank account as that is the default message if the report has isWaitingOnBankAccount property set.

So we now have two system messages so I have updated the code to prevent rendering any content if the IOU action type is pay and it is not a send money flow and if the user needs to add their wallet or bank account.
Fixed Issues

$ https://github.com/Expensify/App/issues/30075
PROPOSAL:
Tests

Create userA and by default they will be on silver wallet.
Create another userB and add them to gold wallet by completing the kyc.
As userA request money from userB.
As userB, pay the money request.
As userA and userB, confirm we only see a single system message stating user needs to enable their wallet. And a button to enable the wallet.

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

Same as test steps.

[ ] Verify that no errors appear in the JS console

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 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] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[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(themeColors.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 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 author checklist, including those that don't apply to this PR.

Screenshots/Videos

MacOS: Chrome / Safari

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Desktop

Fixing the conflicts and testing the changes.

I am seeing something weird. For some reason props.IOUReportID is an empty object.

We seem to be loading the iouReport here: https://github.com/Expensify/App/blob/fcee2073f096ad60dd9f30c536342de7d3893282/src/pages/home/report/ReportActionItem.js#L728 but we are using the property originalMessage.linkedReportID but it looks like the iouReportID info is actually on originalMessage.IOUReportID key.

This is ready for a review. @situchan @mountiny

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
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] 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(themeColors.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 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

Web
https://github.com/Expensify/App/assets/108292595/81d1093c-10ca-412b-8fa9-2f9ffde58b5c
https://github.com/Expensify/App/assets/108292595/46e5fac1-da18-4a8e-bc03-bafbe0060f95

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

@mountiny Can you do the final review for this? We will need to CP this.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Cherry-picked to staging by https://github.com/mountiny in version: 1.3.89-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

@mountiny we have silver wallet only. Is this internal QA?

Yes

🚀 Deployed to production by https://github.com/marcaaron in version: 1.3.89-6 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/marcaaron in version: 1.3.91-8 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Find a way to keep this consistent with IntervalArithmetic.jl

It could for example be a submodule of IntervalArithmetic.jl.
The tests could also be generated as an automatic build step in CI.
(from today call)

@lucaferranti


mplayer: 1.1.1 -> 1.3.0

Motivation for this change
https://lwn.net/Alerts/686424/
https://github.com/NixOS/nixpkgs/issues/18856
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] OS X
[ ] Linux

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

@grahamc Stupid question: is there a reason you didn't just commit it yourself? Looks good to me.

@7c6f434c As part of https://github.com/NixOS/nixpkgs/issues/18856 I've been putting in so many PRs I haven't been checking each individual one quite as closely as if I made a one-off change. I do test them a bit, but not as rigorously.
I also like to give maintainers a chance to check out the diff before it goes on in :) that's all
thanks for checking it out!


append query comment backport (#2138)

resolves #2138 but for 0.16.1
Description
This is just me rebasing #2199 onto dev/0.16.1 - I didn't really have to change anything beyond dropping a couple 0.17 commits and updating the changelog.
Checklist

[X] I have signed the CLA
[X] I have run this code in development and it appears to resolve the stated issue
[X] This PR includes tests, or tests are not required/relevant for this PR
[X] I have updated the CHANGELOG.md and added information about my change to the "dbt next" section.

merging before tests again - another CHANGELOG.md-only merge.


PowerShell SDK: out-of-process Runspace doesn't allow using proxy.

Steps to reproduce
PSSessionOption pSSessionOption = new PSSessionOption
{
pSSessionOption.ProxyAccessType = ProxyAccessType.WinHttpConfig;
}

Runspace runspace = RunspaceFactory.CreateOutOfProcessRunspace(TypeTable.LoadDefaultTypeFiles());
// Runspace runspace = RunspaceFactory.CreateRunspace();
PowerShell powerShell = PowerShell.Create();
powerShell.Runspace = runspace;
powerShell.Commands.AddCommand("Import-Module");
powerShell.Commands.AddParameter("Name", "ExchangeOnlineManagement");
powerShell.Commands.AddCommand("Connect-ExchangeOnline");
PSCredential psCredential = new PSCredential(user, password.ToSecureString());
powerShell.Commands.AddParameter("Credential", psCredential);
powerShell.Commands.AddParameter("PSSessionOption", pSSessionOption);
powerShell.Invoke();

Expected behavior
To connect to Exchange Online

Actual behavior
The module doesn't connect to the internet. If we use RunspaceFactory.CreateRunspace, it works.

Environment data
Name                           Value

PSVersion                      5.1.19041.1
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.19041.1
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

It doesn't work in other Operating systems too. Tried in different OSes.

@tonyoscarad The repository is only for PowerShell Core dev process.
To report Windows PowerShell issue you should use other resources like UserVoice site, MSFT forums and so on.
You could repro on PowerShell Core but Exchange Online module is still not supported on the version.


DKG Stats Bug Fixes and UI enhancements

Summary of changes

Updates DKG stats-dapp logo from webb logo to tangle logo.
Updates Footer component links.
Updates DKG stats-dapp background image.
Timeline component in key detail page now show all the 3 key status - Generated, Signed and Rotated.
Updates DKG stats-dapp tooltips.
Fixes inaccurate validator uptime and reputation display.

Proposed area of change

[ ] apps/bridge-dapp
[ ] apps/hubble-stats
[x] apps/stats-dapp
[ ] apps/webbsite
[ ] apps/faucet
[ ] apps/tangle-website
[x] libs/webb-ui-components

Reference issue to close (if applicable)

Closes #1596
Closes #1593 (By PR in webb-graphql)
Closes #1582
Closes #1581

Screen Recording
https://github.com/webb-tools/webb-dapp/assets/53374218/5db1cc22-27ad-42d0-9b69-7fdc367e00e6

Footer Component:

Discord link is invalid, requires update: https://discord.gg/xnDGzdjt
Jobs link to here: https://wellfound.com/company/webb-4
Remove Tangle under Network
Add Polkadot JS under Network: https://polkadot.js.org/apps/?rpc=wss://tangle-standalone-archive.webb.tools#/explorer

Tangle Identity

[ ] Update favicon to Tangle Logo: https://www.notion.so/hicommonwealth/Tangle-Logo-029bec068f1a4690a7defc92125be03d?pvs=4


Cairo context missing show_glyphs method

I noticed that the method named show_glyphs is missing from the cairo context. Its line in the lgi/override/cairo.lua file is commented.
The method hasn't yet been implemented or can't it be implemented for some specific reason?
Is there an other way one should draw glyphs instead in lgi?
I've been looking at http://zetcode.com/gfx/cairo/cairotext/ and https://github.com/SimonSapin/pycairo/blob/master/examples/cairo_snippets/snippets/show_glyphs.py

From a quick look through the supported functions, it seems like the problem here is to express "array whose length is passed in the next field" in the poor-man's-ffi used for lgi/override/cairo.lua, but I'm not quite sure. Sorry, that is all the information that I can provide on that.
On the two links that you provide: Both of them just use glyphs with consecutive numbers without querying the actual meaning of the glyph. Are you sure you need glyphs for what you are doing (whatever that is)? How do you mean with glyph index to use to e.g. display an "a"?

Is there an other way one should draw glyphs instead in lgi?

I'd suggest show_text, but I bet for some reason you don't like that suggestion...

I can't say that I need it at this moment because I was just going through some guides to learn Cairo a bit more.
I found out that it is missing so I reported it.


Fix body1/body2 for 2018 Material Design (#38904).

Description
In 2018, Material Design did a major update to its typography, renaming all of its styles as well as changing all of their default sizes and weights. One notable aspect of this change is that what used to be body1 is best mapped to what is now body2. While Flutter has decided to enshrine for all eternity the old naming scheme, it has provided new TextTheme variants for the 2018 styles. These were, correctly, documented to swap body1 and body2 (which is the same behavior that was used for React Native). However, while as far as I can tell (based on relative sizing), this was done correctly for the "dense" and "tall" variants, the swap was not done for the englishLike variant. Without this swap, the 2018 typography is incompatible with all of the existing code that is using body1 as the default size.
Of course, fixing this will, I would expect, break people who have added one-off adjustments to their font sizes in an attempt to work around this bug, but 1) it was documented correctly (so I would hope that if anything this helps people and fixes things that were slightly broken before), 2) the englishLike variant is the only one that is broken (so workarounds are going to either be crazy or incomplete), 3) workarounds likely would have just further broken existing code (as the existing code would be assuming body1 is the default), and 4) because Flutter has decided to maintain the 2014 styles as the default--despite now being almost two years out of date--it is unlikely that many people even ever discovered that to get the correct/modern sizes they would need to switch to this broken TypeTheme anyway: so, really, anything that would make this path more usable seems like a positive thing to get done ASAP.
Related Issues
Months ago, someone reported this issue as #38904.
Tests
Any test for this would just be a second copy of the same table verifying the data from the first copy, which would be pointless. FWIW, I did run the existing test suites in packages/flutter and examples/flutter_gallery and none of them noticed.
Checklist

[X] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[X] I signed the [CLA].
[X] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[X] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[X] I updated/added relevant documentation (doc comments with ///).
[X] All existing and new tests are passing.
[X] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[X] I am willing to follow-up on review comments in a timely manner.

Breaking Change

[X] No, no existing tests failed, so this is "not a breaking change".

Even though no tests failed, this is probably a breaking change as existing apps will look a bit different after this is merged

@Zazo032 Hence the quotation marks I added around "not a breaking a change" from the template (which seemed to consider that statement to be an implication) ;P. The issue is that this is a bug which makes this mechanism useless, and as I mentioned it seems like no one is really trying to use it (as it is so i obvious that you need to do this... using the 2018 sizes should probably be part of the new project template to ensure anyone actually notices it has to be done)... if nothing else so few people have noticed this bug. Leaving this broken just makes this entire thing even less usable.

We're planning to update the TextTheme's text style names per the current Material spec: https://github.com/flutter/flutter/pull/45745.
I'm going to close this PR, as the project is already being actively worked on. Thanks for you contribution and for the passionate write-up!

@HansMuller I just reviewed the patch and discussion in #45745, and I am concerned that the names are being fixed but the table is not; like; if you want to correctly get Material 2018 using Hixie's patch (which does correctly flip the names) you also separately need to commit my patch (to make the table put the correct font sizes to the correct entries). Are you sure this isn't going to be forgotten when the table's names are updated?

@saurik is right, the numbers in this table are wrong irrespective of #45745.

We should add a test before landing this, though.

@saurik per https://github.com/flutter/flutter/pull/47918#issuecomment-570891311
I'll attempt to update the font size and letter spacing for bodyText1 and bodyText2 (aka body1 and body2) per this PR and  #38904, after #48547 lands.

We haven't  pursued this change yet because it will break existing layouts and golden image tests.

I'm going to close this in favor of https://github.com/flutter/flutter/pull/49756 - which makes the very same change. To my surprise, these changes did not break existing tests (at least not as far as I've been able to tell). I will try and land them now.


Allow parent resources to be redeployed while leaving their child resources alone

Is your feature request related to a problem? Please describe.
Whenever I redeploy a VNET using Azure Bicep, it will clear out all subnets in the VNET that are not explicitly listed in the VNET resource definition. This prevents me from partitioning my resource definitions into logical groups that can be separately deployed (and redeployed), which is a common strategy with infrastructure as code approaches. (For reference, see, e.g.,  the "stack" patterns from the "Infrastructure as Code" book by Kief Morris.)
There is a similar situation with AKS cluster deployments, which require details about all node pools.
This has also been discussed in https://github.com/Azure/bicep/issues/4023#issuecomment-995697660, but I'm creating a new issue because #4023 originally came from a different angle.
I also want to mention #5806 (which I created), which is also from a slightly different perspective, but might show there are different issues that all relate to the higher goal of being able to partition infrastructure definitions into smaller units.
Describe the solution you'd like
I would like to have a way to define a resource in such a way that the Azure Resource Manager will either leave existing child resources alone, if any, or merge them with what I have declared.
In https://github.com/Azure/bicep/issues/4023#issuecomment-1024456195, an upsert modifier was mentioned, this would work well.
An alternative would be a merge keyword as mentioned in #5806.

In general, you can deploy parent resources without affecting child resources (i.e. sql servers & databases). The reason this happens for VNETs is because subnets were originally modelled as a property on the vnet resource, then later they added the ability to deploy subnets as a child resource, so when you redeploy a vnet, the networking RP think you are asking for an empty vnet since the subnets property is empty. It's a long standing issue with a long discussion here: https://github.com/Azure/azure-quickstart-templates/issues/2786
I'm not as familiar with the AKS node pools example, do you have a full code sample?

@alex-frankel Thank you for pointing me to that existing issue on VNETs. So this is actually a problem in the specific resource provider rather than a general design issue.
I wonder if Bicep/ARM could and should still provide a mechanism to work around the issue? Apparently, the VNET problem is not going to be fixed (assuming the team responsible is aware of the issue). In addition, the workaround might provide additonal benefits, e.g., also support #5806 and similar.

I'm not as familiar with the AKS node pools example, do you have a full code sample?

I've actually only run into the VNET problem myself (and #5806, which, however, is not a child resource). The AKS issue is detailed in https://github.com/Azure/bicep/issues/4023#issuecomment-1019489479 .

To follow up on this: We've since encountered this problem also on Load Balancers (frontend IP configurations), NSGs (rules), and Storage Accounts (virtual network rules). We always need to fall back to scripting for those resources 🙁  .


GitHub action to rebuild website MD files upon pushes

Need a GitHub action for this repo which:

Detects commits to kyverno/policies
Runs the render program on kyverno/website
Generates the new Markdown files
Pushes those to kyverno/website in /content/en/policies (should wipe contents first!)

Need to handle other files in /content/en/policies to account for tests and kustomize manifests.

In order to do this without resorting to lengthy scripting hacks, need https://github.com/kyverno/website/issues/59

Lots of problems with this. Will potentially reevaluate later.


Question regarding OS compatibility in docker documentation

Hello,
first thank you for the project. We are just starting to try it out and it works amazingly well.
We have one clarifying question regarding the docker documentation. In the first paragraph is a warning regarding running different OS in the container and the host.
Does this apply to the sidecar scenario only or does it also apply to running litestream in the same docker container as our own application?
From the placement in the docs it looks like it applies to everything. From our understanding of the underlying technology it should only apply to the sidecar scenario.
Which one is correct?
Thank you

It applies to all scenarios where Litestream and the SQLite database could be accessed across operating system boundaries.
Usually on Docker you'd run both the application and Litestream as containers so they would likely be running on the same operating system withing that the container runtime.
So if the application runs on Linux, Litestream must also run on Linux. If application runs on macOS, Litestream must also run on macOS.

Hello,
thanks for the quick response and explanation.
So, just to reiterate, if we run litestream in the same docker container as our app and we only have one instance of the container running at the same time and have the sqlite db local in the container somewhere we are fine?!
Thanks :)

Yes, that should be perfectly fine. You could also consider using litestream exec to run both in the same container where Litestream will start your application as a sub-process so Litestream can always start first and exit last.

Yep, this is what we are using.
Thank you very much for the quick help!


Allow sorting on spot instance pricing

It would be great if on the web page for a particular machine type there was an option to sort by spot instance price (this sort order is often suprisingly different!).

Hi,
Good idea. I have added a few more sorting options.
Depending on the caching you should see it in the next hours.

For your analysis, however, I recommend the Instance Picker:
https://gcloud-compute.com/grid.html
BR Nils

This is just what I wanted, thank you!


Fix Ambiguity When Using Names and --IDS

Fixes #793 and fixes issue seen in PR #1426.
Previously, the logic of the IDs parameter would have unpredictable and ambiguous results if you supplied --ids along with --foo-name. In PR #1426, the team wishes to have a default value for one of the name parameters, which means that name component will always have a value even if --ids is used. In that case, it caused a crash.
This PR checks for an existing value and explicitly overwrites it if exists, logging a warning. Absent some mechanism to know whether a parameter was populated by the user or a default value (technically there is one but it's so ugly so as not to recommend anyone do it) this is reasonable compromise.

@derekbekoe, cc/ @xscript since this pertains to #1426.


Manifest is trying to analyze vim's swap files

I use vim, which produces files like /.foo.js.swp, but this causes webpack to emit errors like:
ERROR in ./client/.entry.js.swp
15:21:45 dev.1      | Module parse failed: /tmp/client/.entry.js.swp Line 1: Unexpected number
15:21:45 dev.1      | You may need an appropriate loader to handle this file type.
15:21:45 dev.1      | (Source code omitted for this binary file)

From what I understand, this is coming from the walkAndPrefetchAssets, where it doesn't use the common pattern of optionally including or excluding files based off of a regex. That would let me filter out the .swp files, or just explicitly consider the files I would want included. Could this be supported?

Sounds like it would be beneficial to add new options for both including and excluding specific files that supports regex matching. Right now you can optionally ignore paths but not files.
Would you be willing to open a PR on this?

Any progress on this? I'd be down to tackle as a PR if nobody else has yet.

@jpassaro A patch was merged in a few months ago that added the ability to filter asset types through a regex in PR #19.
It's in the docs https://github.com/nickjj/manifest-revision-webpack-plugin#api and available since v0.3.


api/ui: show peak/total samples in analyze

Show the new peak/total fields in analyze output next to each operator. Add tooltips to explain what is the meaning of each field.

cc @saswatamcode @fpetkovski

Nice work


Unable to query z3 solver : exec format error

Hi, I got an Exec format error when trying to invoke souper to extract SMT queries from a bitcode file.
~/Documents/souper_build/souper -z3-path=~/Documents/souper/third_party/z3-install/bin/z3 test.bc
; Listing valid replacements.
; Using solver: Z3 + internal cache
Unable to query solver: Exec format error
Exec format error often come from architecture differences:
file souper
souper: ELF 64-bit LSB pie executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=e4e891f60e489712eb3b9126b4d1d1aa47962a8c, for GNU/Linux 3.2.0, with debug_info, not stripped
file z3
z3: ELF 64-bit LSB pie executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=11deeea9161aa4e829d91e422bde3ad961fe5cd1, for GNU/Linux 3.2.0, not stripped
I used the souper clang executable to generate the test.bc file.
file clang-11
clang-11: ELF 64-bit LSB pie executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=181289344bcef8c2f4846a711a7e901a9ec87487, for GNU/Linux 3.2.0, not stripped
uname -m
x86_64
everything seems correct to me, that's why I don't understand the error message.
Thanks in advance.

What's the output of

~/Documents/souper/third_party/z3-install/bin/z3 -version
Z3 version 4.8.8 - 64 bit

ok, put the full path in the SOUPER_SOLVER environment variable, instead of putting a shell expansion in there

~/Documents/souper_build/souper -z3-path=/home/foo/Documents/souper/third_party/z3-install/bin/z3 test.bc' '; Listing valid replacements.' '; Using solver: Z3 + internal cache
ok seems to be better, I got no exec format error anymore


Changing Gateway.Class to Gateway.GatewayClassName

This matches the corresponding naming on Ingress and PersistentVolume resources.

/lgtm

/approve


Does not detect class extend from module without file extension

This does not work:
import DataSource from './DataSource';

class ArrayDataSource extends DataSource {}

It does not detect that ArrayDataSource extends from DataSource. The documentation lists it as "src/ArrayDataSource.js~DataSource".
If I include the file extension of DataSource.js it works.
import DataSource from './DataSource.js';

class ArrayDataSource extends DataSource {}

I think both imports should work the same way, as they do in Node, Browserify, etc. Perhaps use require.resolve internally to resolve the filename of imports?

@devongovett Hi! Thanks for this issue.
I will support non-extension file at next version.

I support this issue at ESDoc v0.4.4


feat: update pool details

#963 needs to be merged first

add beets support for pool details

keep remote branch for now


PM To: typeahead should use message view context

At present, when composing a PM, the @-mention typeahead ordering takes into account the stream that the user is viewing, but the To: typeahead does not.
There isn't a good reason for this discrepancy. We should change the To: typeahead to take the stream the user is viewing (if there is one) into account as well, same as an @-mention.
CZO discussion thread

@zulipbot claim

@zulipbot claim

A few technical notes:

static/js/recent_senders.js is an adjacent data module; reading the compose typeahead code for how that module is used should help one figure out how the existing logic for mentions works.

@zulipbot claim

@timabbott thanks! I fixed the bug in the UI, but it broke the initialize test of composebox_typeahead due to this.$element not existing. So I need to figure out what happened there, and then add my own test. Is this.$element a Bootstrap thing?

Can you post a draft pull request? That'll make it easier to discuss the test issue.

Still working on this, trying to figure out how to add the correct narrow in tests


Fix for cases when the .NET streams are not contiguous due to alignment.

@snemes would you test these samples to see if you have the same issues? Some month ago I got a similar request from other user and I think it could be related.
https://drive.google.com/file/d/0B4D2y-ZnUx80RklyWFAwWGhJSUU/view?usp=sharing
Be careful, those are malware samples too. pwd is "infected".

@poxyran The file "njserver" is okay, but "predServer" exhibits exactly the same problem I had (and it is also fixed by this commit).

@snemes Thanks for the fix and the tests!. If you find any other bug just let me know!. Btw, if you have any idea for new features/improvements do not hesitate to contact me!.


Inner clone puts nested submodules in unexpected locations

Describe the Bug
I attempted to introduce xunit to source-build-externals. It has a submodule, and SBE uses submodules. When building under source build, the inner clone appears to place the inner submodule as a peer directory to the main xunit submodule.
Steps to Reproduce

Clone https://github.com/mmitche/source-build-externals/tree/add-xunit-bug
Source build.

    CSC : error CS2001: Source file '/home/mmitche/source-build-externals/artifacts/source-build/self/src/src/xunit/src/xunit.core/../xunit.assert/Asserts/Sdk/AssertEqualityComparer.cs' could not be found. [/home/mmitche/source-build-externals/artifacts/source-build/self/src/src/xunit/src/xunit.core/xunit.core.csproj]
    CSC : error CS2001: Source file '/home/mmitche/source-build-externals/artifacts/source-build/self/src/src/xunit/src/xunit.core/../xunit.assert/Asserts/Sdk/AssertEqualityComparerAdapter.cs' could not be found. [/home/mmitche/source-build-externals/artifacts/source-build/self/src/src/xunit/src/xunit.core/xunit.core.csproj]
    CSC : error CS2001: Source file '/home/mmitche/source-build-externals/artifacts/source-build/self/src/src/xunit/src/xunit.core/../xunit.assert/Asserts/Sdk/ArgumentFormatter.cs' could not be found. [/home/mmitche/source-build-externals/artifacts/source-build/self/src/src/xunit/src/xunit.core/xunit.core.csproj]

Expected location:
/home/mmitche/source-build-externals/artifacts/source-build/self/src/src/xunit/src/xunit.assert/Asserts/Sdk/ArgumentFormatter.cs
Actual location:
/home/mmitche/source-build-externals/artifacts/source-build/self/src/src/xunit.assert/Asserts/Sdk/ArgumentFormatter.cs

@mmitche can this be closed now that https://github.com/dotnet/arcade/pull/13819 was merged?


Hide "Star Gitfy on Github" if project has already been starred

Hide "Star Gitfy on Github" if project has already been starred.

@ekonstantinidis please

Ready for next release! 🎉 🎉 🎉
Gitify checks if the user has starred the repo when the app launches and hides the message conditionally.


InvalidCastException in  Xamarin.RangeSlider.RangeSliderControl.OnRestoreInstanceState

Unable to duplicate but have seen InvalidCastException logged in crashes coming from here. Most likely one of the two casts is casting null. Cannot fix or bypass with override since Android requires base.OnRestoreInstanceState to be called.
        protected override void OnRestoreInstanceState(IParcelable parcel)
        {
            Bundle bundle = (Bundle)parcel;
            base.OnRestoreInstanceState((IParcelable)bundle.GetParcelable("SUPER"));
            NormalizedMinValue = bundle.GetFloat("MIN");
            NormalizedMaxValue = bundle.GetFloat("MAX");
        }

Suggest alternate code:
            if (parcel is Bundle bundle)
            {
                base.OnRestoreInstanceState(bundle.GetParcelable("SUPER") as IParcelable);
                NormalizedMinValue = bundle.GetFloat("MIN");
                NormalizedMaxValue = bundle.GetFloat("MAX");
            }
            else
            {
                base.OnRestoreInstanceState(parcel);
            }

Can you provide a sample project to reproduce the problem?


accuracy  problems,

I followed the instructions completely and used the data provided in Google drive, but the accuracy of ST-GCN was extremely low in NTU-RGB-D-xsub

you mean you use the pre-train model or train a new model by using dataset  NTU-RGB-D-xsub

you mean you use the pre-train model or train a new model by using dataset NTU-RGB-D-xsub

train a new model

Yeah, I think I met the same problem with you. I use the original model to train, in theory, its accuracy should as same as the pre-train model. But the accuracy is extreme low, top-1 1%, top-5 8%.

So how did you solve it

The same problem

Hi is there any reason for this? I made use of the pre-trained model and got pretty low accuracies of 1-8% too


[STM32L476RGT6] SPI data read mismatch

Hi David,
I've been struggling for a couple of days with an SPI issue on STM32L476RGT6.
I am trying to communicate with a TI DRV8301 slave device (16 bit word). But, when reading one of its registers, what I get in the read buffer is not what I expect/measure with the Logic Analyzer.
Here's my app. code:
// Configure I/Os
defmt::println!("Configuring I/Os");
// SPI I/Os
let mut sck1 = Pin::new(Port::A, 5, PinMode::Alt(5));
let mut miso1 = Pin::new(Port::B, 4, PinMode::Alt(5)); // Shall be connected to SDO
let mut mosi1 = Pin::new(Port::B, 5, PinMode::Alt(5)); // Shall be conntected to SDI
let mut drv8301_cs = Pin::new(Port::A, 0, PinMode::Output);
let mut en_gate = Pin::new(Port::A, 1, PinMode::Output);

// We use SPI1 for the IMU
// The limit is the max SPI speed of the ICM-42605 IMU of 24 MHz. The Limit for the St Inemo ISM330  is 10Mhz.
let drv8301_baud_div = BaudRate::Div256; // Adjust this based on MCU speed, and IMU max speed.

let drv8301_spi_cfg = SpiConfig {
    mode: SpiMode::mode1(),
    data_size: DataSize::D16,
    fifo_reception_thresh: ReceptionThresh::D16,
    ..Default::default()
};

let mut spi1 = Spi::new(cx.device.SPI1, drv8301_spi_cfg, drv8301_baud_div);

defmt::println!("Setting CS high");
drv8301_cs.set_high();
defmt::println!("Setting EN_GATE low");
en_gate.set_low();

defmt::println!("Resetting DRV8301");
en_gate.set_low();
cortex_m::asm::delay(899);
en_gate.set_high();
cortex_m::asm::delay(450000);
defmt::println!("Reset done!");

let mut read_buf = [0x0000];
defmt::println!("Writing read command");
drv8301_cs.set_low();
spi1.write(&[0x8800]).ok();
drv8301_cs.set_high();
// spi1.write(&[0xFFFF]).ok();
defmt::println!("Data: {:?}", read_buf);
defmt::println!("Reading register content");
drv8301_cs.set_low();
spi1.transfer(&mut read_buf).ok();
drv8301_cs.set_high();
defmt::println!("Data: {}", read_buf);
defmt::println!("Setting CS high");

(Note that I configured DataSize::D16 and ReceptionThresh::D16).
I've modified this HAL SPI implementation to support 16 bits transactions with the following (dirty) patches:
/// Write two bytes if available, or block until it's available.
/// See L44 RM, section 40.4.9: Data transmission and reception procedures.
pub fn write_word(&mut self, word: u16) -> nb::Result<(), Error> {
    let sr = self.regs.sr.read();

    cfg_if! {
        if #[cfg(feature = "h7")] {
            let crce = sr.crce().bit_is_set();
            let rdy = sr.txp().bit_is_set();
        } else {
            let crce = sr.crcerr().bit_is_set();
            let rdy = sr.txe().bit_is_set();
        }
    }

    if sr.ovr().bit_is_set() {
        Err(nb::Error::Other(Error::Overrun))
    } else if sr.modf().bit_is_set() {
        Err(nb::Error::Other(Error::ModeFault))
    } else if crce {
        Err(nb::Error::Other(Error::Crc))
    } else if rdy {
        cfg_if! {
            if #[cfg(feature = "h7")] {
                // todo: note: H7 can support words beyond u8. (Can others too?)
                unsafe { ptr::write_volatile(&self.regs.txdr as *const _ as *mut u16, word) };
                // write CSTART to start a transaction in master mode
                self.regs.cr1.modify(|_, w| w.cstart().started());
            }
             else {
                unsafe { ptr::write_volatile(&self.regs.dr as *const _ as *mut u16, word) };
            }
        }
        Ok(())
    } else {
        Err(nb::Error::WouldBlock)
    }
}

/// Write multiple bytes on the SPI line, blocking until complete.
/// See L44 RM, section 40.4.9: Data transmission and reception procedures.
pub fn write(&mut self, words: &[u16]) -> Result<(), Error> {
    for word in words {
        nb::block!(self.write_word(word.clone()))?;
        nb::block!(self.read())?;
    }

    Ok(())
}

/// Read a single byte if available, or block until it's available.
/// See L44 RM, section 40.4.9: Data transmission and reception procedures.
pub fn read_sixteen(&mut self) -> nb::Result<u16, Error> {
    let sr = self.regs.sr.read();

    cfg_if! {
        if #[cfg(feature = "h7")] {
            let crce = sr.crce().bit_is_set();
            let not_empty = sr.rxp().bit_is_set();
        } else {
            let crce = sr.crcerr().bit_is_set();
            let not_empty = sr.rxne().bit_is_set();
        }
    }

    if sr.ovr().bit_is_set() {
        Err(nb::Error::Other(Error::Overrun))
    } else if sr.modf().bit_is_set() {
        Err(nb::Error::Other(Error::ModeFault))
    } else if crce {
        Err(nb::Error::Other(Error::Crc))
    } else if not_empty {
        #[cfg(feature = "h7")]
        // todo: note: H7 can support words beyond u8. (Can others too?)
        let result = unsafe { ptr::read_volatile(&self.regs.rxdr as *const _ as *const u16) };
        #[cfg(not(feature = "h7"))]
        let result = unsafe { ptr::read_volatile(&self.regs.dr as *const _ as *const u16) };
        Ok(result)
    } else {
        Err(nb::Error::WouldBlock)
    }
}

/// Read multiple bytes to a buffer, blocking until complete.
/// See L44 RM, section 40.4.9: Data transmission and reception procedures.
pub fn transfer<'w>(&mut self, words: &'w mut [u16]) -> Result<(), Error> {
    for word in words.iter_mut() {
        nb::block!(self.write_word(word.clone()))?;
        *word = nb::block!(self.read_sixteen())?;
    }

    Ok(())
}

Basically, I just modified write and transfer functions and their underlying functions to read self.regs.dr as a u16 instead of u8.
The read and write are OK from a transaction point of view:

So I expect to read 2049 in read_buf after transfer, instead I get 384:
0 Systick = 80000000
└─ minimal::app::init @ src/bin/minimal.rs:64
1 Configuring I/Os
└─ minimal::app::init @ src/bin/minimal.rs:67
2 Setting CS high
└─ minimal::app::init @ src/bin/minimal.rs:103
3 Setting EN_GATE low
└─ minimal::app::init @ src/bin/minimal.rs:105
4 Resetting DRV8301
└─ minimal::app::init @ src/bin/minimal.rs:108
5 Reset done!
└─ minimal::app::init @ src/bin/minimal.rs:113
6 Writing read command
└─ minimal::app::init @ src/bin/minimal.rs:116
7 Data: [0]
└─ minimal::app::init @ src/bin/minimal.rs:121
8 Reading register content
└─ minimal::app::init @ src/bin/minimal.rs:122
9 Data: [384]
└─ minimal::app::init @ src/bin/minimal.rs:126
10 Setting CS high
└─ minimal::app::init @ src/bin/minimal.rs:127
11 Initializing TIM1
└─ minimal::app::init @ src/bin/minimal.rs:163
12 Configuring TIM1 output channels
└─ minimal::app::init @ src/bin/minimal.rs:168

I spent hours looking at the code and the RM without success. Any idea?
Thanks.

I noticed that 2049 = 0x0801, and 384 = 0x0108. So, you are probably interpreting the data in Little Endian (default on STM32), while the bits come in as Big Endian.

I noticed that 2049 = 0x0801, and 384 = 0x0108. So, you are probably interpreting the data in Little Endian (default on STM32), while the bytes come in as Big Endian. I think you need to swap the bytes of result: u16.

384 = 0x0180 (not 0x0108). It's too close to be a coincidence though... I'll try to check with a different register.


cudaPackages: __structuredAttrs works with autoPatchelf since #272752

Description of changes

#272752 introduced support for using __structuredAttrs with autoPatchelf to ignore dependencies.
This PR updates use-sites across cudaPackages to switch away from the env workaround.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

[!
Template log archival command:
PR=281376; \
RUN_NUMBER=13; \
SYSTEM="aarch64-linux"; \
CUDA_CAPABILITIES="7_5"; \
tar -cvf "$SYSTEM-cap-$CUDA_CAPABILITIES-pr-$PR-$RUN_NUMBER.tar.zst" \
  -I "zstd -T0 --ultra -22" \
  -C "$HOME/.cache/nixpkgs-review/pr-$PR-$RUN_NUMBER" \
  .

Logs are made available at https://drive.google.com/drive/folders/1GgABhwa2ooKeZXMqf5He6PcyClNrE6cQ?usp=share_link

:clock1: aarch64-darwin
In progress.
:clock1: x86_64-darwin
In progress.
:clock1: aarch64-linux
:clock1: CUDA (Jetson)
In progress.
:clock1: CUDA (Non-Jetson)
In progress.
:clock1: Non-CUDA
In progress.
:clock1: x86_64-linux
:clock1: CUDA (Non-Jetson)
In progress.
:clock1: Non-CUDA
In progress.

Reformatted with the latest nixfmt (https://github.com/piegamesde/nixfmt/commit/1eff7a84ac82fbebb5f586244f1c80e1fcc4f494).


Implement quote highlighting in ScripturePanes for reference range

based on the Spike #357
This will require Abel's quotes rcl to implement

Seeing highlighting in the ScripturePanes for reference range.Tested with v2.0.0 build 2c0eca3 QA.

Looks good in v2.0.0 build a2a20c1 QA. Highlights are seen in a reference range.


👷 Remove autoformatter and replace with MegaLinter

Overview
This PR introduces a robust MegaLinter configuration to our GitHub repository. This addition aims to significantly improve our code quality, enforce consistent coding standards, and ensure codebase security.
Linters and Formatters Included

Python Tools: PYTHON_PYLINT, PYTHON_FLAKE8, PYTHON_BLACK, PYTHON_ISORT

PYLINT & FLAKE8: For Python code quality checks, identifying bugs, and enforcing coding standards.
BLACK: An opinionated formatter for consistent Python code styling.
ISORT: For sorting and organizing Python imports in a consistent manner.

YAML Tools: YAML_PRETTIER, YAML_YAMLLINT

YAMLLINT: Ensures YAML file consistency and correctness.
PRETTIER: Formatter for maintaining a consistent style in YAML files.

Markdown: MARKDOWN_MARKDOWNLINT

MARKDOWNLINT: Enforces standards and consistency for Markdown files.

Security and Repository Checks: REPOSITORY_TRIVY, REPOSITORY_GITLEAKS

TRIVY: Identifies vulnerabilities in the repository.
GITLEAKS: Scans for potential secret leaks in the codebase.

Other Tools:

ACTION_ACTIONLINT, BASH_SHELLCHECK, MAKEFILE_CHECKMAKE, DOCKERFILE_HADOLINT, JSON_PRETTIER: These tools provide linting support for GitHub Actions, Bash scripts, Makefiles, Dockerfiles, and JSON files, ensuring best practices and standards in

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (949aa10) 97.40% compared to head (a55d70d) 97.40%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3939   +/-   ##
=======================================
  Coverage   97.40%   97.40%
=======================================
  Files          65       65
  Lines        5661     5661
  Branches     1025     1025
=======================================
  Hits         5514     5514
  Misses         83       83
  Partials       64       64

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Make cmake modules consistent names

fixes: #1355
I don't think this is required to be mentioned in the change log.

I don't think this is required to be mentioned in the change log.

I agree. But to be certain, can you verify that we don't mention these in any markdown docs and that customers are not meant to include or call these directly in their projects or builds. If both those are true, no need for a CL entry since it isn't useful for the end-user.

I don't think this is required to be mentioned in the change log.

I agree. But to be certain, can you verify that we don't mention these in any markdown docs and that customers are not meant to include or call these directly in their projects or builds. If both those are true, no need for a CL entry since it isn't useful for the end-user.

/azp run cpp - core

/azp run cpp - core


allow for top level terraform flag assignment

fixes #517
also adds tests for FormatTerraformBackendConfigAsArgs

This change is

@brikis98 FormatTerraformBackendConfigAsArgs uses the generic formatTerraformArgs, which is what I modified:
https://github.com/gruntwork-io/terratest/blob/master/modules/terraform/format.go#L71-L75

oh I feel silly. That's the wrong test. I'll get back to you.

Could you add comments to terraform.Options to indicate that terraform.KeyOnly can be used as a value in the BackendConfig map to indicate only the key should be passed to Terraform?

Bumping this one up too :)

@ThisGuyCodes lmk if you could use a hand on this, could deff use this feature.

bump? (4 years later)


Patch TouchBackend to solve e.targetTouches bug in iOS 13

Based on the discussions and findings over #1585, I believe Safari in iOS 13 can somehow lose e.targetTouches after a few renders.
As a workaround I set up a private property in TouchBackend to “cache” a valid target Touch from touchstart event, then use it as a fallback in touchmove event handlers when it fails to get client offset from an empty e.targetTouches list.
And this should fix #1585.

Thanks for the PR! Have you verified that this fix works on an iOS device?

Yes, I've tried it locally in my project with an iPad running iOS 13.2.3. It does seem working properly.


Resolving dependencies failed when using poetry

Seems like metagpt requires qdrant-client == 1.7.0, numpy == 1.24.3, while qdant-client requires numpy >=1.26

Here is my pyproject.toml

Maybe we can follow what langchain does, to isolate third-party dependencies like  pip install langchain-openai

Qdrant is not in use, may be removed in the future. FYI: related issue.

Qdrant is not in use, may be removed in the future. FYI: related issue.

It seems this lib belongs to an example, may be we can isolate the libs required by examples or specified tools (like search api) from main dependencies.

I also encounter the same issue when trying to bring in MetaGPT as a dependency. The issue here is that purely using requirements.txt does not properly check dependency compatibility across packages (as is evident in this case).
The other issue is the practice of locking popular python packages (such as pydantic) down to a specific version, as opposed to a compatible version range. This severely limits the ability to bring in other 3rd party libraries which also rely on these dependencies.
For example if we were to look to langchain for how to best go about things:
numpy = "^1"
pydantic = ">=1,<3"

as compared to being locked down to specific versions as is the case in the current requirements.txt:
numpy==1.24.3
pydantic==2.5.3

Note: The original issue has been present since v0.7.1.

What about using poetry or rye as a package management tool?

@seehi

What about using poetry or rye as a package management tool?

I'd definitely recommend poetry as a candidate, its what I use currently and it seems to be used a fair bit nowadays.

Has this issue been resolved? I meet the same issue when install the lastest 0.8.1 with poetry.
Because qdrant-client (1.7.0) depends on numpy (>=1.26)
 and metagpt (0.8.0) depends on numpy (1.24.3), qdrant-client (1.7.0) is incompatible with metagpt (0.8.0).
So, because metagpt-startup depends on metagpt (0.8.0) which depends on qdrant-client (1.7.0), version solving failed.

I had to use pip and python 3.9. Even had issues installing with 3.12 & pip. qdrant-client was blocking any variation when trying to poetry install.

For now, temporary solution would be poetry add git+https://github.com/geekan/MetaGPT.git.


Keyword parameters not passed to wrapped step

Describe the bug
Keyword parameters are not passed through properly when wrapping step.
To Reproduce
#!/usr/bin/env ruby

require "dry/container"
require "dry/transaction"

Container = Dry::Container.new
Container.register(:foo) do |foo:|
  Dry::Monads::Result::Success.new(foo)
end

class Tr
  include Dry::Transaction(container: Container)

  step :bar, with: :foo

  def bar(bar:)
    super(foo: bar)
  end
end

puts Tr.new.call(bar: "baz")

Results in this error:
bug.rb:7:in `block in <main>': missing keyword: :foo (ArgumentError)
        from /.../gems/dry-transaction-0.15.0/lib/dry/transaction/instance_methods.rb:85:in `method_missing'
        from bug.rb:17:in `bar'
        from /.../gems/dry-transaction-0.15.0/lib/dry/transaction/callable.rb:35:in `call'
        from /.../gems/dry-transaction-0.15.0/lib/dry/transaction/callable.rb:35:in `call'
        from /.../gems/dry-transaction-0.15.0/lib/dry/transaction/step_adapters/around.rb:11:in `call'
        from /.../gems/dry-transaction-0.15.0/lib/dry/transaction/step_adapters/raw.rb:13:in `call'
        from /.../gems/dry-transaction-0.15.0/lib/dry/transaction/step_adapter.rb:43:in `call'
        from /.../gems/dry-transaction-0.15.0/lib/dry/transaction/step_adapter.rb:43:in `call'
        from /.../gems/dry-transaction-0.15.0/lib/dry/transaction/step.rb:57:in `block in call'
        from /.../gems/dry-transaction-0.15.0/lib/dry/transaction/step.rb:64:in `with_broadcast'
        from /.../gems/dry-transaction-0.15.0/lib/dry/transaction/step.rb:57:in `call'
        from /.../gems/dry-transaction-0.15.0/lib/dry/transaction/stack.rb:21:in `block (3 levels) in compile'
        from /.../gems/dry-monads-1.6.0/lib/dry/monads/right_biased.rb:52:in `bind'
        from /.../gems/dry-transaction-0.15.0/lib/dry/transaction/stack.rb:21:in `block (2 levels) in compile'
        from /.../gems/dry-transaction-0.15.0/lib/dry/transaction/stack.rb:14:in `call'
        from /.../gems/dry-transaction-0.15.0/lib/dry/transaction/instance_methods.rb:29:in `call'
        from bug.rb:21:in `<main>'

Expected behavior
Should print Success("baz")
My environment

Affects my production application: Yes
Ruby version: 3.2.2
OS: Fedora 37

Ah this is because I misunderstood how the library intends for inputs to be passed to steps.
For others who run into this, the first parameter passed to the step is its input. Only one argument is passed to steps, which is either the value passed to call or the value of a successful previous step. All extra arguments to a step are set using with_step_args.
So the correct way to do my example would be:
#!/usr/bin/env ruby

require "dry/container"
require "dry/transaction"

Container = Dry::Container.new
Container.register(:foo) do |input|
  Dry::Monads::Result::Success.new(input[:foo])
end

class Tr
  include Dry::Transaction(container: Container)

  step :bar, with: :foo

  def bar(input)
    super({foo: input[:bar]})
  end
end

puts Tr.new.call(bar: "baz")


[main < E-graphQL] Add compatibility for graphQL

Description
Change refactor, label, and create procedures to have camelCase output and input params. Change map and collections procedures to functions. Change schema NodeTypeProperties and schema RelTypeProperties to use camel case input and output parameters.
Pull request type

[ ] Bugfix
[ ] Algorithm/Module
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

Related issues
Delete if this PR doesn't resolve any issues. Link the issue if it does.
######################################
Reviewer checklist (the reviewer checks this part)
Module/Algorithm

[ ] Core algorithm/module implementation
[ ] Query module implementation
[ ] Unit tests
[ ] End-to-end tests
[ ] Code documentation
[ ] README short description
[ ] Documentation on memgraph/docs
[ ] Update GQLALchemy signatures in query builder using query module signature generator

######################################

@vpavicic release note:
Change refactor, label, and create procedures to have camelCase output and input params. Change map and collections procedures to functions. Change schema NodeTypeProperties and schema RelTypeProperties to use camel case input and output parameters.


Fix the wrong figure for multiclass in summary plot.

Overview
Closes #3835
Description of the changes proposed in this pull request:
The issue is caused by the change in 0.45, where the multiclass output is stacked on the last dimension, instead of list anymore.
Fix this issue by checking the explanation object passed in. If the multiclass is detected, revert the shap values to list form.
Checklist

[ ] All pre-commit checks pass.
[ ] Unit tests added (if fixing a bug or adding a new feature)

Thank you for the PR! It's fantastic to have new contributors in shap, welcome aboard.
I merged master into your feature branch to get the tests running, as we had a temporary CI issue with numba (unrelated to this PR) which has since been fixed.


Map super-reads and unassembled reads to genome

When i runing StringTie addition program <superreads.pl> produce super-reads and two unassembled paired reads,But i don't know how to used this results map to genome，like HISAT（http://ccb.jhu.edu/software/hisat/manual.shtml ）  It seem not have appropriate selectable parameters.Can you help me?Thank you very much.

You can use HISAT (using the -U option) to align the LongReads.fq as single (unpaired) reads. Then you can run HISAT again using the  -1 and -2 options to align the two files with paired unassembled reads that have the extension .notAssembled.fq.gz. (please check the HISAT manual about how to perform HISAT searches).  After both these HISAT searches are performed, it's important to sort the resulting SAM files by converting them to BAM and sorting each BAM file, then merge the 2 sorted BAM files into one sorted BAM file, which you can finally give to StringTie for assembly (please check the samtools documentation about how to convert SAM to BAM, sort each BAM and merge sorted BAMs).

Ok,thanks


lfs: default to basic transfer API

I've fixed the download of LFS objects when the Batch API response does not contain a transfer property. In this case, the transfer property should default to "basic". This behavior conforms with the spec:

All Git LFS clients and servers SHOULD support it, and default to it if the Batch API request or response do not specify a transfer property.

For instance, GitLab's LFS server does not provide the transfer property, which causes scmrepo to fail with:
.../scmrepo/git/lfs/client.py", line 201, in _download
    raise LFSError("Unsupported LFS transfer type")

After this fix, downloading LFS objects from GitLab works.

Thanks for catching this @sisp!
scmrepo==2.0.3 is now released with this fix

Thanks for the quick review, merge and release, @pmrowla! :pray:


Fix first-time inventory hosts from cron

Fixes #38
I'm not positive about the security implications of this change, so if
this makes no sense, just dump it. Not sure how else we'd populate the
~cideploy known_hosts file otherwise though....

Here's a thing I've done at previous locations to prime the known_hosts:
---
- name: Load Keys
  hosts: localhost
  connection: local
  gather_facts: false
  become: false

  tasks:
    - name: simple ssh
      command: ssh -o StrictHostKeyChecking=no -F {{ ssh_config }} {{ item }} echo
      when: item != 'localhost'
      with_items: "{{ groups['all'] }}"

Now the bit here about using an ssh_config, that is just because we had one for this site. We don't need on here, we just have to put more options directly on the command line. This should really only be used in specific scenarios, such as booting new instances.

FYI, OpenSSH includes a command named 'ssh-keyscan' for this purpose. However, has anyone considered scraping keys from the console logs of our booted instances?

Getting the host key is a interesting option, but scraping the log seems fragile.
https://review.openstack.org/#/c/167202/ could make that better, but alas...

Ok, so we need something like the following:
https://raymii.org/s/tutorials/Ansible_-_create_OpenStack_servers_with_os_server.html#Instance_creation_playbook
The only open question on my end is whether os_server.results contains info for all hosts, or just newly-created ones. If it contains results for all hosts, then we're good. If not, we're still in trouble if we decide to spin up a new bastion to manage an already-created set of nodes.

I might be ignorant, but where is that set of code dealing with host keys?

No, you're right. I meant the technique to get the hosts involved in our dynamic inventory. For dealing with known_hosts, you can do this: http://hakunin.com/six-ansible-practices#path-to-success-1

Yah I am -1 on this because it hurts security. First time users can be expected to deal with host keys in the normal way.

Looks like we aren't worried about this, and will just do it manually the first time we spin up a new cloud. I'm gonna close it.


Publish to Chrome Web Store

I know this is already on the roadmap, but I wanted to go ahead and create an issue for it.  I am willing to use my Chrome Developer account since I already have paid the fees if you'd like to take advantage of that!  Firefox's Addon Store is free though, so you should be able to do that yourself fairly easily.

Thank you so much! I will definitely contact you when a few more changes are made to wasteof.plus (likely after PRs #22  and #32)! I am currently planning to publish to the Firefox store myself at the moment 😄

Sounds good!

Renamed this because I am creating a different Issue to track Firefox publishing progress (#82)

Excellent!  Glad to see you're moving towards publishing.

@micahlt Just to confirm, can I email you using the email listed on your website<EMAIL_ADDRESS>with the info for the Chrome Web Store listing?

Definitely!


Add this repo to ustwo.github.io?

@emmaguy - Would this be a good candidate to add to our github.io profile? You can have a chat with @simonlindsay if you like to get it in there and we can help you with that.

@mikaelha yes - that sounds like it'd be good - I'll say hi to @simonlindsay to get the ball rolling :smile:

Added repo to http://ustwo.github.io, awaiting images from @emmaguy

How about this @simonlindsay ?

@emmaguy while you are at it, the BDD repo could do with a link to the post on the ustwo blog!

Updated on http://ustwo.github.io/


Freezes when using video concat

Q
A

Bug?
no

New Feature?
no

Version Used
^0.14 (laravel-ffmpeg)

FFmpeg Version
ffmpeg version 2.8.15-0ubuntu<IP_ADDRESS>

OS
Docker - Ubuntu

Actual Behavior
 $disk = FFMpeg::fromDisk('local');

  $pathVideos = [];

 foreach ($this->videos as $key => $video) {
    $pathVideos[$key] = $video->getPath();
  }

 $disk->open("{$this->videos[0]->id}/{$this->videos[0]->file_name}")
     ->concat($pathVideos)
     ->saveFromSameCodecs(storage_path('app/' .  $this->videos[0]->collection_name) . ".mp4", TRUE);

Expected Behavior
No freezing, output_video duration = total_video duration
Steps to Reproduce
Video demo output: https://streamable.com/hnuzyp
Possible Solutions
Is it related to the processor thread or amd chip?

Could you provide samples you can reproduce wiwth?

Could you provide samples you can reproduce with?

List videos:
video 1
video error
video 3

Could you provide samples you can reproduce with?

I have solved the problem with framerate (), due to the different aspect ratios of videos.

I'm having the same trouble, the videos have diferent framerates and different aspect ratios, how did you manage to solve it ?
$video = $ffmpeg->open( '01.mp4' );
$video->filters()
->framerate( new FFMpeg\Coordinate\FrameRate(60), 9 )
->resize(new FFMpeg\Coordinate\Dimension(1920, 1080) , FFMpeg\Filters\Video\ResizeFilter::RESIZEMODE_SCALE_HEIGHT )->synchronize();
$video->save(new FFMpeg\Format\Video\X264(), '01-new.mp4');

$video = $ffmpeg->open( '02.mp4' );
$video->filters()
->framerate( new FFMpeg\Coordinate\FrameRate(60), 9 )
->resize(new FFMpeg\Coordinate\Dimension(1920, 1080) , FFMpeg\Filters\Video\ResizeFilter::RESIZEMODE_SCALE_HEIGHT )->synchronize();
$video->save(new FFMpeg\Format\Video\X264(), '02-new.mp4');

$video = $ffmpeg->open( '01-new.mp4' );
$video->concat([
        __DIR__ . '/01-new.mp4' ,
        __DIR__ . '/02-new.mp4' ,
])->saveFromSameCodecs('final.mp4', TRUE);

When playing the video, final.mp4, using VLC, from 01-new.mp4 to 02-new.mp4 the windows is resized and appears a black frame as transition that is not in both videos, even though the height and width of the converted videos are the same.


After running pod install, I'm missing some files in lcl.h

like  "lcl_config_logger.h"

After running pod install, lcl_configure will be available at Pods/LibComponentLogging-pods/configure/lcl_configure
per the LibComponentLogging-pods, you need to run lcl_configure pod to create the files. I'll add this to the steps to perform in the readme or add a pod step which will make it easier for people.

Actually it was already document at step4


Duplicate Display Directive in Card SCSS

Bugs
Please include the following information with your bug report:

What MDL Version are you using? (please be specific, e.g. major.minor.patch)
1.3.0

What browser(s) is this bug affecting (including version)?
N/A

What OS (and version) are you using?
N/A

Any other information you believe would be useful?
Display rule is duplicated here: https://github.com/google/material-design-lite/blob/mdl-1.x/src/card/_card.scss#L47

I think it's more a fallback for browsers which does not support display: flex.

@aburai is correct. This was a fallback for older IE's that were supported but didn't have flex support.
MDL is also no longer maintained. Check out Material Components for Web for what MDL became.


Error: Error when reading '-': The system cannot find the file specified.

Steps to Reproduce

... flutter create project_app
... cd project_app
... flutter run

Logs

Using hardware rendering with device sdk gphone x86. If you notice graphics artifacts, consider enabling software
rendering with "--enable-software-rendering".
Launching lib\main.dart on sdk gphone x86 in debug mode...
Error: Error when reading '-': The system cannot find the file specified.
Running Gradle task 'assembleDebug'...
Running Gradle task 'assembleDebug'... Done                         3.8s
Exception: Gradle task assembleDebug failed with exit code 254

[√] Flutter (Channel stable, 1.20.4, on Microsoft Windows [Version 10.0.18362.1082], locale en-US)
• Flutter version 1.20.4 at C:\Flutter\flutter
• Framework revision fba99f6cf9 (5 days ago), 2020-09-14 15:32:52 -0700
• Engine revision d1bc06f032
• Dart version 2.9.2
[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
• Android SDK at C:\Users\Atharva\AppData\Local\Android\Sdk
• Platform android-28, build-tools 28.0.3
• ANDROID_HOME = C:\Users\Atharva\AppData\Local\Android\Sdk
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
• All Android licenses accepted.
[√] Android Studio (version 4.0)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin version 49.0.2
• Dart plugin version 193.7547
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
[!] VS Code (version 1.49.0)
• VS Code at C:\Users\Atharva\AppData\Local\Programs\Microsoft VS Code
X Flutter extension not installed; install from
https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[√] Connected device (1 available)
• sdk gphone x86 (mobile) • emulator-5554 • android-x86 • Android 11 (API 30) (emulator)

Hi @atharvachavan2000
Can you provide please your flutter run --verbose

Hi @atharvachavan2000
Do you have any - in your system path or user name has -? Please check your path to project
Can you please provide flutter run --verbose
Thank you

Hi @atharvachavan2000
Do you have any - in your system path or user name has -? Please check your path to project
Can you please provide flutter run --verbose
Thank you

[ +116 ms] executing: [C:\Flutter\flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[ +216 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[   +1 ms] fba99f6cf9a14512e461e3122c8ddfaa25394e89
[   +1 ms] executing: [C:\Flutter\flutter/] git tag --contains HEAD
[ +248 ms] Exit code 0 from: git tag --contains HEAD
[   +1 ms] 1.20.4
[   +9 ms] executing: [C:\Flutter\flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[  +66 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/stable
[        ] executing: [C:\Flutter\flutter/] git ls-remote --get-url origin
[  +55 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +91 ms] executing: [C:\Flutter\flutter/] git rev-parse --abbrev-ref HEAD
[  +63 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[   +1 ms] stable
[  +64 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +3 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +15 ms] executing: C:\Users\Atharva\AppData\Local\Android\sdk\platform-tools\adb.exe devices -l
[ +113 ms] List of devices attached
[   +3 ms] Artifact Instance of 'MaterialFonts' is not required, skipping update.
[        ] Artifact Instance of 'GradleWrapper' is not required, skipping update.
[        ] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[        ] Artifact Instance of 'FlutterSdk' is not required, skipping update.
[  +16 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FontSubsetArtifacts' is not required, skipping update.
[ +190 ms] No supported devices connected.
[  +10 ms] "flutter run" took 381ms.
[  +21 ms]
#0      throwToolExit (package:flutter_tools/src/base/common.dart:14:3)
#1      RunCommand.validateCommand (package:flutter_tools/src/commands/run.dart:343:7)

#2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:836:11)

#3      FlutterCommand.run. (package:flutter_tools/src/runner/flutter_command.dart:741:33)

#4      FlutterCommand.run. (package:flutter_tools/src/runner/flutter_command.dart)
#5      AppContext.run. (package:flutter_tools/src/base/context.dart:150:29)
#6      _rootRun (dart:async/zone.dart:1190:13)
#7      _CustomZone.run (dart:async/zone.dart:1093:19)
#8      _runZoned (dart:async/zone.dart:1630:10)
#9      runZoned (dart:async/zone.dart:1550:10)
#10     AppContext.run (package:flutter_tools/src/base/context.dart:149:18)
#11     FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:730:20)
#12     CommandRunner.runCommand (package:args/command_runner.dart:197:27)
#14     _rootRunUnary (dart:async/zone.dart:1198:47)
#15     _CustomZone.runUnary (dart:async/zone.dart:1100:19)
#16     _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
#17     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
#18     Future._propagateToListeners (dart:async/future_impl.dart:725:32)
#19     Future._completeWithValue (dart:async/future_impl.dart:529:5)
#20     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:40:15)
#21     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:311:13)
#22     FlutterVersion.checkFlutterVersionFreshness (package:flutter_tools/src/version.dart)
#23     _rootRunUnary (dart:async/zone.dart:1198:47)
#24     _CustomZone.runUnary (dart:async/zone.dart:1100:19)
#25     _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
#26     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
#27     Future._propagateToListeners (dart:async/future_impl.dart:725:32)
#28     Future._completeWithValue (dart:async/future_impl.dart:529:5)
#29     Future._asyncCompleteWithValue. (dart:async/future_impl.dart:567:7)
#30     _rootRun (dart:async/zone.dart:1190:13)
#31     _CustomZone.run (dart:async/zone.dart:1093:19)
#32     _CustomZone.runGuarded (dart:async/zone.dart:997:7)
#33     _CustomZone.bindCallbackGuarded. (dart:async/zone.dart:1037:23)
#34     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#35     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#36     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#37     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:169:5)
[ +402 ms] ensureAnalyticsSent: 258ms
[   +4 ms] Running shutdown hooks
[   +1 ms] Shutdown hooks complete
[   +1 ms] exiting with code 1
PS G:[FreeCourseSite.com] Udemy - Flutter & Dart - The Complete Guide [2020 Edition]\Flutter Project\my_project> flutter run --verbose
[ +115 ms] executing: [C:\Flutter\flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +83 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[   +1 ms] fba99f6cf9a14512e461e3122c8ddfaa25394e89
[   +3 ms] executing: [C:\Flutter\flutter/] git tag --contains HEAD
[ +224 ms] Exit code 0 from: git tag --contains HEAD
[   +1 ms] 1.20.4
[  +10 ms] executing: [C:\Flutter\flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[  +75 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/stable
[        ] executing: [C:\Flutter\flutter/] git ls-remote --get-url origin
[  +61 ms] Exit code 0 from: git ls-remote --get-url origin
[   +1 ms] https://github.com/flutter/flutter.git
[  +97 ms] executing: [C:\Flutter\flutter/] git rev-parse --abbrev-ref HEAD
[  +65 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[   +1 ms] stable
[  +70 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[  +12 ms] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +5 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[  +11 ms] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[  +13 ms] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +20 ms] executing: C:\Users\Atharva\AppData\Local\Android\sdk\platform-tools\adb.exe devices -l
[  +64 ms] List of devices attached
258b591d               device product:OnePlus7 model:GM1901 device:OnePlus7 transport_id:1
[   +7 ms] C:\Users\Atharva\AppData\Local\Android\sdk\platform-tools\adb.exe -s 258b591d shell getprop
[ +102 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[  +86 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[   +2 ms] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[   +2 ms] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[  +36 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[   +3 ms] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[ +510 ms] Generating G:[FreeCourseSite.com] Udemy - Flutter & Dart - The Complete Guide [2020 Edition]\Flutter
Project\my_project\android\app\src\main\java\io\flutter\plugins\GeneratedPluginRegistrant.java
[  +26 ms] ro.hardware = qcom
[  +68 ms] Starting incremental build...
[   +3 ms] Initializing file store
[  +27 ms] Skipping target: gen_localizations
[   +7 ms] complete
[  +15 ms] Launching lib\main.dart on GM1901 in debug mode...
[  +18 ms] C:\Flutter\flutter\bin\cache\dart-sdk\bin\dart.exe --disable-dart-dev C:\Flutter\flutter\bin\cache\artifacts\engine\windows-x64\frontend_server.dart.snapshot--sdk-root C:\Flutter\flutter\bin\cache\artifacts\engine\common\flutter_patched_sdk/ --incremental --target=flutter --debugger-module-names
-Ddart.developer.causal_async_stacks=true --output-dill C:\Users\Atharva\AppData\Local\Temp\flutter_tools.1a07c7e7\flutter_tool.1819fcbf\app.dill --packages .packages
-Ddart.vm.profile=false -Ddart.vm.product=false
--bytecode-options=source-positions,local-var-info,debugger-stops,instance-field-initializers,keep-unreachable-code,avoid-closure-call-instructions --enable-asserts
--track-widget-creation --filesystem-scheme org-dartlang-root --initialize-from-dill build\cache.dill.track.dill
[  +46 ms] executing: C:\Users\Atharva\AppData\Local\Android\sdk\platform-tools\adb.exe -s 258b591d shell -x logcat -v time -t 1
[ +209 ms] Exit code 0 from: C:\Users\Atharva\AppData\Local\Android\sdk\platform-tools\adb.exe -s 258b591d shell -x logcat -v time -t 1
[   +1 ms] --------- beginning of main
09-26 13:51:42.199<EMAIL_ADDRESS> 903): total connections for client : com.android.chromeare :3
[   +2 ms] executing: C:\Users\Atharva\AppData\Local\Android\sdk\platform-tools\adb.exe -s 258b591d shell -x logcat -v time -t 1
[ +192 ms] Exit code 0 from: C:\Users\Atharva\AppData\Local\Android\sdk\platform-tools\adb.exe -s 258b591d shell -x logcat -v time -t 1
[   +1 ms] --------- beginning of main
09-26 13:51:42.642<EMAIL_ADDRESS> 903): unbindService is called for service :
com.google.android.gms/.chimera.PersistentApiService and for client com.google.android.gms.persistent
[  +48 ms] <- compile package:my_project/main.dart
[  +14 ms] executing: C:\Users\Atharva\AppData\Local\Android\sdk\platform-tools\adb.exe version
[  +71 ms] Android Debug Bridge version 1.0.41
Version 30.0.4-6686687
Installed as C:\Users\Atharva\AppData\Local\Android\sdk\platform-tools\adb.exe
[   +3 ms] executing: C:\Users\Atharva\AppData\Local\Android\sdk\platform-tools\adb.exe start-server
[ +355 ms] Building APK
[  +18 ms] Running Gradle task 'assembleDebug'...
[   +4 ms] gradle.properties already sets android.enableR8
[   +5 ms] Using gradle from G:[FreeCourseSite.com] Udemy - Flutter & Dart - The Complete Guide [2020 Edition]\Flutter Project\my_project\android\gradlew.bat.
[  +22 ms] G:[FreeCourseSite.com] Udemy - Flutter & Dart - The Complete Guide [2020 Edition]\Flutter Project\my_project\android\gradlew.bat mode: 33279 rwxrwxrwx.
[ +140 ms] executing: C:\Program Files\Android\Android Studio\jre\bin\java -version
[+1461 ms] Exit code 0 from: C:\Program Files\Android\Android Studio\jre\bin\java -version
[        ] openjdk version "1.8.0_242-release"
OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
OpenJDK 64-Bit Server VM (build 25.242-b01, mixed mode)
[  +24 ms] executing: [G:[FreeCourseSite.com] Udemy - Flutter & Dart - The Complete Guide [2020 Edition]\Flutter Project\my_project\android/] G:[FreeCourseSite.com]
Udemy - Flutter & Dart - The Complete Guide [2020 Edition]\Flutter Project\my_project\android\gradlew.bat -Pverbose=true -Ptarget-platform=android-arm64
-Ptarget=G:[FreeCourseSite.com] Udemy - Flutter & Dart - The Complete Guide [2020 Edition]\Flutter Project\my_project\lib\main.dart -Ptrack-widget-creation=true
-Pfilesystem-scheme=org-dartlang-root assembleDebug
[+1066 ms] Error: Error when reading '-': The system cannot find the file specified.
[ +190 ms] Running Gradle task 'assembleDebug'... (completed in 2.9s)
[+3664 ms] Exception: Gradle task assembleDebug failed with exit code 254
[   +2 ms] "flutter run" took 8,625ms.
[  +21 ms]
#0      throwToolExit (package:flutter_tools/src/base/common.dart:14:3)
#1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:591:7)

#2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:860:18)
#3      _rootRunUnary (dart:async/zone.dart:1198:47)
#4      _CustomZone.runUnary (dart:async/zone.dart:1100:19)
#5      _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
#6      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
#7      Future._propagateToListeners (dart:async/future_impl.dart:725:32)
#8      Future._completeWithValue (dart:async/future_impl.dart:529:5)
#9      _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:40:15)
#10     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:311:13)
#11     RunCommand.usageValues (package:flutter_tools/src/commands/run.dart)
#12     _rootRunUnary (dart:async/zone.dart:1198:47)
#13     _CustomZone.runUnary (dart:async/zone.dart:1100:19)
#14     _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
#15     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
#16     Future._propagateToListeners (dart:async/future_impl.dart:725:32)
#17     Future._completeWithValue (dart:async/future_impl.dart:529:5)
#18     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:40:15)
#19     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:311:13)
#20     AndroidDevice.isLocalEmulator (package:flutter_tools/src/android/android_device.dart)
#21     _rootRunUnary (dart:async/zone.dart:1198:47)
#22     _CustomZone.runUnary (dart:async/zone.dart:1100:19)
#23     _FutureListener.handleValue (dart:async/future_impl.dart:143:18)
#24     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:696:45)
#25     Future._propagateToListeners (dart:async/future_impl.dart:725:32)
#26     Future._completeWithValue (dart:async/future_impl.dart:529:5)
#27     Future._asyncCompleteWithValue. (dart:async/future_impl.dart:567:7)
#28     _rootRun (dart:async/zone.dart:1190:13)
#29     _CustomZone.run (dart:async/zone.dart:1093:19)
#30     _CustomZone.runGuarded (dart:async/zone.dart:997:7)
#31     _CustomZone.bindCallbackGuarded. (dart:async/zone.dart:1037:23)
#32     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#33     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#34     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#35     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:169:5)
[ +284 ms] ensureAnalyticsSent: 219ms
[   +2 ms] Running shutdown hooks
[  +21 ms] Shutdown hook priority 4
[   +6 ms] Shutdown hooks complete
[   +1 ms] exiting with code 1

Hi @atharvachavan2000
As suspected, this is an issue with your system path, you have few - in your path to folder
[  +24 ms] executing: [G:\[FreeCourseSite.com] Udemy - Flutter & Dart - The Complete Guide [2020 Edition]\Flutter Project\my_project\android/] G:\[FreeCourseSite.com]
Udemy - Flutter & Dart - The Complete Guide [2020 Edition]\Flutter Project\my_project\android\gradlew.bat -Pverbose=true -Ptarget-platform=android-arm64
-Ptarget=G:\[FreeCourseSite.com] Udemy - Flutter & Dart - The Complete Guide [2020 Edition]\Flutter Project\my_project\lib\main.dart -Ptrack-widget-creation=true
-Pfilesystem-scheme=org-dartlang-root assembleDebug
[+1066 ms] Error: Error when reading '-': The system cannot find the file specified.

Please move your project your my_project to a folder without illegal characters such as -
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


Microsoft.OperationalInsights Service Provider required

The Microsoft.OperationalInsights Service Provider must be registered on the subscription you want to monitor for logs to appear in Azure Log Analytics Workspace.
Subscription appear to be connected, but don't report anything
Should be mentioned in the article

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

ID: f58d2fcb-0f3a-e016-e545-e3fd06e7c145
Version Independent ID: fc638c9e-5f2b-975a-fcf9-3ea19a92fb11
Content: Connect Azure Activity data to Azure Sentinel
Content Source: articles/sentinel/connect-azure-activity.md
Service: azure-sentinel
Sub-service: azure-sentinel
GitHub Login: @rkarlin
Microsoft Alias: rkarlin

@anderseide
Thanks for your feedback! We will investigate and update as appropriate.

Thanks @anderseide . I made a pull request to add this note. https://github.com/MicrosoftDocs/azure-docs-pr/pull/92166


[trivial] remove unused function (initialize func of layer)

remove initialize function of layer
because it have been replaced to finalize function (renamed)
Self evaluation:

Build test:   [X]Passed [ ]Failed [ ]Skipped
Run test:     [X]Passed [ ]Failed [ ]Skipped

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #2792. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.


On mac os, pythran -v no longer shows the compilation command

Title says it all.

Maybe something changed at the setuptool level along those lines: https://github.com/serge-sans-paille/pythran/blob/master/pythran/toolchain.py#L309 ?
Can you modify that part to always pass --verbose and report if it has the expected effect?

OK I'll try

I don't get it. It seems to work normally now... I don't know what was going on when I reported this but now I get the compiler command when I use -v. Closing this...


tests: Improve test U256toUint256 tests

Improve tests for src/utils/converters/integer.ts function U256toUint256
Tests must be written in tests/utils/converters/integer.test.ts

Can I hop on this?

assigned

Any updates on this issue @princeibs ?

Hey @ermvrs! 👋
If there are no updates on @princeibs' side, I can grab this issue.

Hello @YakupAltay, assigned 👍 Please complete as soon as you can :)

Merged
https://github.com/keep-starknet-strange/rosettanet/pull/127