Updates to Teams calling policy pages

Updated Get/Set/Grant-CsTeamsCallingPolicy
Added New/Remove-CsTeamsCallingPolicy

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

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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

@JohanFreelancer9

@dariomws @tseward @get-itips

Docs Build status updates of commit 8c1e87e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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 65fdb24:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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 a0c8698:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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 f252aaa:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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 add53d9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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 6e7ab3b:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

Line 0, Column 0: [Error: download-failed] Download failed for file 'https://opdhsblobprod04.blob.core.windows.net/contents/62388832b9c74db69d981c37288c5912/91e4cc0d9debc7e41e599d15667866b4'. Try closing and reopening the PR. If you get this Error again, file an issue.
Line 0, Column 0: [Error: download-failed] Download failed for file 'https://opdhsblobprod04.blob.core.windows.net/contents/62388832b9c74db69d981c37288c5912/91e4cc0d9debc7e41e599d15667866b4'. Try closing and reopening the PR. If you get this Error again, file an issue.
Line 0, Column 0: [Error: download-failed] Download failed for file 'https://opdhsblobprod04.blob.core.windows.net/contents/62388832b9c74db69d981c37288c5912/91e4cc0d9debc7e41e599d15667866b4'. Try closing and reopening the PR. If you get this Error again, file an issue.
Line 0, Column 0: [Error: download-failed] Download failed for file 'https://opdhsblobprod04.blob.core.windows.net/contents/62388832b9c74db69d981c37288c5912/91e4cc0d9debc7e41e599d15667866b4'. Try closing and reopening the PR. If you get this Error again, file an issue.
Line 0, Column 0: [Error: download-failed] Download failed for file 'https://opdhsblobprod04.blob.core.windows.net/contents/62388832b9c74db69d981c37288c5912/91e4cc0d9debc7e41e599d15667866b4'. Try closing and reopening the PR. If you get this Error again, file an issue.
Line 0, Column 0: [Error: download-failed] Download failed for file 'https://opdhsblobprod04.blob.core.windows.net/contents/62388832b9c74db69d981c37288c5912/91e4cc0d9debc7e41e599d15667866b4'. Try closing and reopening the PR. If you get this Error again, file an issue.

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 8ef0e23:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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 d373080:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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 b1f4733:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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 040172c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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

Copy review - @JensTrier, thank you for committing the first set of suggestions. Kindly also commit the rest (you were a bit quick for me). Many thanks.

Thanks @JohanFreelancer9! No worries, I'll continue to commit as long as you request changes :-)

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

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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 9d4c46c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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 8f04c0a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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 a5170d7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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 0048f47:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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 d260164:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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 cf0f438:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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 8be5b8b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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 c651552:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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 b212852:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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 b9cb72c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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 f61fc47:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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 2f4f79d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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 40e6b71:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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 4bc9b3c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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 1298d50:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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 f68a442:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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 7568bec:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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

@tiburd Please merge this PR> Thanks

Docs Build status updates of commit 4305c25:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-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


Use the babel runtime helpers instead of bundling

This PR switches our Babel builds from bundling the helpers to depending on the @babel/runtime package instead. The @babel/runtime package is already a dependency of Radiance's dependencies (i.e. react-transition-group), so we can reduce the bundle size a bit by not bundling another copy of the helpers as part of Radiance.
See https://github.com/rollup/plugins/tree/master/packages/babel#helpers and https://babeljs.io/docs/en/babel-plugin-transform-runtime for more info.

