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/docs, working directory: W:\t4xx-s, target branch: master, target branch commit: 295fe0ee791bce3c5c90dffee7759a08cb6b8970, 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/docs, working directory: W:\isre-s, target branch: master, target branch commit: 295fe0ee791bce3c5c90dffee7759a08cb6b8970, 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/docs, working directory: W:\kmwe-s, target branch: master, target branch commit: 295fe0ee791bce3c5c90dffee7759a08cb6b8970, 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] An exception occurred during the build process. Please retry building your content again. If the issue still happens, open a ticket in http://MSDNHelp and include the URL of publishing report.

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/docs, working directory: W:\os04-s, target branch: master, target branch commit: 295fe0ee791bce3c5c90dffee7759a08cb6b8970, 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] An exception occurred during the build process. Please retry building your content again. If the issue still happens, open a ticket in http://MSDNHelp and include the URL of publishing report.

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/docs, working directory: W:\n2mv-s, target branch: master, target branch commit: 295fe0ee791bce3c5c90dffee7759a08cb6b8970, 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/docs, working directory: W:\khmw-s, target branch: master, target branch commit: 295fe0ee791bce3c5c90dffee7759a08cb6b8970, 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/docs, working directory: W:\bjqj-s, target branch: master, target branch commit: 295fe0ee791bce3c5c90dffee7759a08cb6b8970, 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/docs, working directory: W:\gvv5-s, target branch: master, target branch commit: 295fe0ee791bce3c5c90dffee7759a08cb6b8970, 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/docs, working directory: W:\i043-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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] An exception occurred during the build process. Please retry building your content again. If the issue still happens, open a ticket in http://MSDNHelp and include the URL of publishing report.

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/docs, working directory: W:\unmk-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\qv0l-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\a4nk-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\on4m-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\41zi-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\ocse-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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 d7bf04da73f92b7e8483fd0cdcb21f1457d73eb4 in branch master-sync-work of repository https://github.com/OPS-E2E-PPE/docs into branch master (commit 295fe0ee791bce3c5c90dffee7759a08cb6b8970)

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/docs, working directory: W:\xdst-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\l54l-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\yrt1-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\cny2-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\1vr1-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\b1p5-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\52tk-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\xt1l-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\ai0d-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\5ogn-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\2osg-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\cqgv-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\tfb1-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\hgn1-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\rjsz-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\qpkr-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\ku1z-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\icox-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\0asb-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\vwcx-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\mrss-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\uftc-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\gncw-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\4gvf-s, target branch: master, target branch commit: 0924fcbaa3b72e744bd1f720a943868a00a6da7f, 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/docs, working directory: W:\qldp-s, target branch: master, target branch commit: fd5368632955ea445e17b124d3257ca409521b71, 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/docs, working directory: W:\u5ha-s, target branch: master, target branch commit: fd5368632955ea445e17b124d3257ca409521b71, 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/docs, working directory: W:\1g5v-s, target branch: master, target branch commit: fd5368632955ea445e17b124d3257ca409521b71, 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.


PP-2270 Sanitize Charge details values

WHAT

Mitigate possible mistakes in fields as values might accidentally contain other information that the user intended to send.

Basic sanitization of relevant data. Add Sanitizer where Strings containing more than 10 character digits are obfuscated to * characters.

Looks 👍 . Can merge when 🍏


Student not able to resume exercise

Describe the bug
The bug happens as follows:

Student requests feedback
Student does not get feedback yet, probably queued in the requests list
Student wants to resume exercise (presses resumes exercise)
Artemis displays resume exercise
Student receives the errors on the attached image

Suspected problem: the build is being cleaned up for the exercise
To Reproduce

Request feedback for 100% submission
Do not give feedback for the submission (pending)
Try to resume exercise
The error should occur then

Expected behavior
The Student should be able to resume the exercise
Screenshots

What browsers are you seeing the problem on?
Chrome
Additional context
No response
Relevant log output
No response

Does the Resume Exercise button appear instantly after submitting feedback?

They said after a while they see the resume exercise button but no exact time or reason for it


Use WMI to detect devices instead of the system registry

Fixes #733
Initial attempt at using WMI to detect devices instead of using the system registry. This works on my desktop and detects all my connected Arduinos, as well as a few other non-Arduino devices that are correctly skipped.
A few things to note:

The "FriendlyName" is no longer used to detect boards, only the VID/PID. In practice I don't believe this changes anything since I've never seen FriendlyName match at this stage of the detection, even using the old registry method.
The VID/PID string used to detect is slightly different than in the past but it doesn't matter given how the BoardDefinition class and board definition files were using regex for matching: the current tests are all based on "start of string" so things still work fine.
The log messages look slightly different now since the FriendlyName from the registry is no longer used.

Here's debug output example of this in action on my machine. note that it correctly skips the ACPI device.
Debug	3/11/2022 8:05:59 AM	Checking for compatible module: VID_1B4F&PID_9206&REV_0100&MI_00
Debug	3/11/2022 8:05:59 AM	Found potentially compatible module (Arduino Micro Pro): VID_1B4F&PID_9206&REV_0100&MI_00@COM22
Debug	3/11/2022 8:05:59 AM	Incompatible module skipped: VID/PID: ACPI\VEN_PNP&DEV_0501
Debug	3/11/2022 8:05:59 AM	Checking for compatible module: VID_2341&PID_0042&REV_0001
Debug	3/11/2022 8:05:59 AM	Found potentially compatible module (Arduino Mega 2560): VID_2341&PID_0042&REV_0001@COM3
Debug	3/11/2022 8:05:59 AM	Checking for compatible module: VID_1B4F&PID_9206&REV_0100&MI_00
Debug	3/11/2022 8:05:59 AM	Found potentially compatible module (Arduino Micro Pro): VID_1B4F&PID_9206&REV_0100&MI_00@COM15
Debug	3/11/2022 8:05:59 AM	Checking for compatible module: VID_1B4F&PID_9206&REV_0100&MI_00
Debug	3/11/2022 8:05:59 AM	Found potentially compatible module (Arduino Micro Pro): VID_1B4F&PID_9206&REV_0100&MI_00@COM17
Debug	3/11/2022 8:05:59 AM	Checking for compatible module: VID_1B4F&PID_9206&REV_0100&MI_00
Debug	3/11/2022 8:05:59 AM	Found potentially compatible module (Arduino Micro Pro): VID_1B4F&PID_9206&REV_0100&MI_00@COM7

@neilenns I would merge this so that we can use it in a beta and get some feedback.

If you approve it I think you can still merge it even tho I have it marked as draft

Feel free!

i remember i had two occasions in the past where even in the device manager two connected modules had the same serial port
I think we should keep the check whether  we are already trying to connect - just in case to be able to log this case as an error but don't take a special action. That might allow us to find out if it works for the people during beta but with the log message it will be easier to pin down in case somebody reported a problem.

@DocMoebiuz Reverted the change to the connection test, should be ready for you now.


Added Introduction to Machine Learning with Python

Added the book to subjects md file. Please mark this as hacktoberfest.
What does this PR do?
Add resource(s)
For resources
ML in python
Why is this valuable (or not)?
It's an easy guide for beginners in python ML.
How do we know it's really free?
The direct PDF file is available with no logins or money expenses.
For book lists, is it a book? For course lists, is it a course? etc.
Book
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

This is not an authorized distribution. Refer to docs/CONTRIBUTING.md for guidelines.


