msteams-platform/assets/images/proactive-scenario/ngrok-terminal-window.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo-in-adaptive-card.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-message-sample.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactivebot-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/resolve-error.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/result.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/run-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/stop-debug.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/uninstall-app.png
:white_check_mark:Succeeded
View

msteams-platform/sbs-send-proactive.yml
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 9dab727:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/adaptive-card-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package2.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-setting-values.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-studio-import-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-endpoint-address.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-setup.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png).png.png)
:white_check_mark:Succeeded
View.png?branch=pr-en-us-3657)

msteams-platform/assets/images/proactive-scenario/create-bot.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-password.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/install-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-base-url.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-terminal-window.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo-in-adaptive-card.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-message-sample.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactivebot-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/resolve-error.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/result.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/run-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/stop-debug.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/uninstall-app.png
:white_check_mark:Succeeded
View

msteams-platform/sbs-send-proactive.yml
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 9f477d9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/adaptive-card-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package2.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-setting-values.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-studio-import-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-endpoint-address.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-setup.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png).png.png)
:white_check_mark:Succeeded
View.png?branch=pr-en-us-3657)

msteams-platform/assets/images/proactive-scenario/create-bot.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-password.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/install-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-base-url.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-terminal-window.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo-in-adaptive-card.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-message-sample.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactivebot-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/resolve-error.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/result.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/run-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/stop-debug.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/uninstall-app.png
:white_check_mark:Succeeded
View

msteams-platform/sbs-send-proactive.yml
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/adaptive-card-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package2.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-setting-values.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-studio-import-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-endpoint-address.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-setup.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png).png.png)
:white_check_mark:Succeeded
View.png?branch=pr-en-us-3657)

msteams-platform/assets/images/proactive-scenario/create-bot.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-password.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/install-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-base-url.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-terminal-window.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo-in-adaptive-card.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-message-sample.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactivebot-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/resolve-error.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/result.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/run-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/stop-debug.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/uninstall-app.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

msteams-platform/sbs-send-proactive.yml
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 872335b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/downloads/Send Proactive Messages.zip
:white_check_mark:Succeeded

msteams-platform/assets/images/proactive-scenario/adaptive-card-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package2.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-setting-values.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-studio-import-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-endpoint-address.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-setup.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png).png.png)
:white_check_mark:Succeeded
View.png?branch=pr-en-us-3657)

msteams-platform/assets/images/proactive-scenario/create-bot.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-password.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/install-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-base-url.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-terminal-window.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo-in-adaptive-card.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-message-sample.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactivebot-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/resolve-error.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/result.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/run-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/stop-debug.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/uninstall-app.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

msteams-platform/sbs-send-proactive.yml
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/downloads/Send Proactive Messages.zip
:white_check_mark:Succeeded

msteams-platform/assets/images/proactive-scenario/adaptive-card-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package2.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-setting-values.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-studio-import-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-endpoint-address.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-setup.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png).png.png)
:white_check_mark:Succeeded
View.png?branch=pr-en-us-3657)

msteams-platform/assets/images/proactive-scenario/create-bot.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-password.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/install-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-base-url.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-terminal-window.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo-in-adaptive-card.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-message-sample.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactivebot-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/resolve-error.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/result.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/run-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/stop-debug.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/uninstall-app.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

msteams-platform/sbs-send-proactive.yml
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 28e7ee2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/downloads/Send Proactive Messages.zip
:white_check_mark:Succeeded

msteams-platform/assets/images/proactive-scenario/adaptive-card-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package2.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-setting-values.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-studio-import-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-endpoint-address.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-setup.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png).png.png)
:white_check_mark:Succeeded
View.png?branch=pr-en-us-3657)

msteams-platform/assets/images/proactive-scenario/create-bot.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-password.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/install-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-base-url.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-terminal-window.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo-in-adaptive-card.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-message-sample.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactivebot-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/resolve-error.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/result.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/run-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/stop-debug.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/uninstall-app.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

msteams-platform/sbs-send-proactive.yml
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/adaptive-card-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package2.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-setting-values.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-studio-import-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-endpoint-address.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-setup.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png).png.png)
:white_check_mark:Succeeded
View.png?branch=pr-en-us-3657)

msteams-platform/assets/images/proactive-scenario/create-bot.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-password.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/install-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-base-url.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-terminal-window.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo-in-adaptive-card.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-message-sample.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactivebot-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/resolve-error.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/result.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/run-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/stop-debug.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/uninstall-app.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

msteams-platform/sbs-send-proactive.yml
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/downloads/SendProactiveMessages.zip
:white_check_mark:Succeeded

msteams-platform/assets/images/proactive-scenario/adaptive-card-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package2.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-setting-values.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-studio-import-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-endpoint-address.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-setup.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png).png.png)
:white_check_mark:Succeeded
View.png?branch=pr-en-us-3657)

msteams-platform/assets/images/proactive-scenario/create-bot.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-password.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/install-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-base-url.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-terminal-window.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo-in-adaptive-card.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-message-sample.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactivebot-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/resolve-error.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/result.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/run-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/stop-debug.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/uninstall-app.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

msteams-platform/sbs-send-proactive.yml
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 209138b:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/sbs-send-proactive.yml
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/downloads/SendProactiveMessages.zip
:white_check_mark:Succeeded

msteams-platform/assets/images/proactive-scenario/adaptive-card-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package2.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-setting-values.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-studio-import-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-endpoint-address.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-setup.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png).png.png)
:white_check_mark:Succeeded
View.png?branch=pr-en-us-3657)

msteams-platform/assets/images/proactive-scenario/create-bot.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-password.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/install-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-base-url.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-terminal-window.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo-in-adaptive-card.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-message-sample.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactivebot-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/resolve-error.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/result.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/run-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/stop-debug.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/uninstall-app.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

msteams-platform/sbs-send-proactive.yml

Line 41, Column 29: [Warning-link-out-of-scope] File 'assets/downloads/SendProactiveMessages.zip' referenced by link '~/assets/downloads/SendProactiveMessages.zip' will not be built because it is not included in build scope.

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

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

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/downloads/SendProactiveMessages.zip
:white_check_mark:Succeeded

msteams-platform/assets/images/proactive-scenario/adaptive-card-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package2.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-setting-values.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-studio-import-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-endpoint-address.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-setup.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png).png.png)
:white_check_mark:Succeeded
View.png?branch=pr-en-us-3657)