I need to tweak the external setting for Rollup to account for deep imports from @babel/runtime/*. Going to make a separate PR for that.


[Feature] Testimonial components

Description
Testimonial component for the website is required
Screenshots
No response
Additional Information
No response

Hi should this component be rendered on home page?, please let me know if I can work on this and be assigned to do this.
Thanks!


Logout

How can i logout and login with other account?

There's not really a "log out", you simply use a different account token from a different account.

@meteochu  Thanks


Where is new Page rules documentation, No examples only theories, very worst experience, wasted my 8 hours

Proposed changes
https://developers.cloudflare.com/rules/
Subject Matter
Page Rules/Rules
Content Location
I want old page rules back. they are easy to apply. we wasted 8 hours in redirecting subdomain to root in new page rule, we saw many videos on youtube, nothing found. In the end we add old page rule, that works within a second.
New Rules are very confusing and we still not know ABC of new rules.
Please make a user friendly documentation not bot friendly.
Additional information
No response

cc @nikitacano

@rishavayadav, what kind of redirect were you trying to configure? We already have plans to add more examples to https://developers.cloudflare.com/rules/reference/page-rules-migration/#migrate-forwarding-url and will use your feedback to improve this section.

I agree the new rules are very badly designed.
They ask you to choose between "static" and "dynamic" with no description at all on what those terms are supposed to mean, since there is no such terminology in HTTP standards.
For example I just want to redirect domain1.com/* to domain2.com/$1, is that a "static" or "dynamic" redirect? It was very simple with the old page rules.
Or another common example is to add/remove www, so I want to redirect www.domain1.com/* to https://domain1.com/$1

Hello!
Since this issue was opened, we've done numerous updates to our public documentation. We've also introduced wildcard matching support on all Cloudflare plans so that rule expressions are easier to write.
Also, Page Rules are not going away for the time being. And when the time comes, Cloudflare will perform the migration for you.
If you have other concerns, you can check the Community thread about the future of Page Rules and the features that will replace them:
https://community.cloudflare.com/t/page-rules-are-now-deprecated-without-good-replacements/656245/1


Adding 'navigatorKey' GlobalKey interrupting back button in Android.

Look at the below code snippet.
final navigatorKey = GlobalKey<NavigatorState>();
DropdownBanner(
        child: getContentWidget(context),
        navigatorKey: navigatorKey,
      );

Now when I press the back button in Android, Application quit.
But when I remove above code its works fine.

@hubdestro
Sorry for the delay. I was on Vacay! Does this happen on iOS as well?

@hubdestro


Added link to ML samples repo

Is it a good idea to add the link to the ML samples repo to the docs? If yes, I'll move it to another page in case of the tutorials index isn't perfect place (I've chosen that page because the related issue has been submitted under it).
Related to #5722

@mairaw I've addressed your comment, thank you for review.


Remove duplicate entries from .gitignore

Thanks @findepi for the PR. Thanks @snazy and @ebyhr for the review.


Update the maintenance status badge

Since stillmaintained.com is for sale, here's a simple replacement for the maintenance badge.

Thanks


Using param, which corresponds to handled event

In the handlers of ESP_GATTS_ADD_CHAR_DESCR_EVT was used incorrect param, which corresponding to ESP_GATTS_ADD_CHAR_EVT.
It was work because both params have same type and position in union.

Thanks @SiarheiVolkau . I've pushed this into our review & merge queue.

Cherry-picked in 1922f6c with tweaks in d5301bda .


ENH: Reduce for loops in df.corr(method='kendall')

Reduce for loops in df.corr(method='kendall')
Don't need to loop through lower triangle of the matrix.

this is fine, though actually a better change would be to move this algo to cython (like pearson/spearman) corr already. up for that?

scipy.stats.kendalltau is ~ "Inspired by the Java implementation part of the it.unimi.dsi.law package (http://law.dsi.unimi.it/)"
Fast (O(n log(n)) implementation of Kendall's Tau,  recursively uses mergesorts to count exchanges. More discussion over here
@jreback -- would this be the implementation to be cythonized?

no need to rewrite the actual tau computation
think the loop can be moved to cython then maybe call out to the scipy routines directly (not 100% sure the c-API is callable though)

This implementation doesn't give much gains. In fact, there isn't much cythonized code here, expect for type declarations.
import numpy as np
cimport numpy as np

from scipy.stats import kendalltau

#-------------------------------------------------------------------
# Pairwise tau

@cython.boundscheck(False)
@cython.wraparound(False)
def tau(ndarray[float64_t, ndim=2] mat, minp=None):
    cdef:
        Py_ssize_t xi, yi, N, K
        ndarray[float64_t, ndim=2] result
        ndarray[float64_t, ndim=1] ac, bc
        ndarray[uint8_t, ndim=2] mask
        float64_t c

    N, K = (<object> mat).shape

    if minp is None:
        minp = 1

    mat = mat.T
    result = np.empty((K, K), dtype=np.float64)
    mask = np.isfinite(mat).view(np.uint8)
    mask.dtype = bool

    for xi in range(K):
        ac = mat[xi]
        for yi in range(xi + 1):
            bc = mat[yi]
            valid = mask[xi] & mask[yi]
            if valid.sum() < minp:
                c = np.NaN
            elif not valid.all():
                c = kendalltau(ac[valid], bc[valid])[0]
            else:
                c = kendalltau(ac, bc)[0]

            result[xi, yi] = result[yi, xi] = c

    return result

Missing something here?

so the time is all taken by calling the kendalltau function, right? so that would need to be a cython-level call then to make this benefit (IIRC the implementation of this in scipy is in cython)

As I see here, scipy.stats.kendalltau implementation is not yet in cython, CMIIW.

ugh. can you profile this and see where the time is spent?

In [8]: df = pd.DataFrame(np.random.rand(10000, 10))

In [9]: %prun -l 4 slow.ftau(df)
         650311 function calls (971 primitive calls) in 16.933 seconds

   Ordered by: internal time
   List reduced from 73 to 4 due to restriction <4>

   ncalls  tottime  percall  cumtime  percall filename:lineno(function)
649385/55   15.475    0.000   15.475    0.281 stats.py:2858(mergesort)
       55    1.340    0.024   16.928    0.308 stats.py:2792(kendalltau)
       55    0.098    0.002    0.098    0.002 {numpy.core.multiarray.lexsort}
       55    0.007    0.000    0.007    0.000 {range}

scipy.stats.kendalltau internally uses custom mergesort function, this seems to taking up time?

so here's the question. since we are doing many repeated calls, with only slightly different inputs, is their a way to do this operation that sorts much less?

closing, pls reopen if you can fix according to comments


Python3 Compatibility Issue

I'm getting the following stack trace on macOS High Sierra. See this question for a possible solution
Traceback (most recent call last):
  File "/usr/local/bin/powerline-shell", line 11, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.6/site-packages/powerline_shell/__init__.py", line 218, in main
    segment.add_to_powerline()
  File "/usr/local/lib/python3.6/site-packages/powerline_shell/segments/ruby_version.py", line 13, in add_to_powerline
    if os.environ.has_key("GEM_HOME"):
AttributeError: '_Environ' object has no attribute 'has_key'

Was fixed in https://github.com/b-ryan/powerline-shell/pull/366

@b-ryan Thanks.


Adds pointer input device extension

Change list
Enable AppiumDriver to perform W3CWebDriver Actions and implement support for additional pointer interaction attributes such as pressure, twist, tilt etc.
Types of changes
What types of changes are you proposing/introducing to .NET client?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Integration tests

[x] Have you provided integration tests to pass against the latest version of appium? (for Bugfix or New feature)

Details
I've brought these changes from https://github.com/timotiusmargo/appium-dotnet-driver/pull/1.
Also the integration tests were brought from https://github.com/Microsoft/WinAppDriver/tree/master/Samples/C%23/StickyNotesTest
We needed these changes in order to tap on a specific coordinate in our test for our UWP application.
More details can be found here - https://github.com/Microsoft/WinAppDriver/issues/229
I admit I'm not too familiar with the overall design of this feature, so probably it makes sense to reach out to the guys at Microsoft, for any further information.
I'd like to bring this into the main repository, so we can get rid of our own fork and local .dll.

@timotiusmargo - I've cherry picked your changes from https://github.com/timotiusmargo/appium-dotnet-driver/pull/1
If you are happy with this, I'd appreciate it if you could sign the Contributor License Agreement as per @jsf-clabot.

@timotiusmargo Hi, could you take a look at https://github.com/appium/appium-dotnet-driver/pull/315#issuecomment-468664700 if you have a chance?

@KazuCocoa  & @akinsolb
Worst case scenario, if @timotiusmargo  is unavailable to accept the Contributor License Agreement I can rebase the commits and change his commit author to myself.
Not sure if this violates any license stuff, or copywriting :-? (I'd say that shouldn't be the case)

personally, I would leave his credit in somewhere to respect the code.
So, if he has no response, then what about leaving his credit as a commit message and release note?

personally, I would leave his credit in somewhere to respect the code.
So, if he has no response, then what about leaving his credit as a commit message and release note?

Sounds reasonable, @cosminstirbu If you're happy to do this can you add the release note for this feature by updating the .csproj file?

I've made the changes to the cherry picked commit and the release notes to reflect @timotiusmargo's credit.

@cosminstirbu just noticed there's a typo on the Interactions folder, for example
src/Appium.Net/Appium/Interations/InteractionInfo.cs
should be:
src/Appium.Net/Appium/Interactions/InteractionInfo.cs

Goo catch! I've fixed the typo.

Hello all! Sorry this completely slipped under my radar. Thanks for leaving me the credit for my code!


CloudStorageFileSystemProvider.requesterPays() and listBuckets() don't seem to respect retry settings

I'm not sure if this is strictly a bug or more of an incomplete feature.  All of the operations that perform web requests should retry based on the retry configuration settings.
It appears that CloudStorageFileSystemProvider.requesterPays() and CloudStorageFileSystemProvider.listBuckets() do not perform any retries when making connections.  (except for whatever the internal retry mechanism in storage is).
I don't have strong feelings about listBuckets() but we need the requesterPays check to be resilient against transient  connection issues.
Environment details

gcloud nio
OS type and version: all
Java version: all
version(s): 0.123.24 and previous

Hi @lbergelson,
Both listBuckets() and get(Bucket) are idempotent and expected to automatically retry as outlined in https://cloud.google.com/storage/docs/retry-strategy#java which is implemented in com.google.cloud:google-cloud-storage from v2.2.0 onward. com.google.cloud:google-cloud-nio:0.123.17 and onward use google-cloud-storage >= 2.2.0.
Can you provide any additional detail about how you're configuring/instantiating your CloudStorageFileSystemProvider and CloudStorageFileSystem?

I'm going to close due to inactivity, but feel free to reopen if it's still an issue for you.

@BenWhitehead  Thank you for the clarification and sorry for the confusion.
It looks like I misread the code.  I saw that most of the methods in this library use the CloudStorageRetryHandler and that those methods used a different internal retry mechanism. I looked for the link between the CloudStorageConfiguration and the retry strategy used internally but I was looking at the wrong thing because the relevant settings were actually in the StorageOptions.
Sorry for the time waste.

No Problem, I'm glad you were able to find the relevant settings.


TX Fee Fixed

Fix issue #263

Okay! I have just pushed the latest changes that display the Minting or Staking Denom depending on the fee price.

Oh my bad. I have mixed up the issues. This is good to go.


path length issue for CSCER-CSCAS-CSYCA

Long pathnames fail in CSCER etc. code. When path to executable is long, model fails. See thread on private repo here: https://github.com/DSSAT/dssat-csm/issues/255

Here is a hint as to what is going on. Firstly, it depends on the DSCSM047 binary location. Secondly this is what is happening when looking for files.
On a short path:
Could not find input file!
  File was: //~/d/Genotype/WHCER047.ECO

On a long path:
Could not find input file!
  File was: ///blue/hoogenboom/share/apps/dssat47/<IP_ADDRESS>/Genot/WHCER04

As you can see, it truncates both the directory and the filename. Hopefully this helps.

Hi there!
I have bumped into DSSAT issues with long PATHs when I started to pack a DSSAT-related project (gym-DSSAT) with Spack. Spack installations usually result in really long paths. A real example, from my own system: /home/emilioj/spack/opt/spack/linux-debiann-skylake/gcc-11.3.0/dssat-pdi-<IP_ADDRESS>-bsobpuwizjrudu4ndpdtyn2lvdxo6b4e (114 chars, only the PATH!).
Apparently, the issue arises from the fact that 80-char strings are used in PATH.for functions (I do not know if there are more short allocations for string in other places of the code).
I have seen this open issue here, marked as 'high priority'. Do you know if there are plans to solve this in a near future?
Thanks in advance!
E

Hi, @emilioj. I thought this issue had already been solved by @fabiooliveira72. Which version/branch are you using, and with which models are you facing issues? Is it with CSCER, CSCAS, CSYCA, or other models?

Hi @emilioj and @lpmorenoc!
Yes, we are developing the increase of path lengths for dssat-csm-os. Unfortunately, this is a major issue in DSSAT and we need more time to pull request this issue. There are a lot of testing that need to be done in order to merge this code.
For right now the best way is to use 80 characters maximum for path length. Please try to reduce your paths or compile the project and move the executable to the /DSSAT48/...  In this way, you can keep a short path for the executable. This will help you to keep working with DSSAT while finish to fix this issue.
Thank you. Please let us know if you need anything else.
Fabio Oliveira

Hi @lpmorenoc and @fabiooliveira72!
Thanks for your feedback :-)
I tried both 4.7 & 4.8 versions with similar issues (and looking at PATH.for, the 80-char string limit seems hard-coded in both branches).
This is a snapshot using last commit in 'develop', id 05010abe, tagged as v<IP_ADDRESS>. I am running experiment UFGA8201.MZX, treatment 1. In the upper panes you can see the installation (make install) in a 'short' path and the corresponding execution. Everything works Ok.
Lower panes show the installation & execution when a longer path is used. I've used a path similar to what is required when using a Spack recipe [1] (actually, a real spack path would be even longer as it adds a hash depending on the specific build, such as '/home/emilioj/spack/opt/spack/linux-debiann-skylake/gcc-11.3.0/dssat-pdi-<IP_ADDRESS>-bsobpuwizjrudu4ndpdtyn2lvdxo6b4e').
I cannot reduce the Spack installation paths, but I think that creating a Spack environement view (a Spack facility to group packages and show them in a different path) can work as a workaround if I replace the long paths in DSSATPRO.L48 and run_dssat with the paths in the view.
Thanks again and I will be on alert about the fix in DSSAT :-)
E
[1] Spack https://spack.io https://github.com/spack/spack

Just boosting this issue. When working with DSSAT on HPC machines, it becomes really problematic. Using <IP_ADDRESS> and still run into the issue.

Hi @frostbytten!
Yes, indeed. It is in my list to get this done and I am still trying to find time to work on this.
Thank you!

@frostbytten are you having this issue with all the models or just the CROPSIM legacy models (CSCER, CSCAS, CSYCA)? I know @fabiooliveira72  had a version of the model without that issue but it is outdated, @fabiooliveira72  do you want some help from me?

Hi @lpmorenoc!
Yes, it is very outdated and when we move to this it will be merged into develop ASAP, because it is a major issue. Yes, I will need help to test it! I will let you know.
Thank you!

@fabiooliveira72 Is there any news regarding this issue?
I was recently trying to create a nix package for DSSAT. But I'm encountering this exact issue.
It fails at loading files like CO2047.WDA, because the load path gets truncated.
I found that many PATH variables were indeed set as CHARACTER*80. If there is any news around this issue I'm very interested.


Expansion Items

Provide a way for users to mark expansion items. If possible, any specific information about how expansion items are prioritized should be handled by the user-defined priorities function.

Blocked by #3

This should be able to be implemented easily by the end-user by adding a column to the assets table and then implementing that change in a priorities function. This is not necessary for completing the core of the model or for a reasonable demonstration. Thus, I am closing this issue.
Providing built-in support for features like this may be re-added in a later phase of the project.


Feedback to DLR

Units in output Scalars.csv template
Storage capacities seem to have a wrong unit (charge/discharge for comparison):

UseCase
Region
Modell
Year
Parameter
Unit

FlexMex1_2c
AT
oemof
2050
Storage_Capacity_Electricity_LiIonBatteryCharge
MW

FlexMex1_2c
AT
oemof
2050
Storage_Capacity_Electricity_LiIonBatteryDischarge
MW

FlexMex1_2c
AT
oemof
2050
Storage_Capacity_Electricity_LiIonBatteryStorage
MW GWh

Make separator in input data consistently comma or semicolon.

This has been fed back to DLR and corrected.

This has been fed back to DLR and corrected.


在IntersectionObserver  的回调函数中,set 响应式绑定值时无效(set reactive value in the IntersectionObserver's callback not work, while which is binding with element)

Vue version
3.2.38
Link to minimal reproduction
https://stackblitz.com/edit/vitejs-vite-upumrk?file=src/App.vue
Steps to reproduce
滚动页面到底部，看见红色border矩形元素时, 应该触发 “refresh” 这个函数
What is expected?
当响应式值变量绑定指 Dom 元素时， IntersectionObserver 的回调函数中触发变动时, 值应当更新， 视图应当发生变化。
What is actually happening?
IntersectionObserver 的回调函数中触发变动时,  当响应式变量绑定至 元素，且这样去改变时
 bindKey.value = new Date().getTime().toString();

refresh 函数将不会触发，且视图不会更新。
System Info
System:
    OS: Linux 5.15 Ubuntu 22.04.1 LTS 22.04.1 LTS (Jammy Jellyfish)
    CPU: (12) x64 Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz
    Memory: 12.24 GB / 31.26 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 16.16.0 - ~/.nvm/versions/node/v16.16.0/bin/node
    Yarn: 1.22.19 - /usr/bin/yarn
    npm: 8.11.0 - ~/.nvm/versions/node/v16.16.0/bin/npm
  Browsers:
    Chrome: 105.0.5195.125
    Firefox: 105.0.1
  npmPackages:
    vue: ^3.2.38 => 3.2.38

Any additional comments?
No response

It works fine without v-animate. see playground

It works fine without v-animate. see playground

seems not work with the playground you link .

What is ur expected?

What is ur expected?

this only trigger once while loaded page, the refresh funciton should call every time while the page scroll to the bottom. you can comment  the line6 bindKey.value=xxxx to see how "trigger" log out, that should be the normal action.

ok, I see.
every time bindKey changed target.value will be set as a new element.
So, you need to observe the new element again.

Thanks that you’ve solved my puzzle
获取 Outlook for iOShttps://aka.ms/o0ukef

发件人: edison @.>
发送时间: Tuesday, September 27, 2022 11:39:07 AM
收件人: vuejs/core @.>
抄送: Zhongyi Sun @.>; Author @.>
主题: Re: [vuejs/core] 在IntersectionObserver 的回调函数中,set 响应式绑定值时无效(set reactive value in the IntersectionObserver's callback not work, while which is binding with element) (Issue #6762)
ok, I see.
every time bindKey changed target.value will be set as a new element.
So, you need to observe the new element again.
―
Reply to this email directly, view it on GitHubhttps://github.com/vuejs/core/issues/6762#issuecomment-1258926573, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKSU6B3LQGNH3D4DZ27QP4DWAJT5XANCNFSM6AAAAAAQWJZZKE.
You are receiving this because you authored the thread.Message ID: @.***>


Docker Registry Added via Rancher UI Missing Auth Field

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

add custom docker credential via the UI

Result:
It is missing the auth field. It seems that for a short period of time this was what kubectl did as well, but was fixed in 1.13.2.
The problem is that there are tools like https://github.com/fluxcd/flux/ that expect the auth field to be set once it decodes the base64 of the docker registry secret.
Other details that may be helpful:
To work around I had to add docker registry credentials to multiple namespaces using the CLI.
Environment information

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

Dupe of https://github.com/rancher/rancher/issues/19177


[build] Improve release process

Automate more of the release process
Co-authored by @animelover1984
Co-authored by @nihil-admirari
Closes #823, #385
Test: https://github.com/pukkandan/yt-dlp-dev/releases/tag/2<IP_ADDRESS>

@nihil-admirari The SHA256 changes from #999 have been cherrypicked into this PR


Refactor vendor publish and Artisan commands to prevent errors

At the moment php artisan filament-media-manager:install does not publish the Spatie media database table migration file
Replace custom artisanCommand method with direct \Artisan::call calls for better readability and maintainability. Ensure the 'vendor:publish', 'migrate', and 'optimize:clear' commands are executed directly using \Artisan.

Fresh Laravel and Filament installation
When I run php artisan filament-media-manager:install I get the error

 Illuminate\Database\QueryException

  SQLSTATE[HY000]: General error: 1824 Failed to open the referenced table 'media' (Connection: mysql, SQL: alter table `media_has_models` add constraint `media_has_models_media_id_foreign` foreign key (`media_id`) references `media` (`id`) on delete cascade)

  at vendor/laravel/framework/src/Illuminate/Database/Connection.php:825
    821▕                     $this->getName(), $query, $this->prepareBindings($bindings), $e
    822▕                 );
    823▕             }
    824▕
  ➜ 825▕             throw new QueryException(
    826▕                 $this->getName(), $query, $this->prepareBindings($bindings), $e
    827▕             );
    828▕         }
    829▕     }

Same issue (https://github.com/tomatophp/filament-media-manager/issues/15)

Summary by CodeRabbit

Refactor

Improved the execution of commands in the application by utilizing standard Laravel methods for better clarity and consistency.

hi @mvd81 thanks for this miss config fix.


avoid updating tor onion when not set, avoid copyingto clipboard too

utACK 455f29c

ACK d505cb9

thanks for the ack but it has been a while since I tested this PR and I don't feel as confident as I did


Update Readme - Add Mentions

I had to do a bit of research/play around to figure out how mentioning works.  I updated the readme to add mentioning, maybe it saves someone else a bit of time.

Thanks!


Loading svg from stream does not work

Is loading svgs from stream already supported?
I was trying to load SVG from string, but it does not work:
var myImg = @"<svg    xmlns:svg=""http://www.w3.org/2000/svg""    xmlns=""http://www.w3.org/2000/svg""    version=""1.0""    width=""28""    height=""28""    id=""checkbox"">   <defs      id=""defs7"" />   <path      d=""M 11.94,20.25 8.7,13.64 C 7.5836008,11.362408 8.7449524,11.954942 9.234963,12.670011 12.802978,17.461386 11.781076,19.309624 14.75,13.24 L 20.707,1.0616 C 21.19746,0.0424868 21.563475,1.05578 21.049,2.27 l -6.488,17.07 c -0.381549,1.003861 -1.786,2.05 -2.621,0.9 l -10e-4,0.005 10e-4,0.005 z""      id=""tick""      style=""fill:#440000"" />   <rect      width=""19""      height=""19""      x=""4.5""      y=""4.5""      id=""box""      style=""fill:none;stroke:#000000;stroke-width:1;stroke-opacity:0.33000004"" /> </svg>";
FFImageLoading.ImageService.Instance                               .LoadStream(ct => Task.FromResult<Stream>(new MemoryStream(Encoding.Default.GetBytes(myImg))))                               .Into(myImageView);
Used packages:
<package id="Xamarin.FFImageLoading" version="2.2.6-pre-241" targetFramework="xamarinios10" />   <package id="Xamarin.FFImageLoading.Svg" version="2.2.6-pre-241" targetFramework="xamarinios10" />

I think you need to wrap this in a SvgImageSource. Not sure how exactly this would look.

Adding WithCustomDataResolver solved issue.
Full code:
var svgString = @"<svg...";
			{
				var sw = new StreamWriter(ms, new UnicodeEncoding());
				try
				{
					sw.Write(svgString);
					sw.Flush();//otherwise you are risking empty stream
					ms.Seek(0, SeekOrigin.Begin);

					ImageService.Instance
						   .LoadStream(ct => Task.FromResult<Stream>(new MemoryStream(Encoding.Default.GetBytes(svgString))))
						   .LoadingPlaceholder(placeHolderPath)
						   .WithCustomDataResolver(new SvgDataResolver(64, 0, true))
						   .WithCustomLoadingPlaceholderDataResolver(new SvgDataResolver(64, 0, true))
				           .Into(imageView);
				}
				finally
				{
					sw.Dispose();
				}
			}```

Thanks! :)


Add and/or reduce support to VMLA

Handles the tf.math.reduce_any and tf.math.reduce_all operations.
Added a reduce_test.py file to check all reductions.

@phoenix-meadowlark is there a pithier way to write TF tests now?

Yes, though all of these tests are auto-generated by https://github.com/google/iree/pull/3826 and I'll delete these tests in a merge commit as soon as they land, so there's probably not much point in changing them 😅
It does make writing tests like these a lot less tedious though. See:

docs
concrete example

Yes, though all of these tests are auto-generated by #3826 and I'll delete them in a merge commit as soon as they land, so there's probably not much point in changing them
It does make writing tests like these a lot less tedious though. See:

docs
concrete example

I assume you feed random data as an input? For min/max/sum I can see this working but guaranteeing coverage on binary operation seems a little trickier.

Yes, though all of these tests are auto-generated by #3826 and I'll delete them in a merge commit as soon as they land, so there's probably not much point in changing them
It does make writing tests like these a lot less tedious though. See:

docs
concrete example

I assume you feed random data as an input? For min/max/sum I can see this working but guaranteeing coverage on binary operation seems a little trickier.

Good point! You can specify input_args as well, so for any and all I'll add tests of all true and all false respectively.


Recommended way to set ENABLE_PREFIX_DELEGATION

Description
The amount of pods per node is limited by the vpc cni addon, but there is a feature to increase the limit to something useful by setting "ENABLE_PREFIX_DELEGATION" and "WARM_PREFIX_TARGET" in the EKS cluster.
What is the recommended way to do this? I see other EKS modules that simply fire up a kubectl and set the settings, but that isn't very elegant (plus local-exec won't work using TFcloud).
info
More info can be found in this blog article

Unfortunately, that is the current method for enabling this functionality. You can refer to the example I provided here that demonstrates how to achieve this in Terraform

closing for now since its outside the scope of this module

Description
The amount of pods per node is limited by the vpc cni addon, but there is a feature to increase the limit to something useful by setting "ENABLE_PREFIX_DELEGATION" and "WARM_PREFIX_TARGET" in the EKS cluster.
What is the recommended way to do this? I see other EKS modules that simply fire up a kubectl and set the settings, but that isn't very elegant (plus local-exec won't work using TFcloud).

There seems to be a 3rd-party provider that makes it nicer...
(A 3rd-party provider is not ideal though)


Adding browser-sync to the prototyping kit.

This PR is to replace #144 and #149 but still in response to issue #84.
After discussion with @joelanman I've reverted to adding a callback to the findAvailablePort function and then start browser-sync in server.js (or not if in 'production'). I've also incorporated Joe's updated browser-sync config options into this new PR.
(Only tested on MacOSX 10.11.4 so far though)

nice, but the terminal output looks a bit confusing:

do you think we can make it cleaner/simpler for our users?

logLevel: "error" seems to hide that output, and then we can replace our own "listening on port 3000" with "listening on port 3050" etc
      browserSync({
        proxy:'localhost:'+port,
        port:port+50,
        ui:false,
        files:['public/**/*.*','app/views/**/*.*'],
        ghostmode:false,
        open:false,
        notify:false,
        logLevel: "error"
      });

