[Doc Improvement][Build search based message extension SBS Guide]

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/sbs-messagingextension-searchcommand.yml
84
32
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit be6b716:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/sbs-messagingextension-searchcommand.yml
:warning:Warning
View
Details

msteams-platform/sbs-messagingextension-searchcommand.yml

Line 73, Column 6: [Warning: file-not-found - See documentation] Invalid file link: './assets/images/azure-bot_1.png'.

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

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/sbs-messagingextension-searchcommand.yml
84
30
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 184fce6:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/sbs-messagingextension-searchcommand.yml
:warning:Warning
View
Details

msteams-platform/assets/images/azure-bot_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/meetings-side-panel/terms_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/meeting-token-generator/meeting-token-generator-appidcreate_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/meeting-token-generator/meeting-token-generator-VSopenfile_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/ngrok-url_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/sbs-messagingextension-action/configure-msteams_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/addapp_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/addascope_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/appIDuri_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/appregister_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/appsettings_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/AppStore_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/authend_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/authorizedscope_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/botdeployment_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/bot-page_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/clientvalue_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/exposeanapi_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/fileready_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/gotohome_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/manifest_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/messaging-endpoint_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/review-plus-create_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/scopes_1.PNG
:white_check_mark:Succeeded
View

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

msteams-platform/sbs-messagingextension-searchcommand.yml

Line 372, Column 7: [Warning: file-not-found - See documentation] Invalid file link: './assets/images/Teams-task-module/solutionexplorer_1'.
Line 378, Column 7: [Warning: file-not-found - See documentation] Invalid file link: './assets/images/Teams-Messaging-Extensions-Search/startup_1'.
Line 417, Column 4: [Warning: file-not-found - See documentation] Invalid file link: './assets/images/Teams-Messaging-Extensions-Search/AppStore_1'.
Line 421, Column 4: [Warning: file-not-found - See documentation] Invalid file link: './assets/images/Teams-task-module/upload-app_1'.
Line 429, Column 4: [Warning: file-not-found - See documentation] Invalid file link: './assets/images/Teams-Messaging-Extensions-Search/addapp_1'.

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/sbs-messagingextension-searchcommand.yml
84
30
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/assets/images/azure-bot_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/meetings-side-panel/terms_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/meeting-token-generator/meeting-token-generator-appidcreate_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/meeting-token-generator/meeting-token-generator-VSopenfile_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/ngrok-url_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/sbs-messagingextension-action/configure-msteams_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/addapp_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/addascope_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/appIDuri_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/appregister_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/appsettings_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/AppStore_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/authend_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/authorizedscope_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/botdeployment_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/bot-page_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/clientvalue_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/exposeanapi_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/fileready_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/gotohome_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/manifest_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/messaging-endpoint_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/review-plus-create_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/scopes_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/setlink_1.PNG
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/sbs-messagingextension-searchcommand.yml
84
30
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 49dae0c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/azure-bot_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/meetings-side-panel/terms_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/meeting-token-generator/meeting-token-generator-appidcreate_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/meeting-token-generator/meeting-token-generator-VSopenfile_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/ngrok-url_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/sbs-messagingextension-action/configure-msteams_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/addapp_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/addascope_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/appIDuri_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/appregister_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/appsettings_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/AppStore_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/authend_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/authorizedscope_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/botdeployment_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/bot-page_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/clientvalue_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/exposeanapi_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/fileready_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/gotohome_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/manifest_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/messaging-endpoint_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/review-plus-create_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/scopes_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/setlink_1.PNG
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/sbs-messagingextension-searchcommand.yml
84
30
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 63db4f0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/azure-bot_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/meetings-side-panel/terms_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/meeting-token-generator/meeting-token-generator-appidcreate_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/meeting-token-generator/meeting-token-generator-VSopenfile_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/ngrok-url_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/sbs-messagingextension-action/configure-msteams_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/addapp_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/addascope_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/appIDuri_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/appregister_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/appsettings_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/AppStore_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/authend_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/authorizedscope_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/botdeployment_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/bot-page_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/clientvalue_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/exposeanapi_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/fileready_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/gotohome_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/manifest_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/messaging-endpoint_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/review-plus-create_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/scopes_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/setlink_1.PNG
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/sbs-messagingextension-searchcommand.yml
84
30
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

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

File
Status
Preview URL
Details

msteams-platform/assets/images/azure-bot_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/meetings-side-panel/terms_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/meeting-token-generator/meeting-token-generator-appidcreate_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/meeting-token-generator/meeting-token-generator-VSopenfile_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/ngrok-url_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/sbs-messagingextension-action/configure-msteams_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/addapp_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/addascope_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/appIDuri_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/appregister_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/appsettings_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/AppStore_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/authend_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/authorizedscope_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/botdeployment_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/bot-page_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/clientvalue_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/exposeanapi_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/fileready_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/gotohome_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/manifest_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/messaging-endpoint_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/review-plus-create_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/scopes_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/setlink_1.PNG
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/sbs-messagingextension-searchcommand.yml
85
30
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit a862938:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/azure-bot_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/meetings-side-panel/terms_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/meeting-token-generator/meeting-token-generator-appidcreate_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/meeting-token-generator/meeting-token-generator-VSopenfile_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/ngrok-url_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/sbs-messagingextension-action/configure-msteams_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/addapp_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/addascope_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/appIDuri_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/appregister_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/appsettings_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/AppStore_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/authend_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/authorizedscope_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/botdeployment_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/bot-page_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/clientvalue_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/exposeanapi_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/fileready_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/gotohome_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/manifest_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/messaging-endpoint_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/review-plus-create_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/scopes_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/setlink_1.PNG
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/sbs-messagingextension-searchcommand.yml
85
30
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 4530a70:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/azure-bot_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/meetings-side-panel/terms_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/meeting-token-generator/meeting-token-generator-appidcreate_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/meeting-token-generator/meeting-token-generator-VSopenfile_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/ngrok-url_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/sbs-messagingextension-action/configure-msteams_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/addapp_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/addascope_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/appIDuri_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/appregister_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/appsettings_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/AppStore_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/authend_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/authorizedscope_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/botdeployment_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/bot-page_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/clientvalue_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/exposeanapi_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/fileready_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/gotohome_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/manifest_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/messaging-endpoint_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/review-plus-create_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/scopes_1.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Teams-Messaging-Extensions-Search/setlink_1.PNG
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

The PR contents have been merged into PR #7077.


New login component

Added a new login component that uses Google's login API and Facebook's login API to log in without having the need to store sensitive data. The UI is a bit ugly but the buttons work as intended.

Closing this as it is a duplicate of new_login_system_functional #108


Signup form

Added axios call to signup

the axios call is sending data to the backend, however we are getting a 500 error.

Removed duplicated files

removed the duplicated axiosWithAuth() files.


can be regularities used for classifier?

this code
reg = regularizers.L2(0, 0, .01)
fm_classifier = Classifier(X_t.shape[1] , k=2, X_format="csr",regularizer=reg)
gives error:
File "E:\Recommender_systems\code\PyFactorizationMachines_May2\PyFactorizationMachines\S_May3_changed_hashing_size_Theano_FM_sparse.py", line 74, in
fm_classifier = Classifier(X_t.shape[1] , k=2, X_format="csr",regularizer=reg)
File "E:\Recommender_systems\code\PyFactorizationMachines_May2\PyFactorizationMachines\pyfms\models.py", line 10, in init
feature_count, transformer, **kwargs)
builtins.TypeError: init() got an unexpected keyword argument 'regularizer'

Hi @Sandy4321, the regularizer should be passed to the fit method, not the Classifier constructur.
Something like:
reg = regularizers.L2(0, 0, .01)
fm_classifier = Classifier(X_t.shape[1] , k=2, X_format="csr")
fm_classifier .fit(X_t, y_t, regularizer=reg)

great thanks
by the way
it would be very kind of you to add L1 regularization as well
the difference in code is not big
http://www.chioka.in/differences-between-l1-and-l2-as-loss-function-and-regularization/
penalty = (self.beta_w0 * (w0 ** 2)) \
              + (self.beta_w1 * T.mean(w1 ** 2)) \
              + (self.beta_v * T.mean(v ** 2))

will have change ** by abs??

it would be very kind of you to add L1 regularization as well

Done (1ee9dad19fb477ceada8a7f256bc177526762281).
Please note that the code is extensible. That is, if there is a type of regularization that you would like to use, which is not already included, you can define a regularization class in your code, and use it as the regularizer.


Clarification on Null-Conditional Operator for Member Access

The document for the null-conditional operator for member access should clearly state whether the use of the operator always guarantees that there will never be a NullReferenceException w.r.t. to the left-hand operand. The following statement exists in the document but does so only in the context of the Invoke method called on delegates:

The ?. operator evaluates its left-hand operand no more than once, guaranteeing that it cannot be changed to null after being verified as non-null.

If the above statement is true regardless of the type of the left-hand operand then it should be moved higher up in the doc and outside the section that pertains to its use with delegates.

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

ID: 0a25abe4-2b4e-119e-85e9-af19ed06e8c0
Version Independent ID: 682b8c86-e49a-1d6d-8562-c9f919082bdc
Content: Member access operators and expressions - C# reference
Content Source: docs/csharp/language-reference/operators/member-access-operators.md
Product: dotnet-csharp
Technology: csharp-language-reference
GitHub Login: @pkulikov
Microsoft Alias: wiwagn

Thanks, Bill - I've submitted the PR: https://github.com/dotnet/docs/pull/29966
Prasad
From: Bill Wagner @.>
Sent: Wednesday, June 22, 2022 05:57
To: dotnet/docs @.>
Cc: Prasad Ullal @.>; Mention @.>
Subject: Re: [dotnet/docs] Clarification on Null-Conditional Operator for Member Access (Issue #29953)
Thanks for noting this and submitting a fix @prasadu-microsofthttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fprasadu-microsoft&data=05|01|Prasad.Ullal%40microsoft.com|8d6ec1ee6ed44844456508da544ea432|72f988bf86f141af91ab2d7cd011db47|1|0|637914993984556933|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=CrM9%2BuCQmpJcZd%2F4%2BbyI9Za1MV3XQEBIOESpdFiljPw%3D&reserved=0
I'll review the PR later this morning.

Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdotnet%2Fdocs%2Fissues%2F29953%23issuecomment-1163063763&data=05|01|Prasad.Ullal%40microsoft.com|8d6ec1ee6ed44844456508da544ea432|72f988bf86f141af91ab2d7cd011db47|1|0|637914993984556933|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=4QAo0ENPkkB7QLXofIsMQqRRFCI1bnPCPQAsUb8yoNE%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAIV3KWQPK56IAKO3RKHVTHDVQMEQHANCNFSM5ZNRFKDQ&data=05|01|Prasad.Ullal%40microsoft.com|8d6ec1ee6ed44844456508da544ea432|72f988bf86f141af91ab2d7cd011db47|1|0|637914993984556933|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=JF02lVJK67qYWEMhB1MnB9xl1w9D6JLQ6zdfO0xSjMk%3D&reserved=0.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>


animation date change hangs the webpage

Problem
A change in animation date using the keyboard hangs the webpage
Browser: Only Safari
Spread link: https://view.spreadviz.org/?output=ddf9ff80-334a-475d-8cdd-901925a32877/b6cce491-3fc3-4725-9fd8-a0e56b5afa19.json&maps=RU,MX,US,BS,CA
https://user-images.githubusercontent.com/29096492/151952973-cce12118-e94f-4e8d-9080-e1fce9db09de.mov

Could not reproduce, please check @jpmonettas, if not close it


Fix multiple 'Core' target

Fix #1048

You may need to change other old name imports, please refer https://github.com/yonaskolb/XcodeGen/compare/fix/spm-Core#diff-ac563a49106c2d342e331e34d932ba62ffa0ad0ceebce6edfb78a4efbc31cb6f

Ops sorry, Could you help adding CHAGELOG.md to your changes? https://github.com/yonaskolb/XcodeGen/blob/master/CHANGELOG.md

Thanks @d-date, closing in favour of https://github.com/yonaskolb/XcodeGen/pull/1057


"invalid id:" stats gathering error in logs

Hi,
weavescope version: 0.17.1
kubernetes version: 1.3.6
docker version
Client:
 Version:      1.11.2
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   b9f10c9
 Built:        Wed Jun  1 21:23:39 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.11.2
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   b9f10c9
 Built:        Wed Jun  1 21:23:39 2016
 OS/Arch:      linux/amd64

I get lots of errors in docker logs when probe process runs in kubernetes.
Sep 12 13:26:05 ip-10-100-66-180 docker[6393]: time="2016-09-12T13:26:05.038475237Z" level=error msg="collecting stats for b1417c66b2512b55fb079b5815e86b5611eb125a29100b7a2d4583e44325c575: invalid id: "
Sep 12 13:26:05 ip-10-100-66-180 docker[6393]: time="2016-09-12T13:26:05.041059139Z" level=error msg="collecting stats for d014c832df96fa39ffb91d7880be85024f3a627527f90141f4736f3c52613a0b: invalid id: "
Sep 12 13:26:05 ip-10-100-66-180 docker[6393]: time="2016-09-12T13:26:05.743684587Z" level=error msg="collecting stats for d014c832df96fa39ffb91d7880be85024f3a627527f90141f4736f3c52613a0b: invalid id: "
Sep 12 13:26:05 ip-10-100-66-180 docker[6393]: time="2016-09-12T13:26:05.927764315Z" level=error msg="collecting stats for d55624b69447994c622b681618115b585e9381348f4bd67cbcea6c397a8f5918: invalid id: "
Sep 12 13:26:05 ip-10-100-66-180 docker[6393]: time="2016-09-12T13:26:05.928994551Z" level=error msg="collecting stats for e9c6efe47462e159d66b71966c7a0728a24dad3acd36a97d6e6d534a3ea4a85a: invalid id: "
Sep 12 13:26:05 ip-10-100-66-180 docker[6393]: time="2016-09-12T13:26:05.930907055Z" level=error msg="collecting stats for e1db58d26cf14b0531bad29d9ada1262b6bdebc9c31ca04289eb62735ef1443c: invalid id: "
Sep 12 13:26:05 ip-10-100-66-180 docker[6393]: time="2016-09-12T13:26:05.932262728Z" level=error msg="collecting stats for bb4352d1ab491268cf215416be9f5d6755a785026e2d36769def2a00761b100b: invalid id: "
Sep 12 13:26:05 ip-10-100-66-180 docker[6393]: time="2016-09-12T13:26:05.933434308Z" level=error msg="collecting stats for 999295c8ef123c664d860ef9a307fa65a6658868e5d1525148b151af89f17a38: invalid id: "

Once I stop the probe PODs the error goes away.
probe args
--no-app
--probe.docker.bridge=cbr0
--probe.docker=true
--probe.kubernetes=true
--probe.conntrack=false
--probe.proc.spy=false
--probe.processes=false
--weave=false
$(WEAVESCOPE_APP_SERVICE_HOST):$(WEAVESCOPE_APP_SERVICE_PORT)

I am guessing the containers in question are very short-lived and have vanished by the time scope tries to collect stats for them. The error is harmless, but we should really suppress it.

@rade,
The errors comes from docker logs not from weavescope. The containers runs are not short-lived they up for hours even days.

The errors comes from docker logs not from weavescope.

Are there any errors in the weavescope logs? I rather suspect you'll find similar errors there.

The containers runs are not short-lived they up for hours even days.

Both k8s and scope create short-lived internal (i.e. nothing to do with your app) containers. To check, see whether any of the container IDs mentioned in the logs do in fact exist. I rather suspect they don't (anymore).
If the problem is what I think it is then there is nothing we can do about it. But, as I said, it's harmless.

Don't think kubernets creates short-lived containers without reason. At least not in my case. I don't use any special resources, like jobs or autoscaler, etc ...
If I actually take one of the ids from the above log, I can see that those containers are up and running for long time, so I'm 100% positive it's not related to short-lived or not.
In the weavescope log I don't see anything special, here is the output since it was started:
<probe> INFO: 2016/09/12 11:01:49.200915 command line args: --logtostderr=true --mode=probe --no-app=true --probe.conntrack=false --probe.docker=true --probe.docker.bridge=cbr0 --probe.kubernetes=true --probe.proc.spy=false --probe.processes=false --weave=false <IP_ADDRESS>:80
<probe> INFO: 2016/09/12 11:01:49.200997 probe starting, version 0.17.1, ID 7fa4cdfa80971b0d
<probe> INFO: 2016/09/12 11:01:49.201011 publishing to: <IP_ADDRESS>:80
<probe> INFO: 2016/09/12 11:01:49.204233 Control connection to <IP_ADDRESS>:80 starting
<probe> INFO: 2016/09/12 11:01:49.226009 kubernetes: targeting api server https://<IP_ADDRESS>:443
<probe> ERRO: 2016/09/12 11:01:49.481500 plugins: problem loading: no such file or directory
<probe> INFO: 2016/09/12 11:01:52.538183 Publish loop for <IP_ADDRESS>:80 starting

Also you said the logs are harmless, I have no objections, but when you get about 10th of those messages per second you should start to worry, no?

Hmm doesn't look the problem is what I thought it was. Could be a docker bug; there was a problem with stats, especially in the context of k8s, pre 1.12 - see #1291.

@shamil can you try docker 1.12.1?

closing. if somebody can repro this with Docker >=1.12 then re-open.

Got lots of lines like this one on 1.12.5 on centos7 (No problem on 1.12.3) :
docker: time="2017-01-18T16:04:28.671968138+01:00" level=error msg="collecting stats for 1d1cc403eebd5a50e3e6bed9bfb4591f83c019b55e1a38253d7bc86f95c61968: sandbox 5165aa0643a7b47353183f92306fcbc145440251a0995a1a8acda44f16b46f30 not found"

docker/docker#30274


Raise minimum kubernetes version to v1.18.0 in ./chart/Chart.yaml

longhorn/longhorn#2757

Tested


report bug

in InverseDistTransform fuc,  out is CV_32FC1, but using out.at to get and assign data;
also，in CalibrationTrack，I think GenGridIsometry3f should be initialized in for loop(with iter)，otherwise, the iter may no sense, please check!
Thanks for your code

Thanks for pointing these bugs out !
I will get my hands on them ASAP.

The bug in CalibrationTrack is fixed in commit f0718c99faa4d7c00798559280064bc9ae9803f5.
For the one in InverseDistTransform, the at is used for accessing pixel value in edge_img which is a 8UC1 matrix. https://github.com/NERanger/auto_lidar_cam_calib/blob/f0718c99faa4d7c00798559280064bc9ae9803f5/src/Core.cc#L107
The out matrix is modified with float pointer.
https://github.com/NERanger/auto_lidar_cam_calib/blob/f0718c99faa4d7c00798559280064bc9ae9803f5/src/Core.cc#L109

The bug in CalibrationTrack is fixed in commit f0718c9.
For the one in InverseDistTransform, the at is used for accessing pixel value in edge_img which is a 8UC1 matrix.
https://github.com/NERanger/auto_lidar_cam_calib/blob/f0718c99faa4d7c00798559280064bc9ae9803f5/src/Core.cc#L107
The out matrix is modified with float pointer.
https://github.com/NERanger/auto_lidar_cam_calib/blob/f0718c99faa4d7c00798559280064bc9ae9803f5/src/Core.cc#L109

I mean the single thread(although not used).
// Single thread implementation
for (int col = 0; col < out.cols; ++col) {
for (int row = 0; row < out.rows; ++row) {
const uchar& edge_val = edge_img.at(row, col);
		uchar& out_val = out.at<uchar>(row, col);
		out_val = alpha * edge_val + (1.0f - alpha) * ComputeMaxTermInInverseTransform(edge_img, cv::Point2i(col, row));
	}
}


Add Mountain TZ_ALIASES

Add mst, mdt to Mountain timezone for consistency with the other North America TZ_ALIASES.

Cool. Done.


Big integer literals are not available in the configured target environment

Environment

Operating System: Linux
Node Version:     v18.16.0
Nuxt Version:     3.5.3
Nitro Version:    2.5.1
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      typescript, modules, alias, vite, ssr, build, hooks
Runtime Modules<EMAIL_ADDRESS>Build Modules:    -

Reproduction
https://github.com/specklesystems/speckle-server/pull/1647
Describe the bug
I'm using @vitejs/plugin-legacy to enable support for older browser versions (chrome65 specifically) and after upgrading to nuxt 3.5.3 I can no longer build the app because of the following error:
#31 102.0 ➤ YN0000: Nuxi 3.5.3
#31 102.0 ➤ YN0000: Nuxt 3.5.3 with Nitro 2.5.0
#31 104.1 ➤ YN0000: ℹ Using Tailwind CSS from ~/assets/css/tailwind.css
#31 107.0 ➤ YN0000: ℹ Building client...
#31 107.0 ➤ YN0000: ℹ vite v4.3.9 building for production...
#31 107.3 ➤ YN0000: ℹ transforming...
#31 134.2 ➤ YN0000: ℹ ✓ 5650 modules transformed.
#31 135.3 ➤ YN0000: ℹ rendering chunks...
#31 136.1 ➤ YN0000:
#31 136.1 ➤ YN0000:  ERROR  [vite:esbuild-transpile] Transform failed with 2 errors:
#31 136.1 ➤ YN0000: _nuxt/entry.!~{001}~.js:10665:80: ERROR: Big integer literals are not available in the configured target environment ("chrome65", "edge88", "es2020", "firefox78", "safari14" + 2 overrides)
#31 136.1 ➤ YN0000: _nuxt/entry.!~{001}~.js:10666:66: ERROR: Big integer literals are not available in the configured target environment ("chrome65", "edge88", "es2020", "firefox78", "safari14" + 2 overrides)
#31 136.1 ➤ YN0000:
#31 136.1 ➤ YN0000: Big integer literals are not available in the configured target environment ("chrome65", "edge88", "es2020", "firefox78", "safari14" + 2 overrides)
#31 136.1 ➤ YN0000: 10663|  const revivers = {
#31 136.1 ➤ YN0000: 10664|    NuxtError: (data) => createError(data),
#31 136.1 ➤ YN0000: 10665|    EmptyShallowRef: (data) => shallowRef(data === "_" ? void 0 : data === "0n" ? 0n : JSON.parse(data)),
#31 136.1 ➤ YN0000:    |                                                                                ^
#31 136.1 ➤ YN0000: 10666|    EmptyRef: (data) => ref(data === "_" ? void 0 : data === "0n" ? 0n : JSON.parse(data)),
#31 136.1 ➤ YN0000: 10667|    ShallowRef: (data) => shallowRef(data),
#31 136.1 ➤ YN0000:
#31 136.1 ➤ YN0000: Big integer literals are not available in the configured target environment ("chrome65", "edge88", "es2020", "firefox78", "safari14" + 2 overrides)
#31 136.1 ➤ YN0000: 10664|    NuxtError: (data) => createError(data),
#31 136.1 ➤ YN0000: 10665|    EmptyShallowRef: (data) => shallowRef(data === "_" ? void 0 : data === "0n" ? 0n : JSON.parse(data)),
#31 136.1 ➤ YN0000: 10666|    EmptyRef: (data) => ref(data === "_" ? void 0 : data === "0n" ? 0n : JSON.parse(data)),
#31 136.1 ➤ YN0000:    |                                                                    ^
#31 136.1 ➤ YN0000: 10667|    ShallowRef: (data) => shallowRef(data),
#31 136.1 ➤ YN0000: 10668|    ShallowReactive: (data) => shallowReactive(data),
#31 136.1 ➤ YN0000:
#31 136.1 ➤ YN0000:
#31 136.1 ➤ YN0000: ℹ ✓ built in 29.09s
#31 136.1 ➤ YN0000:
#31 136.1 ➤ YN0000:  ERROR  Transform failed with 2 errors:
#31 136.1 ➤ YN0000: _nuxt/entry.!~{001}~.js:10665:80: ERROR: Big integer literals are not available in the configured target environment ("chrome65", "edge88", "es2020", "firefox78", "safari14" + 2 overrides)
#31 136.1 ➤ YN0000: _nuxt/entry.!~{001}~.js:10666:66: ERROR: Big integer literals are not available in the configured target environment ("chrome65", "edge88", "es2020", "firefox78", "safari14" + 2 overrides)
#31 136.1 ➤ YN0000:
#31 136.1 ➤ YN0000:   _nuxt/entry.!~{001}~.js:10665:80: ERROR: Big integer literals are not available in the configured target environment ("chrome65", "edge88", "es2020", "firefox78", "safari14" + 2 overrides)
#31 136.1 ➤ YN0000:   _nuxt/entry.!~{001}~.js:10666:66: ERROR: Big integer literals are not available in the configured target environment ("chrome65", "edge88", "es2020", "firefox78", "safari14" + 2 overrides)
#31 136.1 ➤ YN0000:   at failureErrorWithLog (node_modules/esbuild/lib/main.js:1636:15)
#31 136.1 ➤ YN0000:   at node_modules/esbuild/lib/main.js:837:29
#31 136.1 ➤ YN0000:   at responseCallbacks.<computed> (node_modules/esbuild/lib/main.js:697:9)
#31 136.1 ➤ YN0000:   at handleIncomingPacket (node_modules/esbuild/lib/main.js:752:9)
#31 136.1 ➤ YN0000:   at Socket.readFromStdout (node_modules/esbuild/lib/main.js:673:7)
#31 136.1 ➤ YN0000:   at Socket.emit (node:events:513:28)
#31 136.1 ➤ YN0000:   at Socket.emit (node:domain:489:12)
#31 136.1 ➤ YN0000:   at addChunk (node:internal/streams/readable:315:12)
#31 136.1 ➤ YN0000:   at readableAddChunk (node:internal/streams/readable:289:9)
#31 136.1 ➤ YN0000:   at Socket.Readable.push (node:internal/streams/readable:228:10)

I've tried adjusting the configuration of @vitejs/plugin-legacy, even enabling all polyfills w/ modernPolyfills: true, but it doesn't help. Support for chrome65 is a requirement in this case so I can't just target a newer chrome version.
Additional context
No response
Logs
No response

I believe this has been resolved in https://github.com/nuxt/nuxt/pull/21427 - you can try the edge channel to confirm. v3.6.0 should be released later today, including this fix.


Include version of CLI in API calls?

Make it possible to check which version a user is using and warn if they need to reinstall

[ ] Add version to header
[ ] In API: Get header, check version
[ ] Warn and block (?) invalid versions / missing version

Moving to Jira.


OnPrem Installation Error BC140/BC150 fails with error concerning Event Log access

We installed a new Windows Server 2019 and tried to install BC140/BC150
When the installer tries to start the NST Service we got allot of error messages in the application event log.
I saw the same error in https://github.com/microsoft/navcontainerhelper/issues/504  but its concerning docker.
We are using a domain user to run the service. This user is local admin. We also tried to use a domain admin but it also failed. We also tried to use the network service. As far as I can remember, we had this issue with NAV 2013 if the user was not local admin.
Error Messages:

The description for Event ID 218 from source MicrosoftDynamicsNavServer$BC150 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

The description for Event ID 712 from source MicrosoftDynamicsNavServer$BC150 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

The description for Event ID 705 from source MicrosoftDynamicsNavServer$BC150 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

The description for Event ID 218 from source MicrosoftDynamicsNavServer$BC150 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

The description for Event ID 701 from source MicrosoftDynamicsNavServer$BC150 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

**Detailes Error Message (first error) **
The description for Event ID 218 from source MicrosoftDynamicsNavServer$BC150 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Server instance: BC150
Tenant ID:
Environment Name:
Environment Type:
User:
Type: System.Data.SqlClient.SqlException
ClientConnectionId: 5878c57b-4097-4e9c-890b-2fb796317ae6
Class: 11
LineNumber: 65536
Number: 4060
Server: ALD-SVW-SQL01\SQL2017
State: 1
Source: .Net SqlClient Data Provider
ErrorCode: -2146232060
Message:
Cannot open database "Demo Database BC (15-0)" requested by the login. The login failed.
Login failed for user 'ALPHA\admin.rgu'.
StackTrace:
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, DbConnectionPool pool, String accessToken, Boolean applyTransientFaultHandling, SqlAuthenticationProviderManager sqlAuthProviderManager)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)      at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource1 retry, DbConnectionOptions userOptions)
at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource1 retry)      at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource1 retry)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.Dynamics.Nav.Runtime.NavSqlConnection.TryConnect()
HResult: -2146232060
StackTrace:
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, DbConnectionPool pool, String accessToken, Boolean applyTransientFaultHandling, SqlAuthenticationProviderManager sqlAuthProviderManager)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)      at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource1 retry, DbConnectionOptions userOptions)
at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource1 retry)      at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource1 retry)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.Dynamics.Nav.Runtime.NavSqlConnection.TryConnect()
The message resource is present but the message was not found in the message table
Best regards
René