msteams-platform/assets/images/proactive-scenario/create-bot.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-password.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/install-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-base-url.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-terminal-window.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo-in-adaptive-card.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-message-sample.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactivebot-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/resolve-error.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/result.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/run-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/stop-debug.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/uninstall-app.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

msteams-platform/sbs-send-proactive.yml
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

msteams-platform/sbs-send-proactive.yml
:x:Error

Details

msteams-platform/sbs-send-proactive.yml

Line 70, Column 1: [Error-yaml-syntax-error] While scanning for the next token, found character that cannot start any token.

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

Docs Build status updates of commit 72ff17d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/downloads/SendProactiveMessages.zip
:white_check_mark:Succeeded

msteams-platform/assets/images/proactive-scenario/adaptive-card-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package2.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-setting-values.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-studio-import-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-endpoint-address.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-setup.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png).png.png)
:white_check_mark:Succeeded
View.png?branch=pr-en-us-3657)

msteams-platform/assets/images/proactive-scenario/create-bot.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-password.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/install-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-base-url.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-terminal-window.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo-in-adaptive-card.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-message-sample.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactivebot-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/resolve-error.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/result.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/run-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/stop-debug.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/uninstall-app.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

msteams-platform/sbs-send-proactive.yml
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/downloads/SendProactiveMessages.zip
:white_check_mark:Succeeded

msteams-platform/assets/images/proactive-scenario/adaptive-card-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package2.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-setting-values.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-studio-import-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-endpoint-address.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-setup.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png).png.png)
:white_check_mark:Succeeded
View.png?branch=pr-en-us-3657)

msteams-platform/assets/images/proactive-scenario/create-bot.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-password.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/install-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-base-url.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-terminal-window.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo-in-adaptive-card.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-message-sample.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactivebot-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/resolve-error.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/result.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/run-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/stop-debug.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/uninstall-app.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

msteams-platform/sbs-send-proactive.yml
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/downloads/SendProactiveMessages.zip
:white_check_mark:Succeeded

msteams-platform/assets/images/proactive-scenario/adaptive-card-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package1.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/add-adaptive-card-package2.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-setting-values.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/app-studio-import-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-endpoint-address.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/bot-setup.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/create-bot-id.png).png.png)
:white_check_mark:Succeeded
View.png?branch=pr-en-us-3657)

msteams-platform/assets/images/proactive-scenario/create-bot.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-id.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/generate-app-password.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/install-app.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-base-url.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/ngrok-terminal-window.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo-in-adaptive-card.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-helo.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-message-sample.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactive-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/proactivebot-project.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/resolve-error.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/result.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/run-code.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/stop-debug.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/proactive-scenario/uninstall-app.png
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

msteams-platform/sbs-send-proactive.yml
:white_check_mark:Succeeded
View

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


Site not opening

https://responsive-css.us/ website is not opening anymore.

@zorluozan this is a tool I personally haven't needed for years now so it didn't make sense to keep paying to host it. If you'd like to clone the repo and host the site yourself, feel free to do so


import/from no longer highlighted after :PluginUpdate

I just did a :PluginUpdate and for some reason, import and from are no longer highlighted like before:

It's official ES syntax now.
So I moved it to yajs.vim.


Should Rules 10 and 4 be reordered?

These two rules are closely related, perhaps the flow of the paper would make more sense if they were adjacent to one another?

Yes this makes sense, especially since the first sentence of rule 10 directly references rule 4.
(could they be combined?)

I agree, I think it should go 4, then 10.


add outdir option per image proposal

By default the pwa assets will be generated in the image source folder, you can use a assetsName callback to change the output dir to create the assets in subfolders or in another path (via relative path using ..).
Since the pwa assets will use node path resolve with the image source folder, we can add a new option (optional) and resolve the asset against the new option or the image folder.
Hint:
We need to change the images signature to (and the usage from the cli-start module):
images: string | string[] | ImageData | ImageData[]
...
export interface ImageData {
  path: string
  outputDir: string
}

https://github.com/vite-pwa/assets-generator/blob/main/src/build.ts#L39 will be:
const folder = typeof image === 'string' ? dirname(imagePath) :  resolve(buildOptions.root, image.outputDir) :

From this comment https://github.com/vite-pwa/assets-generator/pull/13#issuecomment-1693329797

To add for the record:
I thought that adding a relative path to the assetName would be a sufficient workaround to change the output location of the generated files. It indeed worked for majority of them. However, I discovered that when a favicon (favicon.ico) is generated, it remains in the input image's directory. Hence I see this addition as essential (and, subjectively speaking, a lot cleaner!).

However, I discovered that when a favicon (favicon.ico) is generated, it remains in the input image's directory.

Uhmm, you can provide the favicon names with the relative paths, if using defaults the corresponding names will be plain names. You can override favicons with relatives path:
export const minimalPreset: Preset = {
  transparent: {
    sizes: [64, 192, 512],
    favicons: [[64, '../../../public/favicon.ico']], // <== this one
  },
  maskable: {
    sizes: [512],
  },
  apple: {
    sizes: [180],
  },
}

Ahh, you're totally right, that's the way to go in this case ;) appreciate your help

if you need the path change for all the generated assets, add an assetName function to your preset:
import { AssetType, ResolvedAssetSize, defaultAssetName, defineConfig } from '@vite-pwa/assets-generator/config';

export default defineConfig({
  preset: {
    transparent: {
      sizes: [64, 192, 512],
      favicons: [[64, 'icons/favicons/favicon.ico']],
    },
    maskable: {
      sizes: [512],
    },
    apple: {
      sizes: [180],
    },
    assetName: (type: AssetType, size: ResolvedAssetSize) => {
      return `icons/favicons/${defaultAssetName(type, size)}`;
    },
  },
  images: ['public/logo.svg'],
});

Hello all,
any progress on this?
Regards,
Emanuele.

if you need the path change for all the generated assets, add an assetName function to your preset:
import { AssetType, ResolvedAssetSize, defaultAssetName, defineConfig } from '@vite-pwa/assets-generator/config';

export default defineConfig({
  preset: {
    transparent: {
      sizes: [64, 192, 512],
      favicons: [[64, 'icons/favicons/favicon.ico']],
    },
    maskable: {
      sizes: [512],
    },
    apple: {
      sizes: [180],
    },
    assetName: (type: AssetType, size: ResolvedAssetSize) => {
      return `icons/favicons/${defaultAssetName(type, size)}`;
    },
  },
  images: ['public/logo.svg'],
});

This worked for me. Thanks @benkroeger