Plane direction changes to opposite sometimes

For some yet unknown reason direction of the plane of the galaxy changes to opposite every once in a while. It is certainly connected with the same behaviour of the angular momentum vector which is strange.

Galactic plane coordinate system removed in ec7addf629cab1feb196f5cfc7178ddcace69df1


Using Inner/Outer on electrical connector

Reported by sandra.diebel on 4 Nov 2013 14:07 UTC
Hello,
I have a model in which I want to connect a source with an resistor using inner/outer declarations on connectors. The model looks like this:
model Circuit

connector Pin
   Real v;
   flow Real i;
end Pin;

model Ground
 outer Pin p;
equation
  p.v = 0;
end Ground;

model AlternatingSource
  Real U;
  parameter Real U0 = 0;
  parameter Real U1 = 5;
  outer Pin p;
  Pin n;
equation
  U = p.v - n.v;
  n.i = -p.i;
algorithm
  when sample( 0.01,1/1000) then
    if pre(U) == U0 then
       U := U1;
    else
       U := U0;
    end if;
  end when;
end AlternatingSource;

model Resistor
   parameter Real R;
   outer Pin p;
   Pin n;
equation
   p.i*R = p.v - n.v;
  n.i = -p.i;
end Resistor;

  inner Pin p;
  Ground ground;
  AlternatingSource source;
  Resistor resistor( R = 10);
equation
  connect( resistor.n, source.n);

end Circuit;

I always get the following error message: "The model is not well-posed.The model has 7 scalar unknowns and 9 scalar equations."
When I connect the components with "connect" the simulation is correct. Is it not possible to define electrical connectors with inner/outer?
Thank you.
Sandra Diebel

Migrated-From: https://trac.modelica.org/Modelica/ticket/1342

Comment by dietmarw on 20 Jun 2014 10:56 UTC
This is not a bug but basically a modelling question. You should ask your question here instead:
http://stackoverflow.com/questions/tagged/modelica


Create release notes

Here's a good example of our format:
https://github.com/YosefLab/scvi-tools/blob/master/docs/release_notes/v0.11.0.rst

Perhaps an opportunity to set this up too:
https://pypi.org/project/towncrier/


Merge branch 'release/1.1.5' into develop

Coverage remained the same at 100.0% when pulling 948041efce341bb6c210235d4627d2deadd0bc1c on develop into 8ac7904bef7263a4697ae63fa6c513465414e8dc on master.


Save Option

I was wondering if it is possible to include a save function that will save the parsed information to TXT or HTML format under the name of the novel from the URL?

Considering it returns as a dictionary it'd be as simple as writing the term + '.txt' or '.html' as the filename and then writing the entries you want from the dictionaries to the txt/html file. Yes it's possible.

import json
with open('ouput', 'w') as file:
    json.dump(data, file, indent=2)


[BUG] migrating from react-formio - what replaces "ref" prop?

Environment

Hosting type

[ ] Form.io
[x] Local deployment

Version: 5.1.1

Formio.js version: 4.13.2
Frontend framework: react 16.13.1

Migrating to @formio/react from react-formio:
We were using the ref prop to return the instance of the formio object to access its apis:
           <Form
              ref={(form: any) => setFormObj(form)}
              onSubmit={() => {
                ClientLogger.error('FormDisplayPrevious.onsubmit', 'Called submit');
              }}
              options={{ noAlerts: true, readOnly: true, getData: (id: string) => getForm(id), inEditor: false }}
              form={parsedForm}
              onPrevPage={resetScroll}
              onNextPage={resetScroll}
              onCustomEvent={formCustomEvent}
              onRender={formReady}
            />

ref prop has been removed - how do we now get access to form?

I also can reproduce the issue reported by @adventmedia . I got the following warning message in the console log.

Could you mind telling me if there's a way to get the reference? Thank you very much.

Hi,
Like the reporter, I need to access the formio object. Locally, I modified the file https://github.com/formio/react/blob/master/src/components/Form.jsx as follows:
import React, { useCallback, useEffect, useImperativeHandle, useReducer, useRef } from "react"
import PropTypes from "prop-types"
import EventEmitter from "eventemitter2"
import _isEqual from "lodash/isEqual"
import { Formio } from "formiojs"

const FormioForm = Formio.Form

const formioReducer = (state, action) => {
  switch (action.type) {
    case "SET_FORMIO":
      return action.payload
    case "SET_FORMIO_FORM":
      if (state) {
        state.form = action.payload
      }
      return state
    case "SET_FORMIO_SRC":
      if (state) {
        state.src = action.payload
      }
      return state
    case "SET_FORMIO_SUBMISSION":
      if (state) {
        state.submission = action.payload
      }
      return state
    case "SET_FORMIO_URL":
      if (state) {
        state.url = action.payload
      }
      return state

    default:
      return state
  }
}

const Form = (props, ref) => {
  const instance = useRef(undefined)
  const createPromise = useRef(undefined)
  const elementRef = useRef(null)
  const [formio, dispatch] = useReducer(formioReducer, undefined)
  const { src, form, url, options = {}, formioform, formReady, submission } = props

  useImperativeHandle(
    ref,
    () => {
      return formio
    },
    [formio]
  )

  useEffect(() => () => formio ? formio.destroy(true) : null, [formio])

  const createWebformInstance = useCallback(
    srcOrForm => {
      instance.current = new (formioform || FormioForm)(elementRef.current, srcOrForm, options)
      createPromise.current = instance.current.ready.then(formioInstance => {
        dispatch({ type: "SET_FORMIO", payload: formioInstance })

        if (formReady) {
          formReady(formioInstance)
        }
      })

      return createPromise.current
    },
    [options, formioform, formReady]
  )

  const initializeFormio = useCallback(() => {
    const onAnyEvent = (event, ...args) => {
      if (event.startsWith("formio.")) {
        const funcName = `on${event.charAt(7).toUpperCase()}${event.slice(8)}`
        // eslint-disable-next-line no-prototype-builtins
        if (props.hasOwnProperty(funcName) && typeof props[funcName] === "function") {
          props[funcName](...args)
        }
      }
    }

    if (createPromise.current) {
      instance.current.onAny(onAnyEvent)
      createPromise.current.then(() => {
        if (submission) {
          dispatch({ type: "SET_FORMIO_SUBMISSION", payload: submission })
        }
      })
    }
  }, [submission, props])

  useEffect(() => {
    if (src) {
      createWebformInstance(src).then(() => {
        dispatch({ type: "SET_FORMIO_SRC", payload: src })
      })
      initializeFormio()
    }
  }, [src, createWebformInstance, initializeFormio])

  useEffect(() => {
    if (form) {
      createWebformInstance(form).then(() => {
        dispatch({ type: "SET_FORMIO_FORM", payload: form })
        if (url) {
          dispatch({ type: "SET_FORMIO_URL", payload: url })
        }
      })
      initializeFormio()
    }
  }, [form, url, createWebformInstance, initializeFormio])

  useEffect(() => {
    if (!options.events) {
      options.events = Form.getDefaultEmitter()
    }
  }, [options.events])

  useEffect(() => {
    if (formio && submission && !_isEqual(formio.submission.data, submission.data)) {
      dispatch({ type: "SET_FORMIO_SUBMISSION", payload: submission })
    }
  }, [submission, formio])

  return <div ref={elementRef} />
}

