Resolve syncing conflicts from master-sync-work to master

Pull request opened by OPS to resolve syncing conflicts from master-sync-work to master.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\v0kn-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\hamq-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\kkhg-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\xwte-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\1ups-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\4vba-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\ciqv-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\elbb-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\22pi-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot merge commit bb2a4f812ef0ae34be196c0f125322b8ab97475b in branch master-sync-work of repository https://github.com/OPS-E2E-PPE/azure-docs-cli-python into branch master (commit 4f20822fae8239cfbd88370b5331db4c66cf938f)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\l2da-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\jcv4-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\csix-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\ruzw-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\ixro-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\lokn-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\nylk-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\2xln-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\glvu-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\k3lw-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\eomy-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\s3bk-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\dd1o-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\ldgo-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\233k-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\aosi-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\3frk-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\tzzm-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\5ju5-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\aomd-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\zua3-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\ltey-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\iki2-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\t0yw-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\11uv-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\fxqa-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\5pxx-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\qlys-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\chrz-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\03uv-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\24vw-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\0vbv-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\zkft-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\ginx-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\uoqn-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\g0ay-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\wrko-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\ve4r-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\miy1-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\3te1-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\uufb-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\hhje-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\cf4g-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\sv5c-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\eukp-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\vbmj-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\gr2e-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\wmtt-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\psek-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\iao4-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\htlb-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\yyp4-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\b42d-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\ddzx-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\j1gl-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\nko3-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\llm0-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\ilux-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\mts0-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\orq4-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\xrhc-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\lj0d-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\pxqz-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\l2wb-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-cli-python, working directory: W:\et2b-s, target branch: master, target branch commit: 4f20822fae8239cfbd88370b5331db4c66cf938f, source branch: master-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

docs-ref-autogen/TOC.md
:white_check_mark:Succeeded
View

docs-ref-autogen/account.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/acr.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/acr/credential.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/acr/repository.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/acs.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/acs/dcos.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/acs/kubernetes.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/ad.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/ad/app.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/ad/group.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/ad/group/member.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/ad/sp.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/ad/user.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice/plan.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice/web.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice/web/config.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice/web/config/appsettings.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice/web/config/backup.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice/web/config/container.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice/web/config/hostname.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice/web/config/ssl.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice/web/deployment.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice/web/deployment/slot.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice/web/deployment/user.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice/web/log.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice/web/source-control.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/batch/node/file.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/cloud.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/disk.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/dla.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/dla/account.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/dla/catalog.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/dla/catalog/package.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/dla/catalog/table-stats.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/dla/catalog/table.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/dla/catalog/tvf.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/dla/catalog/view.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/dla/job.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/dls/account.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/documentdb.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/documentdb/collection.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/documentdb/database.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/feature.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/group.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/group/deployment.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/group/deployment/operation.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/image.pycliyml
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

docs-ref-autogen/TOC.md
:white_check_mark:Succeeded
View

docs-ref-autogen/account.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/acr.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/acr/credential.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/acr/repository.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/acs.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/acs/dcos.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/acs/kubernetes.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/ad.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/ad/app.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/ad/group.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/ad/group/member.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/ad/sp.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/ad/user.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice/plan.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice/web.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice/web/config.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice/web/config/appsettings.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice/web/config/backup.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice/web/config/container.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice/web/config/hostname.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice/web/config/ssl.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice/web/deployment.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice/web/deployment/slot.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice/web/deployment/user.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice/web/log.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/appservice/web/source-control.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/batch/node/file.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/cloud.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/disk.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/dla.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/dla/account.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/dla/catalog.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/dla/catalog/package.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/dla/catalog/table-stats.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/dla/catalog/table.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/dla/catalog/tvf.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/dla/catalog/view.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/dla/job.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/dls/account.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/documentdb.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/documentdb/collection.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/documentdb/database.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/feature.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/group.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/group/deployment.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/group/deployment/operation.pycliyml
:white_check_mark:Succeeded
View

docs-ref-autogen/image.pycliyml
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Edges are not created if vue-flow is placed in shadow dom

Hello!
I found a mistake in the code https://github.com/bcakmakoglu/vue-flow/blob/9ea87c878c327b7d99c75f657ee196172e2862aa/packages/vue-flow/src/utils/graph.ts#L38
It should be 'elementFromPoint' instead of 'getElementFromPoint'
getHostForElement always returns window.document now.
Because of this, edges are not created if vue-flow is placed in shadow dom (vue custom element).

Thanks for reporting! :)
You're right, I will release a fix asap

@mspostolov Do you require the fix soon? I could provide a release tomorrow if necessary :)

It will be great if you release tomorrow. Thanks for the quick fix!

@mspostolov I might have to defer the release to tomorrow because I would like to fix the snap grid issue as well before publishing - if that takes too long though I will still publish a release with this fix
Latest will be tomorrow, promise 😄

@mspostolov Fixed and released with 0.4.40