Can you post your installation script, please.

This issues list is for docker related issues only, am I right in  assuming that this is non-docker?
However - the error seems to be the connection to the SQL Server:
Cannot open database "Demo Database BC (15-0)" requested by the login. The login failed.
Login failed for user 'ALPHA\admin.rgu'.

Without database connection - all else fails.


#179 add identity_uri to ln_info_lite

fixes #179

Works. :+1:

Do I need to run the "pre-commit" before I make mak local commit or before I push to repo?

Usually before you commit. But the bot also fixes it if you pushed it before.

If like to avoid having the bot add another commit. So if possible, always run locally before committing 🙂


Build failure: devcontainer

Steps To Reproduce
Steps to reproduce the behavior:
$ uname -a
Linux nixos 6.9.1 #1-NixOS SMP PREEMPT_DYNAMIC Fri May 17 10:18:09 UTC 2024 x86_64 GNU/Linux
$ nix-build --check -A devcontainer

Build log
checking outputs of '/nix/store/06kqng7kvgd9vlyz229kww4jlqfpr4ii-devcontainer-0.60.0.drv'...
Running phase: unpackPhase
unpacking source archive /nix/store/axrcfrdihcc90v1sfkfv3s0f6sbkk5p1-source
source root is source
Running phase: patchPhase
Running phase: updateAutotoolsGnuConfigScriptsPhase
Running phase: configurePhase
no configure script, doing nothing
Running phase: buildPhase
yarn config v1.22.22
success Set "yarn-offline-mirror" to "/nix/store/7q311bg1n8v5zgbrkjxx336zycm38ff9-offline".
Done in 0.03s.
yarn install v1.22.22
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
[] 0/554[] 16/554[] 30/554[] 51/554[] 76/554[] 100/554[] 112/554[] 141/554[] 157/554[] 185/554[] 190/554[] 195/554[] 197/554[] 202/554[] 205/554[] 207/554[] 223/554[] 251/554[] 291/554[] 324/554[] 351/554[] 382/554[] 415/554[] 442/554[] 475/554[] 505/554[] 530/554[] 550/554[] 551/554[] 553/554[4/5] Linking dependencies...
[] 554/554[] 0/589[] 0/16489[] 1059/16489[] 2380/16489[] 3929/16489[] 5653/16489[] 7856/16489[] 9257/16489[] 10900/16489[] 13252/16489[] 15246/16489[] 16467/16489[] 0/1017[5/5] Building fresh packages...