Form.getDefaultEmitter = () => {
  return new EventEmitter({
    wildcard: false,
    maxListeners: 0
  })
}

const ReactFormio = React.forwardRef(Form)

ReactFormio.propTypes = {
  src: PropTypes.string,
  url: PropTypes.string,
  form: PropTypes.object,
  submission: PropTypes.object,
  options: PropTypes.shape({
    readOnly: PropTypes.bool,
    noAlerts: PropTypes.bool,
    i18n: PropTypes.object,
    template: PropTypes.string,
    saveDraft: PropTypes.bool
  }),
  onPrevPage: PropTypes.func,
  onNextPage: PropTypes.func,
  onCancel: PropTypes.func,
  onChange: PropTypes.func,
  onCustomEvent: PropTypes.func,
  onComponentChange: PropTypes.func,
  onSubmit: PropTypes.func,
  onSubmitDone: PropTypes.func,
  onFormLoad: PropTypes.func,
  onError: PropTypes.func,
  onRender: PropTypes.func,
  onAttach: PropTypes.func,
  onBuild: PropTypes.func,
  onFocus: PropTypes.func,
  onBlur: PropTypes.func,
  onInitialized: PropTypes.func,
  formReady: PropTypes.func,
  formioform: PropTypes.any
}

export default ReactFormio

The compilation process provides the green light. 🙂
Below is the usage where the form schema doesn't contain a submit button:

NOTE: the provided code is not the same one I use but should give an idea

import ReactFormio from "./ReactFormio"

const MyForm = ({ schema, submission, onSubmit }) => {
  const formioRef = useRef(null)
  const formOptions = {noAlerts: true}

  const onNextClick = () => {
    if (formioRef.current) {
      formioRef.current.submit()
    }
  }

  return (
    <>
      <ReactFormio ref={formioRef} form={schema} submission={submission} onSubmit={onSubmit} options={formOptions} />
      <Button onClick={onNextClick}>Next</Button>
    </>
  )
}

The browser console reports:

Warning: Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in a useEffect cleanup function.
in ForwardRef(Form) (at MyForm.jsx:15)

I don't have much experience in React, and I don't know where to look at it. Running the application so far didn't show any issues.

I suppose you need access to the ref in order to have access to the form instance of formio. Instead of using a ref you can use the formReady prop callback to get the form instance back.

@cesosag That's right. Nowadays, I use the formReady combined with React.useRef(), and programmatically I run validation checkValidity(...) and form submission submit().

@cesosag That's right. Nowadays, I use the formReady combined with React.useRef(), and programmatically I run validation checkValidity(...) and form submission submit().

Hi, @devcovato  I have tried using formReady with React.createRef but the formio is null. Could you please give us an example how you achieved this? Thanks a lot

I figured it out.
constructor(){
  this.formRef = React.createRef();
}

checkValidity(){
  this.formRef.checkValidity(this.formRef.submission, true);
}

<button onClick={this.checkValidity}>Validate</button>
<Form {...otherProps} formReady={this.formRef} />

Hi @namti,
I'm sorry for the slow reply.
I changed the application code. I use a custom Form similar to the code above.
Maybe it's not React-way. I create const formRef = React.useRef(null) and pass it around. In the wrapper component containing the Form component, I set the formReady handler to assign the form to formRef. In the button click handler, I fetch formio from formRef.current, check the validation and programmatically submit the form. Something like:
const formio = formRef.current
if (formio.checkValidity(null, true, null, false)) {
  formio.nosubmit = true
  formio.submit()
}

I hope it will help you.

Thank you for your contribution. As this issue has been inactive for over 90 days, I will close it for now. If you'd like to reopen the issue, please reply and we can resume the triage process.


a child theme does not inherit the parent configuration

as mentioned in discord, when i create a child theme based on quark i get slightly different behavior.
ricardo pointed me to the fact that the child theme is missing the configuration that is in the parent theme.
indeed, copying over the content of quark.yaml, get's me a perfect "copy".
if nothing speaks against it, i would expect my new theme to behave exactly the same as the parent one. this could be achieved by avoiding any config in the "defafult" themes or by letting the child theme read the parent config by default. (being able to turn this off might be a good feature...)

... the theme has been created with the dev plugin...

This is a limitation of child themes.  You need to 'copy' the configuration.
I would only use a child theme if you were making very minor changes to a theme.  For most situations (99% of the time) it just is easier to copy the theme you want to base things from (with devtools) to a new theme.

if child themes are supposed to be used for small changes, it's IMO even more important that the child works in the same way as the parent one...
https://getgrav.org/blog/theme-development-with-inheritance -- the first result in my google -- does not mention the need for copying the settings...
https://learn.getgrav.org/16/themes/customization#theme-inheritance shows a "manual" copy that includes copying the yaml file, but not the usage of the dev plugin (refers to the blog entry above for more).
personally, i'm not a front end designer and appreciate it, if i can build on the shoulders of giants... and inheriting from a base theme is the easiest way for me to track what i have changed (and potentially messed up).
summary:

please improve the documentation, or
get the dev tool to copy the content of the parent settings, or
get the inheritance to also work for the setting.