@joelanman good idea, I've updated it.

great! It's a tiny thing, but I wonder if should set the kit to run on port 2950 (config.port-50), then browser-sync runs on the config port of 3000. Otherwise config doesn't match where you "should" be looking at the kit, and people are going to have to learn a new port, 3050.
I've checked online and can't see anything obvious that runs in this range (2950 - 3000)

I see your point. I think I've managed that. Would appreciate a sanity check; for some reason it took me a little while to get my head around how to do it. :)
My only worry here is that findAvailablePortwon't be checking 2950. It should work because legacy kits will be running on >=3000 and new browser-sync kits will have browser-sync running on those ports but if, for some reason, someone does have something on ports 2950-2999 things will break in a way which might not be dead easy to spot (given we're obscuring the real port now).
I wonder whether it might be more transparent to acknowledge browser-sync is running and sort of say "To use browser-sync, use  instead". People who don't know/care about browser-sync could use either URL and they'll get what they expect, and people familiar with browser-sync will understand the purpose of the second URL.

@joelanman Take a look at at this last commit. I've gone with starting at 3000 and just putting browser-sync on port+1. I've included an extra message below the normal one like:
Listening on port 3000     url: http://localhost:3000
Browsersync on port 3001   url: http://localhost:3001

Any new kit starting up will check both these ports and end up picking 3002 but at least it will have checked both ports and so isn't assuming an empty port without checking.
I know this is a move away from the seamlessness that you're advocating above but I think there's value here in showing the seams! :-)