error /build/source/node_modules/esbuild: Command failed.
Exit code: 126
Command: node install.js
Arguments:
Directory: /build/source/node_modules/esbuild
Output:
/bin/sh: node: Text file busy
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

error: builder for '/nix/store/06kqng7kvgd9vlyz229kww4jlqfpr4ii-devcontainer-0.60.0.drv' failed with exit code 126;
       last 10 log lines:
       >
       > error /build/source/node_modules/esbuild: Command failed.
       > Exit code: 126
       > Command: node install.js
       > Arguments:
       > Directory: /build/source/node_modules/esbuild
       > Output:
       > /bin/sh: node: Text file busy
       > info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
       >
       For full logs, run 'nix log /nix/store/06kqng7kvgd9vlyz229kww4jlqfpr4ii-devcontainer-0.60.0.drv'.

Additional context

Kernel version: 6.9.1
Was looking into this as part of the ZHF - just took this package to look into it
https://hydra.nixos.org/build/260969645

Seems like this is a very specific issue and it's related to this:
https://github.com/nodejs/docker-node/issues/1912
I found that when I dropped down to a lower kernel version (6.1.91), the problem disappeared. I guess that when the kernel version changes, this problem will just go away.
I spent a little time looking into using different node versions, but this did not solve the problem easily; it seems that yarn prob ensures a particular node version for at least some dependencies.
Notify maintainers
Metadata

Pretty sure this is the same issue as reported in #314713 which seems to be fixed with 6.9.3 kernel.

devcontainer is now building properly on hydra so it appears that this issue has been resolved:
https://hydra.nixos.org/job/nixpkgs/trunk/devcontainer.x86_64-linux


Overview on context.Context

It's coming as a built-in for Go 1.7, it's really powerful, and it's time to talk about it as a serious piece of machinery that most or every Go developer should know about

I'd love to get an introduction about the context package!


delete expire links

hi delete expire links not working for me
I set in config -> autologin.php =>  'remove_expired' => true and 'lifetime' => 1440
but not working  , what is problem ?

I believe in the latest version it works on a lottery system - check the config file to see the settings for it and you should be able to control how frequently the removal of expired links occurs.


Include both green and black olivada recipes

The file laura_olivada_recipe.txt includes the instructions for a black olivada.
I would like to:
-Change the name of  laura_olivada_recipe.txt to  laura_black_olivada_recipe.txt
-Add a new file with a recipe for green olivada named  laura_green_olivada_recipe.txt

Sounds great and tasty!
Comments:  laura_black_olivada_recipe.txt is a long filename, maybe have a shorter one?

Would it make sense to give the whole recipe section some structure? e.g. a recipe/ folder with subfolders like starter, main and dessert?

Yes, thanks! Maybe I can have one single file laura_olivada_recipe.txt with both recipes.


[fix] handle-callback-err (closes #146)

The current code for the rule as it stands has a bug. The line
const highlights = this.languageService.getDocumentHighlights(fileName, parameter.pos, [fileName]);

should be
const highlights = this.languageService.getDocumentHighlights(fileName, parameter.name.getStart(), [fileName]);

Making that change fixes issue #146. In this PR however, I have removed the usage of the languageService. Each call togetDocumentHighlights triggers a function which will search for the parameter in the document tree. The change I made is based on the prefer-arrow-function rule which keeps track of each function scope to determine if we make use of the error parameter. Based on some simple comparisons as noted on the issue we do get some performance with this change.

Looks great! Does this handle the error parameter where it may be handled in a nested function? E.g.
function query (cb) {
  doThing(function (err) {
    closeConnection(function (closeErr) {
      cb(err || closeErr)
    })
  })
})