Related to [PR 2143] (https://github.com/getgrav/grav/issues/2537)

Actually, it is not a limitation of child theme -- it was done like that by design. It has been a long time so I cannot really remember why it was done like that, but I'm sure there was a good reason to do it like that (years ago).


Set up automatic merges for a in_testing branch

Right now, we can't merge PRs onto production_testing from monday morning until some point on tuesday when the production merge happens.
This is (1) annoying, (2) prone to errors because we will forget.
Solution:

Enable an automatic pull from production_testing into a new branch in_testing, that happens on monday morning at like 5am.
The testing rig updates to in_testing rather than production_testing
On tuesday we merge in_testing into main

This solution will prevent us from having to remember to delay merges into production testing during the monday testing window.
I think we can use github actions to do this, but I've never used this feature before: https://stackoverflow.com/questions/35445186/can-github-automatically-merge-branches

Any thoughts @hanhou @XX-Yin

I suggest we rename production_testing to develop. Github action sounds a good idea.

Using in_testing as a medium between Monday and Tuesday sounds like a good idea.

created a "develop" branch
better instructions: https://docs.github.com/en/actions/quickstart
Details on using a scheduled action: https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#schedule
first draft: https://github.com/AllenNeuralDynamics/dynamic-foraging-task/blob/branch_automation/.github/workflows/automerge.yml

development notes

[ ] create a github action
[ ] use the schedule feature
[ ] create a PR from an action
[ ] approve or merge the PR from an action
[ ] put everything together

https://github.com/AllenNeuralDynamics/automation_testing

This should be resolved by #325 #324 #323


codon definition [sf#137]

Reported by cmungall on 2008-12-04 19:35 UTC
"A set of (usually) three nucleotide bases in a DNA or RNA sequence, which together signify a unique amino acid or the termination of translation."
Trying to work out what "signify" means in this context.
Strong interpretation: the 3 bases must in some way have a strong potential to code for an amino acid, they must be part_of a CDS. Arbitrary triples in intergenic regions are not codons.
Weak interpretation: the which clause in the definition is descriptive gloss. All triplets are codons.
Given we have:
[Term]
id: SO:0000198
name: noncoding_exon
namespace: sequence
def: "An exon that does not contain any codons." [SO:ke]
I suspect the strong interpretation. I would reword the def with a stronger word than "signify", e.g. "codes_for" and explicitly mention a CDS

Commented by eilbeck on 2008-12-18 20:40 UTC
I agree. Strengthened the definition. A triplet is just 3 bases, but a codon is coding.
--K

Updated by eilbeck on 2008-12-18 20:40 UTC

status: open --> closed-accepted


Incorrect calculation of fuel usage in 3.9.6/3.9.7

The calculation of the fuel bonuses was changed in 3.9.6, but the new formula is incorrect for how it's being used
The following code calculates an offset from 1 of the bonus
const fuelConsumptionBonusMultipler = (profileFuelConsomptionBonusSum + 100) / 100;
It will actually be a number above/below 1 depending on a negative or positive adjustment to the fuel consumption rate. For example at a +20% "bonus" to fuel consumption (Wall level 5), this value will be 1.2. While at wall level 6, it will be 1.0
This value is then added to the management bonus, which is a % bonus (0.10 for a -10% bonus, for example), and subtracted from 1:
const combinedBonus = 1.0 - (fuelConsumptionBonusMultipler + hideoutManagementConsumptionBonusMultipler);
This results in an incorrect combined bonus, as one is an absolute percentage, and the other is a relative percentage. So for a hideout management 10 player, with no wall debuffs, they end up with a "combinedBonus" of 1 - (1 + 0.05) or -0.05, resulting in them gaining fuel every tick instead of losing it

Originally written by DrakiaXYZ

Looks like insurance return bonuses, and flea tax discounts were also broken, fixed those in the PR for this as well: https://dev.sp-tarkov.com/SPT/Server/pulls/397

Originally written by DrakiaXYZ

Merged PR #397 and pushed to 3.9.8

Originally written by chomp


Segment/Analytics.js

Diesel is currently not tracking page views and customer attributes correctly.
When a user is logged in and behind an authenticated route, we need to identify them with an ID, name and email.
analytics.identify(user.id, { name: user.name, email: user.email });
Diesel also should track a page view for each route (authenticated or not).  I think using the title attribute already hooked into our routes would be great.
analytics.page(page.title);
More info:
https://segment.com/docs/libraries/analytics.js/#page
https://segment.com/docs/libraries/analytics.js/#identify

Also important to note that analytics.page(); will trigger the intercom.io integration so it needs to come after we call analytics.identify()

@chasballew Can you mention what other attributes you'd like to see us using to further segment users?

@samyount is going to participate as well

@mixonic @bantic Forgot to mention this issue on the call earlier.  This issue is also a requirement for launch, if possible.

Fixed by #267


Restructure, rename, and clear out repositories

There are currently three repositories

Changes

Create a new private repository called StandaloneCompilerForElan or similar. Copy all code from current Elan repository (which is the C# compiler) into it. Then rename current Elan to Documentation, clean it out, and then move extract the contents of the IDE ~ documentation folder into the Documentation repository.

Rename the IDE repository to LanguageAndIDE

Create a new private repository named 'Website'. Move contents of current website directory (in LanguageAndIDE) into Website.

Move the grammar folder from LanguageAndIDE into StandaloneCompilerForElan

Within LanguageAndIDE get rid of the now-redundant elan directory, moving all its contents up a level.

Clear out all usage of VS code from the main repository - if work keeping put it in with the StandaloneCompilerForElan - or a brand new repo.

step 1 complete

Superseded by subsequent changes


Move period within quotes under 'Forking a repository versus duplicating a repository' heading

Why:
Closes: #35300

What's being changed (if available, include any code snippets, screenshots, or gifs):

Moved period within closing quotation mark for text "Creating a repository from a template". per style guides.
Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[x] For content changes, I have completed the self-review checklist.

so

@carveyh Thanks so much for opening a PR with this fix! I'll update the branch and get this merged once tests are passing 🍏


Using AzureCommunicationChat (1.0.1) I am unable to upload iOS build on AppStore.

I am using AzureCommunicationChat (1.0.1) and AzureCommunicationChat is using Trouter (0.0.1-beta.5) which is now allowing me to upload the app on AppStore.
Exception or Stack Trace
App Store Connect Operation Error
Invalid MinimumOSVersion. Apps that only support 64-bit devices must specify a deployment target of 8.0 or later. MinimumOSVersion in 'iOSVideo.app/Frameworks/Trouter.framework' is ''.
App Store Connect Operation Error
Missing Info.plist value. A value for the key 'MinimumOSVersion' in bundle iOSVideo.app/Frameworks/Trouter.framework is required.
App Store Connect Operation Error
The bundle 'Payload/iOSVideo.app/Frameworks/Trouter.framework' is missing plist key. The Info.plist file is missing the required key: CFBundleShortVersionString. Please find more information about CFBundleShortVersionString at https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleshortversionstring
App Store Connect Operation Error
This bundle Payload/iOSVideo.app/Frameworks/Trouter.framework is invalid. The Info.plist file is missing the required key: CFBundleVersion. Please find more information about CFBundleVersion at https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleversion
App Store Connect Operation Error
Invalid Bundle. The bundle iOSVideo.app/Frameworks/Trouter.framework does not support the minimum OS Version specified in the Info.plist.
Screenshots

Setup (please complete the following information):
Libraries version numbers.
AzureCommunicationChat (1.0.1)
Trouter (0.0.1-beta.5)
Additional context
If I don't set "Enable bitcode" to "YES" for AzureCommunicationChat && Trouter then project don't get build but if I set "Enable bitcode" to "NO" then it gives the above mentioned error.
Please let me know what I can do with this issue.
Thank you
Kamaljeet Singh

@angellan-msft @LuChen-Microsoft for comment. cc/ @juancamilor

Any update on this?

@Kamaljeetsinghpunia I apologize for the delay. @angellan-msft @LuChen-Microsoft @juancamilor are representatives from the service team and should be able to assist.

Hi @Kamaljeetsinghpunia , this is a known issue in version 1.0.1, please try with a later version (1.0.2 or above). Thanks!

Ok Thank you


deps: Update keyboard-types to 0.7.

This brings a use of bitflags 2 and a couple of minor features.

This will require blitz to be updated as well since the dependency is used in the interface of dioxus-html. (Perhaps a re-export of keyboard-types from somewhere and using it via the re-export from blitz-core would be better...)

The original usage is from here in crates in this repo, so the pub use should be here, so that blitz-core can just pick it up when it picks up the structs that it is importing ... I'll take a look in the next day or three.


Partition system and app args to bootstrapped executable

Fixes #848

I finally got all of the bashisms out which fixed all of the previous errors from the bash script when running on Travis. However now CI failed with mismatched output from the checks in travis.sh. It looks as if the cli is being used not from this PR. And I am not able to reproduce this on my machine:
➜  ./cs-echo-launcher-args -Dother=thing foo -Dfoo=baz
foo

It seemed to work locally for me too…

I am not too happy with the solution in my PR as well. It is a bit too magical.
An alternativce approach would be a -J flag which, for example, sbt launcher uses:
-J-X               pass option -X directly to the java runtime

So then the bootstrap generated script could partition the arguments if they start with -J and pass in the ones starting with -J before -jar with -J removed.

I gave this another try and this time implemented the -J support like sbt does.

Thanks for the https://github.com/coursier/coursier/pull/852/commits/d4c57d5432c6ee951367569689257a14b2a4d6ab
It looks like the last implementation of -J works even for the older bash and sh that are in Travis CI environment. So this looks ready to be merged in.

This breaks apps which accept quoted arguments:
Expected:
$ your-app-printing-args a b "c d"
# => List("a", "b", "c d")

Actual:
$ your-app-printing-args a b "c d"
# => List("a", "b", "c", "d")

Yeah, it's not an easy task to process args without arrays.
Another solution with sh might be iterating arguments twice...?
#!/bin/sh

nargs=$#

i=1; while [ "$i" -le $nargs ]; do
         eval arg=\${$i}
         case $arg in
             -J-*) set -- "$@" "${arg#-J}" ;;
         esac
         i=$((i + 1))
     done

set -- "$@" -jar "$0"

i=1; while [ "$i" -le $nargs ]; do
         eval arg=\${$i}
         case $arg in
             -J-*) ;;
             *) set -- "$@" "$arg" ;;
         esac
         i=$((i + 1))
     done