I'll have a think about an approach that can work, but just wondering what the value is showing the seam here? If someone is new to programming and the kit, what should they do after running npm start? If they were to ask why they have two versions?

Hey @joelanman. OK I've reverted that last change so we've got express listening on port 2950 and Browsersync on port 3000, with no mention of it in the output. If you're happy to go ahead with that then that's cool.


Feature Request - Auto Anno text if marked

Is it possible to extend this component so that if I mark I word with my courser,
it gets automatically annotated by the class I chose in advance?
Just an ide I wanted to share. I'd really much like it.

Hi @ChrisChross , thanks for posting. I don't really understand the idea, though. Can you provide some more information?

Hi @tvst ,
you can check https://prodi.gy/demo.
The idea is simple: you choose a label or class e.g. Person and than click on the person's name in the text.
Consecutive the text gets marked with the label.


How to sum digits in a string?

I've tried the following:
local data = "ms0010110"
data:gmatch("%d"):sum() -- runtime error
sum(data:gmatch("%d")) -- runtime error
data:gmatch("%d"):reduce(operation.add, 0) -- runtime error

-- but this works fine
local total = 0
for digit in data:gmatch("%d") do
  total = total + digit
end

What have I misunderstood?
For some background info, this script is just parsing the various messages reported over the serial line of some old motion controllers. If the result is > 0 we know that there are still axes reporting activity, otherwise we can proceed with whatever foobarbizbaz needs to happen once the motors are positioned.