@blakeembrey Yup. Seems like a good test to add to the custom regex examples.


The ladybug table sorts incorrectly on storage id

See figure

Also happens for other fields (duration, memory usage, storage size), it seems to be sorting as strings instead of numbers.


Game crash

https://forums.factorio.com/viewtopic.php?f=92&t=30980&start=40#p243924

the current version seems to have a nasty bug, which crashes not only the game but ultimately can destroy the savegame too (the last at least if you are running it on a server like we do) :!: Good thing that there's the autosave feature.
Regarding the bug: I'm/was using the street sign version, which should be indestructible with the default settings. Well, turn's out they aren't indestructible. Yes, you can run into them with a tank and nothing happens, BUT if fire gets just close enough or you deconstruct the note with your right click or you lag into the sign with a vehicle (yes, happened to me-.-) the game crashes. In case of the game running on a server this destroys your current savegame, since the map is saved even with the client and server crashing, resulting in another crash of the server the moment it beginns to load the map for a connecting client. I attached the server log for debugging purposes.

Closed as "possibly fixed/can't reproduce".


Manual changes on heater are not registered by HA

The setup for Andersson heaters are working very well through HA and Nodered. The issue is that when any changes are made manualy directly from the heater, like for example turning it on or off is not registered by HA.
Today I turned the heater off directly from the touch panel in the heater, but it stayed as «Heat» in HA. Can we fix this somehow?

@make-all Any update on this?
Another thing I notice is that after a power outage in the house, the HA starts up before the WIFI is ready. HA then registers the devices as «unavailable» as the internet connection was down because of the power outage. This kills all my automations, and do not work until I restart HA.
Is there any way to check the status automatically every minutes or every 5 mins?

I intend to change the underlying tuya library to tuyaface in future, which may help to resolve some protocol level issues like this, since it has been more recently maintained and has some fixes for the latest tuya protocol.

Please check with 0.2.0, which has updated the underlying library (to tinytuya, as the tradeface library also seems unmaintained now).


[Impeller] Investigate framebuffer blend based backdrop blurs.

 Mechanically, this works by stopping the current entity pass, saving the result as a texture, running that texture through the filter, and then filling that texture back onto the screen. This is require because the backdrop filter itself applies to "everything" and not particular widget subtrees. When there are multiple backdrop filters in a scene, this results in these full screen texture fills running multiple times, which can be extra expensive.
One optimization we could try for iOS to avoid the pass ending/texture fill switcharoo would be to implement a directional blur with the framebuffer blend feature. This would allow us to sample from the current pass without ending it, which would reduce the amount of texture work there. BUT, this would remove our ability to do the texture shrinking trick that we do for general purpose blurs.
To evaluate this tradeoff, we could use the example applications posted in https://github.com/flutter/flutter/issues/126353 .

Another advantage is that it makes techniques like https://github.com/flutter/flutter/issues/126696 easier, since all we need to do is adjust the geometry.

This has come up a couple up before in the weekly IIRC. I don't think the immense fragment load increase can offset the RT switches and two (smaller than the parent pass) texture allocations.

Probably true! though it might work okay for the other filters - not that they are used very often at all.
However, I suspect the real gain would come from fixing https://github.com/flutter/flutter/issues/126696 . If we can't get the math right for the clipping, then this approach would probably still have less fragment load if the backdrop filter only covers a small region of the screen.

@jonahwilliams says we can close this as we have better alternatives.


Run the Quick Start/README in Binder

This PR makes the Quick Start runnable in Binder. It adds a notebook version of the example code in README.md, an environment.yml to install its dependencies with conda and a postBuild to pre-install the missingno_data package from Qulit.

Very nice! I can't say no to free reproducibility. =)


Running docker build from a script

Hi,
I'm building a Docker container from a script. However:

docker build has no option that will give you the image id in a readable format; best you can do is parse the whole output on stdout with a regex.
docker build's output really should be on stderr
I was expecting --quiet to suppress that output, but it only removes the output from commands run in containers, not the rest of the client's output.