line break missing between stacked urls in sidefoot

looks like there may be spacing/formatting issues too
example:  /consumer-help/financial-resources-servicemembers/

@kurtw, should the sidefoot have the Related-Links molecule. It looks like that's why they are recreating.

I think that makes the most sense. I'll send up a change briefly.

@tnferrell The Related Links molecule is now in refresh. The links you've had problems with will have to be re-entered in that molecule to attained the desired result.


Get rid of dots

Recently been facing this issue. Whenever i click on the button a dot shows up. like the second button in the GIF

Hi @rahulbbit! Could you please tell me what OS and simulator you are using?
I can't seem to reproduce this bug while using Xcode 9.1 (9B55) and iOS 11 on any simulator device.
Thanks!

It magically disappeared. I just restarted XCODE

Thanks I hope that will be the end of them and they won't come back :)


Add backend user searching

As the number of users continues to grow, add user query searching on the backend and limit the number of returned users

I'm pretty sure this already exists in API repo


Cannot open a cordova project that was created using VS2013 Update 4 into Visual Studio 2015 Community Edition

Hi,
Cannot open a cordova project that was created using VS2013 Update 4 into Visual Studio 2015 Community Edition.
I get "his project is incompatible with the current edition of Visual Studio".
Any suggestions or workaround?

See the first item under
https://github.com/Microsoft/cordova-docs/blob/master/known-issues/known-issues-vs2015.md


updated to version 1.1

Change(s):

Updated OptimizationWorkbook.json file
Updated WorkbookMetadata file

Reason for Change(s):

Fix minor bugs

Testing Completed:

Yes

Checked that the validations are passing and have addressed any issues that are present:

Yes

Hi @tatecksi,

To test the modified workbook, please add sample data to the path below.
https://github.com/Azure/Azure-Sentinel/tree/master/Sample Data/Custom
And is possible please attach screenshots of the working workbook.
Thanks.

Hi @v-atulyadav ,
To test the workbook, it has to be created in a Sentinel workspace. Sample data would not help as it is also querying APIs to get some of the data.
Please contact me via my alias 'tatecksi' for more details. But I already done the testing in my lab. Thanks


Fix indentation of closing delimiters

This fixes #76 with the proposed solution in that issue. @muflax writes they are unsure about the wider scope of things, but the tests pass, so I thought I would suggest it, anyway.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @nikomatsakis (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.


Move to opentelemetry-contrib

Would you be willing to submit this package to https://github.com/open-telemetry/opentelemetry-erlang-contrib/ ?
You can of course still maintain rights to the hex package and approval for any changes to the library with it in -contrib, but it makes it easier for users to find.

Hey @tsloughter, we are already discussing this internally.
I'll come back to you as soon as we take a final decision! Thank you!

Hi @tsloughter!
We tried reasoning about giving this project to the community and maybe retaining our CI/CD pipeline, but that's not really possible. The easiest thing (for us) would be to "give you the code", we could still review PRs and solve eventual issues, but we wouldn't have ownership anymore.
If you think this is not convenient, another solution could be making one (or more) of us part of the opentelemetry organization and/or giving us grants on that repo, so we still could have a "relevant" impact on PRs and the evolution of the library.
What do you think?

@cpiemontese adding the code to -contrib you still get ownership. We use the AUTHORS file to provide github access per project in that repo to appropriate owners. You'll also have perms for hex publishing.

But is there any automation in place or would we need to publish to hex manually? I don't know how other projects under -contrib are managed e.g. if there are actions in place that run on release creation or something like that

It is currently manual, with both the original authors and otel maintainers able to publish.

Sorry for the n-th question but I'm trying to understand better :sweat_smile:
You said we'll retain "approval for any changes to the library with it in -contrib", does that mean we won't be able to merge PRs ourselves?

Hm, sadly I don't think that is possible without giving permission to merge for all PRs to the repo. Would be more than happy to have more contrib maintainers (we need it) ;), but github doesn't provide a way to only give merge rights for PRs that touch specific parts of the repo.

Hi again @tsloughter, I think we are ready to move telepoison to opentelemetry-erlang-contrib. Is there a checklist or something of what has to be done (aside from opening a PR with the code contained in this library)?

Great! There is just this right now https://github.com/open-telemetry/opentelemetry-erlang-contrib/blob/main/CONTRIBUTING.md


Iss26

Simplified UI

based on the Figma wireframe from the Design & UI/UX team
taking account consideration the end-user feedback summary
contains a login page
contains 4 input parameter pages
appropriate update in server page and run_model page

The additional dependancies for this branch are breaking the build (See Actions). @pardf did you install any other libraries to get this working locally ?

Hi @kariso2000 how should I check that?


Customization of sign column separately

As far as I am aware, and apologies if I'm wrong, but you can't set the sign column foreground/background separately from the rest of the groups.

Note above how the background for the sign column isn't matched which makes sense based on the highlight groups I've defined, but my Normal and SignColumn have different background colors for both. The current set of highlight groups ended up looking like:

along with a configuration that looks like:
signs = true,
keywords = {
    FIX = {
        icon = ' ',
        color = 'error',
        alt = { 'FIXME', 'BUG', 'FIXIT', 'FIX', 'ISSUE' },
    },
    TODO = {
        icon = ' ',
        color = 'info',
    },
    HACK = {
        icon = ' ',
        color = 'warning',
    },
    WARN = {
        icon = ' ',
        color = 'warning',
        alt = { 'WARNING', 'XXX' },
    },
    PERF = {
        icon = ' ',
        color = 'warning',
        alt = { 'OPTIM', 'PERFORMANCE', 'OPTIMIZE' },
    },
    NOTE = {
        icon = ' ',
        color = 'hint',
        alt = { 'INFO', 'HINT' },
    },
},
highlight = {
    before = '',
    keyword = 'wide',
    after = 'fg',
},
colors = {
    error = { 'TodoCommentError' },
    warning = { 'TodoCommentWarning' },
    info = { 'TodoCommentInfo' },
    hint = { 'TodoCommentHint' },
    default = { 'TodoCommentDefault' },
},
pattern = '(KEYWORDS):',

I'll change it so that the signs use the same bg color as the SignColumn. Won't have time till this evening to add this though. Thank you for reporting!

I just pushed a fix that correctly uses the configured SignColumn bg color.


line terminator to console output because pytest doesn't

Thanks for this. There are a few strange formatting things we're still learning about pytest. I'll publish a new version soon


Move "Toggle" to top of tray menu

Makes it easier to click (Fitt's Law and all that), and I think it's what the official Electron client does.

Currenly I've heard the opinions from people having their panel at top, but I can imagine this isn't going to be the case for people having their menu displayed on bottom of their screen.
I don't really want to move it right now but if I will, I'll probaby experiment with other changes in the menu. See #269.

My bad for not checking for open Issues. I wasn't aware that not having left-click-to-open was a bug in Electron. I much prefer that method. But until that's fixed I'll continue using this branch, so I might as well leave the PR open.

My bad for not checking for open Issues. I wasn't aware that not having left-click-to-open was a bug in Electron. I much prefer that method. But until that's fixed I'll continue using this branch, so I might as well leave the PR open.

I'll probably work on the changes myself from this PR + add a few modifications to the menu. I have to admit I'm also using the panel on the top, so I guess that would be useful for me as well. I hope not to p—s anybody using the bottom panel through...

Resolved in https://github.com/SpacingBat3/WebCord/commit/2f39b40a3bb788b4a4410851509782d503d97a07.


The github.com/GoogleCloudPlatform/kubernetes is no more.

It was renamed to https://github.com/kubernetes/kubernetes but the Kubernetes documentation seems to live at https://kubernetes.io.

This change is

/lgtm


Copy of v1.3 scan: Emissions API Med 2

CampDAPI_Med&Lows.xlsx
DNS Rebinding allows a malicious host to spoof or redirect a request to an alternate IP address,
potentially allowing an attacker to bypass security authentication or authorization.  DNS resolution
on its own does not properly constitute a valid authentication mechanism.  Servers should validate that
the Host header of the request matches the expected hostname of the server.  In cases where the hostname
is missing or does not match the expected value, the server should return a 400.  The X-Forwarded-Host
header is sometimes used instead of the Host header in cases where the request is being forwarded.  In
these cases, the X-Forwarded-Host header should also be validated if it is being used to determine the
Host of the original request.
DNS Rebinding on 'https://api.epa.gov/easey/staging/emissions-mgmt/emissions/submission-progress?submissionPeriod=2019-01-01'

Invalid

GET requests are allowed by browsers to retrieve resources, like javascript that might have sensitive data from your domain if it happens to be an array, not an object. So to avoid such attacks, we can change this API request to POST and return a JSON object instead of an array.


docs: fix a dead link in GitHub pages

The link that using relative-path is "404 not found" on GitHub pages.
This PR change URL to the repository from relative-path.
Visitors will is able to found some files.

Thank you for your review :)


Fixes clang-cl compilation issue

Fixes issue https://github.com/microsoft/DirectXMath/issues/156

What scenario is this that's failing?

What scenario is this that's failing?

When winrt is used/included:
#include <winrt\base.h>
winrt\base.h includes directxmath.h from the SDK.
with the clang-cl as the compiler frontend.

Which Windows SDK?

Which Windows SDK?

The latest insider SDK: 10.0.25276.0


The "ELECTRON_MIRROR" environment variable in the terminal does not work

VSCode Version:
版本: 1.46.1 (user setup)
提交: cd9ea6488829f560dc949a8b2fb789f3cdc05f5d
日期: 2020-06-17T21:13:20.174Z
Electron: 7.3.1
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.17134
OS Version:Microsoft Windows [版本 10.0.17134.1550]