string.gmatch() does not return an iterator triplet, only a function:
> return data:gmatch("%d")
function: 0xf2c2b0
>

I don't know why you can still use for .. in with it, but it seems all fun functions expect iterator triplets.
The functional way would be to use filter instead of gmatch:
local fun = require("fun")
local data = "ms0010110"
fun.filter(function (x) return x >= "0" and x <= "9" end, data):sum()

Also gmatch makes C calls which are not compiled by LuaJIT


Add Humanizer.Core

This is https://github.com/Humanizr/Humanizer (different from https://github.com/Humanizer/Humanizer !)
Humanizer shows up as a dependency of ASP.NET Core and roslyn-analyzers. This tries to fix that. Supposedly it also ships with the SDK.
Fixes: #1767

Looks like it isn't quite building the .Core package (the prebuilt is still there):
  [00:52:11.33] Building 'humanizer'...done
  New NuGet package(s) after building humanizer:
    -> Humanizer 2.2.0
  roslyn using package version properties saved at /src/artifacts/obj/x64/Release/PackageVersions.props.pre.roslyn.xml

I guess we need to pack https://github.com/Humanizr/Humanizer/blob/v2.2/NuSpecs/Humanizer.Core.nuspec in particular... looks like it's normally done directly by the repo's CI with nuget.exe: https://github.com/Humanizr/Humanizer/blob/v2.2/appveyor.yml#L33. 😕
I'm not familiar with a good way to do something like nuget pack--not sure if dotnet nuget pack or something works at this point. If it ends up with the same content, maybe we can just set the package id to Humanizer.Core in the current csproj and keep repos/humanizer.proj the same. /cc @dseefeld @crummel

Thanks, I was able to put together a dotnet pack incantation to build using the .nuspec file.
Now that I see that Humanizer.Core packages are produced:
./packages/restored/humanizer.core/2.2.0/humanizer.core.2.2.0.nupkg
./artifacts/src/Humanizer.b30550eed103a6970d8465fe7c5c16300b70be81/src/Humanizer/bin/Release/Humanizer.Core.2.2.0.nupkg
./artifacts/obj/x64/Release/blob-feed/packages/Humanizer.Core.2.2.0.nupkg

Strangely, as you can see in the output, something in roslyn downloads Humanizer.Core 2.2.0 again, even though it's in the blob feed

Nice, I think that command seems reasonable.
I'm not quite following what's pointing to a download happening. If it's about the nupkg in packages/restored/, that seems normal to me, NuGet restoring Humanizer and placing a copy of the restored nupkg in the package cache (whether downloaded or from a local source).
I don't really know why NuGet always does that, but it's convenient for us. We use it to do a check for this exact problem. 😄 We look for any package in the package restore cache that has the same id/version as a nupkg in the source-built blob feed. If there are any, we make sure it's byte-for-byte identical, as proof that the source-built version of the package is what ended up being used: https://github.com/dotnet/source-build/blob/master/tools-local/tasks/Microsoft.DotNet.SourceBuild.Tasks.XPlat/GetSourceBuiltNupkgCacheConflicts.cs. I'd expect that to throw a decently clear warning if you have a restore happening from the wrong feed here.

I'm not quite following what's pointing to a download happening. If it's about the nupkg in packages/restored/, that seems normal to me

Oh. I see. Thanks, that clears things up. The nuget packages are indeed bit-by-bit identical:
$ sha256sum $(find -iname 'humanizer*nupkg')
2255dc5c64cd27ca8d926974801fec0acff7a4ca219d99d2dbd013f093b54518  ./packages/restored/humanizer.core/2.2.0/humanizer.core.2.2.0.nupkg
2255dc5c64cd27ca8d926974801fec0acff7a4ca219d99d2dbd013f093b54518  ./artifacts/src/Humanizer.b30550eed103a6970d8465fe7c5c16300b70be81/src/Humanizer/bin/Release/Humanizer.Core.2.2.0.nupkg
2255dc5c64cd27ca8d926974801fec0acff7a4ca219d99d2dbd013f093b54518  ./artifacts/obj/x64/Release/blob-feed/packages/Humanizer.Core.2.2.0.nupkg


Fix mkdocs relpath

After https://github.com/rtfd/readthedocs.org/pull/5377/
The code calling the config module is in charge of getting the full
path.

I encountered this error here. I was able to reproduce it on the same repo locally. This PR did fix the issue.

I also checked all the usages of self.yaml_file, they are good

@stsewd do you think this should be hotfixed today?

@ericholscher yeah, it affects people using mkdocs with a rtd configuration file. Which I think are most of our users now


Return isolated windows from Window* methods

This allow tests from #653 to pass and fix #652

@atifaziz can you review this please.
Fix #652

The only trouble with the new correction is that it now eagerly allocates and prepares the next window

this should be fixed in #656

And when the sequence reach its end, all allocated array have been passed to the caller

How do you know you'll reach the end of the sequence. The caller is in control of asking the next window and may stop iteration earlier due to some condition.