What I was expecting is all the current output to happen on stderr, unless an option silences it (--quiet is already taken, but that's really what it should do), and the new image id to be printed on stdout for script consumption (my_shiny_image=$(docker build . 2>/dev/stderr)).
The best I can do right now is redirect stderr and stdout to /dev/null to suppress them, and generate a unique tag name myself to pass in with -t (parsing stdout just doesn't make sense).
(version: 1.0.0, 63fe64c)

#dibs

Just an FYI.  @creack commented on stackoverflow [1] that the build log should go out on stderr and the image ID on stdout.  I intended to file a bug as suggested, and found this issue coincided.
While I'm happy with a command line flag that dumps the ID, I'm curious why the build log didn't remain on stderr.
[1] http://stackoverflow.com/questions/22080706/how-to-create-named-and-latest-tag-in-docker/22081272#comment38742167_22081272

@boxofrox thanks for notifying me about this. I didn't know that.
Looking at the current api/client/build.go, it looks like the daemon is using cli.out to stream its output. However, it has been like that from the beginning. So, I'm probably searching at the wrong place. Maybe someone else can answer this question?

@ripcurld00d found it.  CLI commands used to be in one file api/client/commands.go before they were split in Mar 2015 (from the beginning as you said ;) ).  commit 5c91bb9.
Seems to me like the fix at the time should have been to disable output on cli.err when the --quiet flag was given instead of switching build output to cli.out.

More FYI.  As a linux user, I use scripts to automate/customize tedious tasks with command line tools.  I've found Hints for writing Unix tools inspirational when writing my own CLI programs, particularly the bits about stdout being succint and effectively an API, while stderr is for errors, debugging, and misc info like the build log in this issue.

@boxofrox :+1: Good job! Thanks.

@ripcurld00d @boxofrox I'd be curious to know what you thought about these semantics:
1 - no -s -> keep today's output, most everything goes to stdout, final error msg, if any, goes to stderr
2 - -s + build error -> stdout is empty, stderr is full build output
3 - -s + successful build -> stdout has image ID, stderr is empty
My reasoning for having the stderr be empty in the third case is because it feels a bit odd to have a "silent" flag that still allows for output to appear, even if its on stderr, in the successful case.  However, if there is an error then I think showing it (on stderr) makes some sense.  However, I do tend to agree with the comment above that it would be nice if even w/o -s the build output went to stderr and just the final ID appeared on stdout, but I think that's a bigger/breaking change that might be harder to get thru.

@duglin @boxofrox :+1: (fine with me).

@duglin
(2) doesn't seem like anything is silenced.  If I were to write my script relying on (3), I'd always be redirecting my stderr to /dev/null if I wanted to silence docker build's "misc" output.  Other than that quibble, I can work with that.
@duglin, @ripcurld00d
I understand that docker's CLI may run into difficult technical problems, especially supporting an HTTP interface, and won't be an "ideal" unix command line tool.  And breaking existing behavior is definitely a valid concern.
Ideally, IMHO, the silent flag -s would be the equivalent of redirecting stderr to null 2>/dev/null.  Presence of errors is indicated primarily by a non-zero return value, and the image ID is the only output on stdout.
It looks like there are three types of output here: the image ID, the build log, and the final error message.  And we only have two channels for output: stdout, stderr.  Image ID belongs only on stdout, final error message belongs only on stderr, but where to put the build log?  Some want it on stdout, others and myself prefer it on stderr.
Perhaps it makes sense to have an output flag.
docker build --output=unix-cli ...
docker build --output=logger ...

--output=unix-cli would put the build log and final error message on stderr, and -s just silences stderr.  only image ID or nothing appears on stdout.
--output=logger would put the build log on stdout, with final error message on stderr.  I dunno what -s would do in this case (maybe silence stderr?).
if --output is omitted, it defaults to logger.

I'm just spitballing here, more so to just consider other possibilities that makes everyone happy, so I'm not adamant about this proposal.  There are obvious downsides:

adds another cli flag.
other cli flags -s could behave differently based on --output's value unless restrained by policy.
the build code may have a severe split personality disorder.

The one pro I can think of is that if I want the build log + final error on stderr, it's available to me.
Actually, this proposal sounds like @ripcurld00d's original intent with --silent switching to script mode.  Maybe he just had the wrong flag name :stuck_out_tongue_winking_eye:
Sorry for the really long post.

@boxofrox  said:

(2) doesn't seem like anything is silenced. If I were to write my script relying on (3), I'd always be redirecting my stderr to /dev/null if I wanted to silence docker build's "misc" output. Other than that quibble, I can work with that.

In the successful build case the redirect wouldn't be needed since nothing would be sent to stderr, so things are silenced but just when the build worked.
Let me ask you this.... in the case where the build fails would you be more annoyed with having to rerun the build again just to see the error message, or would you be more annoyed with the error messages being there at all? I'm not totally thrilled with -s not actually being silent in (2) but the more I thought about it the more it seemed to make sense from a UX perspective.  If something goes wrong then we're asking people to rerun the command all over again w/o the -s just to see the error message.  Seems kind of annoying.  However, I do agree that if "-s" means "silent" then (like curl) perhaps it really should be.  Of course, even then we're not totally silent because of the ID.  :-)   I did struggle with this as I was writing up the previous comment and in the end I landed on "-s" lying a little about how silent it is.  But I can be convinced to make it totally silent (modulo the ID).  We're in kind of a bad spot due to the way it was originally designed.
Not too excited about adding an "output" flag - seems like it might be overkill.

In the successful build case the redirect wouldn't be needed since nothing would be sent to stderr, so things are silenced but just when the build worked.

There's no way for my bash script to know in advance whether a build will fail so it could redirect to /dev/null.  Hence, it's always there if I'm certain I don't want to see output from stderr.

Let me ask you this.... in the case where the build fails would you be more annoyed with having to rerun the build again just to see the error message, or would you be more annoyed with the error messages being there at all?

I definitely don't want to run the build again.  That seems like a harsh precedent to impose on fellow scripters, so I won't advocate it.  I'm honestly more concerned with the build log being on stderr than a --silent flag.  Once there, I can decide with redirection how silent I want to be, and I'd always get an image ID on stdout I can stash in a variable without resorting to fragile grep/awk/sed regexes.

Of course, even then we're not totally silent because of the ID.

This did cross my mind.  I think it varies from tool to tool.  When you only care about the return value, total silence is preferred.  Since docker build can take quite some time to complete, I'd prefer to always have an image ID come back, otherwise we might need separate silent flags, or silent modes.  It's definitely a tradeoff.
So, in conclusion, I can work with your 3 point proposal.  It gets me (and @remram44 I believe) where we want to be: only image ID on stdout.

docker run has a --cidfile argument. It's a bit strange that docker build doesn't have a similar thing, if it did then we wouldn't need to worry as much about how silent or not silent the output was.

@ripcurld00d opened a PR to make docker build -q (quiet) only output the image-id on success; https://github.com/docker/docker/pull/17428, so this will be resolved in docker 1.10
@virtuald could be useful, but I think we should have a separate issue for that

@thaJeztah it's related to this issue, as a --cidfile option is something that would really only be useful for scripting

I agree with @thaJeztah.
@virtuald - it is not really related to this issue. However, it is a nice-to-have feature.
I will write a proposal for it in the following days, though.
Thanks.

@thaJeztah -- #17428 closes this too. Thanks :)

@ripcurld00d oh, yes!


Review governance pages

This PR results from reviewing two pages in the Governance section: Amendments history and TZIPs.

@NicNomadic Shall I merge this?


fix: sort schemas when uploading data

SUMMARY

In https://github.com/apache/superset/pull/29604 we made the list of schemas a set, since it makes more sense in the backend and makes manipulation easier. This PR introduces sorting in the frontend, to display the schemas in alphabetical order.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

I have to say I'm surprised to see some jquery here, hoping we can get rid of these forms ... In the meantime the change seems fair and fine.

Yeah, I was surprised to find this file when looking for the place in the frontend where we fetch the schemas available for upload!


x/crypto/ssh: bad kexinit during handshake

What version of Go are you using (go version)?
1.7.x
What operating system and processor architecture are you using (go env)?
Linux, amd64
What operating system and processor architecture are you using (go env)?
What did you do?
Initiate a SSH connection.
What did you expect to see?
Successful handshake and healthy connection.
What did you see instead?
After upgrading x/crypto/ssh to https://github.com/golang/crypto/commit/2e74c773682f59dc50a56475f7918dd8fa6dcaf8 to fix #18439 I'm seeing handshakes fail occasionally with the following message coming from the ssh client:
input_userauth_error: bad message during authentication: type 20

Type 20 being SSH_MSG_KEXINIT. Maybe that's firing concurrently with the handshake or something? It appears to be flaky.
/cc @hanwen

Here's ssh -vvv, if it helps:
[d][tsa] spawned /tmp/gexec_artifacts525385636/g608192691/tsa (pid: 31372)
[o][tsa] {"timestamp":"1484772013.263648510","source":"tsa","message":"tsa.listening","log_level":1,"data":{}}
[e][ssh] OpenSSH_7.4p1 Debian-5, OpenSSL 1.0.2j  26 Sep 2016
[e][ssh] debug1: Reading configuration data /etc/ssh/ssh_config
[e][ssh] debug1: /etc/ssh/ssh_config line 19: Applying options for *
[e][ssh] debug2: resolving "<IP_ADDRESS>" port 9801
[e][ssh] debug2: ssh_connect_direct: needpriv 0
[e][ssh] debug1: Connecting to <IP_ADDRESS> [<IP_ADDRESS>] port 9801.
[e][ssh] debug1: Connection established.
[e][ssh] debug1: identity file /tmp/tsa-key613344226/id_rsa type 1
[e][ssh] debug1: key_load_public: No such file or directory
[e][ssh] debug1: identity file /tmp/tsa-key613344226/id_rsa-cert type -1
[e][ssh] debug1: Enabling compatibility mode for protocol 2.0
[e][ssh] debug1: Local version string SSH-2.0-OpenSSH_7.4p1 Debian-5
[e][ssh] debug1: Remote protocol version 2.0, remote software version Go
[e][ssh] debug1: no match: Go
[e][ssh] debug2: fd 3 setting O_NONBLOCK
[e][ssh] debug1: Authenticating to <IP_ADDRESS>:9801 as 'alex'
[e][ssh] debug3: put_host_port: [<IP_ADDRESS>]:9801
[e][ssh] debug3: hostkeys_foreach: reading file "/tmp/known-hosts154180302"
[e][ssh] debug3: record_hostkey: found key type RSA in file /tmp/known-hosts154180302:1
[e][ssh] debug3: load_hostkeys: loaded 1 keys from [<IP_ADDRESS>]:9801
[e][ssh] debug3: order_hostkeyalgs: prefer hostkeyalgs: ssh-rsa-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256,ssh-rsa
[e][ssh] debug3: send packet: type 20
[e][ssh] debug1: SSH2_MSG_KEXINIT sent
[e][ssh] debug3: receive packet: type 20
[e][ssh] debug1: SSH2_MSG_KEXINIT received
[e][ssh] debug2: local client KEXINIT proposal
[e][ssh] debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,ext-info-c
[e][ssh] debug2: host key algorithms: ssh-rsa-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256,ssh-rsa,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519
[e][ssh] debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc
[e][ssh] debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc
[e][ssh] debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
[e][ssh] debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
[e][ssh] debug2: compression ctos: none,zlib@openssh.com,zlib
[e][ssh] debug2: compression stoc: none,zlib@openssh.com,zlib
[e][ssh] debug2: languages ctos:
[e][ssh] debug2: languages stoc:
[e][ssh] debug2: first_kex_follows 0
[e][ssh] debug2: reserved 0
[e][ssh] debug2: peer server KEXINIT proposal
[e][ssh] debug2: KEX algorithms: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
[e][ssh] debug2: host key algorithms: ssh-rsa
[e][ssh] debug2: ciphers ctos: aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,arcfour256,arcfour128
[e][ssh] debug2: ciphers stoc: aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,arcfour256,arcfour128
[e][ssh] debug2: MACs ctos: hmac-sha2-256,hmac-sha1,hmac-sha1-96
[e][ssh] debug2: MACs stoc: hmac-sha2-256,hmac-sha1,hmac-sha1-96
[e][ssh] debug2: compression ctos: none
[e][ssh] debug2: compression stoc: none
[e][ssh] debug2: languages ctos:
[e][ssh] debug2: languages stoc:
[e][ssh] debug2: first_kex_follows 0
[e][ssh] debug2: reserved 0
[e][ssh] debug1: kex: algorithm<EMAIL_ADDRESS>[e][ssh] debug1: kex: host key algorithm: ssh-rsa
[e][ssh] debug1: kex: server->client cipher: aes128-ctr MAC: hmac-sha2-256 compression: none
[e][ssh] debug1: kex: client->server cipher: aes128-ctr MAC: hmac-sha2-256 compression: none
[e][ssh] debug3: send packet: type 30
[e][ssh] debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
[e][ssh] debug3: receive packet: type 31
[e][ssh] debug1: Server host key: ssh-rsa SHA256:QA5i5Qh2CpcrRbwiqYu+KIa66313opd5+KB9EFeqL9s
[e][ssh] debug3: put_host_port: [<IP_ADDRESS>]:9801
[e][ssh] debug3: put_host_port: [<IP_ADDRESS>]:9801
[e][ssh] debug3: hostkeys_foreach: reading file "/tmp/known-hosts154180302"
[e][ssh] debug3: record_hostkey: found key type RSA in file /tmp/known-hosts154180302:1
[e][ssh] debug3: load_hostkeys: loaded 1 keys from [<IP_ADDRESS>]:9801
[e][ssh] debug1: Host '[<IP_ADDRESS>]:9801' is known and matches the RSA host key.
[e][ssh] debug1: Found key in /tmp/known-hosts154180302:1
[e][ssh] debug3: send packet: type 21
[e][ssh] debug2: set_newkeys: mode 1
[e][ssh] debug1: rekey after<PHONE_NUMBER> blocks
[e][ssh] debug1: SSH2_MSG_NEWKEYS sent
[e][ssh] debug1: expecting SSH2_MSG_NEWKEYS
[e][ssh] debug3: receive packet: type 21
[e][ssh] debug1: SSH2_MSG_NEWKEYS received
[e][ssh] debug2: set_newkeys: mode 0
[e][ssh] debug1: rekey after<PHONE_NUMBER> blocks
[e][ssh] debug2: key: alex@think (0x55784ec7f910), agent
[e][ssh] debug2: key: /tmp/tsa-key613344226/id_rsa (0x55784ec70020), explicit
[e][ssh] debug3: send packet: type 5
[o][tsa] {"timestamp":"1484772013.293787241","source":"tsa","message":"tsa.connection.handshake-failed","log_level":1,"data":{"error":"EOF","remote":"<IP_ADDRESS>:42512","session":"1"}}
[e][ssh] debug3: receive packet: type 20
[e][ssh] input_userauth_error: bad message during authentication: type 20

Looks like some flavor of https://github.com/golang/go/issues/15066 reappearing (sigh)
curious; you'd think the user-auth code in SSH would be able a kex during auth.

@hanwen I'm curious, is the information provided in this issue sufficient or is more information needed to assess the bug and ultimately fix it? I don't feel capable of fixing the problem on my own but I'm happy to provide more information/investigate if necessary.

your info is not sufficient to be sure, but I suspect you could repro by adding sleep statements in the right places (see #15066). if you could that would be helpful.
I'm a bit swamped with normal work, but I'll try to have a look tonight.

I tried creating a repro by sprinkling the  handshake part of the golang ssh crypto lib with some sleeps but was not able make it work.
I'm also tried reproducing the original error that led to this issue being raised without luck so far.
Is my understanding of this issue correct that this is probaply caused because the openssh client receives a KEXINIT at a later stage in the handshake where the initial key exchange already took place?
And this is probably caused because both ends start the initial key exchange simultaneously and there is a race which one actually succeeds?

almost:
the first kex is special because it is mandatory, and I think the Go code has a race where the remote request for the first kex is somehow interpreted as a second kex, which then fires during the user authentication stage. (the word "handshake" is a bit overloaded here: there is the kex which has the dual purpose of setting up the secure channel and verifying the server identity, and there is authentication which verifies the user identity)
technically, OpenSSH is not following the spec, since it should be legal to request a kex during user authentication, but in practice it doesn't make sense, and is apparently not implemented. It suggests that OpenSSH doesn't have proper layering in their code (something which you can also tell from the<EMAIL_ADDRESS>compression method, which switches on compression after the user auth succeeded).

I'm still failing at creating a somewhat reliable repro here.
I managed to hit that bug once with ssh -v on the client side and the golang.org/x/crypto/ssh.debugHandshake=true:
[e][ssh] OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g  1 Mar 2016
[e][ssh] debug1: Reading configuration data /etc/ssh/ssh_config
[e][ssh] debug1: /etc/ssh/ssh_config line 19: Applying options for *
[e][ssh] debug1: Connecting to <IP_ADDRESS> [<IP_ADDRESS>] port 9801.
[e][ssh] debug1: Connection established.
[e][ssh] debug1: permanently_set_uid: 0/0
[e][ssh] debug1: identity file /tmp/tsa-key684306212/id_rsa type 1
[e][ssh] debug1: key_load_public: No such file or directory
[e][ssh] debug1: identity file /tmp/tsa-key684306212/id_rsa-cert type -1
[e][ssh] debug1: Enabling compatibility mode for protocol 2.0
[e][ssh] debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.1
[e][ssh] debug1: Remote protocol version 2.0, remote software version Go
[e][ssh] debug1: no match: Go
[e][ssh] debug1: Authenticating to <IP_ADDRESS>:9801 as 'root'
[e][ssh] debug1: SSH2_MSG_KEXINIT sent
[e][tsa] 2017/01/25 15:54:08 server got *ssh.kexInitMsg &{[197 213 16 41 48 24 167 162 134 173 18 2 28 114 65 78]<EMAIL_ADDRESS>ecdh-sha2-nistp256 ecdh-sha2-nistp384 ecdh-sha2-nistp521 diffie-hellman-group-exchange-sha256 diffie-hellman-group-exchange-sha1 diffie-hellman-group14-sha1 ext-info-c]<EMAIL_ADDRESS>rsa-sha2-512 rsa-sha2-256 ssh-rsa<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>ecdsa-sha2-nistp256 ecdsa-sha2-nistp384 ecdsa-sha2-nistp521 ssh-ed25519]<EMAIL_ADDRESS>aes128-ctr aes192-ctr aes256-ctr<EMAIL_ADDRESS><EMAIL_ADDRESS>aes128-cbc aes192-cbc aes256-cbc 3des-cbc]<EMAIL_ADDRESS>aes128-ctr aes192-ctr aes256-ctr<EMAIL_ADDRESS><EMAIL_ADDRESS>aes128-cbc aes192-cbc aes256-cbc 3des-cbc]<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>hmac-sha2-256 hmac-sha2-512 hmac-sha1]<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>hmac-sha2-256 hmac-sha2-512 hmac-sha1] [none<EMAIL_ADDRESS>zlib] [none<EMAIL_ADDRESS>zlib] [] [] false 0} (<nil>)
[e][tsa] 2017/01/25 15:54:08 server sent *ssh.kexInitMsg &{[41 82 56 208 44 141 156 205 128 122 190 155 141 74 50 84]<EMAIL_ADDRESS>ecdh-sha2-nistp256 ecdh-sha2-nistp384 ecdh-sha2-nistp521 diffie-hellman-group14-sha1 diffie-hellman-group1-sha1] [ssh-rsa] [aes128-ctr aes192-ctr aes256-ctr<EMAIL_ADDRESS>arcfour256 arcfour128] [aes128-ctr aes192-ctr aes256-ctr<EMAIL_ADDRESS>arcfour256 arcfour128] [hmac-sha2-256 hmac-sha1 hmac-sha1-96] [hmac-sha2-256 hmac-sha1 hmac-sha1-96] [none] [none] [] [] false 0} (<nil>)
[e][tsa] 2017/01/25 15:54:08 server entered key exchange
[e][ssh] debug1: SSH2_MSG_KEXINIT received
[e][ssh] debug1: kex: algorithm<EMAIL_ADDRESS>[e][ssh] debug1: kex: host key algorithm: ssh-rsa
[e][ssh] debug1: kex: server->client cipher: aes128-ctr MAC: hmac-sha2-256 compression: none
[e][ssh] debug1: kex: client->server cipher: aes128-ctr MAC: hmac-sha2-256 compression: none
[e][ssh] debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
[e][ssh] debug1: Server host key: ssh-rsa SHA256:yFsvolxTqYqUVEZeWPO7/8WxXT/L+cNHhH2xtYFf8JE
[e][ssh] debug1: Host '[<IP_ADDRESS>]:9801' is known and matches the RSA host key.
[e][ssh] debug1: Found key in /tmp/known-hosts569235609:1
[e][ssh] debug1: rekey after<PHONE_NUMBER> blocks
[e][ssh] debug1: SSH2_MSG_NEWKEYS sent
[e][ssh] debug1: expecting SSH2_MSG_NEWKEYS
[e][tsa] 2017/01/25 15:54:08 server sent *ssh.kexInitMsg &{[218 164 69 121 146 194 66 107 252 76 130 170 132 29 4 127]<EMAIL_ADDRESS>ecdh-sha2-nistp256 ecdh-sha2-nistp384 ecdh-sha2-nistp521 diffie-hellman-group14-sha1 diffie-hellman-group1-sha1] [ssh-rsa] [aes128-ctr aes192-ctr aes256-ctr<EMAIL_ADDRESS>arcfour256 arcfour128] [aes128-ctr aes192-ctr aes256-ctr<EMAIL_ADDRESS>arcfour256 arcfour128] [hmac-sha2-256 hmac-sha1 hmac-sha1-96] [hmac-sha2-256 hmac-sha1 hmac-sha1-96] [none] [none] [] [] false 0} (<nil>)
[e][tsa] 2017/01/25 15:54:08 server exited key exchange (first true), err <nil>
[e][ssh] debug1: rekey after<PHONE_NUMBER> blocks
[e][ssh] debug1: SSH2_MSG_NEWKEYS received
[e][tsa] 2017/01/25 15:54:08 server got *ssh.serviceRequestMsg &{ssh-userauth} (<nil>)
[e][ssh] input_userauth_error: bad message during authentication: type 20