Steps to Reproduce:
1.Set the system-level environment variable "ELECTRON_MIRROR" in the System Properties dialog box
2.Open the CMD window and execute the "set" command, and you can see that the ELECTRON_MIRROR environment variable is in effect
3.When you open vscode, open the terminal, and execute the "set" command, you do not see the ELECTRON_MIRROR environment variable.
4.Other names have been tested, "ELECTRON_" and “ELECTRO_MIRROR” are valid, while "ELECTRON_1" and “ELECTRON_M” are not.
5.Duplicate problem on two computers.

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

This happens because we remove any environment variables of the form ELECTRON_.* when creating processes. We could go to a more specific list of variables like it used to but historically we ended up having variables slip in.
https://github.com/microsoft/vscode/blob/b8131113576908b042d2c4fab86128047181a09d/src/vs/base/common/processes.ts#L109-L114


Enchancement 1.20-9 crashes with beta 33

Mod Name
Enchancement
Mod Homepage
https://modrinth.com/mod/enchancement
Minecraft version
1.20.1
Describe the bug
Crashed during startup
Steps to reproduce

Connector + FFAPI and Enchancement with its dependencies
Launch game
Crash
...

Logs
https://mclo.gs/5M1ZwJG
Additional context
Beta 33 works with enchancement 1.20-8 but crashes with 1.20-9

still crashes with beta 34
crash log: https://mclo.gs/zSTd5fU
debug log: https://mclo.gs/UF6lohM

Can confirm that this issue still persists with beta 27

Can confirm that this issue still persists with beta 37


Improve travis automation

https://github.com/veandco/go-sdl2/blob/master/.travis.yml#L18 should be augmented to building all of the examples, currently the go build command does nothing at all and will always exit with status 0.

Actually just changing the go build to "go build github.com/veandco/go-sdl2/{sdl,img,mix,ttf}" should also improve things quite nicely. That would have caught #386

Hi @depili, nice suggestion! I have changed the Travis configuration file accordingly. The CI should build the other packages now.


How to change the app name in notification

I can't find a string for changing "social app" from notification area. Where is it located ? anybody plz help

Hi, @jishnurajm !
Did you change the app name in manifest file?
If it doesn't help, please provide screenshot with push notification. We will try to help you.


#[wasm_bindgen(getter_with_clone)]: unknown attribute

Summary
I am just trying the trivial example from documentation:
#[wasm_bindgen(getter_with_clone)]
pub struct Foo {
    pub bar: String,
    pub baz: String,
}

And I receive this error:
error: unknown attribute
  --> src/lib.rs:21:16
   |
21 | #[wasm_bindgen(getter_with_clone)]
   |                ^^^^^^^^^^^^^^^^^

Project is absolutely clear and is created by wasm-pack new
What am I doing wrong?

Thanks for the report, but support landed for this yesterday so it just hasn't been released to crates.io yet.

@alexcrichton, could you tell when support for this will be released?

Yes I can release a new version today.


dist.init_process_group hangs

Hi,
I'm trying to train CenterPoint on KITTI. Single GPU training is fine, but 4-GPU training hangs at this line:
https://github.com/tianweiy/CenterPoint-KITTI/blob/df2b099c057686aec832a55046c272108e310e2f/pcdet/utils/common_utils.py#L147-L152
I'm using a nccl backend, tcp_port is free.
Any help would be appreciated!

comment out those few lines ?
See https://github.com/open-mmlab/OpenPCDet/blob/e948c537858d4e468a9ef50b023324f6bc96db2a/pcdet/utils/common_utils.py#L181

It worked! Thanks for the quick reply!


Question about Evaluating

How can I obtain the FPS and AP data for the Neural Network on the validation set?

FPS is measured by total frames in a validation dataset, divided by the total seconds it took to process the dataset.
Total time gets scripted when an inference is completed, so you can use the time to measure the FPS.
For AP, you should upload the result file on Codalab evaluation server, which you can check on the YouTube-VIS challenge website.


Feature Request: Integration with Mirascope Framework

Background
Currently, the weave.op() decorator does not capture internal Mirascope calls or their associated costs. This creates a gap in observability.
Current Behavior

Internal Mirascope calls are executed but not logged
Cost information for these operations is not tracked

Desired Behavior

Log all internal Mirascope calls with their:

Operation name
Input/output
Execution time
Cost (tokens used)

Provide ability to trace the full call hierarchy including nested Mirascope operations

Hey @ramon-prieto , we don't have this on our roadmap atm, but happy to accept contrib!
Here's an example external contrib from NotDiamond:
https://github.com/wandb/weave/pull/2606


[DOCS] styles handling

How can the documentation be improved?
we have in the tutorial some info about how to style an app but nothing is written in the official docs section. the following topics would be a nice enrichment:

overview

built in options (postcss, sass, scss)
tailwind option (qwik add tailwind)