And when the sequence reach its end, all allocated array have been passed to the caller

How do you know you'll reach the end of the sequence. The caller is in control of asking the next window and may stop iteration earlier due to some condition.

It's an hypothesis.
For a partially enumerated sequence both algorithm instantiate the same number of array  (of the size of the window).
For a fully enumerated sequence your algorithm instantiate one array more than the actual code.

@atifaziz I do a re-read of the code

I re-read as well, and in detail this time, and it looks good! 💯


Hue buttons weird acting

I have 4 Hue buttons and all of a sudden all of them began to do a weird thing.
The buttons are set to turn on/off one or more lights (depends on the room they are in), using an if statement in the singe press action.
When I press a button the related lights turns on and off right away, this happens multiple times before they stay On. Same happens when I press the button to turn off the related lights (they go back On after one or two seconds).
I've tried to:

build the button action from scratch
reinstall the Hue plugin
unpair the buttons from the conbee and pair them back
reboot all of my HomeKit hubs (HomePod minis and Apple TVs)

The logs in HomeBridge shows only a single button press.
What could cause this? And how can I solve it?
Thanks a lot!

I have same issue with Hue Dimmer Switch + homebridge/conbee. Tried using wait in shortcut (thinking second trigger will pass to same if condition), but it looks like the second shortcut is triggered after the first completes, not running parallel.

Hm, looks like my original reply didn’t stick, sorry for that.
I’ve seen the same issue a couple of times, albeit with an IKEA Trådfri remote controller.  Homebridge Hue registers the button event once, and notifies HomeKit once, but somehow, HomeKit triggers the automation twice, a second or so apart.  As far as I can tell, this is an issue with HomeKit itself, in particular with the iCloud sync between the HomeKit runtimes on your IDevices and home hubs.  I think the second trigger is the home hub receiving the notification over iCloud, but not recognising it has received it already.
In my cases restarting Homebridge (forcing the home hubs to reconnect to Homebridge) remedied the situation.  I have an Apple TV 4K and a HomePod mini.  HomeKit automations tend to become unreliable, when the HomePod mini is the active home hub.  Also, occasionally my iPhone depletes its battery charge in a couple of hours, with Home consuming over 80%, being constantly active in background, and the iPhone getting warm, strengthening my hunch that it’s somehow related to the iCloud sync.  I’m afraid all I can do is hope the iOS 16 and family finally fix stability issues on large HomeKit installations.


Generatable Task URLs are broken in labelstudio 1.6.0

Describe the bug
Prior to labelstudio 1.6.0, given a task id and a project id, I used to be able to generate a valid url that opens up that task in labelstudio.
https://<labelstudio_url>/projects/<project_id>/data?task=<task_id>

This redirects to:
https://<labelstudio_url>/projects/<project_id>/data?task=<task_id>&tab=<lowest tab id in this project>

And the task is just blank. :(

In our case, tab 363 doesn’t have any filters so I’m not sure why it shows as blank anyway.
Expected behavior
The task/image loads normally.
Environment (please complete the following information):

Client OS: macOS
Client Browser: Brave | 1.45.113 Chromium: 107.0.5304.62 (Official Build) (arm64)
Label Studio Version: heartexlabs/label-studio:1.6.0

Additional context
Ideally we'd like to avoid workarounds that involve fetching the proper task id(if that's even possible), because calling the labelstudio api for each task will be time-consuming and the urls won't work once that tab is removed.
Here's the related conversation in labelstudio's slack workspace

It's a bug, I've created a ticket, hope we will fix it soon.

Please check there latest develop branch, it should be fixed there.


Idea of new rule: use slash instead of backslash for image path

Correct:
![foo](images/foo.jpg)

Not recommended:
![foo](images\foo.jpg)

What's the state of this rule?  It seems that markdown document written in typora use backslash for image path, it make the image broken in gitlab.

It sounds like a fairly straightforward rule to implement if anybody wants to do so for npm or as a custom rule in their repository. I have not added it to the core library so far.


Cluster-Autoscaler: fix delete taint failing

It was using old node version (which in general is always going to be outdated, as we've likely modified it by adding delete taint).
@mwielgus

This change is

/lgtm
/approve


Fix reconnect

Because the error function has the call
seneca.fail({code: 'entity/error', store: name}, cb)
it will never retry connection as the following code is never executed.

fixed with latest PR


added menc event handling and replaced zrtp module zrtp command with two commands

Based on Alfred's suggestion, added menc_event handler. Call event is still CALL_EVENT_MENC and the type is in the parameter.  Should there be separate CALL_EVENT_SECURE, CALL_EVENT_VERIFY_REQUEST, and CALL_EVENT_PEER_VERIFIED events instead?
-- Juha

Great, many thanks!
I think this is looking much better. It should be enough with one event handler
for the session level I think. Other protocols can wait for all media lines to be secure
and then call the session event handler.
If needed in the future, additional events can be added.

Alfred E. Heggestad writes:

I think this is looking much better. It should be enough with one
event handler for the session level I think. Other protocols can wait
for all media lines to be secure and then call the session event
handler.

I didn't quite understand the above.  What kind of change you propose to
the pull request?
-- Juha

Closing due to conflicts.  Will create a new one.


Extending Roles Workflow Activities with "Unassign Role" Activity

I have to manage a scenario in which we should Assign/Unassign Roles automatically based on the update of the value of a particular Field (of the User). We designed to implement that scenario using workflows. No problem for assigning the role because we have the approriate Task in the Workflow module but what is missing is something like an "Unassign Role" ActivityTask. So what I suggest is to implement it, unless there is another solution. I mean a "simple" solution, not using Decision Activity or similar.

I am working on it


🌐 [i18n-KO] Translated guides/model_cards.md to Korean"

What does this PR do?
Translated the guides/model_cards.md file of the documentation to Korean.
Thank you in advance for your review.
Part of https://github.com/huggingface/huggingface_hub/issues/1626
Before reviewing

[x] Check for missing / redundant translations (번역 누락/중복 검사)
[x] Grammar Check (맞춤법 검사)
[x] Review or Add new terms to glossary (용어 확인 및 추가)
[x] Check Inline TOC (e.g. [[lowercased-header]])
[x] Check live-preview for gotchas (live-preview로 정상작동 확인)

Who can review? (Initial)
Team PseudoLab, may you please review this PR?
@jungnerd, @heuristicwave, @harheem, @cjfghk5697, @seoulsky-field, @nuatmochoi, @boyunJang, @SeungAhSon, @seoyoung-3060, @junejae
Before submitting

[x] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[x] Did you read the contributor guideline,
Pull Request section?
[ ] Was this discussed/approved via a Github issue or the forum? Please add a link
to it if that's the case.
[x] Did you make sure to update the documentation with your changes? Here are the
documentation guidelines, and
here are tips on formatting docstrings.
[ ] Did you write any new necessary tests?

Who can review? (Final)

@jungnerd, @heuristicwave May you please review this PR?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

@Wauplin I've reviewed this translation, please merge it.
I have a question, Is there a way to make sure my review commit is reflected in Live Preview?

@Wauplin I've reviewed this translation, please merge it. I have a question, Is there a way to make sure my review commit is reflected in Live Preview?

@Wauplin This PR is ready to merge!
By the way, @heuristicwave is Jihun Lim, co-leader of this team.🤗

Great! Thanks for the ping! :)
Sorry @heuristicwave I missed the ping 4 days ago but for sure I can merge! :tada:
Thanks @SeungAhSon @heuristicwave @jungnerd!

I have a question, Is there a way to make sure my review commit is reflected in Live Preview?

Yes and no. The problem is that I need to click on "Approve and Run" to run the CI which makes the live preview active again. Otherwise the CI won't run. Problem is that I need to click on it after every commit to make the live preview up to date. Given the number of PRs and commits I kinda skipped it but if you want I can go back to it let's say once per day.