se hai bisogno del cambio di percorso per tutte le risorse generate, aggiungi una assetNamefunzione alla tua preimpostazione:
import { AssetType, ResolvedAssetSize, defaultAssetName, defineConfig } from '@vite-pwa/assets-generator/config';

export default defineConfig({
  preset: {
    transparent: {
      sizes: [64, 192, 512],
      favicons: [[64, 'icons/favicons/favicon.ico']],
    },
    maskable: {
      sizes: [512],
    },
    apple: {
      sizes: [180],
    },
    assetName: (type: AssetType, size: ResolvedAssetSize) => {
      return `icons/favicons/${defaultAssetName(type, size)}`;
    },
  },
  images: ['public/logo.svg'],
});

This isn't working for me :(
When i try to build project i got this error:
error during build:
Error: ENOENT: no such file or directory, open '/workspaces/Saturday/dist/icons/favicons/pwa-64x64.png'
The manifest.webmanifest is created with the correct path for the icons but the assets isn't generated and the dist/icons/favicons/ folder isn't created.
Any suggestion?


404 when using unstable_cache

Brief Description of the Bug
Browser shows 404 page when using unstable_cache function.
Severity
Major (not Critical because unstable_cache is unstable)
Frequency of Occurrence
Always
Steps to Reproduce

Use the unstable_cache function on the page.
Open the page.
See 404 page instead of actual content.

Expected vs. Actual Behavior
Pages which are using unstable_cache must work.
Environment:

OS: all supported OS
Node.js version: all supported Node.js versions
@neshca/cache-handler version: all above 1.0.0
next version: all supported Next.js versions

Attempted Solutions or Workarounds
There is no workaround for now. CacheHandler doesn't read files from the file when using App Router. This was intentionally made. To overcome this bug, we must either read the file system or fix the unstable_cache function for Next.js. Reading the file system is a viable strategy only if we can identify if the page uses unstable_cache. As far as I know, it is not possible.
I also have a third idea: implement our unstable_cache function, which will allow Next.js to render a page if it was not read from the file system. It seems the easiest to me.
Impact of the Bug
unstable_cache is not working.

I'm kind of suprised by this, because I've been using the usntable_cache with @neshca/cache-handler and redis just fine 😀 Is there some specific use case when it crashes that I'm unaware of?

I tested all my functions with unstable_cache, and they work fine with Redis + Nextjs 14.1.3. I guess sometimes it doesn't work properly. But I still haven't made it productive.

@ezeparziale thank you for pointing out that you can not reproduce the issue. I've rerun the test and found out that the issue was in test case itself. I am closing the issue with the documentation update.


Input character bug

Hello, I found a character input bug,
No response when entering Chinese,
Here's my solution:
#include "imgui/imgui_impl_win32.h"
HWND hwnd = nullptr;

	void* get_init_addr(char* arcversionstr, void* imguicontext, IDirect3DDevice9* id3dd9)
	{
		ImGui::SetCurrentContext((ImGuiContext*)imguicontext);
		ImGui_ImplWin32_Init(hwnd);
	}

	uintptr_t mod_wnd(HWND hWnd, UINT uMsg, WPARAM wParam, LPARAM lParam)
	{
		hwnd = hWnd;
                 ....
                case WM_CHAR:
		if (wParam > 0 && wParam < 0x10000)
			io->AddInputCharacter((unsigned short)wParam);
		return 0;

Can you provide an example of how to input chinese symbols for me to reproduce this issue?
Also when testing your suggested code all normal characters are registered twice by imgui's io.

Sorry, should use io->AddInputCharacterUTF16((unsigned short)wParam);
I just found out about this bug a few days ago,
You can check out the plug-in code I wrote at https://github.com/jiangyi0923/d3d9_arcdps_sytool
d3d9_arcdps_sytool/pch.cpp
If you compile this plugin directly, it will be a Chinese version. You will need to put a Chinese font file in the addons/arcdps folder called arcdps_font.ttf

You can copy and paste "草" this Chinese character to try

Issue should be resolved after switching to the custom font renderer.


don't match dtype with first input in where

Tensor([1, 2, 3]).where(1.2, 2.3) the first [1, 2, 3] can directly cast into bool without casting float (in broadcasted) first

@Qazalin fyi this is the root cause of the double cast you mentioned earlier


Test pytorchbot merging

Stack from ghstack (oldest at bottom):

-> #461

@pytorchbot merge

@pytorchbot merge


[Feat] V10 Installation & Upgrading Script - Major Update

Support upgrading from V9.x to V10 (Or V10.x to latest)
Automatically create a full backup before upgrading.
Support both en_us and zh_cn locale
Add option to install daemon, web, or both. (-c web/daemon/all). If not specified, default is all.)
By default, the service will be installed as user "mcsm"
Add option to run the service as root (-u root)
For en_us version, use GitHub as the download source.
Optimize display styles.
Revise some texts and details
Backup has been disabled due to potential large file size being archived.

2024-05-06: Backup function has been disabled due to potential large file size being archived.

2024-05-09: Update function signatures.


Main rebase

update msgs from rebased px4-firmware (release v1.14.0)

Already updated, this PR is not needed


Make Readline::flush() always erase the prompt string

Fixes #21.

Just tested the PR, and I couldn't replicate the issue on zsh or bash, but the issue was fixed when I just used plain sh... :thinking:


possible bug? all applications become unpinned when visiting flame from bookmark

When I visit the dashboard from bookmark all applications become unpinned and only bookmarks are showing. The browser is Vivaldi though not sure if that matters

Are you using Docker integration?

Are you using Docker integration?

Thats a good point going to turn that off and test as i didnt add labels to my containers


update compatibility for KSP 1.2 and 1.3!

Hey man, this is super. I have Oculus Rift DK1 on Mac, and will love to test it here, but only if it can be ported to KSP 1.2 and 1.3. So, please, please please, continue evolving!

See release 2.0.3, it is now compatible with KSP 1.4. Thanks for your interest!


The Auth API changed in the SDK, I updated the app to reflect those changes.

Updated loginSession() in FCViewController, and Application sourceApplication to conform to updated Firebase auth SDK

FUIAuth is correct. Please see the forum post or the FirebaseUI documentation.


feat: port RingTheory.Polynomial.Hermite.Basic

(I now see that due to an error in the dashboard page this message was unfortunately not visible)

Yes, there is no comment on the port status page I see so I did not know I had to ping @lukemantle. I apologize for this.