shift "$nargs"

java "$@"

Woa. That looks great! Did not know that you can change the arguments with set like that. :)
The only modification this will need is to incorporate the javaOpts that could be passed to the bootstrap command when generating the bootstrap launcher.
https://github.com/coursier/coursier/blob/13582d6ee6571f0712e7c5a9987f654b9c283fc1/cli/src/main/scala-2.12/coursier/cli/Bootstrap.scala#L88-L91

Thank you for checking! I'll try creating PR later.


Crash when spawning cube on Chapter 4.

Chapter 4 says to set up the CameraConstants Uniform Buffer as such (in CreateResources()):
size_t numberOfCuboids = 64 + 2 + 2;
m_uniformBuffer_Camera = m_graphicsAPI->CreateBuffer({GraphicsAPI::BufferCreateInfo::Type::UNIFORM, 0, sizeof(CameraConstants) * numberOfCuboids, nullptr});

In RenderCuboid() we set the offset to the buffer for that cube as such:
size_t offsetCameraUB = sizeof(CameraConstants) * renderCuboidIndex;
/* ... */
m_graphicsAPI->SetBufferData(m_uniformBuffer_Camera, offsetCameraUB, sizeof(CameraConstants), &cameraConstants);
m_graphicsAPI->SetDescriptor({0, m_uniformBuffer_Camera, GraphicsAPI::DescriptorInfo::Type::BUFFER, GraphicsAPI::DescriptorInfo::Stage::VERTEX, false, offsetCameraUB, sizeof(CameraConstants)});

When spawning a cube this makes it index out of bounds of the buffer.
Suggested fix: Allocate the CameraConstants buffer for size 1, set the offsets to 0 in the other calls, and remove the renderCuboidIndex. We update the buffer for each cube anyway.

please have a look at the updated code (release 1.0.6 and up) it should fix the crash.

Works for me in a build, Quest 2 + OpenGL ES. No crash and I can see the blocks being reused when it hits max. Closing this issue. Thanks for the quick response!
Btw, I noticed a separate minor issue you may want to check out. When both controllers are active, a block spawns simultaneously for both controllers when pressing the A button.

Thanks for the report, I'll check it out.


Server not respondoing

The server provided in the validation test does not respond, you may want to enhance your documentation to reflect that and what changes are appropriate to pass this validation test.

Thanks. I have updated the server list. It is not easy to find running DSTU2 terminology servers, so I updated the readme as well.


koord-scheduler: fix status is not handled correctly in DeviceShare

Ⅰ. Describe what this PR does

Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist

[ ] I have written necessary docs and comments
[ ] I have added necessary unit tests and integration tests
[ ] All checks passed in make test

/lgtm


Added a fix for the Chrome on android

If max textures is one it can omit the attribute. This check that it exists..

smoooooth 👍


Feat:Update the bg color of progress bar in dark mode

Describe the feature
The background colour in dark mode of progress bar is white, I want to match it with dark mode's colours.
@huamanraj @RitiChandak @anuragverma108 please assign this to me under GSSoC'24.
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Assigned!
Make sure to attach before & after screenshots in your PR. Also, star the repo
before working on it. While creating your PR, ensure you pull all existing changes
beforehand to avoid conflicts.
Happy open-source contributing!


Issue rendering Font Awesome 5 in Chrome

Please make sure you are testing with the latest release of html2canvas.
Old versions are not supported and issues reported for them will be closed.
Please follow the general troubleshooting steps first:

[x] You are using the latest version
[x] You are testing using the non-minified version of html2canvas and checked any potential issues reported in the console

Bug reports:
I have an issue with rendering of font awesome 5 icons, they will only show up as squares. I'm using Google Chrome and Font Awesome 5 Pro.

Specifications:

html2canvas version tested with: 1.0.0-rc.3
Browser & version: Google Chrome 75.0.3770.80
Operating system: Windows 10

Same issue here. Any updates on this one? Thank you

Same issue.

Exactly the same issue. Any updates so far? Thanks.

I did some digging around and think this is down to the number within the CSS font family value (e.g. "Font Awesome 5 Free"). This causes an issue in the canvas renderer, since it uses the short-hand CSS syntax for setting the canvas context font.
Wrapping the font names in quotes fixed the issue for me. Submitted a PR for it.

hey, I have the same issue, I tried many solutions that exist in Github reported the issue but it still the same. any practical solution?

@ghafooridev use this PR (thank you @grahamkane)

For those having issues with this, also try to remove the spaces from your all.min.css file in Font awesome.  Your classnames should be this, for example FontAwesome5Pro, FontAwesome5Brands, etc.
My class names were in quotes and still not working, but after changing them to be without space my icons started rendering in html2canvas.

same issue for me?
using  html2canvas 1.0.0-rc.5  version.


In the zap UI, some attributes or event state or values do not reflect the zap config