Atom.exe command-line output cannot be redirected to a file/pipe

Description
On Windows atom.exe command-line does not respect redirecting output to a file (or pipe).
Steps to Reproduce

Open command-line.
Type atom.exe -v -w >out.txt
Check contents of out.txt

Expected behavior: out.txt contains Atom version.
Actual behavior: out.txt is empty and Atom version is printed to the console.
Versions
1.5.3

This is due to Electron directly attaching to the console. The behavior can be suppressed by setting OS=cygwin (< Electron 0.36.x) or ELECTRON_NO_ATTACH_CONSOLE=true (> Electron 0.36.x).

Thanks for sharing the solution!


Add web request functionality to datadog send functions

Insert web request functions analogous to sendevent and sendmetric
Provide the user with option between using port (datadog agent) or web
request functions
Create the api key and datadog url environment variables
Closes #254

Testing Evidence
Output on datadog of sendevent function via datadog agent ('Old') and web request ('New Function'):

Output on datadog of sendmetric function via datadog agent and web request - first metric sent using agent, second sent using web request:

Environment variables successfully called by file:


Fix port closing in CommunicationBase

Overview

The SILS port of the I2C emulated components is not closed properly.
If the CommunicationBase class is copied, double freeing of memory can occur.

Issue
https://github.com/ut-issl/s2e-core/issues/66
Details
Description

In the destructor of ObcI2cTargetCommunicationBase for SILS test, the function CloseComPort for UART is used when the function I2cCloseComPort for I2C should be used.
In UART and I2C CommunicationBase, memory is freed in the destructor. If CommunicationBase class is copied, double freeing of memory can occur.

Validation results
Link to tests or validation results.
Scope of influence
The behavior of CommunicationBase will be change.
Supplement
NA
Note

If there are related Projects, tie them together.
Assignees should be set if possible.
Reviewers should be set if possible.
Set priority label if possible.

@200km レビューお願いします。


Link text for inline content fails to inline MultiMarkdown-style image references

Followup for #407:
With newly landed fixes, the following example works correctly in ParserEmulationProfile.MULTI_MARKDOWN:
[![][moon]](/uri)

[moon]: moon.jpg

yields:

However, MultiMarkdown format image references with width and height included do not.
[![][moon]](/uri)

[moon]: moon.jpg width: 80px height: 90px

yields:

![][moon]

[moon]: moon.jpg width: 80px height: 90px

MultiMarkdown-style image references that include width and height metadata fail to parse the inner content as an ImageRef.
More info:
This repro is not quite as crystal clear as the previous one, because out of the box ParserEmulationProfile.MULTI_MARKDOWN does not render the correct HTML for the following non-inline content case:
![][moon]

[moon]: moon.jpg width: 80px height: 90px

yields:

![][moon]

[moon]: moon.jpg width: 80px height: 90px

It does, however, parse this as an ImageRef, which has been good enough to get me to the goal line in my project.

@jingibus, parser family currently affects mostly list item nuances particular to a family, not all the possible extensions present in the markdown parser.
MultiMarkdown has a lot of extensions which are not implemented or would require writing new extensions.
As a workaround you can use the attributes extension then you can add any attributes to almost any node. For references the attributes need to be specified after the definition to keep them away from the reference definition line.
![][moon]

[moon]: moon.jpg
{width=80px height=90px}

Renders as:

Thank you for the information. I have an opportunity to "clean up" Markdown source when it's imported into the system, so if the attributes will emit cleanly that workaround should serve.
I may have time to do the extensions work as well if it's not too much hassle.


workflow: read OPA version from go.mod

Just reducing the manual work required when updating the OPA version... 🤞

Whenever I trust auto-complete, it's wrong.


Add pod-network-cidr flag on kubeadm init.

This PR updates the Vagrantfiles to reflect the changes in #649,
where kube-proxy has to learn the Pod CIDR.

Coverage decreased (-0.03%) to 75.216% when pulling 1975c73a7946cfb367b4fb8a0975d695598dd720 on brecode:vagrant-proxy into 1d28907144434b403f5a82e138759c2e2e3bc27b on contiv:master.


Remove if UNITY_EDITOR check

Overview
GridObjectCollection was throwing errors on device because assets were being loaded without the asset version in runtime but saved with the asset version. See comment from @gilbdev  in #6938. Thank you for the help!
Changes

Fixes: #6938

/azp run


Copy of "Fix deadlock where opening database fails"

Applied the patch proposed in
https://github.com/RaRe-Technologies/sqlitedict/pull/107
As a backup until the original author of the repo #107 decides to merge their changes.
If the author doesn't merge their changes soon, I created this PR, to get these changes merged in sooner.
Don't want to step on any toes here :)

Closing as the original author has pushed their changes and the original PR can now be merged

Closing as the original author has pushed their changes and the original PR can now be merged


fix: Avoid leaks when using PictureRecorders

Description
When using PictureRecorder, the Picture object that it creates needs to be properly disposed after it is no longer used.
Checklist

[x] The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs: etc).
[x] I have read the Contributor Guide and followed the process outlined for submitting PRs.
[-] I have updated/added tests for ALL new/updated/fixed functionality.
[-] I have updated/added relevant documentation in docs and added dartdoc comments with ///.
[-] I have updated/added relevant examples in examples.

Breaking Change

[-] Yes, this is a breaking change.
[x] No, this is not a breaking change.

Related Issues

It would be really nice to be able to have a custom lint rule that checks so that toImage isn't used, but I don't think that is possible (or not worth the amount of time it would take to fix that at least).


CICD Multi Account or Multi Region Deployment Fails

Describe the bug
When trying to deploy multi env, multi account or multi region cicd pipelines using CICDPipelineStack, the cdk synth fails at pipeline.synth() step with the error "RuntimeError: Error: Pipeline stack which uses cross-environment actions must have an explicitly set region".
How to Reproduce
pipeline = CICDPipelineStack(
    app,
    id=pipeline_name,
    environment_id="cicd",
    pipeline_name=pipeline_name,
    env=cdk.Environment(
        account=cicd_params.get_config_attribute("account"),
        region=cicd_params.get_config_attribute("region"),
    ),
)
pipeline.add_source_action(repository_name=repository_name)
pipeline.add_synth_action()
pipeline.build_pipeline() # type:ignore
pipeline.add_stage(
    stage_id="dev-storage",
    stage=DataStorageStage(
    app,
    env=cdk.Environment(
        account=storage_params.get_config_attribute("account"),
        region=storage_params.get_config_attribute("region"),
    ),
    environment_id="stor",
    mode=mode,
    compute_params=compute_params,

),
)
pipeline.add_stage(
    stage_id="dev-compute",
    stage=DataComputeStage(
    app,
    environment_id="comp",
    mode=mode,
    storage_params=storage_params,
    env=cdk.Environment(
        account=compute_params.get_config_attribute("account"),
        region=compute_params.get_config_attribute("region"),
    ),
),
)

pipeline.synth()
#######################

app.synth()

If you use the cross account cross region pipeline example with the above code changes and then run cdk synth you can go to cdk.out and check the assembly-comp and assembly stor manifest.json will take in the correct region and account from ddk.json, likewise if you check the manifest.json for the pipeline, you will see that even though we pass environment it will be unknown, i think ddk ts version doesnt pass env to the top most inherited stack, this issue was not there in 0.6.2 where we passed env (line 154 in super init) https://github.com/awslabs/aws-ddk/blob/main/core/aws_ddk_core/cicd/pipeline.py
Expected behavior
It should synthesize correctly with supplied env (account and region)
Your project
No response
Screenshots
No response
Environment
Provide your `pip list` output, particularly the version of the AWS DDK library you used. Providing this information may significantly improve resolution times.

OS
Mac
Python version
3.9
AWS DDK version
1.0.0b
Additional context
No response