@hanwen I created a repro for this error: https://github.com/databus23/golang-issue-18711
Unfortunately I wasn't able to trigger this bug in a single run by adding sleep statements in the right places but instead went for a  test case the loops until the error occurs.
At least on my computer this usually triggers the error with 30 seconds.
Some observations I made in the process:

it does not seem to happen with the OpenSSH client on macOS Sierra (OpenSSH_7.3p1)
I hit the error on debian jessie and ubuntu 16.04 (OpenSSH_6.7p1 & OpenSSH_7.2p2) and from the above comment by @vito it seems at least OpenSSH_7.4p1 is affected as well
Its quite time sensitive adding -v's to the client invocation seem to reduce the chances of triggering the bug. I assume because the client spends some time printing the debug statements.

Reverting golang.org/x/crypto to before https://github.com/golang/crypto/commit/2e74c773682f59dc50a56475f7918dd8fa6dcaf8 seems to make the problem go away. At least the repro doesn't trigger it anymore.

We've also run into a different issue during the kex/handshake.
panic: ssh: no key material for msgNewKeys
goroutine 31868301 [running]:
panic(0x7ce020, 0xc42414c260)
/usr/local/go/src/runtime/panic.go:500 +0x1a1
bitbucket.org/bitbucket/conker/vendor/golang.org/x/crypto/ssh.(*connectionState).writePacket(0xc422774068, 0xc4218a8480, 0xa90080, 0xc42000c2d0, 0xc420010790, 0x9, 0x9, 0x0, 0x0)
/go/src/bitbucket.org/bitbucket/conker/vendor/golang.org/x/crypto/ssh/transport.go:163 +0x226
bitbucket.org/bitbucket/conker/vendor/golang.org/x/crypto/ssh.(*transport).writePacket(0xc422774000, 0xc420010790, 0x9, 0x9, 0x0, 0x0)
/go/src/bitbucket.org/bitbucket/conker/vendor/golang.org/x/crypto/ssh/transport.go:144 +0x77
bitbucket.org/bitbucket/conker/vendor/golang.org/x/crypto/ssh.(*handshakeTransport).pushPacket(0xc422326140, 0xc420010790, 0x9, 0x9, 0x0, 0x0)
/go/src/bitbucket.org/bitbucket/conker/vendor/golang.org/x/crypto/ssh/handshake.go:211 +0x51
bitbucket.org/bitbucket/conker/vendor/golang.org/x/crypto/ssh.(*handshakeTransport).kexLoop(0xc422326140)
/go/src/bitbucket.org/bitbucket/conker/vendor/golang.org/x/crypto/ssh/handshake.go:291 +0x303
created by bitbucket.org/bitbucket/conker/vendor/golang.org/x/crypto/ssh.newServerTransport
/go/src/bitbucket.org/bitbucket/conker/vendor/golang.org/x/crypto/ssh/handshake.go:126 +0x227