When opening a zap file in the Zap UI, Events are shown as disabled when there are in fact enabled in the zap file
here an example for the all-cluster-app.zap The following access control cluster events are enabled
          "events": [
            {
              "name": "AccessControlEntryChanged",
              "code": 0,
              "mfgCode": null,
              "side": "server",
              "included": 1
            },
            {
              "name": "AccessControlExtensionChanged",
              "code": 1,
              "mfgCode": null,
              "side": "server",
              "included": 1
            }

But the UI shows them as disabled.

You can enable them, save the file and close it. Re-open it and the UI will show those events as disabled again. The zap file will not be impacted, the event stay actually enabled and you can generate correctly.
I have seen similar phenomenon with default values set for attributes in the UI. Config files are saved correctly with the correct default values. But if you reopen it in the zap UI the value box will be empty.

fixed in latest commit + nightly


Network request error creates non-serializable action

I'm using redux-toolkit which includes custom middleware that checks if Redux actions are serializable. When a RequestError occurs, it looks like redux-api-middleware creates a non-serializable Redux action, which it probably shouldn't:
A non-serializable value was detected in an action, in the path: `payload`. Value:, [RequestError: Network request failed],
Take a look at the logic that dispatched this action: , Object {
  "error": true,
  "meta": undefined,
  "payload": [RequestError: Network request failed],
  "type": "auth/authFailure",
},
(See https://redux.js.org/faq/actions#why-should-type-be-a-string-or-at-least-serializable-why-should-my-action-types-be-constants)
- node_modules/expo/build/logs/LogSerialization.js:166:14 in _captureConsoleStackTrace
- node_modules/expo/build/logs/LogSerialization.js:41:24 in serializeLogDataAsync
- ... 9 more stack frames from framework internals

Actually it will throw this warning in more cases for all this errors InvalidRSAA, RequestError, InternalError.
I think that this errors can be replaced with some raw objects. But this will imply a breaking change, because this errors a part of public API
https://github.com/agraboso/redux-api-middleware/blob/master/src/errors.js

I am using redux toolkit with react native and custom fetch implementation and I've noticed something similar. It fails intermittently with the  non-serializable error complaining about the provided fetch property. It is really hard to debug cause It happens like 2% of the times.

A solution would be to implement toJSON for each non-serializable error.

I am experiencing the same issue but with ApiError which is provided by redux-api-middleware and occurs on request failure (401 HTTP status in my case).

I actually solved the problem. In my case it was my token refresh functionality and custom fetch attached to every action. After receiving 401 (expired token) I was getting new token and retrying all queued requests. All re-tries were getting non-serializable action warning. I simply passed my custom fetch implementation to createMiddleware() instead of passing to each action as a prop.


React Native 0.70.0

Hello,
I am looking forward to trying your library out, but I am using react-native 0.68.
Is there a particular reason for putting react-native >= 0.70.0 in your peerDependencies list?
Thanks a lot!

hello @danyzor  sorry for late response I have to enable notifications for the project.
to be honest its not necessary for the app to be >= 70, did you face any issues using it?

I can confirm it works on react native 0.68. Thanks for your response and your library! :)


Selectors

What about pulling a Lua where objects names must start with a character which would get rid of needing the # syntax.
@a.b -- object[a][b]
@1.b -- [b] object within the first root object

Ambiguous, properties are referenced using that syntax right now.
@#a.width and @a.#width are two different things and I require selectors to be completely unambiguous.


Creating a Microsoft.Build.Evaluation.Project with an SDK fails with an "Internal MSBuild Error"

Microsoft Visual Studio Enterprise 2017 Int Preview
Version 15.6.0 Preview 5.0 [27411.0.d15.6]

Run the following:

           var projectRootElement = @"
<Project Sdk=""Microsoft.NET.Sdk"">

</Project>"

            var stringReader = new System.IO.StringReader(projectRootElement);
            var xmlReader = new XmlTextReader(stringReader);
            var root = ProjectRootElement.Create(xmlReader);
            var project = new Project(root);

Result StackTrace:
at Microsoft.Build.Shared.ErrorUtilities.ThrowInternalError(String message, Object[] args)
   at Microsoft.Build.Shared.ErrorUtilities.VerifyThrow(Boolean condition, String unformattedMessage, Object arg0)
   at Microsoft.Build.Shared.AssemblyResources.GetStringFromEngineResources(String name)
   at Microsoft.Build.Shared.AssemblyResources.GetString(String name)
   at Microsoft.Build.BackEnd.Logging.LoggingService.LogWarningFromText(BuildEventContext buildEventContext, String subcategoryResourceName, String warningCode, String helpKeyword, BuildEventFileInfo file, String message)
   at Microsoft.Build.BackEnd.Logging.LoggingService.LogWarning(BuildEventContext buildEventContext, String subcategoryResourceName, BuildEventFileInfo file, String messageResourceName, Object[] messageArgs)
   at Microsoft.Build.BackEnd.SdkResolverLoader.LoadResolvers(LoggingContext loggingContext, ElementLocation location)
   at Microsoft.Build.BackEnd.SdkResolution.Initialize(LoggingContext loggingContext, ElementLocation location)
   at Microsoft.Build.BackEnd.SdkResolution.GetSdkPath(SdkReference sdk, LoggingContext loggingContext, ElementLocation sdkReferenceLocation, String solutionPath, String projectPath)
   at Microsoft.Build.Evaluation.Evaluator`4.ExpandAndLoadImportsFromUnescapedImportExpressionConditioned(String directoryOfImportingFile, ProjectImportElement importElement, List`1& projects, Boolean throwOnFileNotExistsError)
   at Microsoft.Build.Evaluation.Evaluator`4.ExpandAndLoadImports(String directoryOfImportingFile, ProjectImportElement importElement)
   at Microsoft.Build.Evaluation.Evaluator`4.EvaluateImportElement(String directoryOfImportingFile, ProjectImportElement importElement)
   at Microsoft.Build.Evaluation.Evaluator`4.PerformDepthFirstPass(ProjectRootElement currentProjectOrImport)
   at Microsoft.Build.Evaluation.Evaluator`4.Evaluate(ILoggingService loggingService, BuildEventContext buildEventContext)
   at Microsoft.Build.Evaluation.Evaluator`4.Evaluate(IEvaluatorData`4 data, ProjectRootElement root, ProjectLoadSettings loadSettings, Int32 maxNodeCount, PropertyDictionary`1 environmentProperties, ILoggingService loggingService, IItemFactory`2 itemFactory, IToolsetProvider toolsetProvider, ProjectRootElementCache projectRootElementCache, BuildEventContext buildEventContext, ProjectInstance projectInstanceIfAnyForDebuggerOnly, SdkResolution sdkResolution)
   at Microsoft.Build.Evaluation.Project.Reevaluate(ILoggingService loggingServiceForEvaluation, ProjectLoadSettings loadSettings)
   at Microsoft.Build.Evaluation.Project.ReevaluateIfNecessary(ILoggingService loggingServiceForEvaluation, ProjectLoadSettings loadSettings)
   at Microsoft.Build.Evaluation.Project.Initialize(IDictionary`2 globalProperties, String toolsVersion, String subToolsetVersion, ProjectLoadSettings loadSettings)
   at Microsoft.Build.Evaluation.Project..ctor(ProjectRootElement xml, IDictionary`2 globalProperties, String toolsVersion, String subToolsetVersion, ProjectCollection projectCollection, ProjectLoadSettings loadSettings)
   at Microsoft.Build.Evaluation.Project..ctor(ProjectRootElement xml)
   at Microsoft.VisualStudio.ProjectSystem.VS.Input.Commands.Ordering.OrderingHelperTests.MoveDownFolder_ContainsNestedFolder_IsSuccessful()
Result Message:	Microsoft.Build.Shared.InternalErrorException : MSB0001: Internal MSBuild Error: Missing resource ''

This is failing all our tests that use MSBuild.

@jeffkl Was there any changes around this?

Was there any changes around this?

I sort of rewrote the whole thing in 15.6...
It looks like from the stack trace that MSBuild is trying to log a warning from an embedded resource string but the resource was not found.  What is the layout of your assemblies?  Do you have en\Microsoft.Build.resources.dll?
I'll also see if I can repro the problem.

Hmm another thing is the stack trace doesn't make sense.  The Microsoft.Build.BackEnd.SdkResolution class does not exist anymore.  Are you sure your Microsoft.Build.dll is 15.6?
This is the only LogWarning call in the now deleted class:
https://github.com/Microsoft/msbuild/blob/d026eba43c429802f14ad4bfe57b18e56d2519c7/src/Build/BackEnd/Components/SdkResolution/SdkResolverLoader.cs#L49
My commit on Jan 8 to improve SDK resolution https://github.com/Microsoft/msbuild/commit/03d1435c95e6a85fbf949f94958e743bc44c4186

I am using 15.1.548 and have started seeing this since updating my VS to 15.6. Not sure if thats a coincidence
Output:

Test Name:	DnnVsProjectSystem.BuildTools.Tests.ManifestBuildTests.Replaces_Tokens_In_Manifest
Test FullName:	DnnVsProjectSystem.BuildTools.Tests.ManifestBuildTests.Replaces_Tokens_In_Manifest
Test Source:	E:\Repos\DnnVsProjectSystem\src\DnnVsProjectSystem.BuildTools.Tests\ManifestBuildTests.cs : line 88
Test Outcome:	Failed
Test Duration:	0:00:01.462

Result StackTrace:
at Microsoft.Build.Shared.ErrorUtilities.ThrowInternalError(String message, Object[] args)
at Microsoft.Build.Shared.ErrorUtilities.VerifyThrow(Boolean condition, String unformattedMessage, Object arg0)
at Microsoft.Build.Shared.AssemblyResources.GetStringFromEngineResources(String name)
at Microsoft.Build.Shared.AssemblyResources.GetString(String name)
at Microsoft.Build.BackEnd.Logging.LoggingService.LogWarningFromText(BuildEventContext buildEventContext, String subcategoryResourceName, String warningCode, String helpKeyword, BuildEventFileInfo file, String message)
at Microsoft.Build.BackEnd.Logging.LoggingService.LogWarning(BuildEventContext buildEventContext, String subcategoryResourceName, BuildEventFileInfo file, String messageResourceName, Object[] messageArgs)
at Microsoft.Build.BackEnd.SdkResolverLoader.LoadResolvers(LoggingContext loggingContext, ElementLocation location)
at Microsoft.Build.BackEnd.SdkResolution.Initialize(LoggingContext loggingContext, ElementLocation location)
at Microsoft.Build.BackEnd.SdkResolution.GetSdkPath(SdkReference sdk, LoggingContext loggingContext, ElementLocation sdkReferenceLocation, String solutionPath, String projectPath)
at Microsoft.Build.Evaluation.Evaluator4.ExpandAndLoadImportsFromUnescapedImportExpressionConditioned(String directoryOfImportingFile, ProjectImportElement importElement, List1& projects, Boolean throwOnFileNotExistsError)
at Microsoft.Build.Evaluation.Evaluator4.ExpandAndLoadImports(String directoryOfImportingFile, ProjectImportElement importElement)    at Microsoft.Build.Evaluation.Evaluator4.EvaluateImportElement(String directoryOfImportingFile, ProjectImportElement importElement)
at Microsoft.Build.Evaluation.Evaluator4.PerformDepthFirstPass(ProjectRootElement currentProjectOrImport)    at Microsoft.Build.Evaluation.Evaluator4.Evaluate(ILoggingService loggingService, BuildEventContext buildEventContext)
at Microsoft.Build.Evaluation.Evaluator4.Evaluate(IEvaluatorData4 data, ProjectRootElement root, ProjectLoadSettings loadSettings, Int32 maxNodeCount, PropertyDictionary1 environmentProperties, ILoggingService loggingService, IItemFactory2 itemFactory, IToolsetProvider toolsetProvider, ProjectRootElementCache projectRootElementCache, BuildEventContext buildEventContext, ProjectInstance projectInstanceIfAnyForDebuggerOnly, SdkResolution sdkResolution)
at Microsoft.Build.Evaluation.Project.Reevaluate(ILoggingService loggingServiceForEvaluation, ProjectLoadSettings loadSettings)
at Microsoft.Build.Evaluation.Project.ReevaluateIfNecessary(ILoggingService loggingServiceForEvaluation, ProjectLoadSettings loadSettings)
at Microsoft.Build.Evaluation.Project.Initialize(IDictionary2 globalProperties, String toolsVersion, String subToolsetVersion, ProjectLoadSettings loadSettings)    at Microsoft.Build.Evaluation.Project..ctor(String projectFile, IDictionary2 globalProperties, String toolsVersion, String subToolsetVersion, ProjectCollection projectCollection, ProjectLoadSettings loadSettings)
at Microsoft.Build.Evaluation.ProjectCollection.LoadProject(String fileName, IDictionary2 globalProperties, String toolsVersion)    at Microsoft.Build.Evaluation.ProjectCollection.LoadProject(String fileName)    at DnnVsProjectSystem.BuildTools.Tests.MsBuildHelper.Build(String fileName, Action1 configure, String& consoleOutput) in E:\Repos\DnnVsProjectSystem\src\DnnVsProjectSystem.BuildTools.Tests\Util\MsBuildHelper.cs:line 108
at DnnVsProjectSystem.BuildTools.Tests.ManifestBuildTests.BuildTestProject(String projectFileName, Boolean assertIsSuccess, Action1 onBeforeBuild, String& consoleOutput) in E:\Repos\DnnVsProjectSystem\src\DnnVsProjectSystem.BuildTools.Tests\ManifestBuildTests.cs:line 198    at DnnVsProjectSystem.BuildTools.Tests.ManifestBuildTests.WhenProjectIsBuilt(String projectName, Boolean assertSuccess, Action1 assert) in E:\Repos\DnnVsProjectSystem\src\DnnVsProjectSystem.BuildTools.Tests\ManifestBuildTests.cs:line 136
at DnnVsProjectSystem.BuildTools.Tests.ManifestBuildTests.Replaces_Tokens_In_Manifest() in E:\Repos\DnnVsProjectSystem\src\DnnVsProjectSystem.BuildTools.Tests\ManifestBuildTests.cs:line 89
Result Message:	Microsoft.Build.Shared.InternalErrorException : MSB0001: Internal MSBuild Error: Missing resource ''

@dazinator the stack trace references a class that no longer exists.  Are you sure you're running the latest MSBuild?  When you compile your app, are you getting the assemblies from a NuGet package?

Here is some more info:
I see this error thrown when trying to load an sdk style proj file into a ProjectCollection during a unit test.
My unit test project is xunit and targets net461.
It has a project reference to the project containing the msbuild task that it is testing.
The test first does some "prep" work by attempting to build the task project itself (which I also have open in VS) and then pack the task project in order to produce a nuget package with a packageversion that the test has supplied. The test then generates a proj file that has a package reference to the nuget package with the version it created in the previous step. The test then restores this test proj file and then builds the test proj file - and then asserts on the output of the build to see if the msbuild task contained in the package did its job.
The msbuild task project is compiled against :-

Microsoft.Build.Framework 15.1.548
Microsoft.Build.Utilities.Core 15.1.548

My test project actually pulls in a higher version of those msbuild packages plus a couple exrtra:

Microsoft.Build.Framework 15.3.409
Microsoft.Build.Utilities.Core 15.3.409
Microsoft.Build.Tasks.Core 15.3.409
Microsoft.Build 15.3.409

..and then uses an app.config binding redirect to downgrade the MsBuild.Framework binary to newVersion=15.1.0
This was a workaround after many many attempts at trying to load an SDK style project file using msbuild nuget packages, unsuccessfully, this was the only approach I could find that worked.
When the test runs it also has to set the following Environment Variables before trying to load a project with msbuild, otherwise I was seeing all sorts of other problems raised elsewhere about not being able to find certain paths:
                    Environment.SetEnvironmentVariable("VSINSTALLDIR", "C:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\Community"):

            Environment.SetEnvironmentVariable("VisualStudioVersion", "15.0");

This test has been running fine, but like I say, today it has started breaking when trying to load an sdk style project, and the only thing I can think of that has changed is the vs upgrade. Perhaps I am missing something!