No worries, this is certainly not your fault. The mistake was caused by a file rename in mathlib3 without updating the corresponding name on the dashboard

Hey, thanks for porting this! @lukemantle was my student and I can say that he's not working actively on the project any more; I have taken over with merging his PRs into mathlib3. That said, there's still one last PR to do (the explicit formula for the coefficient of a Hermite polynomial) which is currently waiting on #18995. Can this PR perhaps wait til that #18995 and the followup PR are done?
I could also put the new code into a new file when I PR it, which would mean it wouldn't require further edits to the work you've done here.

Oh thanks for spotting this Eric! When I was reviewing the PR I only compared the diff with the output of mathlib3port so I also missed this message.

@EmilieUthaiwat, to confirm your work is not wasted. We can leave this PR open, and git will be able to merge in any subsequent changes.
I can take care of this when @jakelev's work is done.

@jakelev I am of course fine with waiting until #18994 and the followup PR are done before switching back to the awaiting-review tag.
Personally, I do not mind doing further edits to this PR if it makes more sense to add the new code to this file. Should it not make much difference where the new code is, then I also think it would be better to create a separate file.

@eric-wieser Thank you!

@EmilieUthaiwat @eric-wieser The last PR is ready #19044.

The PR https://github.com/leanprover-community/mathlib/pull/19044 has been merged into mathlib3. Could someone please tell me what I should do to port the merged changes?

I just rebased

Thank you for having rebased! I finished fixing the file.


PULL_REQUEST_URL env variable unbound

when promotion-method is set to push the PULL_REQUEST_URL is never set it up https://github.com/kustomize-everything/action-promote/blob/f4cd6d811935df07a8e8192c1dbb917b7b7cafd6/src/commit-and-pull-request.sh#L137
As result since in the entrypoint.sh we have https://github.com/kustomize-everything/action-promote/blob/f4cd6d811935df07a8e8192c1dbb917b7b7cafd6/src/entrypoint.sh#L7, the promote action fails.
@highb could you confirm this bug? i was able to reproduce on my side.

@highb ping here

Hey sorry my GH notifications are a mess. I've opened a PR that adds the push method to the test matrix and I'm not seeing it fail yet. Could you share how you are calling the action to help me repro it? I don't think that nounset should have an issue if a particular branch with unset values isn't being run so I thought that the pull request specific env var there would have been fine.

Also @mazzy89 FYI Akuity has a new tool called Kargo that may be a good replacement for what I have written with this action, as well as the env rendering action. I'd appreciate your thoughts on using Kargo as a replacement for these actions. https://github.com/kustomize-everything/action-promote/issues/60

Hey sorry my GH notifications are a mess. I've opened a PR that adds the push method to the test matrix and I'm not seeing it fail yet. Could you share how you are calling the action to help me repro it? I don't think that nounset should have an issue if a particular branch with unset values isn't being run so I thought that the pull request specific env var there would have been fine.