Tested with current build of #280
Simple code for a pipeline with CICD pipeline deploying into an external account...
import aws_cdk as cdk
import aws_cdk.aws_s3 as s3
from aws_ddk_core import CICDPipelineStack, Configurator

app = cdk.App()
cicd_params = Configurator(app, "./ddk.json", "cicd")
dev_params = Configurator(app, "./ddk.json", "dev")
dev_stage = cdk.Stage(
    app,
    "dev-stack",
    env=cdk.Environment(
        account=dev_params.get_config_attribute("account"),
        region=dev_params.get_config_attribute("region"),
    ),
)
stack = cdk.Stack(dev_stage, "foobar")
s3.Bucket(
    stack,
    "mybucket",
)

pipeline_name = "foobar"
repository_name = "foobar"

pipeline = CICDPipelineStack(
    app,
    id=pipeline_name,
    environment_id="cicd",
    pipeline_name=pipeline_name,
    env=cdk.Environment(
        account=cicd_params.get_config_attribute("account"),
        region=cicd_params.get_config_attribute("region"),
    ),
)
pipeline.add_source_action(repository_name=repository_name)
pipeline.add_synth_action()
pipeline.build_pipeline() # type:ignore
pipeline.add_stage(
    stage_id="dev",
    stage=dev_stage,
)
pipeline.synth()
app.synth()


Make the frequency and bandwidth print with xmt.

Currently the frequency and bandwidth is printed every 10 sec. We should make it print with xmt.

https://github.com/upowerrobotics/ros2_fabric/pull/29


First step is error'ing and needs to be updated or add additional clarification to the process

$response = Invoke-WebRequest -Uri 'http://<IP_ADDRESS>/metadata/identity/oauth2/token?api-version=2018-02-01&resource=https%3A%2F%2Fvault.azure.net' -Method GET -Headers @{Metadata="true"}
RETURN:
Invoke-WebRequest : {"error":"invalid_request","error_description":"Identity not found"}
At line:1 char:13

$response = Invoke-WebRequest -Uri 'http://<IP_ADDRESS>/metadata/i ...

        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebException
FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

Just returns an error stating invalid request. This is a blocker from continuing and is the first step in the document. Are there any alterations needed to the link to conform to your specified Key Vault?
Thanks.
Zach

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

ID: b6ae37a8-0a93-e077-d15f-50d2d0d6aa99
Version Independent ID: 41e1b28a-704d-431c-5dc8-9cbf063f9cc3
Content: Use a Windows VM system-assigned managed identity to access Azure Key Vault
Content Source: articles/active-directory/managed-identities-azure-resources/tutorial-windows-vm-access-nonaad.md
Service: active-directory
GitHub Login: @daveba
Microsoft Alias: daveba

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

@wacsintegra We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Refine schema for the manifest CRD

As story discussed, we refined CRD schema which support "one manifest, multiple ops files".
For example, following cr.spec defines base manifest from configmap/bosh-manifest and applies two ops from configmap/bosh-ops and secret/bosh-ops-secret:
spec:
  manifest:
    type: "configmap"
    ref: "bosh-manifest"
  ops:
    - type: "configmap"
      ref: "bosh-ops"
    - type: "secret"
      ref: "bosh-ops-secret"

Resolver will get bosh-manifest from config map, secret or URL(ops file too) and follow ops order to resolve manifest. So secret/bosh-ops-secret will override configmap/bosh-ops operations if they have same ops paths.
And this PR also add more UTs to test resolver functionality.
Best,
@edwardstudy && @zhangtbj, IBM

Hi, @manno. I rebased and set tracker id to first commit.


Custom headers absent for monorepo continuous deployment

** Please describe which feature you have a question about? **
I am trying to add custom security headers. And adding customHeaders in amplify.yml works for traditional repo, but fails to add headers during monorepo deployment.
** Provide additional details**
This is my amplify.yml file:
version: 1
applications:
  - frontend:
      phases:
        preBuild:
          commands:
            - cd ../..
            - npm ci
            - npx lerna bootstrap --no-ci
            - cd packages/backend
        build:
          commands:
            - envCache --set stackInfo ""
            - amplifyPush --simple
            - cd ../..
            - cd $AWS_MONOREPO_APPROOT
            - npm run build
      artifacts:
        baseDirectory: dist
        files:
          - '**/*'
      cache:
        paths:
          - node_modules/**/*
      customHeaders:
       - pattern: '**/*'
         headers:
         - key: 'Content-Security-Policy'
           value: 'default-src self'
    appRoot: packages/backoffice

@okaluhina Can you please provide your App ID and region? I will start investigation this.

@hsspain thank you. App ID: d31kllttcnaaf0, region eu-west-1

Hi @okaluhina.  We've identified a bug here and are working on a fix.

Just to add to this, I'm also experiencing this issue when attempting to add a CORS policy with an Access-Control-Allow-Origin customHeader. Hopefully the fix is not far off.

Hi @okaluhina thank you for your patience. We have deployed a fix to the region your app is in. Can you please try adding custom headers again and let us know if your issue is resolved? Thanks!
(the fix will be deployed to all of our regions by the end of the week)

@Athena96 working like a charm, thank you.

Great! Going to close this issue, feel free to re-open if you face another related issue.


[5521] Do not show HESA trainees as incomplete with missing degree information

Context
This is because a lot of this information is optional over HESA. However, these trainees were still able to get a TRN, so we do not think we should be flagging this as incomplete, until we can make this information compulsory for 2024-2025.
Changes proposed in this pull request

Modify Submissions::BaseValidator so it ignores degree validation for HESA trainees
Data migration to recalculate Trainee#submission_ready

Guidance to review

Data migration affects about 300 trainees

Important business

[ ] Does this PR introduce any PII fields that need to be overwritten or deleted in db/scripts/sanitise.sql?
[ ] Does this PR change the database schema? If so, have you updated the config/analytics.yml file and considered whether you need to send 'import_entity' events?
[ ] Do we need to send any updates to DQT as part of the work in this PR?
[ ] Does this PR need an ADR?

NB: Please notify the #twd_data_insights team and ask for a review if new fields are being added to analytics.yml

 [M] Do not show HESA trainees as incomplete & allow them to be recommended for QTS if they are missing degree information


Error on save

Hello, I tried to add a Title to my comics and appear the error on save

I am not sure why exactly this is happening but I know where it is happening. I will push a new release shortly that will fix the issue.


MatroskaExtractor: fixed typo when determining 'rotationDegrees'

Changed 'projectionPosePitch' to 'projectionPoseRoll'.

I'm going to send this for internal review now. You may see some more commits being added as I make changes in response to review feedback. Please refrain from pushing any more substantive changes as it will complicate the internal review - thanks!


Update docs.neo.org - neo-python section

http://docs.neo.org/en-us/sc/getting-started-python.html
Instructions are outdated. Replace with current instructions from the neo-python readme, or simply link there and to the docs.

I think this has to be done by the neo team?

It can be a PR to the docs repo: https://github.com/neo-project/docs/blob/master/en-us/sc/getting-started-python.md

https://github.com/neo-project/docs/pull/448

Worked on the docs. Waiting on a review.
neo-project/docs#449

@metachris Neo Docs now point/link to theneo-python documentation. Perhaps this issue could be closed.

👍


tests: write unit tests for common.py

Fixes #72

@anujsinha3 Noted! I will probably remove then and update today evening!

Hey @anujsinha3, I have removed the extra checks I had in common.py, can you please review once?


fix: context create with 'use'

Signed-off-by: Keming<EMAIL_ADDRESS>
close #618

https://github.com/tensorchord/envd/issues/161#issuecomment-1129475975

It seems the API part is down.

I am merging it since the e2e does not break by this PR.


Exclude images from crate

Next time this crate is published to crates.io, this should make the crate around 26KB, instead of 312KB (checked with cargo package && ls -lh target/package/).

Well done!