@dazinator Is there anyway you can use something like fusion log viewer or procmon to verify which Microsoft.Build.dll is being loaded?  Its definitely not loading the one you installed with 15.6 because the class in the stack trace is long gone.  It could be a bug in 15.3 that we've fixed but the mystery is still why it started to manifest all of a sudden.  I haven't been able to repro the issue.
@davkean Are you still hitting this?

@dazinator, maybe one more attempt and try compiling against 15.6.82 from NuGet (released 8 days ago) or 15.7.0-preview-000066 from myget (released 12 hours ago) to see if the problem persists.
For myget preview, add msbuild feed as additional sources:
<PropertyGroup>
  <RestoreAdditionalProjectSources>https://dotnet.myget.org/F/msbuild/api/v3/index.json</RestoreAdditionalProjectSources>
</PropertyGroup>

I have figured out the problem.  MSBuild 15.3 shipped with two bugs in the SDK resolver loader logic:

When searching for classes in an SDK resolver, abstract classes were not filtered out.  If an SDK resolver had a class that inherited SdkResolver but was abstract, it would attempt to create an instance of the abstract class and throw an exception
The above exception would be caught and logged as a warning but the LogWarning call passed String.Empty instead of null which would throw an internal error which is treated as a fatal MSBuild error

We fixed the two bugs in MSBuild 15.6 but we also shippped a NuGet-based SDK resolver which has a public abstract class that inherits from SdkResolver.
Your unit tests are using MSBuild 15.3 to create an MSBuild environment but are pointing to the installation of MSBuild 15.6.  The logic in Microsoft.Build.dll is loading SDK resolvers from the installed location and so you hit these bugs.
You can update your references to the latest MSBuild which will fix the issue.  We cannot patch 15.3 to fix the bugs and we can't patch 15.6 to remove the abstract class that is causing the bugs to manifest.
In some cases, it might be best to use MSBuildLocator instead which finds and loads the Microsoft.Build.dll from the installed location rather than your output directory.  This means that even if you're compiled against an older version, you'll be running the latest Microsoft.Build.dll.
FYI @AndyGerlicher

@jeffkl  Thank you for investigating and I am glad for the answer.
I will try what you have suggested, MSBuildLocator seems like a good way forward.
On a slight tangent, may I ask, in the situation where I have an msbuild task compiled against 15.1 and I know that msbuild environments in the wild might be on 15.1, or 15.3 or 15.6, I need to test that my msbuild task works in all those msbuild environments. In this case would MSBuildLocator be a capable strategy - for example, can I install 15.1, 15.3, and 15.6 alongside each other on a single machine and then use MSBuildLocator at test time to use the specific version required for the test?

@dazinator if you have just a task library, you should not have to worry about testing against all versions.  MSBuild's assembly version is always 15.1 so your references will be that and you'll get whatever versions are next to MSBuild.exe.
You'll only need to use MSBuildLocator if you want to programatically evaluate or build projects outside of MSBuild.exe.  This is common in unit tests or a custom program that does stuff with projects.

@jeffkl Ok thanks. I would prefer to have test coverage of my task running in various different msbuild environments but I suppose I can consider dropping that idea if MSBuild "swears" to maintain compatibility with 15.1 :-)
I'll switch to MSBuildLocator for my tests and update my references in my test project to 15.6. Thanks again.

We try very hard to not break back compat especially for tasks.  If we do, please open an issue!  Unfortunately, doing programmatic evaluations and builds is just more complex because you need to load Microsoft.Build.dll in order to find MSBuild and we don't put our assemblies in the GAC anymore.   This is because you can have numerous instances of Visual Studio installed side-by-side.  So programmatic evaluations need to load Microsoft.Build.dll from the appropriate installed location rather than their own.
But again, task assemblies are loaded by MSBuild itself and do not have to worry about it.  Even if we shipped MSBuild 16.0, we have assembly binding redirects in our app.config so your task compiled against 15.1 would still work, unless of course there was a breaking change, which again we try very hard not to do.

Going to reopen this

Also hit here: https://github.com/dotnet/docfx/issues/2491


Imported material.dart for Rect class

Could not source Rect class due to missing import

Flutter analyzer recommends that material.dart import is not necessary but without it there is a build error

@Saahir999 : you need to update your flutter version

I think https://github.com/bharat-biradar/Google-Ml-Kit-plugin/pull/401 fixes this one.


libinput: Touch event handling is not reliable

The current way to handle a touch event, gets the x/y position of the event, and the size of the device and reports them as x/y+width/height in the wlr_event.
There's also libinput_event_touch_get_x_transformed which gets a pre-transformed x value.
This uses evdev variables internally, that I don't think get exported to us.
It applies the transformation with a minimum and maximum axis value.
On my machineTM things work if I simply replace width/height with 1, and let libinput transform the event coordinates into a a width/height of 1.

Fixed in #765


Assign a license

Once your application has at least one license credit available, you can assign it to a Pushover user by their Pushover account e-mail address or their Pushover user key if known.
If a license is assigned to an e-mail address, it will remain pending in our systems (but deducted from your available credits) until a user signs up with that e-mail address, at which time the license will be automatically activated.
https://pushover.net/api/licensing#assign

#28 Implements this changes.


Refactor to avoid features mingling, and some bug fixs

refactor openid feature to avoid minglign with crates-io-mirroring.
Current implementation mingles openid feature with crates-io-mirroring,  which can certainly work, but in the future it can be really hard to maintain when more features adding in. Now 4 functions is written to handle different case for two features, then what if we have dozens of features?
#[cfg(all(feature = "crates-io-mirroring", feature = "openid"))]
fn apis(
    db_manager: Arc<RwLock<impl DbManager>>,
    index_manager: Arc<IndexManager>,
    dl_dir_path: Arc<PathBuf>,
    http_client: Client,
    cache_dir_path: Arc<PathBuf>,
    dl_path: Vec<String>,
    openid_config: Arc<OpenIdConfig>,
) -> impl Filter<Extract = impl Reply, Error = Rejection> + Clone;

Actually, current implementation does not handle feature conflicts correctly, that disable crates-io-mirroring feature can actually fail the cargo build.

fix a some minor bug that disallow any user to publish when authorized_users and authorized_groups is Some(vec![]).

Thanks a lot for your help on that. I totally forgot variable shadowing is a thing :)


Enable manually controllable tri-state selection

I have a situation where I have a large checkbox tree with thousands of individual nodes. I want the child nodes to be lazy loaded, but I also want to display a half-check based upon my own state information.
Currently, it seems that this is impossible as this state information is only tracked when the builtin tri-state behavior is enabled.

Did you find a custom solution to this?

No, I never found a suitable solution.

Hi,
this could be accomplished with custom templates and your own management of the checkbox state.
All the best


The "Database Size" widget in "Server dashboard" does not show the size value in the diagram on some localized systems

SQL Operations Studio Version:
0.25.4

Steps to Reproduce:
Environment: Windows 10  localized in Italian (or the same should be reproducible by setting the system language to Italian or French or German, so that the decimal separator is ',' (comma)).
Open SqlOpsStudio, connect on a Sql Server instance and click on a database to see the "Server dashboard". The Database Size widget shows only a list of databases without the size value.
The same problem occurs if you try to see the chart for a generic query that produces a non-integer number.

On Brazilian Portuguese too

Closing out older issues that we won't be able to fix in an upcoming milestone.  We've made significant updates to the problem in this area so it is possible the issue is resolved in the latest release.  Thanks for reporting the bug!