This is on a server running on golang/crypto@41d678d1df78cd0410143162dff954e6dc09300f
We were previously running golang/crypto@ca7e7f10cb9fd9c1a6ff7f60436c086d73714180

@belak While your problem also happens at the handshake phase it seems unrelated to the issue described here. This issue has been handled in https://go-review.googlesource.com/#/c/35851/ and was merged as https://github.com/golang/crypto/commit/6fb066875c8002ccd49dbd9a16b522711cb8f59d.
If you problem persists I suggest you open a new issue for it.

@hanwen Thanks again for taking this. I can confirm that with the merged fix, I can't reproduce the issue anymore.

opened issue 18850 for the msgNewKeys problem.

issue #18850  , that is.

Looking good so far in my pipeline, thanks again!

Hi, I am still hitting this issue, even though I have the golang/x/crypto commit mentioned above in my code. (I am at dc137beb6cce2043e). OpenSSH fails to connect with:
debug1: SSH2_MSG_NEWKEYS received
debug2: key: /home/immesys/.ssh/id_rsa (0x56917eb1c120), agent
debug2: key: /home/immesys/.ssh/id_dsa ((nil))
debug2: key: /home/immesys/.ssh/id_ecdsa ((nil))
debug2: key: /home/immesys/.ssh/id_ed25519 ((nil))
debug3: send packet: type 5
debug3: receive packet: type 20
input_userauth_error: bad message during authentication: type 20

Same as @immesys.
...
debug3: send packet: type 21
debug2: set_newkeys: mode 1
debug1: rekey after<PHONE_NUMBER> blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug3: receive packet: type 21
debug2: set_newkeys: mode 0
debug1: rekey after<PHONE_NUMBER> blocks
debug1: SSH2_MSG_NEWKEYS received
debug2: key: /Users/sam/.ssh/id_rsa (0x7fd295d15f30)
debug2: key: /Users/sam/.ssh/id_dsa (0x0)
debug2: key: /Users/sam/.ssh/id_ecdsa (0x0)
debug2: key: /Users/sam/.ssh/id_ed25519 (0x0)
debug3: send packet: type 5
debug3: receive packet: type 20
input_userauth_error: bad message during authentication: type 20

Sure. Reopening for @hanwen.

Although I will say that with 641ab6b32 I have not seen this again. If someone can confirm that in the ~10 commits that have happened in the past two weeks that one of those could plausibly have fixed this problem (with 641ab6b32 being the one that looks most likely) then I am happy to leave this closed.

I cannot reproduce after an update 👍


Rename aya-bpf* to aya-ebpf*

We should s/bpf/ebpf/ across all crates, and this is about aya-bpf.
The bpf crates should be renamed to aya-ebpf*. Since this is going to break everything, it should come with a semver bump, and the release notes (and probably the book somewhere?) should point to https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#renaming-dependencies-in-cargotoml to help people migrate.

I feel this change is rather pointless. libbpf is named libbpf and not libebpf. The eBPF community use these two terms interchangeably to a large degree, and I don’t think there’s a demand nor benefit to changing the name.

When I submitted the bpf* rustc targets, they were almost dismissed by some since people thought it was actually bpf and not ebpf, and they said we should probably have ebpf targets intead. Whenever I blog or tweet about aya and related efforts, someone always gets confused by bpf vs ebpf. Do not assume that because you're part of a community that uses a language, people gravitating around or outside the community share your knowledge and understand the language.


goto-char does not work in line visual state (V)

Observed behavior
Enter line visual state (V), then evaluate goto-char (point-max). The point does not move.
Expected behavior
The point is at the end of the file with everything selected from where it was to the end.
Additional notes
It works in normal visual state (v), but not in line visual state.

I don't know. I was trying to figure out why mu4e-compose-goto-bottom does not work in line visual mode, and I tracked it down to this.

This appears to be the intended behavior of evil's visual-line mode. Even in vanilla Emacs+evil it behaves this way, unless you use M-x goto-char, rather than M-x eval-expression RET (goto-char (point-max)). Perhaps it should be reported to the evil guys?

Thank you for the investigation, I'll open an issue with the evil people.

To solve it I can add
(evil-set-command-property 'mu4e-compose-goto-bottom :keep-visual t)
(evil-set-command-property 'mu4e-compose-goto-top :keep-visual t)

This could be a useful addition to the mu module.

Thanks for looking into this for me. I've pushed it in ab79799, so I'll consider this resolved.
Perhaps the evil-collection guys should be informed. This might be a better fit for their evil-collection-mu4e package.

I opened an issue on the evil-collection page, I'll let you know when/if they integrate it.

And they've just done it.

Great. I've reverted the changes in app/email in 1f3c41a8 (though I marked the wrong issue, whoops!).
Thanks for letting me know!


Updated welcome screen to a newer style

Updated layout to single screen, updated to be in line with apple standard designs. Friendly for dark mode and dynamic text. Includes accessibility improvements to work better with VoiceOver and Voice Control.
Partially resolves https://github.com/5calls/ios/issues/331

Adjusted alignment of symbols, made symbols bigger, and adjusted the colors a bit. We could add a little red in the spend 5 minutes symbol, if you like. I removed the period after "Spend 5 minutes, make 5 calls" so it's more consistent with other content.
Still ready to go for dark mode, dynamic text, accessibility support (VoiceOver, Voice Control). One small issue I see is that on the iPhone SE, the continue button is a little cut off. Not sure if it's worth adjusting for? I'll include a screen shot of it below.