Here how the action is called:
    steps:
      - name: Checkout
        uses: actions/checkout@v4
        with:
          sparse-checkout: |
            .github

      - name: Checkout
        uses: actions/checkout@v4
        with:
          fetch-depth: 0
          path: deployment
          ref: ${{ env.RELEASE_BRANCH }}

      - name: Promote built image to staging
        uses: mazzy89/action-promote
        with:
          target-repo: myorg/repo
          target-branch: ${{ env.RELEASE_BRANCH }}
          github-token: ${{ secrets.GITHUB_TOKEN }}
          working-directory: deployment
          promotion-method: push
          git-commit-user: ${{ github.actor }}
          git-commit-email: ${{ github.actor<EMAIL_ADDRESS>          images: ${{ inputs.builds }}

Also @mazzy89 FYI Akuity has a new tool called Kargo that may be a good replacement for what I have written with this action, as well as the env rendering action. I'd appreciate your thoughts on using Kargo as a replacement for these actions. https://github.com/kustomize-everything/action-promote/issues/60

I took a look. Although the tool looks very promising, at the moment seems like shooting with a bazooka to a fly. It requires running ArgoCD which in my case I do not plan to run it. A github action is a much lighter way to do promotion. The team is working to decouple it from ArgoCD and run it as standalone but they are not there yet.

@highb can we do something about it?
I have this bug that makes the action not usable. If we look at the code it is clearly a bug. When promotion-method: push, the PULL_REQUEST_URL is never set.

This commit fixes the issue https://github.com/kustomize-everything/action-promote/pull/49/commits/5b7905db7171728debd983bf97931fc457f9a38c

@highb would you mind if I wire a PR with that fix?


Recaf crash

Diagnostics:
JavaFX on Recaf's classpath was too old

Can you send your launcher log?
Also, try building launcher from this fork and see if it helps.
See https://github.com/Col-E/Recaf-Launcher/pull/33 that is not merged yet.

Looking in 'C:\Users\ruwag\AppData\Roaming\Recaf' for Recaf/dependencies...
Attempting to resolve JFX version in current classpath...
No JavaFX version class found in the current classpath
The current runtime bundles JavaFX that is too old (null).
- Try running with a JDK that has an up-to-date JavaFX bundled
- Or use a JDK that does not bundle JavaFX and let the launcher grab it for you
Failed launching Recaf: JavaFX on Recaf's classpath was too old

The fork has been merged and released as launcher 0.8.0


Uncaught Error: Cannot find module 'chai'

I am currently trying to get our JavaScript tests to run in Karma as some of our code references the global window object which is not available in tests. I run karma start my.conf.js and I get this error
{     "message": "Uncaught Error: Cannot find module 'chai'\nat node_modules/mocha/mocha.js:1:196\n\nError: Cannot find module 'chai'\n    at s (node_modules/mocha/mocha.js:1:156)\n    at s (node_modules/mocha/mocha.js:1:122)\n    at test/CatenaBackbone.test.js:4:12",     "str": "Uncaught Error: Cannot find module 'chai'\nat node_modules/mocha/mocha.js:1:196\n\nError: Cannot find module 'chai'\n    at s (node_modules/mocha/mocha.js:1:156)\n    at s (node_modules/mocha/mocha.js:1:122)\n    at test/CatenaBackbone.test.js:4:12"   }
I have done some searching and I do have chai installed locally, not globally as I've seen in a few other places. Any ideas on why its not finding chai? Here is my conf file
module.exports = function(config) {
config.set({
basePath: '',
frameworks: ['mocha'],
files: [
'./test/*.js'
],
exclude: [
],
preprocessors: {
},
reporters: ['progress'],
port: 9876,
colors: true,
logLevel: config.LOG_INFO,
autoWatch: true,
browsers: ['Chrome'],
singleRun: true,
concurrency: Infinity
})
}

The chai lib is not in your test folder.

@inf3rno Thanks!


Implement discovery endpoints

Streamer should enable the player applications to access indexed data of the blockchain. Meaning, it should expose expose endpoints to store values and returned the list of entities. We'll replace this functionality with Lisk Service once it's stable enough.
Therefore the following endpoints are required:

Collection

getAll

Method: GET
Params: limit, offset.
Description: List of all collections in the system including the details of their Audios.

getByAddress

Method: GET
Params: address, limit, offset.
Description: List of all collections of a given account including the details of their Audios.

Subscription

getTypes

Method: GET
Params: none.
Description: List of all subscriptions types and 10 available IDs for each type

Resolved by #37


When updating codebase, it happens that Cline assumes file does not exists without checking it and writes new file, ignoring its previous content, that is destructive.

Which API Provider are you using?
Anthropic
Which Model are you using?
Claude Sonnet 3.5 new
What happened?
When updating codebase, it happens that Cline assumes file does not exists without checking it and writes new content into the file, ignoring its previous content, that is destructive.
Steps to reproduce

Let the cline roll over some project with list of updates he should implement.
He will get correct idea, but sometimes will ignore previous code.
He fills in his fragments like no code from before would exist.
A lot of "red" marked code is left out on left side of the editor view. This is different than the lasy coding, no placeholders here.

Relevant API REQUEST output
I understand that we need to expose the refreshToken method from the BaseApiService through the api object. Let me check the api service implementation to make this change:
Cline wants to read this file:
I see the issue now. We need to expose the refreshToken method from BaseApiService through the api object. Let me update the api/index.ts file to include this method:
Cline wants to edit this file:
I see the TypeScript errors. The refreshToken method is protected in BaseApiService and the connect method requires a sessionId parameter. Let me fix these issues by updating the AuthApiService to expose a public refresh method and fixing the WebSocket connect signature:
Cline wants to edit this file:
seems radical, read the file again before suggesting changes
You're right, let me check the auth service implementation first before making changes:
Cline wants to read this file:
I see now - the AuthApiService already has a public refresh() method that handles token refresh properly. Let me update just the api/index.ts file to expose this existing method:
Cline wants to edit this file:
Additional context
he assumed, never red the file before and went to fit is something, ignoring the existing code, that was invisible to him.

"read the file before updating it" instruction fixes this as next step.


Add guards to cast all keys as strings, and tests

Both YAML and Python allow dict keys to be many different types. This complexity is unintuitive for the user and a potential font of very weird bugs (0123, etc).
We should enforce stringifying all keys when reading and writing (load/dump) YAML. All other functions can be naive, which should keep things simple both in logic and type annotations (see #665).

Open question:
Can we enforce this as a schema rather than in Onyo itself?
Otherwise some keys will be quoted and others not, and it won't be terribly user friendly.


fix bug trailing comma

bump version

Hi @sahalMoidu
Sorry I just saw this.
I just fixed the issue in #11


For INCREMENTAL_BY_UNIQUE_KEY, add an option to DO NOTHIN when matched

To support insert-only use cases, please provide an option to do nothing when the key is matched.
when_matched WHEN MATCHED THEN DO NOTHING

is this not solved with a custom when_matched expression?
https://sqlmesh.readthedocs.io/en/stable/concepts/models/model_kinds/?h=matched#when-matched-expression

Do you mean something like this:
when_matched WHEN MATCHED AND FALSE THEN UPDATE SET
So, the update never gets executed.

or when matched then update a.id = a.id or something

That works too. Wouldn't it cause an additional operation? I'm trying to avoid the UPDATE altogether and only do INSERT.

if it can be done with a custom when match, then i think that would work for you. but this sounds like there's an option for this so closing.

i'm not too familiar with duckdb's merge statement.


Replace unwraps with expects in bevy_pbr

Objective

Replacing all the unwraps with either expect or unwrap_or_else .
Fixes #3899 .

Solution

Replacing all the unwraps with more helpful error messages.

Something went wrong here. You have two commits (Fix mesh2d_manual example and Fix unnecessary casts) that have nothing to do with this PR. Could you please remove those commits so that you only have your Replaced unwraps for bevy_pbr crate in there? Thanks.

Something went wrong here. You have two commits (Fix mesh2d_manual example and Fix unnecessary casts) that have nothing to do with this PR. Could you please remove those commits so that you only have your Replaced unwraps for bevy_pbr crate in there? Thanks.

I did fix it now. Sorry, this is my first pull request.

I did fix it now. Sorry, this is my first pull request.

Perfect, thanks! Don't worry about it it's all good :)

Good stuff by the way! I'm just clarifying some of the error messages a little. :)

Good stuff by the way! I'm just clarifying some of the error messages a little. :)

Thank you for your suggestions. I did commit your suggestions except for the one about the display of primitive_topology_bits. I am not really sure how can I test it?

Good stuff by the way! I'm just clarifying some of the error messages a little. :)

Thank you for your suggestions. I did commit your suggestions except for the one about the display of primitive_topology_bits. I am not really sure how can I test it?

I guess try println!(“{}”, primitive_topology_bits); and see what it prints and whether it makes sense. If that doesn’t work due to a missing Display trait implementation, then you can try ”{:?}” instead, which I am pretty confident works as I think I’ve used it for wgpu::Features which are also bitflags.

Good stuff by the way! I'm just clarifying some of the error messages a little. :)

Thank you for your suggestions. I did commit your suggestions except for the one about the display of primitive_topology_bits. I am not really sure how can I test it?

I guess try println!(“{}”, primitive_topology_bits); and see what it prints and whether it makes sense. If that doesn’t work due to a missing Display trait implementation, then you can try ”{:?}” instead, which I am pretty confident works as I think I’ve used it for wgpu::Features which are also bitflags.

Yes, what I actually meant was is there's a specific example or test that I can run that calls this function just to make sure that it displays correctly?

Yes, what I actually meant was is there's a specific example or test that I can run that calls this function just to make sure that it displays correctly?

I don’t think this should fail so I unfortunately have no suggestion how to trigger the error case. That’s why I’m suggesting just testing separately that a print or panic with a particular format string works.

Yes, what I actually meant was is there's a specific example or test that I can run that calls this function just to make sure that it displays correctly?

I don’t think this should fail so I unfortunately have no suggestion how to trigger the error case. That’s why I’m suggesting just testing separately that a print or panic with a particular format string works.

Ok , I just tested it now with load_gltf example using println! and just {} and it works and prints a u8 number. so. I guess it should work fine for the panic! as well. right?

Ok , I just tested it now with load_gltf example using println! and just {} and it works and prints a u8 number. so. I guess it should work fine for the panic! as well. right?

Ohhhhh, I'm sorry! primitive_topology_bits is a u32! D'oh. That was a thinko on my part. Consider it resolved.

So, now it just needs updating on top of main.

So, now it just needs updating on top of main.

What do you mean by on top of main?

Ah you mean to update it in sync with the main branch?

Your latest commit (merging main into your branch) went wrong. You didn't resolve the merge conflicts the right way. #4047 removed a lot of unwraps which probably caused most of the merge conflicts. Like cart already suggested, we should use world.resource now instead of world.get_resource in most cases, because this version panics with a good error message.

Your latest commit (merging main into your branch) went wrong. You didn't resolve the merge conflicts the right way. #4047 removed a lot of unwraps which probably caused most of the merge conflicts. Like cart already suggested, we should use world.resource now instead of world.get_resource in most cases, because this version panics with a good error message.

Yes, got it I am working on updating it to main branch now.

Closing per discussion in https://github.com/bevyengine/bevy/issues/3899 <3


Added ESP32 image and partition entry signatures

This PR adds signatures for the image header and partition entries found in ESP32 firmware.

@eacmen I just realized that docker test failed for some reason. The link 404's on me. Is there a way to check why it failed?


RTC-server: listen to TLS connections

Connections between RTC-server and RTC-clients must be secured with TLS

Resolved in 867518c


Use a different country for tier1 price fetching

The one that suffers the least from region locks
Belgium seems the best choice.

Done.


After formatting, the character "," (that is, a comma) appears at the very end before "}"

After formatting, the character "," (that is, a comma) appears at the very end before "}":
loop:
- {item_name: doc_tools.plugin, item_path: '{3ACCEF78-860F-4D81-89E5-464C907F3628}'}
- {item_name: QRCode.plugin, item_path: '{D20D0768-6968-482B-8CEB-212D801030CF}'}
- {item_name: randomizer.plugin, item_path: '{2E935B75-113D-4613-BEA0-8879A775A42F}',}
or
with_items:
- {path: /root/.bashrc, regex: '[\033[01;32m\]', replace: '[\\033[01;31m\]',}

Hi @Andy-Solo thanks for opening a feature request.
I won't have time to work on this in the near future. I'll put an explanation for what I think needs to be done, for either my future self or someone else who might be able to pick it up.
Getting this to work might be non-trivial. I think this is the code that produces the comma for flow mapping nodes: https://github.com/braydonk/yaml/blob/10bcc859418b821726f51e2beb7406449cf0b4a2/emitterc.go#L712-L716
It's hard to tell by reading if that's the spot that matters here, but that's my best guess.
Somehow the parser would need to figure out that the current node is the final flow mapping value, and then optionally emit the comma depending on a yaml_emitter config value. Might be nasty to get working, but perhaps someone other than me will be able to do something easier than what I'm suggesting.

( duplicate of #110 )


Show a confusing message when copying block blobs to a premium blob container

Storage Explorer Version: 1.5.0
Platform/OS Version: Windows 10/ Linux Ubuntu 16.04/ MacOS High Sierra
Architecture: ia32/x64
Build Number: 20180911.1
Commit: 5a9d37a6
Regression From: Not a regression
Steps to Reproduce:

Expand a non-premium storage account -> Open a blob container then try to upload a block blob to it.
Copy the uploaded block blob to one premium blob container.
Check the displayed error message on Activities.

Expected Experience:
This block blob cannot be copied successfully due to it doesn't support.
Actual Experience:

It shows a confusing error message on Activities.
The activity is successful after clicking 'Retry' and the copied block blob shows well on the editor after refreshing.

This issue still reproduces on build 2190927.10.

It shows a confusing error message on Activities.

It still shows the confusing error after clicking 'Retry' or refreshing the editor.

This issue has been fixed on build 20191123.2. So we close it.


Fix python 3 issue

Resolve this log format issue with Python 3
https://github.com/spreaker/prometheus-pgbouncer-exporter/issues/30

Confirmed fix for Python 3.8.5.

Works for me as well. Can we merge this and update the pip package?


Mothership web cannot upload json character file

Created character using android app and exported to json character file for upload to web.
Upon importing, webpage goes white/blank and is not recoverable without deleting cookies/browsing data etc.
Tested on Chrome 127.0.6533.103 for Android 14, chrome desktop 64bit 127.0.6533.120, and Firefox desktop 64bit 129.0.1, all have same behaviour.

GAEL.json

Have found that json structure is different between app and web versions. Manually entering details from app into web json structure gives expected results


Not working since last gw patch

Crashes right after injection

Try the latest update (4.9), the issues should be fixed.

I didn't see there was an update; thank you!
On Thu, Apr 8, 2021 at 7:35 AM Leo Friedrichs @.***>
wrote:

Try the latest update (4.9), the issues should be fixed.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/HasKha/GWToolboxpp/issues/583#issuecomment-815770648,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADH72CH52WFWLFMHH4P2O73THWPKBANCNFSM42SZRSGQ
.


Need consistent handling of lbry credits as either Decimal or string encoded Decimal

Representation of lbry credits in lbrynet is sometimes handled as float or returned as float in Daemon API.
This is wrong as we need exact decimal amount to avoid floating point errors.

https://github.com/lbryio/lbry/issues/630


Checksum safeAddress when creating a message and propagate type

Summary
In order to maintain a strict type and checksummed address throughout the project, we should validate the incoming addresses. In newer controllers, we started doing this by adding an AddressSchema to address. This begins adding it to "existing" controllers.
This checksums the incoming signer/safeAddress of EmailController and propagates the stricter (0x${string}) type throughout the project accordingly. These were done together as emails are experimental.
Changes

Checksum addresses in MessagesController['createMessage']
Increase strictness of safeAddress in MessageService['createMessage'] and IMessagesRepository['createMessage'] and its implementation
Increase strictness ofsafeAddress in ITransactionApi['postMessage'] and its implementation
Update tests accordingly

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 92.851%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
7103

Relevant Lines:
7357

💛  - Coveralls


removed log at import

Hi @rossant
We developed a framework called SpikeInterface that implements several sorters (https://github.com/SpikeInterface).
At import, it tries to import the spike sorter-related packages to check if they are installed.
Klusta has a log ouput in the init, so I was wondering if you are ok in removing it from the init.
Thanks,
Alessio

sure!

thanks @rossant !
Do you mind releasing a new tag so we can sugget users to install with pip?


Filters on the pages will be closed as default

ping @utkuaydin
Related https://github.com/okulbilisim/ojs/issues/945


spec: typo in "Embedded interfaces" section

The type set of T is the intersection of the type sets defined by T's explicitly declared methods and the type sets of T’s embedded interfaces.

Sounds like term "intersection" must be replaced with "union".

I don't think it should. For
type Inner interface { ... }

type Outer interface {
  M()
  Inner
}

The type set of Outer is the types that implement Inner and also have an M method, which is the intersection of the type set of Inner and the type set that has an M method.
Thanks.

@cherrymui The problem is "type set" contains both a union and an intersection: it's a union of (union of methods) and (intersection of types). To me current wording sounds incorrect and misleading.

"Type set" is the set of types (that implement that interface). It is different from "method set", which is the union of the method sets of the embedded interfaces and the explicitly included methods.


dynamic-modal/lib/Modal.jsx Line 1: Unexpected token

When I import react-dynamic-modal to my project:
import { Modal, ModalManager} from 'react-dynamic-modal';
I get this:
ERROR in ./~/react-dynamic-modal/lib/Modal.jsx
Module parse failed: /Users/anton/pwork/net-engine/connect-two-admin-portal/node_modules/react-dynamic-modal/lib/Modal.jsx Line 1: Unexpected token
You may need an appropriate loader to handle this file type.
| import React,{ Component } from 'react';
| import ReactDOM from 'react-dom';
| import Assign from 'lodash.assign';
 @ ./~/react-dynamic-modal/lib/index.js 1:17-39

That says you need to add jsx loader or babel loader to the webpack.config.js

I have:
var path    = require('path');
var webpack = require('webpack');

module.exports = {
  entry: [
    'babel-polyfill',
    './src/style/app.scss',
    './src/main',
    'webpack-dev-server/client?http://localhost:8080'
  ],
  output: {
    path: __dirname + '/dist/',
    publicPath: '/',
    filename: 'bundle.js'
  },
  devServer: {
    port: 8080
  },
  debug: true,
  devtool: 'source-map',
  module: {
    loaders: [
      {
        test: /\.(js|jsx)$/,
        include: path.join(__dirname, 'src'),
        loader: 'babel-loader',
        query: {
          presets: ['es2015', 'react'],
          plugins: ['transform-class-properties']
        }
      },
      {
        test: /\.scss$/,
        loader: "style!css!autoprefixer!sass"
      },
      /* eslint-disable */
      { test: /\.woff(\?.*)?$/,  loader: 'url?prefix=fonts/&name=[path][name].[ext]&limit=10000&mimetype=application/font-woff' },
      { test: /\.woff2(\?.*)?$/, loader: 'url?prefix=fonts/&name=[path][name].[ext]&limit=10000&mimetype=application/font-woff2' },
      { test: /\.ttf(\?.*)?$/,   loader: 'url?prefix=fonts/&name=[path][name].[ext]&limit=10000&mimetype=application/octet-stream' },
      { test: /\.eot(\?.*)?$/,   loader: 'file?prefix=fonts/&name=[path][name].[ext]' },
      { test: /\.svg(\?.*)?$/,   loader: 'url?prefix=fonts/&name=[path][name].[ext]&limit=10000&mimetype=image/svg+xml' },
      { test: /\.(png|jpg)$/,    loader: 'url?limit=8192' }
      /* eslint-enable */
    ]
  },
  devServer: {
    contentBase: "./dist",
    historyApiFallback: true
  }
};

OK.I see the problem.I will solve it immediately.

The problem is that  the react-dynamic-modal needs to be parsed by the babel-loader.But you specify the  include path : "path.join(__dirname, 'src')",which stops parsing React-dynamic-modal.So the solution may be : add the path of the lib to the include path. Or remove the include path and modify "test: /.(js|jsx)$/" to "test: /.jsx$/"

It's working with:
include: [path.join(__dirname, 'src'), path.join(__dirname, 'node_modules')],

I am new to react and webpack, so I will ask someone if this kind of configuration is ok.
Thanks @xue2han
I will continue trying react-dynamic-modal :)

This is a big problem!  The vast majority of folks dont want babel to go through their node_modules directory to parse 1000's  of files.  I thought all NPM modules were supposed to be ES-5
http://jamesknelson.com/writing-npm-packages-with-es6-using-the-babel-6-cli/

Hi,I have released the latest version which have just solved the problem.Also I add many effects for modal windows.You can try it here : http://xue2han.github.io/react-dynamic-modal/


fix: core and docs

What:

Additional issues:

:tada: This PR is included in version 5.1.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 6.1.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Oppo device when my app is not in background than i am not getting notification

Oppo device when my app is not in the background then I am not getting push notification else app is open than push notification getting successfully

Sorry, i couldnt understand your problem. While the app is not in background, it only can be terminated / killed or in foreground. Are notifications not shown only when the app is in the background?

getting notification only when the app is in background or foreground but when the app is not in background or foreground than not getting notification this is a issue

To receive a notification while the app is killed or you do a scheduled notification or a push notification. What are you trying to do and what platform are you using?

not receive a push notification while the app is killed. and we have used android platform

This can be a issue with your firebase project configuration or the google-services.json file was placed in the wrong place, inside your flutter project. Please, check the firebase documentation to verifi if this conditions was accomplished.

but the same scenario I am checking in other device working fine only issue is getting in oppo device

What is an oppo device?

I am getting this issue in all oppo device


Break retain cycle of ImageDownloader

This fixes #235

Current coverage is 75.49%

Merging #236 into master will decrease coverage by -0.06% as of e105200

@@            master    #236   diff @@
======================================
  Files           11      11
  Stmts         1252    1273    +21
  Branches         0       0
  Methods          0       0
======================================
+ Hit            946     961    +15
  Partial          0       0
- Missed         306     312     +6

Review entire Coverage Diff as of e105200

Powered by Codecov. Updated on successful CI builds.


KNOX-1952 - Add NiFi Registry service definition

(It is very important that you created an Apache Knox JIRA for this change and that the PR title/commit message includes the Apache Knox JIRA ID!)
What changes were proposed in this pull request?
This PR adds a service definition for Apache NiFi Registry.

Still working on NiFi Registry side implementation
Sharing changes as a draft PR to get review comments early

How was this patch tested?

Installed Knox and NiFi Registry locally
Applied this patch to Knox and added NIFI-REGISTRY role to sandbox topology
Applied NiFi Registry side change (Merged)
Confirmed NiFi Registry web app can be accessed via Knox

Please review Knox Contributing Process before opening a pull request.

@risdenk Thanks for the review comments. This PR is now ready for full review as NiFi Registry side change apache/nifi-registry#211 has been merged.

Changes look good. Pulling down and running tests. Need to check that changes are packaged properly. If all looks good locally will merge.


Address #264: fix fonts.lied = undefined

Fixes the case when fonts.lied is undefined. It should be "false".

Nice. I will merge this.


Feedback for “Custom Theme”

I would like to hide my documentation behind an authentication system.
Can we use Custom Theme to handle authentication on client side? Do you have any guide for this kind of use case?

see https://github.com/shuding/nextra/issues/1121#issuecomment-1374958546

Thanks for quick reply. _app component will definitely be useful for this case. I totally forgot it.


Unable to log into formatic account.

This looks like spam/bot, so closing. @TwoCuteCult feel free to re-open with more information if you disagree.


Validate Activity and Nodes

Validate that:

The source nodes for activity are under our control (ie in the node set)
The destination nodes are in our graph + support keysend (which will be implemented by has_feature)

note to self: this should also validate that all of the source nodes are on the same network

Ready for review when folks have a minute! cc: @sr-gi @okjodom

I think this should be good now


Add Roles to .net core 3 react with identity?

Hi in the default create .net core 3 app with identity ApplicationDbContext : ApiAuthorizationDbContext<ApplicationUser>
I was wondering to add roles would it be a matter of inheriting from IdentityDbContext and what impact would that have on the token based auth etc? I was wondering what differs between ApiAuthorizationDbContext? Is there an example somewhere on how one might add roles in a spa setup?
Thanks :)

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

ID: d9869895-9ba2-5027-46cd-89d1d995cba4
Version Independent ID: 8750939b-6ae5-3b9a-6c32-5e84b7fea22c
Content: Identity model customization in ASP.NET Core
Content Source: aspnetcore/security/authentication/customize-identity-model.md
Product: aspnet-core
Technology: aspnetcore-security
GitHub Login: @ajcvickers
Microsoft Alias: avickers

Hello! Thanks for contacting us. This sounds like a general question about using ASP.NET Core. While we try to look at and respond to all issues, for questions like this we recommend posting to a community support group like Stack Overflow with the asp.net-core tag.


jboss eap 7 - WFLYCTL0030

Hello,
we use jolokia-1.6.2.war in JBoss to monitor the application.
With JBoss EAP 6.4 everything works without errors.
With JBoss EAP 7.3 we get the following error every time we start JBoss:
12:34:07,820 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 91) WFLYCTL0013: Operation ("read-resource-description") failed - address: ([
("subsystem" => "resource-adapters"),
("resource-adapter" => " ldap-resource-adapter"),
("connection-definitions" => "ldap-connection-pool"),
("statistics" => "extended")
]) - failure description: "WFLYCTL0030: No resource definition is registered for address [
("subsystem" => "resource-adapters"),
("resource-adapter" => "ldap-resource-adapter"),
("connection-definitions" => "ldap-connection-pool"),
("statistics" => "extended")
]"
After startup, jolokia and the application runs without errors.
If I deploy jolokia only after JBoss startup, the error does not come.
I tried to add a dependency in Jolokia to the resource-adapter via the web.xml and the jboss-deployment-structure.xml, but this did not solve the problem.
Also with jolokia-agent-war-2.0.0-M3.war the error comes.
I guess Jolokia polls the MBeans before the JBoss is fully loaded and that's where the error comes from?
Is there any way to set a delay in Jolokia before triggering the JBoss MBean?
Do you have any idea how I can solve this problem?
Thanks a lot
Marcel