useStyles$ (https://qwik.builder.io/tutorial/style/styles/)

how to use
output

useStylesScoped$ (https://qwik.builder.io/tutorial/style/scoped/)

how to use
output

import with ?inline

when to use

i could start with it but would need to know where you want to have it and what to add as well to the above mentioned list 🙏

I also collected styling docs ideas a month ago, here my notes from discord.
Topics:
Different possibilities of styling
• Globally: import './styles.css'
• Component-specific styles: useStyles$
• Either Inline String or
• Load CSS file with ?inline
• Component-specific styles - SCOPED!: useStylesScoped$
• Either Inline String or
• Load CSS file with ?inline
• Dynamic style tags: style={{ background: state.background }}
• Explain Scoping
• useStyles$ Styles strings are treated as static - no dynamic strings for styling!
• Escaping Scoping in useStylesScoped$ using :global(...)
I think by now there are also efforts to enable css in js.
And I always encourage writing for people who have not worked with frameworks before. For some devs this might be the first one.

@wtho if you have a minute i'd appreciate if you could have a look at the current state and provide some feedback 🙏
https://github.com/BuilderIO/qwik/pull/1977


Add transfer related columns

@guachikuo thank you for your contribution. sorry for my late reply.
You closed this PR, If you want to merge your code, please re-open it. I'll merge as soon as possible.


Update configure-rdp-shortpath.md

The link points to top of document instead of the regions for TURN availability. Please help/guide correct the link as I am unsure what the correct link is
The external link should be:
https://learn.microsoft.com/en-us/azure/virtual-desktop/rdp-shortpath?tabs=public-networks#turn-availability

#sign-off


CB-12269 Remove CDP_FREEIPA_BACKUP_LOCATION_CONFIG entitlement check

We have qe-tested freeipa backup change for AWS, AZURE, and GCP. We will remove CDP_FREEIPA_BACKUP_LOCATION_CONFIG entitlement check.
See detailed description in the commit message.

@jamisonbennett @lacikaaa
In this PR, I am only removing the entitlement check. I still kept CDP_FREEIPA_BACKUP_LOCATION_CONFIG in entitlement service and all tests in case we want to turn on the entitlement again. I think there is no need to remove CDP_FREEIPA_BACKUP_LOCATION_CONFIG now immediately.
Later, under the same JIRA, I can remove all related code in entitlement service and all tests here and also from UMS.

I think you can remove all related code safely. We would just revert the commit if we need this again. No need to keep the unused code around. So please remove those too.

@lacikaaa
OK. I removed all related code. This exactly reverted CB-11633 in which I created the entitlement. I've tested locally. Could you take another look? Thanks!


Add support for non-ephemeral storage

Hi,
We have recently switched to the latest plugin version (as soon as #133 got merged), and this became a problem on out OS instance, because we have no support of ephemeral storage (i.e. when no volumes are being created for the VM). Due to that, slaves creation have stopped working on out instance. We've been able to fix it as follows: these two commits (these are 2 links). The question is: are we alone with this problem? If not, we could make ephemeral storage an option, and let user chose whether to use it or not.

Adding @clicman, an interested person

You might want to check out #194 as that might interest you.


Azure CLI not asking for 2FA and therefore unable to login

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az login
Errors:
AADSTS50076: Due to a configuration change made by your administrator, or because you moved to a new location, you must use multi-factor authentication to access '797f4846-ba00-4fd7-ba43-dac1f8f63013'.

Trace ID: 34750106-c9e4-4238-b6eb-484960ca3e00

Correlation ID: 3b85e4be-06c7-4da5-a53c-3eff6526a4eb

Timestamp: 2021-11-19 10:20:06Z

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az login -u {} -p {}

Expected Behavior
Environment Summary
Windows-10-10.0.19041-SP0
Python 3.8.9
Installer: MSI

azure-cli 2.30.0

Additional Context

@jiasli for awareness

Could you try to re-login with
az account clear
az login

This gives me the same result.

The ID token is not yet valid.

The ID token is not yet valid.

This is a new error, indicating your computer's time is not correct. Please see the discussion at #20434.

Ah, I see. This was indeed the case. For some reason my computer's clock wouldn't synchronize. I changed the time manually and now I'm able to login!

Glad to know that! 😊


api/weldr: bring tars back from the future

By default, go's tar archiver uses USTAR header format. Unfortunately, this
format doesn't support sub-second resolution for ModTime. Go solves this by
rounding the time. Sometimes, this creates an archive containing a file
with modtime from the future. When such archive is untarred by GNU tar,
the following message is produced:
tar: bf548dfd-0a90-40e6-bbf2-dcdd82fcbb4e.json: time stamp 2020-07-13
13:34:31 is 0.356223173 s in the future

We have two options here:

Use gnu header format that supports sub-second resolution. Unfortunately,
it seems that not all tar archivers support this format (e.g. 7-zip).

The other option is to truncate the date (instead of rounding).

I went with option 2.
Also, this commit adds a test to check that the header is not from the future.
Without this fix, the test is actually failing, I verified this manually.
Fixes #854

The CI failure is unrelated, issue #862.


Tweak LightmapGI defaults to be closer to the CPU lightmapper

Use 3 bounces by default. This is slower but gives significantly better results out of the box. The GPU lightmapper is very fast compared to the CPU lightmapper anyway.
Enable environment lighting from the scene by default.

This is not done in 3.x for compatibility with existing projects, but it makes sense to do this by default since pretty much all outdoor scenes benefit from this.

Set the custom environment color to white (like ReflectionProbe).

Its default energy is still 0, so it's invisible by default.

Enable the generation of dynamic object probes by default.
Tweak the max_texture_size property hint for better usability.
Improve error messages when passing invalid sizes to LightmapGI.set_max_texture_size().

Preview
Using the All bake mode for the DirectionalLight, which means both direct and indirect lighting are baked.
Testing project: test_lightmap_normalmap_2.zip (master only, won't work in 3.x)
Before

After

I am not sure, I think it really depends on the scene and for the most part it will be better for users that a first attempt happens fast. They can see how much to increase quality vs performance later.

I am not sure, I think it really depends on the scene and for the most part it will be better for users that a first attempt happens fast. They can see how much to increase quality vs performance later.

When compared to the CPU lightmapper, GPU lightmapping is still pretty fast in my experience when using 3 bounces. It's like an order of magnitude faster or so on a scene of similar complexity.

Needs rebase, and would be good to get a review from @JFonS too :)

Looks good to me too. I agree, the quality tradeoff for having mutliple bounces is really good. Let's keep an eye out and see if anyone experiences a notable increase in bake times.


Update commit hash for custom-tabs-client in using-twa article

As described in https://bugs.chromium.org/p/chromium/issues/detail?id=928701 using a default browser that does not support TWA causes a confusing exception to be thrown.
I did not report this issue, but I did run into it and Googling the issue didn't produce any great answers.
The (current) latest commit appears to have fixed this issue, at least for me: https://github.com/GoogleChrome/custom-tabs-client/commit/d08e93fce3fb3e1f22214ee2f23fddc4f4e92634
This new commit works regardless of what browser I have set as my default albeit with one inconsistency I logged here: https://bugs.chromium.org/p/chromium/issues/detail?id=942930
What's changed, or what was fixed?

Commit timestamp in using-twa article updated to latest commit

:tada: This has been pushed live to https://developers.google.com/web/


Documentation refers to old version of pr0ps-trackmap-panel plugin

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
The documentation says:
sudo grafana-cli plugins install pr0ps-trackmap-panel 2.1.2

But this version suffers from #2770.
Expected Behavior
The correct version should be 2.1.4
sudo grafana-cli plugins install pr0ps-trackmap-panel 2.1.4

Steps To Reproduce
No response
Relevant log output
Not relevant.

Screenshots
No response
Additional data
No response
Type of installation
Docker
Version
main branch

Would submit a pull request, but I can't see where this documentation comes from.

https://github.com/adriankumpf/teslamate/tree/master/website/docs
Does are located there.

Thanks, not sure why I couldn't find this now.

Would be great to move to geomap native Panel and newer grafana Version

I see no reason we can't move up grafana versions, I myself use Grafana 10.2, but I don't have time to fully test and vet this unless someone else can take it on. Otherwise, I can review when I am back from vaca.
We need to do the following for a PR:

Update grafana to 10.2
Verify all dashboards work, and edit those that don't.
Update the dasbhoard that uses pr0ps-trackmap-panel
I noticed Charging stats is broke for me on 10.2, but it may be a plugin issue on my side.
Update docs


can not connect to twemproxy

@nrk
English is not good
This is my fault：
ConnectionException in AbstractConnection.php line 155:
Error while reading line from the server. [tcp://<IP_ADDRESS>:6379]
in AbstractConnection.php line 155
at AbstractConnection->onConnectionError('Error while reading line from the server.') in StreamConnection.php line 314
at StreamConnection->read() in AbstractConnection.php line 120
at AbstractConnection->readResponse(object(RawCommand)) in AbstractConnection.php line 112
at AbstractConnection->executeCommand(object(RawCommand)) in StreamConnection.php line 260
at StreamConnection->connect() in AbstractConnection.php line 180
at AbstractConnection->getResource() in StreamConnection.php line 288
at StreamConnection->write('*2 $3 GET $48 laravel:138d0512d0cab506b3b30a91688a4272889305da ') in StreamConnection.php line 394
at StreamConnection->writeRequest(object(StringGet)) in AbstractConnection.php line 110
at AbstractConnection->executeCommand(object(StringGet)) in Client.php line 331
at Client->executeCommand(object(StringGet)) in Client.php line 315
at Client->__call('get', array('laravel:138d0512d0cab506b3b30a91688a4272889305da')) in RedisStore.php line 54
at Client->get('laravel:138d0512d0cab506b3b30a91688a4272889305da') in RedisStore.php line 54
at RedisStore->get('138d0512d0cab506b3b30a91688a4272889305da') in Repository.php line 129
at Repository->get('138d0512d0cab506b3b30a91688a4272889305da', '') in CacheBasedSessionHandler.php line 58
at CacheBasedSessionHandler->read('138d0512d0cab506b3b30a91688a4272889305da') in Store.php line 124
at Store->readFromHandler() in Store.php line 108
at Store->loadSession() in Store.php line 92
at Store->start() in StartSession.php line 104
at StartSession->startSession(object(Request)) in StartSession.php line 57
at StartSession->handle(object(Request), object(Closure))
at call_user_func_array(array(object(StartSession), 'handle'), array(object(Request), object(Closure))) in Pipeline.php line 136
at Pipeline->Illuminate\Pipeline{closure}(object(Request))
at call_user_func(object(Closure), object(Request)) in Pipeline.php line 32
at Pipeline->Illuminate\Routing{closure}(object(Request)) in AddQueuedCookiesToResponse.php line 37
at AddQueuedCookiesToResponse->handle(object(Request), object(Closure))
at call_user_func_array(array(object(AddQueuedCookiesToResponse), 'handle'), array(object(Request), object(Closure))) in Pipeline.php line 136
at Pipeline->Illuminate\Pipeline{closure}(object(Request))
at call_user_func(object(Closure), object(Request)) in Pipeline.php line 32
at Pipeline->Illuminate\Routing{closure}(object(Request)) in EncryptCookies.php line 59
at EncryptCookies->handle(object(Request), object(Closure))
at call_user_func_array(array(object(EncryptCookies), 'handle'), array(object(Request), object(Closure))) in Pipeline.php line 136
at Pipeline->Illuminate\Pipeline{closure}(object(Request))
at call_user_func(object(Closure), object(Request)) in Pipeline.php line 32
at Pipeline->Illuminate\Routing{closure}(object(Request))
at call_user_func(object(Closure), object(Request)) in Pipeline.php line 103
at Pipeline->then(object(Closure)) in Router.php line 726
at Router->runRouteWithinStack(object(Route), object(Request)) in Router.php line 699
at Router->dispatchToRoute(object(Request)) in Router.php line 675
at Router->dispatch(object(Request)) in Kernel.php line 246
at Kernel->Illuminate\Foundation\Http{closure}(object(Request))
at call_user_func(object(Closure), object(Request)) in Pipeline.php line 52
at Pipeline->Illuminate\Routing{closure}(object(Request)) in AfterMiddleware.php line 22
at AfterMiddleware->handle(object(Request), object(Closure))
at call_user_func_array(array(object(AfterMiddleware), 'handle'), array(object(Request), object(Closure))) in Pipeline.php line 136
at Pipeline->Illuminate\Pipeline{closure}(object(Request))
at call_user_func(object(Closure), object(Request)) in Pipeline.php line 32
at Pipeline->Illuminate\Routing{closure}(object(Request)) in BeforeMiddleware.php line 24
at BeforeMiddleware->handle(object(Request), object(Closure))
at call_user_func_array(array(object(BeforeMiddleware), 'handle'), array(object(Request), object(Closure))) in Pipeline.php line 136
at Pipeline->Illuminate\Pipeline{closure}(object(Request))
at call_user_func(object(Closure), object(Request)) in Pipeline.php line 32
at Pipeline->Illuminate\Routing{closure}(object(Request)) in CheckForMaintenanceMode.php line 44
at CheckForMaintenanceMode->handle(object(Request), object(Closure))
at call_user_func_array(array(object(CheckForMaintenanceMode), 'handle'), array(object(Request), object(Closure))) in Pipeline.php line 136
at Pipeline->Illuminate\Pipeline{closure}(object(Request))
at call_user_func(object(Closure), object(Request)) in Pipeline.php line 32
at Pipeline->Illuminate\Routing{closure}(object(Request))
at call_user_func(object(Closure), object(Request)) in Pipeline.php line 103
at Pipeline->then(object(Closure)) in Kernel.php line 132
at Kernel->sendRequestThroughRouter(object(Request)) in Kernel.php line 99
at Kernel->handle(object(Request)) in index.php line 55
Hope to get help
Thank!

Did you manage to connect to it ?


SyntaxError in README.md

Hi! Thanks for fixing the previous problem.
I found a syntax error in the README:
SyntaxError: missing ) after argument list
I sent a pull request to fix this.
Cheers,
Aprilsnows

Thanks for pointing this out! Merged.


Add configurations for CI to fail on OSH scan failures and new findings

This is a follow up on https://github.com/packit/packit/discussions/2371#discussioncomment-10474198
We should add two separate configuration options to cause CI to fail on scan failures and new findings:

fail_ci_on_scan_failure should cause CI to become red if OSH scan fails.
fail_ci_on_new_findings should cause CI to become red on new findings.

Both of these options should be kept false by default. Because there may be issues with buildroot that can cause a scan to fail, or there may be large amount of false positives for certain projects.

Thanks @siteshwar for writing this down.
As a first thing, we need to resolve the reporting in general: https://github.com/packit/packit-service/issues/2516

I would probably prefer blocking attribute… On GitHub we could set non-blocking to neutral status, if it fails (that doesn't block merging)

fail_ci_on_new_findings should cause CI to become red on new findings.

On a second thought, the status should not be "fail", it should be "action_required" on new findings. Also, it should be "neutral" if there is a new finding, but the CI is not configured to fail.

Can't the CodeQL replace the checks? :thinking:

Can't the CodeQL replace the checks? 🤔

It seems configurable, but the default setting hides results from the user.
We can only keep the osh-diff-scan check and avoid uploading to CodeQL. Check should directly reference the final html report from OpenScanHub.

A note from today's meeting, we might want to consider having this for all the jobs.


Add a coroutine-enabling wrapper for caf::result<T>

This is best explained using a tony table:

BEFORE
AFTER

[self](T&...) -> caf::result<R> {
  A();
  self->request(d1, t, xs...).then(
    [](response_type& value) {
      B(value);
    },
    [](caf::error& err) {
      C(err);
    });
  D();
  return r;
}

co_lift([self](T...) noexcept -> co_result<R> {
  A();
  auto task = co_request_then(*self, d1, t, xs...);
  D();
  auto tag = co_await co_deliver(r);
  if (auto value = co_await task)
    B(*value);
  else
    C(value.error());
  co_return tag;
})

The main benefit is immediately obvious: We've got rid of callback hell.
There exist a few pitfalls with this that might be easy to run into:

Using self->request, self->make_response_promise, and self->delegate within a co_result coroutine leads to undefined behavior and is inherently unsafe. Use co_request_then(self, ...), co_request_await(self, ...), co_make_response_promise<T>(self), and co_delegate(self, ...) instead.
After awaiting a response handle, self->current_sender() might return an unexpected value because the resumed coroutine behaves as if it was called from the response handle continuation.
To deliver values early, i.e., on first suspend, use co_deliver(...), which returns a tag type that later must be returned from the coroutine.
CAF supports catching exceptions via set_exception_handler. Throwing exceptions from a co_result<T> coroutine will always bypass CAF's exception handler and call std::terminate().

co_request_then
The analog to self.request(dest, timeout, args...).then(...) for co_result<T> coroutines.
When awaited suspends the coroutine, returns an expected value similar to caf::function_view, and continues the coroutine execution in the response handlers CAF runtime context.
co_request_await
The analog to self.request(dest, timeout, args...).await(...) for co_result<T> coroutines.
When awaited suspends the coroutine, returns an expected value similar to caf::function_view, and continues the coroutine execution in the response handlers CAF runtime context.
co_request_receive
The analog to self.request(dest, timeout, args...).receive(...) for co_result<T> coroutines.
When awaited does not suspend the coroutine, returns an expected value similar to caf::function_view, and continues the coroutine execution in the the current CAF runtime context immediately.
co_deliver
The analog to returning a value from an actor behavior for co_result<T> coroutines. The value is returned to the CAF runtime on the next suspend.
When awaited does not suspend the coroutine, returns an empty tag value that must later be returned from the coroutine, and continues the coroutine execution in the the current CAF runtime context immediately.
This exists only to solve a corner case in which the return value of the coroutine is known before suspending it via co_await co_request_*. Use with caution.
co_delegate
The analog to self.delegate(dest, args...) for co_result<T> coroutines.
When awaited does not suspend the coroutine, returns an empty tag value that must later be returned from the coroutine, and continues the coroutine execution in the the current CAF runtime context immediately.
co_make_response_promise
The analog to self.make_response_promise<T>() for co_result<T> coroutines.
When awaited does not suspend the coroutine, returns the response promise and an empty tag value that must later be returned from the coroutine, and continues the coroutine execution in the the current CAF runtime context immediately.
It is the caller's responsiblity to fulfill the returned response promise from the same actor context.
:memo: Checklist

[x] All user-facing changes have changelog entries.
[x] The changes are reflected on docs.tenzir.com/vast, if necessary.
[x] The PR description contains instructions for the reviewer, if necessary.

:dart: Review Instructions
The first commit contains the bulk of the changes. Read the commit description first, then the start at the 2nd commit to review the changes this incurs to existing actor behaviors that I rewrote as an example. Lastly, do a deep-dive into the first commit that contains the actual implementation.
There's still some compiler errors when using gcc 10, but everything runs as expected using clang 13. I'll gladly take help hunting those down.
This change is developer-facing only, so it doesn't need changelog entries or a documentation update.

I did a review of this in a call with @lava and @dispanser; there are a few lifetime things to work out still and then I think we can merge this soon.

I haven't forgotten about this PR. There are some bugs related to lingering response promises that are really hard to work around with CAF 0.17, so I've been waiting for us to upgrade to CAF 0.18 instead.

We've finally upgraded to CAF 0.18, so technically this is unblocked now. I plan to pick this up sometime in the near future, but since this is ultimately just a developer nicety it is not a current priority. I will re-open the PR when I have time to continue working on this.