This has been inactive for long time, and meanwhile we've already released Jolokia 2.0. Please try it with 2.0 and see if there's still the issue. If there are no further activities here, I'd like to close it. Thank you.


Facebook Analytics is going away

Facebook Analytics is going away:
https://www.facebook.com/business/help/966883707418907
It should affect on AppEventsLogger i suppose. Right?
Facebook says there is an alternative like "Events Manager"
Can we use it here?

I just read it in my mail hehe
Need to check how to include it, at least it's going away only by mid of this year

I think this issue can be closed easily. Let me state quickly:
What is Facebook Analytics about?
Facebook Analytics has (in theory) nothing to do with the App Events other than showing the stats that were sent to Facebook's servers.
Events Manager to the rescue
Events Manager is right in the same business dashboard that you are currently using for creating a new Facebook App or managing your Ads, etc.
Am I experiencing a breaking change?
You are only experiencing a "breaking change", if you are currently relying on Facebook Analytics to run tests(e.g. measuring success-figures by checking analytics and see the conversion values or using the Funnel feature of Facebook Analytics). So the best thing would be to migrate your analytics to something like Firebase/GA (see below) or Flurry.
However, you don't need to update anything in your code, everything should keep working as before. Only the Software from Facebook is being closed, not the Endpoints AppEvents is calling.
What can I do?
Case 1: You are not even using AppEvents? → Nothing to do.
Case 2: You are using AppEvents as "Analytics" like feature? → Migrate to Flurry or Firebase
Case 3: You are using AppEvents as Measuring Tool for Mobile App Ads only? → Nothing to do.
Quick Links:

Events Manager
Facebook Analytics
Flurry
Firebase / Google Analytics

I guess it would be the case to just remove the reference to this AppEvents and in docs somehow state this chances would be enough for now right?

It's merged now :)

I think this issue can be closed then?


Add invoice payment transactions endpoint

@mganisin can you please review this PR, specifically if stripe api is ok to add to dev-packages

I am not sold to the idea that such integration test should be here.

this represents another external dependency - doesn't have to be clear how to fullfil it
without proper setup this will fail always, if ran as of now, the result would be red (kind of a regression, but not a regression actually)

I am still undecided

@averevki split it into two requests please, keep tests in separate PR, that will allow us to merge the feature and give bit more time to think about the tests