Norm messaging extensions

Changes to terminology. Compose extension changed to messaging extension.  References to composeExtensions the manifest have not been changed.

:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:warning:Warning

Details

msteams-platform/concepts/apps/apps-overview.md
:warning:Warning

Details

msteams-platform/concepts/apps/apps-sideload.md
:warning:Warning

Details

msteams-platform/concepts/bots/bots-overview.md
:warning:Warning

Details

msteams-platform/concepts/bots/bots-test.md
:warning:Warning

Details

msteams-platform/concepts/compose-extensions.md
:warning:Warning

Details

msteams-platform/get-started/design.md
:warning:Warning

Details

msteams-platform/get-started/get-started.md
:warning:Warning

Details

msteams-platform/overview.md
:warning:Warning

Details

msteams-platform/publishing/apps-package.md
:warning:Warning

Details

msteams-platform/publishing/apps-publish.md
:warning:Warning

Details

msteams-platform/resources/design/framework/submitting.md
:warning:Warning

Details

msteams-platform/resources/design/overview.md
:warning:Warning

Details

msteams-platform/resources/general/developer-preview-features.md
:warning:Warning

Details

msteams-platform/resources/schema/manifest-schema.md
:warning:Warning

Details

msteams-platform/samples/code-samples.md
:warning:Warning

Details

msteams-platform/get-started/code.md
:white_check_mark:Succeeded

msteams-platform/resources/design/framework/compose-extensions.md
:white_check_mark:Succeeded

msteams-platform/TOC.yml

[Warning] Invalid file link:(~/resources/design/framework/search).
[Warning] Invalid file link:(~/concepts/bots/bots-test).
[Warning] Invalid file link:(~/resources/general/cross-domain).
[Warning] Invalid file link:(~/concepts/activity-feed).
[Warning] Invalid file link:(~/concepts/bots/bots-overview).
[Warning] Invalid file link:(~/concepts/bots/bots-conversations).
[Warning] Invalid file link:(~/concepts/tabs/tabs-context).
[Warning] Invalid file link:(~/concepts/tabs/tabs-content).
[Warning] Invalid file link:(~/resources/design/components/color).
[Warning] Invalid file link:(~/concepts/cards-actions).
[Warning] Invalid file link:(~/resources/design/framework/apps).
[Warning] Invalid file link:(~/publishing/apps-package).
[Warning] Invalid file link:(~/concepts/connectors).
[Warning] Invalid file link:(~/resources/design/resources).
[Warning] Invalid file link:(~/resources/design/framework/submitting).
[Warning] Invalid file link:(~/resources/design/framework/basics).
[Warning] Invalid file link:(~/concepts/tabs/tabs-configuration).
[Warning] Invalid file link:(~/samples/code-samples).
[Warning] Invalid file link:(~/concepts/bots/bots-notifications).
[Warning] Invalid file link:(~/resources/schema/manifest-schema).
[Warning] Invalid file link:(~/resources/design/overview).
[Warning] Invalid file link:(~/resources/design/framework/cards).
[Warning] Invalid file link:(~/resources/design/framework/tabs).
[Warning] Invalid file link:(~/resources/design/framework/bots).
[Warning] Invalid file link:(~/troubleshoot/faq).
[Warning] Invalid file link:(~/scenarios/bots-personal-conversations).
[Warning] Invalid file link:(~/concepts/tabs/tabs-update-remove).
[Warning] Invalid file link:(~/concepts/bots/bots-menus).
[Warning] Invalid file link:(~/get-started/get-started).
[Warning] Invalid file link:(~/concepts/bots/bots-create).
[Warning] Invalid file link:(~/resources/general/developer-preview-features).
[Warning] Invalid file link:(~/resources/design/components/fields).
[Warning] Invalid file link:(~/resources/design/framework/activity-feed).
[Warning] Invalid file link:(~/scenarios/bots-channel-conversations).
[Warning] Invalid file link:(~/publishing/apps-publish).
[Warning] Invalid file link:(~/resources/general/developer-preview).
[Warning] Invalid file link:(~/resources/general/rate-limit).
[Warning] Invalid file link:(~/resources/design/components/typography).
[Warning] Invalid file link:(~/resources/microsoft-graph).
[Warning] Invalid file link:(~/publishing/office-store-guidance).
[Warning] Invalid file link:(~/concepts/apps/apps-overview).
[Warning] Invalid file link:(~/resources/design/framework/compose-extensions).
[Warning] Invalid file link:(~/concepts/deep-links).
[Warning] Invalid file link:(~/resources/design/components/buttons).
[Warning] Invalid file link:(~/resources/design/components/dialogs).
[Warning] Invalid file link:(~/resources/general/requirements).
[Warning] Invalid file link:(~/concepts/authentication).
[Warning] Invalid file link:(~/publishing/office-store-checklist).
[Warning] Invalid file link:(~/overview).
[Warning] Invalid file link:(~/concepts/compose-extensions).
[Warning] Invalid file link:(~/resources/design/components/themes).
[Warning] Invalid file link:(~/resources/general/debug).
[Warning] Invalid file link:(~/concepts/custom-bot).
[Warning] Invalid file link:(~/feedback).
[Warning] Invalid file link:(~/troubleshoot/troubleshoot).
[Warning] Invalid file link:(~/concepts/bots/bots-cards).
[Warning] Invalid file link:(~/concepts/tabs/tabs-static).
[Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
[Warning] Invalid file link:(~/concepts/bots/bots-context).
[Warning] Invalid file link:(~/concepts/apps/apps-sideload).

msteams-platform/concepts/apps/apps-overview.md

Line 15: [Warning] Invalid file link:(~/publishing/apps-package).
Line 21: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 22: [Warning] Invalid file link:(~/concepts/bots/bots-overview).
Line 23: [Warning] Invalid file link:(~/concepts/compose-extensions).
Line 31: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 32: [Warning] Invalid file link:(~/concepts/bots/bots-overview).
Line 32: [Warning] Invalid file link:(~/concepts/compose-extensions).
Line 33: [Warning] Invalid file link:(~/concepts/connectors).
Line 34: [Warning] Invalid file link:(~/concepts/compose-extensions).
Line 35: [Warning] Invalid file link:(~/concepts/custom-bot).
Line 43: [Warning] Invalid file link:(~/get-started/design).
Line 44: [Warning] Invalid file link:(~/get-started/code).
Line 45: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 46: [Warning] Invalid file link:(~/concepts/bots/bots-overview).
Line 47: [Warning] Invalid file link:(~/concepts/connectors).
Line 48: [Warning] Invalid file link:(~/concepts/compose-extensions).
Line 49: [Warning] Invalid file link:(~/concepts/activity-feed).
Line 51: [Warning] Invalid file link:(~/publishing/apps-package).
Line 52: [Warning] Invalid file link:(~/concepts/apps/apps-sideload).
Line 53: [Warning] Invalid file link:(~/publishing/apps-publish).

msteams-platform/concepts/apps/apps-sideload.md

Line 11: [Warning] Invalid file link:(~/concepts/bots/bots-test#adding-a-bot-for-11-chat-only).
Line 20: [Warning] Invalid file link:(~/publishing/apps-package).
Line 61: [Warning] Invalid file link:(~/concepts/tabs/tabs-configuration).
Line 81: [Warning] Invalid file link:(~/concepts/connectors).
Line 102: [Warning] Invalid file link:(~/publishing/apps-package).
Line 102: [Warning] Invalid file link:(~/resources/schema/manifest-schema).
Line 104: [Warning] Invalid file link:(~/troubleshoot/troubleshoot).

msteams-platform/concepts/bots/bots-overview.md

Line 14: [Warning] Invalid file link:(~/concepts/custom-bot).
Line 24: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 46: [Warning] Invalid file link:(~/get-started/design#designing-a-great-bot).
Line 46: [Warning] Invalid file link:(~/concepts/tabs/tabs-static).
Line 46: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 47: [Warning] Invalid file link:(~/concepts/bots/bots-create).
Line 48: [Warning] Invalid file link:(~/concepts/bots/bots-conversations).
Line 48: [Warning] Invalid file link:(~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk).
Line 49: [Warning] Invalid file link:(~/concepts/bots/bots-test).
Line 50: [Warning] Invalid file link:(~/publishing/apps-publish).
Line 54: [Warning] Invalid file link:(~/concepts/custom-bot).

msteams-platform/concepts/bots/bots-test.md

Line 17: [Warning] Invalid file link:(~/publishing/apps-package).
Line 17: [Warning] Invalid file link:(~/concepts/apps/apps-sideload).
Line 19: [Warning] Invalid file link:(~/concepts/bots/bots-notifications).
Line 60: [Warning] Invalid file link:(~/assets/images/bot/botdisable.png).
Line 78: [Warning] Invalid file link:(~/publishing/apps-publish).

msteams-platform/concepts/compose-extensions.md

Line 11: [Warning] Invalid file link:(~/resources/general/developer-preview).
Line 29: [Warning] Invalid file link:(~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk).
Line 35: [Warning] Invalid file link:(~/concepts/bots/bots-create).
Line 41: [Warning] Invalid file link:(~/resources/schema/manifest-schema#composeextensions).
Line 140: [Warning] Invalid file link:(~/concepts/apps/apps-sideload).
Line 206: [Warning] Invalid file link:(~/concepts/bots/bots-conversations#receiving-messages).
Line 275: [Warning] Invalid file link:(~/concepts/cards-actions).
Line 275: [Warning] Invalid file link:(~/concepts/connectors#using-office-365-connector-cards-in-microsoft-teams).
Line 413: [Warning] Invalid file link:(~/resources/schema/manifest-schema#validdomains).

msteams-platform/get-started/design.md

Line 49: [Warning] Invalid file link:(~/concepts/bots/bots-notifications).

msteams-platform/get-started/get-started.md

Line 60: [Warning] Invalid file link:(~/concepts/apps/apps-sideload).
Line 64: [Warning] Invalid file link:(~/resources/general/developer-preview).
Line 74: [Warning] Invalid file link:(~/concepts/apps/apps-overview).
Line 75: [Warning] Invalid file link:(~/get-started/design).
Line 76: [Warning] Invalid file link:(~/get-started/code).
Line 77: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 78: [Warning] Invalid file link:(~/concepts/bots/bots-overview).
Line 79: [Warning] Invalid file link:(~/concepts/connectors).
Line 80: [Warning] Invalid file link:(~/concepts/compose-extensions).
Line 81: [Warning] Invalid file link:(~/concepts/activity-feed).
Line 85: [Warning] Invalid file link:(~/publishing/apps-package).
Line 86: [Warning] Invalid file link:(~/concepts/apps/apps-sideload).
Line 87: [Warning] Invalid file link:(~/resources/general/debug).
Line 91: [Warning] Invalid file link:(~/publishing/apps-publish).
Line 92: [Warning] Invalid file link:(~/concepts/deep-links).
Line 96: [Warning] Invalid file link:(~/troubleshoot/troubleshoot).

msteams-platform/overview.md

Line 19: [Warning] Invalid file link:(~/get-started/get-started#1-set-up-your-office-365-tenant).
Line 25: [Warning] Invalid file link:(~/concepts/apps/apps-overview).
Line 47: [Warning] Invalid file link:(~/feedback).

msteams-platform/publishing/apps-package.md

Line 9: [Warning] Invalid file link:(~/concepts/apps/apps-sideload).
Line 18: [Warning] Invalid file link:(~/resources/schema/manifest-schema).
Line 57: [Warning] Invalid file link:(~/troubleshoot/troubleshoot).

msteams-platform/publishing/apps-publish.md

Line 10: [Warning] Invalid file link:(~/publishing/apps-package).
Line 10: [Warning] Invalid file link:(~/resources/schema/manifest-schema).
Line 51: [Warning] Invalid file link:(~/publishing/apps-package).
Line 51: [Warning] Invalid file link:(~/publishing/office-store-checklist).
Line 56: [Warning] Invalid file link:(~/publishing/office-store-guidance).
Line 89: [Warning] Invalid file link:(~/resources/schema/manifest-schema#bots).

msteams-platform/resources/design/framework/submitting.md

Line 124: [Warning] Invalid file link:(~/resources/design/framework/bots).
Line 188: [Warning] Invalid file link:(~/resources/design/framework/compose-extensions).

msteams-platform/resources/design/overview.md

Line 16: [Warning] Invalid file link:(~/resources/design/framework/basics).
Line 22: [Warning] Invalid file link:(~/resources/design/framework/tabs).
Line 28: [Warning] Invalid file link:(~/resources/design/framework/cards).
Line 34: [Warning] Invalid file link:(~/resources/design/framework/bots).
Line 40: [Warning] Invalid file link:(~/resources/design/framework/activity-feed).
Line 46: [Warning] Invalid file link:(~/resources/design/framework/compose-extensions).
Line 52: [Warning] Invalid file link:(~/resources/design/framework/basics).

msteams-platform/resources/general/developer-preview-features.md

Line 9: [Warning] Invalid file link:(~/resources/general/developer-preview).
Line 15: [Warning] Invalid file link:(~/overview).
Line 19: [Warning] Invalid file link:(~/publishing/apps-publish).
Line 23: [Warning] Invalid file link:(~/concepts/compose-extensions).
Line 27: [Warning] Invalid file link:(~/concepts/activity-feed).
Line 31: [Warning] Invalid file link:(~/concepts/connectors).
Line 35: [Warning] Invalid file link:(~/concepts/bots/bots-conversations#updating-messages).

msteams-platform/resources/schema/manifest-schema.md

Line 10: [Warning] Invalid file link:(~/resources/schema/manifest-schema-migrate).
Line 159: [Warning] Invalid file link:(~/concepts/bots/bots-create).
Line 211: [Warning] Invalid file link:(~/publishing/apps-package#icons).
Line 273: [Warning] Invalid file link:(~/resources/general/developer-preview).
Line 275: [Warning] Invalid file link:(~/concepts/bots/bots-menus).
Line 286: [Warning] Invalid file link:(~/resources/general/developer-preview).
Line 301: [Warning] Invalid file link:(~/resources/general/developer-preview).

msteams-platform/samples/code-samples.md

Line 26: [Warning] Invalid file link:(~/get-started/get-started).
Line 89: [Warning] Invalid file link:(~/resources/general/debug).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:warning:Warning

Details

msteams-platform/concepts/apps/apps-overview.md
:warning:Warning

Details

msteams-platform/concepts/apps/apps-sideload.md
:warning:Warning

Details

msteams-platform/concepts/bots/bots-overview.md
:warning:Warning

Details

msteams-platform/concepts/bots/bots-test.md
:warning:Warning

Details

msteams-platform/concepts/compose-extensions.md
:warning:Warning

Details

msteams-platform/get-started/design.md
:warning:Warning

Details

msteams-platform/get-started/get-started.md
:warning:Warning

Details

msteams-platform/overview.md
:warning:Warning

Details

msteams-platform/publishing/apps-package.md
:warning:Warning

Details

msteams-platform/publishing/apps-publish.md
:warning:Warning

Details

msteams-platform/resources/design/framework/submitting.md
:warning:Warning

Details

msteams-platform/resources/design/overview.md
:warning:Warning

Details

msteams-platform/resources/general/developer-preview-features.md
:warning:Warning

Details

msteams-platform/resources/schema/manifest-schema.md
:warning:Warning

Details

msteams-platform/samples/code-samples.md
:warning:Warning

Details

msteams-platform/concepts/cards-actions.md
:warning:Warning

Details

msteams-platform/get-started/code.md
:white_check_mark:Succeeded

msteams-platform/resources/design/framework/compose-extensions.md
:white_check_mark:Succeeded

msteams-platform/TOC.yml

[Warning] Invalid file link:(~/resources/design/framework/search).
[Warning] Invalid file link:(~/concepts/bots/bots-test).
[Warning] Invalid file link:(~/resources/general/cross-domain).
[Warning] Invalid file link:(~/concepts/activity-feed).
[Warning] Invalid file link:(~/concepts/bots/bots-overview).
[Warning] Invalid file link:(~/concepts/bots/bots-conversations).
[Warning] Invalid file link:(~/concepts/tabs/tabs-context).
[Warning] Invalid file link:(~/concepts/tabs/tabs-content).
[Warning] Invalid file link:(~/resources/design/components/color).
[Warning] Invalid file link:(~/concepts/cards-actions).
[Warning] Invalid file link:(~/resources/design/framework/apps).
[Warning] Invalid file link:(~/publishing/apps-package).
[Warning] Invalid file link:(~/concepts/connectors).
[Warning] Invalid file link:(~/resources/design/resources).
[Warning] Invalid file link:(~/resources/design/framework/submitting).
[Warning] Invalid file link:(~/resources/design/framework/basics).
[Warning] Invalid file link:(~/concepts/tabs/tabs-configuration).
[Warning] Invalid file link:(~/samples/code-samples).
[Warning] Invalid file link:(~/concepts/bots/bots-notifications).
[Warning] Invalid file link:(~/resources/schema/manifest-schema).
[Warning] Invalid file link:(~/resources/design/overview).
[Warning] Invalid file link:(~/resources/design/framework/cards).
[Warning] Invalid file link:(~/resources/design/framework/tabs).
[Warning] Invalid file link:(~/resources/design/framework/bots).
[Warning] Invalid file link:(~/troubleshoot/faq).
[Warning] Invalid file link:(~/scenarios/bots-personal-conversations).
[Warning] Invalid file link:(~/concepts/tabs/tabs-update-remove).
[Warning] Invalid file link:(~/concepts/bots/bots-menus).
[Warning] Invalid file link:(~/get-started/get-started).
[Warning] Invalid file link:(~/concepts/bots/bots-create).
[Warning] Invalid file link:(~/resources/general/developer-preview-features).
[Warning] Invalid file link:(~/resources/design/components/fields).
[Warning] Invalid file link:(~/resources/design/framework/activity-feed).
[Warning] Invalid file link:(~/scenarios/bots-channel-conversations).
[Warning] Invalid file link:(~/publishing/apps-publish).
[Warning] Invalid file link:(~/resources/general/developer-preview).
[Warning] Invalid file link:(~/resources/general/rate-limit).
[Warning] Invalid file link:(~/resources/design/components/typography).
[Warning] Invalid file link:(~/resources/microsoft-graph).
[Warning] Invalid file link:(~/publishing/office-store-guidance).
[Warning] Invalid file link:(~/concepts/apps/apps-overview).
[Warning] Invalid file link:(~/resources/design/framework/compose-extensions).
[Warning] Invalid file link:(~/concepts/deep-links).
[Warning] Invalid file link:(~/resources/design/components/buttons).
[Warning] Invalid file link:(~/resources/design/components/dialogs).
[Warning] Invalid file link:(~/resources/general/requirements).
[Warning] Invalid file link:(~/concepts/authentication).
[Warning] Invalid file link:(~/publishing/office-store-checklist).
[Warning] Invalid file link:(~/overview).
[Warning] Invalid file link:(~/concepts/compose-extensions).
[Warning] Invalid file link:(~/resources/design/components/themes).
[Warning] Invalid file link:(~/resources/general/debug).
[Warning] Invalid file link:(~/concepts/custom-bot).
[Warning] Invalid file link:(~/feedback).
[Warning] Invalid file link:(~/troubleshoot/troubleshoot).
[Warning] Invalid file link:(~/concepts/bots/bots-cards).
[Warning] Invalid file link:(~/concepts/tabs/tabs-static).
[Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
[Warning] Invalid file link:(~/concepts/bots/bots-context).
[Warning] Invalid file link:(~/concepts/apps/apps-sideload).

msteams-platform/concepts/apps/apps-overview.md

Line 15: [Warning] Invalid file link:(~/publishing/apps-package).
Line 21: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 22: [Warning] Invalid file link:(~/concepts/bots/bots-overview).
Line 23: [Warning] Invalid file link:(~/concepts/compose-extensions).
Line 31: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 32: [Warning] Invalid file link:(~/concepts/bots/bots-overview).
Line 32: [Warning] Invalid file link:(~/concepts/compose-extensions).
Line 33: [Warning] Invalid file link:(~/concepts/connectors).
Line 34: [Warning] Invalid file link:(~/concepts/compose-extensions).
Line 35: [Warning] Invalid file link:(~/concepts/custom-bot).
Line 43: [Warning] Invalid file link:(~/get-started/design).
Line 44: [Warning] Invalid file link:(~/get-started/code).
Line 45: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 46: [Warning] Invalid file link:(~/concepts/bots/bots-overview).
Line 47: [Warning] Invalid file link:(~/concepts/connectors).
Line 48: [Warning] Invalid file link:(~/concepts/compose-extensions).
Line 49: [Warning] Invalid file link:(~/concepts/activity-feed).
Line 51: [Warning] Invalid file link:(~/publishing/apps-package).
Line 52: [Warning] Invalid file link:(~/concepts/apps/apps-sideload).
Line 53: [Warning] Invalid file link:(~/publishing/apps-publish).

msteams-platform/concepts/apps/apps-sideload.md

Line 11: [Warning] Invalid file link:(~/concepts/bots/bots-test#adding-a-bot-for-11-chat-only).
Line 20: [Warning] Invalid file link:(~/publishing/apps-package).
Line 61: [Warning] Invalid file link:(~/concepts/tabs/tabs-configuration).
Line 81: [Warning] Invalid file link:(~/concepts/connectors).
Line 102: [Warning] Invalid file link:(~/publishing/apps-package).
Line 102: [Warning] Invalid file link:(~/resources/schema/manifest-schema).
Line 104: [Warning] Invalid file link:(~/troubleshoot/troubleshoot).

msteams-platform/concepts/bots/bots-overview.md

Line 14: [Warning] Invalid file link:(~/concepts/custom-bot).
Line 24: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 46: [Warning] Invalid file link:(~/get-started/design#designing-a-great-bot).
Line 46: [Warning] Invalid file link:(~/concepts/tabs/tabs-static).
Line 46: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 47: [Warning] Invalid file link:(~/concepts/bots/bots-create).
Line 48: [Warning] Invalid file link:(~/concepts/bots/bots-conversations).
Line 48: [Warning] Invalid file link:(~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk).
Line 49: [Warning] Invalid file link:(~/concepts/bots/bots-test).
Line 50: [Warning] Invalid file link:(~/publishing/apps-publish).
Line 54: [Warning] Invalid file link:(~/concepts/custom-bot).

msteams-platform/concepts/bots/bots-test.md

Line 17: [Warning] Invalid file link:(~/publishing/apps-package).
Line 17: [Warning] Invalid file link:(~/concepts/apps/apps-sideload).
Line 19: [Warning] Invalid file link:(~/concepts/bots/bots-notifications).
Line 60: [Warning] Invalid file link:(~/assets/images/bot/botdisable.png).
Line 78: [Warning] Invalid file link:(~/publishing/apps-publish).

msteams-platform/concepts/compose-extensions.md

Line 11: [Warning] Invalid file link:(~/resources/general/developer-preview).
Line 29: [Warning] Invalid file link:(~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk).
Line 35: [Warning] Invalid file link:(~/concepts/bots/bots-create).
Line 41: [Warning] Invalid file link:(~/resources/schema/manifest-schema#composeextensions).
Line 140: [Warning] Invalid file link:(~/concepts/apps/apps-sideload).
Line 206: [Warning] Invalid file link:(~/concepts/bots/bots-conversations#receiving-messages).
Line 275: [Warning] Invalid file link:(~/concepts/cards-actions).
Line 275: [Warning] Invalid file link:(~/concepts/connectors#using-office-365-connector-cards-in-microsoft-teams).
Line 413: [Warning] Invalid file link:(~/resources/schema/manifest-schema#validdomains).

msteams-platform/get-started/design.md

Line 49: [Warning] Invalid file link:(~/concepts/bots/bots-notifications).

msteams-platform/get-started/get-started.md

Line 60: [Warning] Invalid file link:(~/concepts/apps/apps-sideload).
Line 64: [Warning] Invalid file link:(~/resources/general/developer-preview).
Line 74: [Warning] Invalid file link:(~/concepts/apps/apps-overview).
Line 75: [Warning] Invalid file link:(~/get-started/design).
Line 76: [Warning] Invalid file link:(~/get-started/code).
Line 77: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 78: [Warning] Invalid file link:(~/concepts/bots/bots-overview).
Line 79: [Warning] Invalid file link:(~/concepts/connectors).
Line 80: [Warning] Invalid file link:(~/concepts/compose-extensions).
Line 81: [Warning] Invalid file link:(~/concepts/activity-feed).
Line 85: [Warning] Invalid file link:(~/publishing/apps-package).
Line 86: [Warning] Invalid file link:(~/concepts/apps/apps-sideload).
Line 87: [Warning] Invalid file link:(~/resources/general/debug).
Line 91: [Warning] Invalid file link:(~/publishing/apps-publish).
Line 92: [Warning] Invalid file link:(~/concepts/deep-links).
Line 96: [Warning] Invalid file link:(~/troubleshoot/troubleshoot).

msteams-platform/overview.md

Line 19: [Warning] Invalid file link:(~/get-started/get-started#1-set-up-your-office-365-tenant).
Line 25: [Warning] Invalid file link:(~/concepts/apps/apps-overview).
Line 47: [Warning] Invalid file link:(~/feedback).

msteams-platform/publishing/apps-package.md

Line 9: [Warning] Invalid file link:(~/concepts/apps/apps-sideload).
Line 18: [Warning] Invalid file link:(~/resources/schema/manifest-schema).
Line 57: [Warning] Invalid file link:(~/troubleshoot/troubleshoot).

msteams-platform/publishing/apps-publish.md

Line 10: [Warning] Invalid file link:(~/publishing/apps-package).
Line 10: [Warning] Invalid file link:(~/resources/schema/manifest-schema).
Line 51: [Warning] Invalid file link:(~/publishing/apps-package).
Line 51: [Warning] Invalid file link:(~/publishing/office-store-checklist).
Line 56: [Warning] Invalid file link:(~/publishing/office-store-guidance).
Line 89: [Warning] Invalid file link:(~/resources/schema/manifest-schema#bots).

msteams-platform/resources/design/framework/submitting.md

Line 124: [Warning] Invalid file link:(~/resources/design/framework/bots).
Line 188: [Warning] Invalid file link:(~/resources/design/framework/compose-extensions).

msteams-platform/resources/design/overview.md

Line 16: [Warning] Invalid file link:(~/resources/design/framework/basics).
Line 22: [Warning] Invalid file link:(~/resources/design/framework/tabs).
Line 28: [Warning] Invalid file link:(~/resources/design/framework/cards).
Line 34: [Warning] Invalid file link:(~/resources/design/framework/bots).
Line 40: [Warning] Invalid file link:(~/resources/design/framework/activity-feed).
Line 46: [Warning] Invalid file link:(~/resources/design/framework/compose-extensions).
Line 52: [Warning] Invalid file link:(~/resources/design/framework/basics).

msteams-platform/resources/general/developer-preview-features.md

Line 9: [Warning] Invalid file link:(~/resources/general/developer-preview).
Line 15: [Warning] Invalid file link:(~/overview).
Line 19: [Warning] Invalid file link:(~/publishing/apps-publish).
Line 23: [Warning] Invalid file link:(~/concepts/compose-extensions).
Line 27: [Warning] Invalid file link:(~/concepts/activity-feed).
Line 31: [Warning] Invalid file link:(~/concepts/connectors).
Line 35: [Warning] Invalid file link:(~/concepts/bots/bots-conversations#updating-messages).

msteams-platform/resources/schema/manifest-schema.md

Line 10: [Warning] Invalid file link:(~/resources/schema/manifest-schema-migrate).
Line 159: [Warning] Invalid file link:(~/concepts/bots/bots-create).
Line 211: [Warning] Invalid file link:(~/publishing/apps-package#icons).
Line 273: [Warning] Invalid file link:(~/resources/general/developer-preview).
Line 275: [Warning] Invalid file link:(~/concepts/bots/bots-menus).
Line 286: [Warning] Invalid file link:(~/resources/general/developer-preview).
Line 301: [Warning] Invalid file link:(~/resources/general/developer-preview).

msteams-platform/samples/code-samples.md

Line 21: [Warning] Invalid file link:(~/get-started/get-started).
Line 84: [Warning] Invalid file link:(~/resources/general/debug).

msteams-platform/concepts/cards-actions.md

Line 12: [Warning] Invalid file link:(~/concepts/cards-actions#hero-card).
Line 12: [Warning] Invalid file link:(~/concepts/cards-actions#hero-card).
Line 13: [Warning] Invalid file link:(~/concepts/cards-actions#thumbnail-card).
Line 13: [Warning] Invalid file link:(~/concepts/cards-actions#thumbnail-card).
Line 61: [Warning] Invalid file link:(~/concepts/bots/bots-conversations#message-format).
Line 61: [Warning] Invalid file link:(~/concepts/bots/bots-conversations#message-format).
Line 76: [Warning] Invalid file link:(~/concepts/bots/bots-conversations#message-format).
Line 76: [Warning] Invalid file link:(~/concepts/bots/bots-conversations#message-format).
Line 85: [Warning] Invalid file link:(~/concepts/connectors#using-office-365-connector-cards-in-microsoft-teams).
Line 85: [Warning] Invalid file link:(~/concepts/connectors#using-office-365-connector-cards-in-microsoft-teams).
Line 95: [Warning] Invalid file link:(~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk).
Line 95: [Warning] Invalid file link:(~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:warning:Warning

Details

msteams-platform/concepts/apps/apps-overview.md
:warning:Warning

Details

msteams-platform/concepts/apps/apps-sideload.md
:warning:Warning

Details

msteams-platform/concepts/bots/bots-overview.md
:warning:Warning

Details

msteams-platform/concepts/bots/bots-test.md
:warning:Warning

Details

msteams-platform/concepts/compose-extensions.md
:warning:Warning

Details

msteams-platform/get-started/design.md
:warning:Warning

Details

msteams-platform/get-started/get-started.md
:warning:Warning

Details

msteams-platform/overview.md
:warning:Warning

Details

msteams-platform/publishing/apps-package.md
:warning:Warning

Details

msteams-platform/publishing/apps-publish.md
:warning:Warning

Details

msteams-platform/resources/design/framework/submitting.md
:warning:Warning

Details

msteams-platform/resources/design/overview.md
:warning:Warning

Details

msteams-platform/resources/general/developer-preview-features.md
:warning:Warning

Details

msteams-platform/resources/schema/manifest-schema.md
:warning:Warning

Details

msteams-platform/samples/code-samples.md
:warning:Warning

Details

msteams-platform/concepts/cards-actions.md
:warning:Warning

Details

msteams-platform/get-started/code.md
:white_check_mark:Succeeded

msteams-platform/resources/design/framework/compose-extensions.md
:white_check_mark:Succeeded

msteams-platform/TOC.yml

[Warning] Invalid file link:(~/resources/design/framework/search).
[Warning] Invalid file link:(~/concepts/bots/bots-test).
[Warning] Invalid file link:(~/resources/general/cross-domain).
[Warning] Invalid file link:(~/concepts/activity-feed).
[Warning] Invalid file link:(~/concepts/bots/bots-overview).
[Warning] Invalid file link:(~/concepts/bots/bots-conversations).
[Warning] Invalid file link:(~/concepts/tabs/tabs-context).
[Warning] Invalid file link:(~/concepts/tabs/tabs-content).
[Warning] Invalid file link:(~/resources/design/components/color).
[Warning] Invalid file link:(~/concepts/cards-actions).
[Warning] Invalid file link:(~/resources/design/framework/apps).
[Warning] Invalid file link:(~/publishing/apps-package).
[Warning] Invalid file link:(~/concepts/connectors).
[Warning] Invalid file link:(~/resources/design/resources).
[Warning] Invalid file link:(~/resources/design/framework/submitting).
[Warning] Invalid file link:(~/resources/design/framework/basics).
[Warning] Invalid file link:(~/concepts/tabs/tabs-configuration).
[Warning] Invalid file link:(~/samples/code-samples).
[Warning] Invalid file link:(~/concepts/bots/bots-notifications).
[Warning] Invalid file link:(~/resources/schema/manifest-schema).
[Warning] Invalid file link:(~/resources/design/overview).
[Warning] Invalid file link:(~/resources/design/framework/cards).
[Warning] Invalid file link:(~/resources/design/framework/tabs).
[Warning] Invalid file link:(~/resources/design/framework/bots).
[Warning] Invalid file link:(~/troubleshoot/faq).
[Warning] Invalid file link:(~/scenarios/bots-personal-conversations).
[Warning] Invalid file link:(~/concepts/tabs/tabs-update-remove).
[Warning] Invalid file link:(~/concepts/bots/bots-menus).
[Warning] Invalid file link:(~/get-started/get-started).
[Warning] Invalid file link:(~/concepts/bots/bots-create).
[Warning] Invalid file link:(~/resources/general/developer-preview-features).
[Warning] Invalid file link:(~/resources/design/components/fields).
[Warning] Invalid file link:(~/resources/design/framework/activity-feed).
[Warning] Invalid file link:(~/scenarios/bots-channel-conversations).
[Warning] Invalid file link:(~/publishing/apps-publish).
[Warning] Invalid file link:(~/resources/general/developer-preview).
[Warning] Invalid file link:(~/resources/general/rate-limit).
[Warning] Invalid file link:(~/resources/design/components/typography).
[Warning] Invalid file link:(~/resources/microsoft-graph).
[Warning] Invalid file link:(~/publishing/office-store-guidance).
[Warning] Invalid file link:(~/concepts/apps/apps-overview).
[Warning] Invalid file link:(~/resources/design/framework/compose-extensions).
[Warning] Invalid file link:(~/concepts/deep-links).
[Warning] Invalid file link:(~/resources/design/components/buttons).
[Warning] Invalid file link:(~/resources/design/components/dialogs).
[Warning] Invalid file link:(~/resources/general/requirements).
[Warning] Invalid file link:(~/concepts/authentication).
[Warning] Invalid file link:(~/publishing/office-store-checklist).
[Warning] Invalid file link:(~/overview).
[Warning] Invalid file link:(~/concepts/compose-extensions).
[Warning] Invalid file link:(~/resources/design/components/themes).
[Warning] Invalid file link:(~/resources/general/debug).
[Warning] Invalid file link:(~/concepts/custom-bot).
[Warning] Invalid file link:(~/feedback).
[Warning] Invalid file link:(~/troubleshoot/troubleshoot).
[Warning] Invalid file link:(~/concepts/bots/bots-cards).
[Warning] Invalid file link:(~/concepts/tabs/tabs-static).
[Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
[Warning] Invalid file link:(~/concepts/bots/bots-context).
[Warning] Invalid file link:(~/concepts/apps/apps-sideload).

msteams-platform/concepts/apps/apps-overview.md

Line 15: [Warning] Invalid file link:(~/publishing/apps-package).
Line 21: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 22: [Warning] Invalid file link:(~/concepts/bots/bots-overview).
Line 23: [Warning] Invalid file link:(~/concepts/compose-extensions).
Line 31: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 32: [Warning] Invalid file link:(~/concepts/bots/bots-overview).
Line 32: [Warning] Invalid file link:(~/concepts/compose-extensions).
Line 33: [Warning] Invalid file link:(~/concepts/connectors).
Line 34: [Warning] Invalid file link:(~/concepts/compose-extensions).
Line 35: [Warning] Invalid file link:(~/concepts/custom-bot).
Line 43: [Warning] Invalid file link:(~/get-started/design).
Line 44: [Warning] Invalid file link:(~/get-started/code).
Line 45: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 46: [Warning] Invalid file link:(~/concepts/bots/bots-overview).
Line 47: [Warning] Invalid file link:(~/concepts/connectors).
Line 48: [Warning] Invalid file link:(~/concepts/compose-extensions).
Line 49: [Warning] Invalid file link:(~/concepts/activity-feed).
Line 51: [Warning] Invalid file link:(~/publishing/apps-package).
Line 52: [Warning] Invalid file link:(~/concepts/apps/apps-sideload).
Line 53: [Warning] Invalid file link:(~/publishing/apps-publish).

msteams-platform/concepts/apps/apps-sideload.md

Line 11: [Warning] Invalid file link:(~/concepts/bots/bots-test#adding-a-bot-for-11-chat-only).
Line 20: [Warning] Invalid file link:(~/publishing/apps-package).
Line 61: [Warning] Invalid file link:(~/concepts/tabs/tabs-configuration).
Line 81: [Warning] Invalid file link:(~/concepts/connectors).
Line 102: [Warning] Invalid file link:(~/publishing/apps-package).
Line 102: [Warning] Invalid file link:(~/resources/schema/manifest-schema).
Line 104: [Warning] Invalid file link:(~/troubleshoot/troubleshoot).

msteams-platform/concepts/bots/bots-overview.md

Line 14: [Warning] Invalid file link:(~/concepts/custom-bot).
Line 24: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 46: [Warning] Invalid file link:(~/get-started/design#designing-a-great-bot).
Line 46: [Warning] Invalid file link:(~/concepts/tabs/tabs-static).
Line 46: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 47: [Warning] Invalid file link:(~/concepts/bots/bots-create).
Line 48: [Warning] Invalid file link:(~/concepts/bots/bots-conversations).
Line 48: [Warning] Invalid file link:(~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk).
Line 49: [Warning] Invalid file link:(~/concepts/bots/bots-test).
Line 50: [Warning] Invalid file link:(~/publishing/apps-publish).
Line 54: [Warning] Invalid file link:(~/concepts/custom-bot).

msteams-platform/concepts/bots/bots-test.md

Line 17: [Warning] Invalid file link:(~/publishing/apps-package).
Line 17: [Warning] Invalid file link:(~/concepts/apps/apps-sideload).
Line 19: [Warning] Invalid file link:(~/concepts/bots/bots-notifications).
Line 60: [Warning] Invalid file link:(~/assets/images/bot/botdisable.png).
Line 78: [Warning] Invalid file link:(~/publishing/apps-publish).

msteams-platform/concepts/compose-extensions.md

Line 11: [Warning] Invalid file link:(~/resources/general/developer-preview).
Line 29: [Warning] Invalid file link:(~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk).
Line 35: [Warning] Invalid file link:(~/concepts/bots/bots-create).
Line 41: [Warning] Invalid file link:(~/resources/schema/manifest-schema#composeextensions).
Line 142: [Warning] Invalid file link:(~/concepts/apps/apps-sideload).
Line 208: [Warning] Invalid file link:(~/concepts/bots/bots-conversations#receiving-messages).
Line 277: [Warning] Invalid file link:(~/concepts/cards-actions).
Line 277: [Warning] Invalid file link:(~/concepts/connectors#using-office-365-connector-cards-in-microsoft-teams).
Line 415: [Warning] Invalid file link:(~/resources/schema/manifest-schema#validdomains).

msteams-platform/get-started/design.md

Line 49: [Warning] Invalid file link:(~/concepts/bots/bots-notifications).

msteams-platform/get-started/get-started.md

Line 60: [Warning] Invalid file link:(~/concepts/apps/apps-sideload).
Line 64: [Warning] Invalid file link:(~/resources/general/developer-preview).
Line 74: [Warning] Invalid file link:(~/concepts/apps/apps-overview).
Line 75: [Warning] Invalid file link:(~/get-started/design).
Line 76: [Warning] Invalid file link:(~/get-started/code).
Line 77: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 78: [Warning] Invalid file link:(~/concepts/bots/bots-overview).
Line 79: [Warning] Invalid file link:(~/concepts/connectors).
Line 80: [Warning] Invalid file link:(~/concepts/compose-extensions).
Line 81: [Warning] Invalid file link:(~/concepts/activity-feed).
Line 85: [Warning] Invalid file link:(~/publishing/apps-package).
Line 86: [Warning] Invalid file link:(~/concepts/apps/apps-sideload).
Line 87: [Warning] Invalid file link:(~/resources/general/debug).
Line 91: [Warning] Invalid file link:(~/publishing/apps-publish).
Line 92: [Warning] Invalid file link:(~/concepts/deep-links).
Line 96: [Warning] Invalid file link:(~/troubleshoot/troubleshoot).

msteams-platform/overview.md

Line 19: [Warning] Invalid file link:(~/get-started/get-started#1-set-up-your-office-365-tenant).
Line 25: [Warning] Invalid file link:(~/concepts/apps/apps-overview).
Line 47: [Warning] Invalid file link:(~/feedback).

msteams-platform/publishing/apps-package.md

Line 9: [Warning] Invalid file link:(~/concepts/apps/apps-sideload).
Line 18: [Warning] Invalid file link:(~/resources/schema/manifest-schema).
Line 57: [Warning] Invalid file link:(~/troubleshoot/troubleshoot).

msteams-platform/publishing/apps-publish.md

Line 10: [Warning] Invalid file link:(~/publishing/apps-package).
Line 10: [Warning] Invalid file link:(~/resources/schema/manifest-schema).
Line 51: [Warning] Invalid file link:(~/publishing/apps-package).
Line 51: [Warning] Invalid file link:(~/publishing/office-store-checklist).
Line 56: [Warning] Invalid file link:(~/publishing/office-store-guidance).
Line 89: [Warning] Invalid file link:(~/resources/schema/manifest-schema#bots).

msteams-platform/resources/design/framework/submitting.md

Line 124: [Warning] Invalid file link:(~/resources/design/framework/bots).
Line 188: [Warning] Invalid file link:(~/resources/design/framework/compose-extensions).

msteams-platform/resources/design/overview.md

Line 16: [Warning] Invalid file link:(~/resources/design/framework/basics).
Line 22: [Warning] Invalid file link:(~/resources/design/framework/tabs).
Line 28: [Warning] Invalid file link:(~/resources/design/framework/cards).
Line 34: [Warning] Invalid file link:(~/resources/design/framework/bots).
Line 40: [Warning] Invalid file link:(~/resources/design/framework/activity-feed).
Line 46: [Warning] Invalid file link:(~/resources/design/framework/compose-extensions).
Line 52: [Warning] Invalid file link:(~/resources/design/framework/basics).

msteams-platform/resources/general/developer-preview-features.md

Line 9: [Warning] Invalid file link:(~/resources/general/developer-preview).
Line 15: [Warning] Invalid file link:(~/overview).
Line 19: [Warning] Invalid file link:(~/publishing/apps-publish).
Line 23: [Warning] Invalid file link:(~/concepts/compose-extensions).
Line 27: [Warning] Invalid file link:(~/concepts/activity-feed).
Line 31: [Warning] Invalid file link:(~/concepts/connectors).
Line 35: [Warning] Invalid file link:(~/concepts/bots/bots-conversations#updating-messages).

msteams-platform/resources/schema/manifest-schema.md

Line 10: [Warning] Invalid file link:(~/resources/schema/manifest-schema-migrate).
Line 159: [Warning] Invalid file link:(~/concepts/bots/bots-create).
Line 211: [Warning] Invalid file link:(~/publishing/apps-package#icons).
Line 273: [Warning] Invalid file link:(~/resources/general/developer-preview).
Line 275: [Warning] Invalid file link:(~/concepts/bots/bots-menus).
Line 286: [Warning] Invalid file link:(~/resources/general/developer-preview).
Line 301: [Warning] Invalid file link:(~/resources/general/developer-preview).

msteams-platform/samples/code-samples.md

Line 21: [Warning] Invalid file link:(~/get-started/get-started).
Line 84: [Warning] Invalid file link:(~/resources/general/debug).

msteams-platform/concepts/cards-actions.md

Line 12: [Warning] Invalid file link:(~/concepts/cards-actions#hero-card).
Line 12: [Warning] Invalid file link:(~/concepts/cards-actions#hero-card).
Line 13: [Warning] Invalid file link:(~/concepts/cards-actions#thumbnail-card).
Line 13: [Warning] Invalid file link:(~/concepts/cards-actions#thumbnail-card).
Line 61: [Warning] Invalid file link:(~/concepts/bots/bots-conversations#message-format).
Line 61: [Warning] Invalid file link:(~/concepts/bots/bots-conversations#message-format).
Line 76: [Warning] Invalid file link:(~/concepts/bots/bots-conversations#message-format).
Line 76: [Warning] Invalid file link:(~/concepts/bots/bots-conversations#message-format).
Line 85: [Warning] Invalid file link:(~/concepts/connectors#using-office-365-connector-cards-in-microsoft-teams).
Line 85: [Warning] Invalid file link:(~/concepts/connectors#using-office-365-connector-cards-in-microsoft-teams).
Line 95: [Warning] Invalid file link:(~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk).
Line 95: [Warning] Invalid file link:(~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk).

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


Parameter should be MARATHON_HOST instead of URL

The expected value in MARATHON_URL as per implementation is Hostname or IP. Hence, the parameter should be changed to MARATHON_HOST

Thanks for the PR! Merged.


release 2.8.3

FYI.. this is what I'm seeing:

This is expected right now as this is still building. It should sort itself out once the build is finished.

@wallacekelly-da The deployment is now done, please check again.

@garyverhaegen-da All good! I just happened to hit it during the transition.

@garyverhaegen-da Is this difference an expected transient issue?

No, there is nothing transient anymore. The 2.8.3 publication is fully finished. Note that 2.8.1 showed the same discrepancy.
Canton docs snippet directives are not direct inclusion, they go through a mapping from snippet name to content. You'll have to consult with the Canton team to know whether this discrepancy is expected here.

@wallacekelly-da This should have been fixed by #650. Please shout if it wasn't.

Yes, the docs are correct now. Thank you for double-checking!


Add PHP7.4 to travis

I would like to migrate CI at the GitHub Actions.

Closing in favour https://github.com/phalcon/vokuro/issues/150


kubedctl enable services has conflict with knative services

What happened:
run $ ./bin/kubefedctl enable services --kubefed-namespace default
returns  F0802 15:16:29.293248   61760 enable.go:110] Error: Multiple resources are matched by "services": services, services.serving.knative.dev. A group-qualified plural name must be provided.
The reason is that i installed knative services crd before. However, we cannot enable kube services using command line, since it has no group.
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
install knative services and run kubefedctl enable services
Anything else we need to know?:
Environment:

Kubernetes version (use kubectl version)
KubeFed version
Scope of installation (namespaced or cluster)
Others

/kind bug

@qiujian16 Good catch.  The 'core' API types lack of a group doesn't allow providing a group-qualified name in cases like this where the kind/plural name is ambiguous.  Would it make sense for kubefedctl enable to accept core as a qualifier (e.g. services.core) for these types and then strip the suffix before use?

for better user experience, should we have kubefedctl enable service points to the v1/services instead of running kubefedctl enable service.core? It is similar for federated deployment, today we need to run kubefedctl enable deployment.apps or kubefedctl enable deployment.extensions, but it will be better if we can run kubefedctl enable deployment which then points to a certain api group. WDYT?

@qiujian16 The current approach is requiring that the user be explicit, and I don't think this case suggests deviating from that approach. We can't assume that we know better than the user as to what they should be enabling.

yes..that makes sense. So if there are not multiple match, should still use kubefedctl enable service, otherwise, should use kubefedctl enable service.core

And not just for services - kubefedctl should accept *.core as a type name and strip the .core suffix for interaction with the API.

So what's the solution?
I still got error message while execute command kubefedctl enable service.core.
F0904 16:14:12.809596   49450 enable.go:111] Error: Unable to find api resource named "service.core".

/reopen.

/reopen

/remove-lifecycle rotten

I issued a PR with a potential fix: #1294


One-shot static compilation method without exit

In integration with our tooling it would be convenient to have a one-shot static method to perform compilation. Invoking main results in System.exit being called. Normally I would just add a compile overload which only took a String[] (#283), but that conflicts with the instance method of the same signature.
This isn't a must-have, of course. I can continue invoking the builder or just pass my own wrapper around System.err as a second argument to the existing static method, but it'd be nice.
Some alternatives:

Change the static helpers to compileForResult (or something) to more accurately describe what they do.
Change the instance compile(String[]) method to be named run, execute, etc. Not sure how set-in-stone this method is. My guess would be "very" though :)

Thoughts?

Renaming to run SGTM. It's not very set-in-stone :)
Our internal integration mostly uses the Scanner class directly.

Ok! I'll send a PR shortly.


npm run build fails with Type Mismatch Errors

Describe the bug
When trying to build the PXT repo, a typescript error occurs related to the @types/react package. The error indicates the following:
  Its instance type 'Provider<AnyAction>' is not a valid JSX element.
    The types returned by 'render()' are incompatible between these types.
      Type 'React.ReactNode' is not assignable to type 'import("/Users/ethanshafranmoltz/node_modules/@types/react/ts5.0/index").ReactNode'.
        Type '{}' is not assignable to type 'ReactNode'.
    20 | ReactDOM.render(
    21 |     <React.StrictMode>
  > 22 |         <Provider store={store}>
       |          ^^^^^^^^
    23 |             <App />
    24 |         </Provider>
    25 |     </React.StrictMode>,

To Reproduce
clone this repo
run npm i
run npm run build
It fails with the above error.
Desktop
OS: MacOS M1
Node.js version: 18.17.0
TypeScript Version: 4.4.3
@types/react version: 17.0.5
Additional Info
I've tried for the last few days to resolve this issue -- chatGPT, Google, StackOverflow, etc. So far, no luck. I am eager to contribute to this project -- let me know how I can get this going on my end!

Fixed: running this on a folder located within an iCloud folder causes the issue.


EPIC Library authentication fails - using EPIC log in (can't import games).

The issue happens sometimes (not 100% of the time).
When importing games for the EPIC Library, the authentication fails (the bell shows the number 1).

When clicking the bell it reads "... EPIC... An error occurred while sending the request".
When clicking on the "EPIC..."message, I can see a pop-up dialog with a button that says [Authenticate] and a message to its right reading "Checking Authentication Status...".
2a. Most of the times it resolves to "Authenticated".
2b. Sometimes it resolves to "Requires authentication". Then I click the button, fill in all the details and it resolves to "Authenticated".
Still, after being Authenticated, trying again to import from library fails, and I need to start all over again.

Things I've tried:

Disabling the plugin (EPIC).
Playnite safe mode (as requested).
restarting the app a few times.
log in to EPIC with the EPIC login (not the google one, or any other). It fails!.
log in to EPIC through the Web browser and the app (successfully in all those cases).
Updating the app (both. EPIC launcher, and playnite).
Everything has been restarted 2 or 3 times at least (browser, app, playnite)
Most other libraries work fine without issue. But sometimes might have the log in issue as well, from time to time. But all the log in issues of the other libraries (not counting EPIC) together  are 1/3-1/2 the issues with EPIC (maybe it's EPIC's site, maybe the integration).
Tried several times to import. Sometimes it works on the 4th/5th try, sometimes on the 2nd, sometimes ... on the 20th.

Please note, that I have a very restrictive firewall in place.
Playnite is running as a browser (So ports: 80, 443, 53, 21, and some other. That should suffice), but I had it running as a full outbound/inbound app as well (just for testing). The issues were the same.
But I have also blocked (for years now, and different systems and windows versions) "system" (whatever that means on the firewall) and svchost.exe (only the DNS port and some basic ports are allowed) NEVER AN ISSUE (for windows update, I do allow some IPs when needed).
If it were a firewall problem, please let us know what processes and ports are needed through, so we can act accordingly. Thanks.
EPIC used to log in using some windows processes (maybe svchost, maybe windows update processes). I did contact them about that, and they told me so, and that they were working on an alternative (which is the way it's working now). So no issue there either.

[x] Check for an existing issue
[x] Describe the bug
[x] To Reproduce
[ ] Screenshots
[x] Diagnostics ID: 87c0277e-de3a-46cf-a392-b888c83bb7b2

PS: Just mentioning that as of now it's working (I don't know for how long). And no wifi is used. Cat-6 cable.

This is network issue according to logs, nothing I can fix. It's either an issue on Epic's side or in your environment.
System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it <IP_ADDRESS>:443

Ok, thanks. Then sorry about that. I'll check the network for issues.
Is there a way for me to be able to see the logs?

Nevermind, I'll try to find it!
Thanks.
PS:I'll keep the issue open until I do some tests and see the results on the logs to make sure of it. ^_^

Logs are in %appdata%\playnite\playnite.log if you are using installed version.

just tested on p9 beta and p8 both exhibit the same problem with me as well displaying authentication failed so it's not related to the beta, could be an issue with epic or they have changed something

joyrider3774 on discord says this is also broken on P8. I'd close this, but it's up to you

The issue that started happening today is not the same as original issue reported here, which is clearly caused by network error.

The issue that started happening today is not the same as original issue reported here, which is clearly caused by network error.

someone gave me wrong link to issue then on discord, i asked if it was reported

Closing, authentication right now works properly. The original issue is caused by a network issue, which is something we can't do anything about.


Cancel buy of Tile Card

When paying for a Tile Card, before placing it in either the Town or the Spare Yard, the player may cancel the purchase.

Depends on #40


Memory leakage

Haha, it's still me. I deployed the service on Unraid and replaced the graphics card with a Tesla P4.
The program successfully started running!
However, it seems that there is a memory leak issue in the program. When I add multiple tasks to the task queue at once, it consumes a large amount of memory and crashes the service. When I use "--memory=5G" in docker,  a single file can run (but I can observe a significant peak in system memory usage), but when I run multiple files, the log shows multiple "Model was purged, need to re-create" messages, followed by an error saying "died with <Signals,SIGKILL.9>" and stops.

And it seems that CONCURRENT_TRANSCRIPTIONS is not working. Although I set CONCURRENT_TRANSCRIPTIONS=1, in debug mode, I still see multiple progress bars in the log and it consumes more than the VRAM of a single video.

Yeah, CONCURRENT_TRANSCRIPTIONS doesn't really do anything right now.  I need to fix queuing and threading.  I've had better luck with WHISPER_THREADS.
I've never had a leak or an OOM issues with the container on the P4.  The only time i've had it crash was trying to use a Large model with >60 min files.  I've easily had 100+ items in the 'queue' (use it loosely because it doesn't quite work) with 5+ items transcribing at the same time without any issues.
Are you somehow memory constrained on your machine?  I'm running 32gb have have run the the exact container configuration you have for months without issue.

I'm currently running Unraid with 16GB of memory, but only 7GB is available.  Using a medium model with >120 min files.

I'm not sure.  This is what I see with about a dozen Mediums queued up in Bazarr.

Finally, I found that there was a peak in RAM usage when loading large media files, even during GPU transcription. I solved this by enabling Swap Memory in Unraid.
By the way, I fix queuing by using threading.Thread() and create a PR


reboot the crate

rebooting the crate, as in rewriting it from scratch into a new crate totally independent of current code.

manually reset main to shin_sekai branch and closed pr


"struggling on" warnings

Hi - thanks for the note on Wikipedia citations.   I am still not really satisfied with how those show up.
For some time, it was discouraged to use Wiki citations in publications, but there is SO little original source material
on the Web, that is accessible to the average reader, for these subjects, that it is becoming more
acceptable to take advantage of Wiki.   I think it is important for my readers to have these Wiki citations clearly available to
get more details.  But I'm not satisfied with the .bib file entries I am using, or how they appear
so verbosely in the text.   We and the editors can correspond more on this in production.  Just a heads up.
So, I am doing whole-book passes now, trying to get everything in order for submission around Sept 4,
and I am getting these errors for images I took as MacOS screen shots, converted to pdf, then to eps.
I've used the same process with no problems for years, but here is what I get for these four images:
[44] [45<./img2/QuatRot1.eps>
/Library/TeX/texbin/dvips:  expected to see %%EndBinary at end of data; struggling on
<./img2/QuatRot2.eps>
/Library/TeX/texbin/dvips:  expected to see %%EndBinary at end of data; struggling on
] [46<./img2/QuatRot3.eps>
/Library/TeX/texbin/dvips:  expected to see %%EndBinary at end of data; struggling on
<./img2/QuatRot4.eps>
/Library/TeX/texbin/dvips:  expected to see %%EndBinary at end of data; struggling on
I tried to give you the actual .eps files, but GitHub refuses.   Here are the source .png screenshots
that give the .eps files with the above error messages.
Best, Andy

Hi,
One option would be to do nothing (if the PDF output is OK)
or you could try to fix EPS files with utilities like e.g.  purifyeps  and pstoedit
or you could try to convert PNG files to EPS with tools like  pngtopnm and pnmtops
(cat foo.png | pngtopnm  | pnmtops > foo.eps)
or you could try to convert via PDF: PNG -> PDF -> EPS.
best, deimi


change password request

My haxelib user name is miriti.
Thank you.

I've sent you an email to your haxelib account email address.

Done


Modified documentation page

Fixes: #31
@Abhijit2505 I have made the change in the documentation section. Please have a look. I have also modified the pages such that it will redirect to the same page (Issue number 18).

@all-contributors add @sakshikhachane for code


Return promises from service methods

Having the service methods return promises instead of taking callbacks as inputs would probably make them more ember-friendly since most folks might end up wrapping the service calls in promises again.

Yeah,  I find that they end up getting wrapped in promises in most use
cases anyway.  I'll explore ways to provide some meaningful promises which
could be more convenient. I'd also really appreciate some context for
similar suggested functionality.
On Jun 11, 2017 10:33 PM, "Sivakumar Kailasam"<EMAIL_ADDRESS>wrote:

Having the service methods return promises instead of taking callbacks as
inputs would probably make them more ember-friendly since most folks might
end up wrapping the service calls in promises again.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/PrinceCornNM/ember-algolia/issues/4, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AD3MarLyGIhlfCtILzp-RXw7oZDsnSTAks5sDLGKgaJpZM4N2nz-
.

You can use RSVP's denodeify to convert from node style callbacks to promises. Here's a sampler: https://github.com/ember-learn/ember-api-docs/pull/233/files#diff-319f96f3a3558fc217c4e30a5fd10487R50

Would you mind giving an example of how to use denodeify and ember-algolia? I could not get it to work properly. I really appreciate it!


Feature/9 force login

Added logic to force login in environments like integration, preproduction etc.
Used https://ericceric.com/2022/03/04/make-optimizely-dxp-integration-and-preproduction-sites-force-login/ as source

#15


Missing "./generated" specifier in "contentlayer" package

PNPM build breaks with error
Internal server error: Missing "./generated" specifier in "contentlayer" package
doc:dev:   Plugin: vite:import-analysis

The file with the error is a sveltekit +server.ts and has this import lines
import type { Post } from 'contentlayer/generated';
import { allPosts } from 'contentlayer/generated';

.contentlayer/generated folder is generated successfully including Post directory.
I am not sure, if the reason is pnpm, vite, sveltekit or contentlayer.
Is this known?
This is the tsconfig.json
{
  "extends": "./.svelte-kit/tsconfig.json",
  "compilerOptions": {
    "allowJs": true,
    "checkJs": true,
    "esModuleInterop": true,
    "forceConsistentCasingInFileNames": true,
    "resolveJsonModule": true,
    "skipLibCheck": true,
    "sourceMap": true,
    "strict": true,
    "baseUrl": ".",
    "paths": {
      "$lib": [
        "./src/lib"
      ],
      "$lib/*": [
        "./src/lib/*"
      ],
      "contentlayer/generated": [
        "./.contentlayer/generated"
      ]
    }
  },
  "include": [
    "./.svelte-kit/ambient.d.ts",
    "./.svelte-kit/types/**/$types.d.ts",
    "./vite.config.ts",
    "./src/**/*.js",
    "./src/**/*.ts",
    "./src/**/*.svelte",
    "./tests/**/*.js",
    "./tests/**/*.ts",
    "./tests/**/*.svelte",
    ".contentlayer/generated"
  ]
}

Beside this, contentlayer is a great, very helpful solution and I am eager to use it in the next project.

PNPM 7.29.1
Turborepo (latest) with sveltekit 1.12.0
Contentlayer version: 0.3.0

I got it. It works now.
In my case it needed an alias not only in the tsconfig.json but also in vite.config.js.
With this vite.config.js it works fetching data like allPosts.
import { fileURLToPath, URL } from "url";
...
	resolve: {
		alias: [
			{
				find: 'contentlayer/generated',
				replacement: fileURLToPath(new URL('./.contentlayer/generated', import.meta.url)) ,
			},
		],
	},

See also Vite Documention of resolve-alias


refactor(trajectory_follower/trajectory_follower_nodes): remove motion_common

Signed-off-by: Takayuki Murooka<EMAIL_ADDRESS>Description
related to https://github.com/autowarefoundation/autoware.universe/issues/2229
remove motion_common dependency, which is added in autoware.auto, from trajectory_follower/trajectory_follower_nodes

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

I confirmed locally that planning simulator works well


Oracle Summer Internship no longer accepting applications

Thanks for letting us know. I'll remove the post tomorrow.


In Memory Antimalware Scanning

Does it mean Azure defender will perform hash value validation against known malicious content after a file was written to Azure storage, and there is no in-memory scanning (upload in progress) before the file is being uploaded?

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

ID: e6fdc03a-8b15-c019-a972-ebde82f6479a
Version Independent ID: 829ec787-ea71-d02a-1d4f-336129a6ab14
Content: Microsoft Defender for Storage - the benefits and features
Content Source: articles/defender-for-cloud/defender-for-storage-introduction.md
Service: defender-for-cloud
GitHub Login: @memildin
Microsoft Alias: memildin

Thanks for the feedback! We have assigned the issue to the content author to further review this and provide an update as appropriate.

Hi @donchai, thanks for the question.
Today, Microsoft Defender for Storage doesn’t provide full antimalware scanning. You're correct that, as the docs explain, we provide hash reputation analysis performed when a file has already been uploaded.
I'm going to close this issue, but feel free to comment again here or open a new one if you have additional requests.
#please-close


Traefik auto-update broke path-matching, until deployments were restarted

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?
At midnight, Traefik updated itself:
➜ k get pods --namespace kube-system
NAME                                      READY   STATUS      RESTARTS   AGE
helm-install-traefik-nrsmt                0/1     Completed   0          8h

After this, all my ingresses with path-matching stopped working. I had an ingress like this:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: chess
  annotations:
    traefik.ingress.kubernetes.io/router.entrypoints: web,websecure
    cert-manager.io/cluster-issuer: letsencrypt-prod
spec:
  rules:
    - host: chessmadra.com
      http: &http_rules
        paths:
          - path: "/api"
            pathType: Prefix
            backend:
              service:
                name: chess
                port:
                  number: 80
  tls:
    - hosts:
        - chessmadra.com
      secretName: chess-madra-cert-prod

After the update, /api requests were no longer routed to this service. Instead they were routed to this service:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: chess-frontend
  annotations:
    traefik.ingress.kubernetes.io/router.entrypoints: web,websecure
    cert-manager.io/cluster-issuer: letsencrypt-prod
spec:
  rules:
    - host: chessmadra.com
      http:
        paths:
          - path: "/"
            pathType: Prefix
            backend:
              service:
                name: chess-frontend
                port:
                  number: 80
  tls:
    - hosts:
        - chessmadra.com
      secretName: chess-madra-cert-prod

This caused the site to go down, until I ran kubectl -n kube-system rollout restart daemonsets,deployments and kubectl rollout restart deployments.
Is there anything wrong with my ingress config for these, that would cause traefik to not pick up their paths until they were restarted?
Is there a way to disable auto-updates so this doesn't happen again?
What did you see instead?
_
What version of Traefik are you using?
2.9.4
What is your environment & configuration?
k3s, helm installed traefik
If applicable, please paste the log output in DEBUG level
No logs unfortunately, the old pod isn't around anymore after the restart.

Hello @marcusbuffett and thanks for your interest in Traefik,

Is there a way to disable auto-updates so this doesn't happen again?

Traefik is not auto-updating itself when a new version is published. This mechanism does not exist but maybe this is something handled by your infrastructure.

Is there anything wrong with my ingress config for these, that would cause traefik to not pick up their paths until they were restarted?

The Ingress configurations looks good. Maybe a resource linked to the Ingress was not available, and as a side effect the corresponding router was not created.
Without more information, it is hard to diagnose if something is wrong on our side. For that reason, we are closing this issue, but feel free to open a new one with more details (infrastructure, debug logs, or even better a reproducible case) if you are still convinced that something is wrong on our side.


A bug in killChild

index.ts, lines 83 +
  }         private killChild(){             this.cancelled = true;             this.child.kill(); }
i don't know why it gets there, maybe because it starts before it finished a previous scan, but it crashes  on this.child = undefined.
perhaps it would be better to write:
   this.child && this.child.kill();
Btw, is this module maintain? reliable?

I have the same issue. index.js:66
this.child.kill()
TypeError: cannot call method 'kill' of undefined.
Is this perhaps a permissions error?

Hey guys, I'll look into this bug.  @dharmax are you attempting to run simultaneous scans?
@menja12 I typically ran this with admin permissions.  I'll try to recreate this issue.
What OS
Version of Node
Version of NMAP installed

@dharmax @menja12  I'm absolutely up to continuing to maintain this repo, however I was unsure of usage due to lack of feedback.  I wanted to make an nmap module that didn't require a firm understanding of NMAP itself.  If you have any feedback, I'd love to hear it.
I've also been toying with the idea of creating an alternate module that relies on Node's core APIs rather than NMAP.  Is that something anyone would be interested in?  It'd definitely be more performant.

I'm doing a single scan.
OS: Raspian Jessie (Raspberry pi os)
Node version: running through a node-red module
version of NMAP: Embarrassed look...

Node version 0.10.29
Nmap version 6.47
Still getting the cannot call method 'kill' of undefined error..

Hey guys, I'll look into this bug. @dharmax are you attempting to run simultaneous scans?

i do a scan, cancel it and attempt to do a new scan.

I've also been toying with the idea of creating an alternate module that relies on Node's core APIs rather than NMAP. Is that something anyone would be interested in? It'd definitely be more performant.

Yes, i believe the performance and behavior might be much better, but will it be able to discover all the information nmap does?


LayerNorm

Implement LayerNorm as a fused op
TODO:

[x] Add unit test
[x] Add type prop test

PlaidML IntelGPU Mac fails tests nut PlaidML IntelGPU ubuntu passes. Very strange.


snmpsimd.py: Value evaluation error for subprocess and hexlified values

I encounter a value evaluation error when using the subprocess variation module to update hexlified values in .snmprec files.
I'm using HOST-RESOURCES-MIB::hrSystemDate for illustration with the use case to return the current timestamp whenever polled.  The value is a RFC2579 DateAndTime octet string.
Raw capture:
<IP_ADDRESS>.<IP_ADDRESS>.2.1|4x|07e30307001b01152b0000

snmpwalk result using the default raw capture:
HOST-RESOURCES-MIB::hrSystemDate.1 = STRING: 2019-3-7,0:27:1.21,+0:0

I now update the snmprec to use subprocess to provide the octetstring.  snmpsimd logs the following error:
ERROR data error at /home/someuser/pydev/snmpsim/data/snmpwalk/host.snmprec controller for <IP_ADDRESS>.<IP_ADDRESS>.2: value evaluation error for tag '4', value b'07e30307001b01152b0000\n'

The issue remains no matter which approach I use e.g.
<IP_ADDRESS>.<IP_ADDRESS>.2.1|4x:subprocess|get_date.py  <=== this is the desired approach
<IP_ADDRESS>.<IP_ADDRESS>.2.1|4x:subprocess|echo 07e30307001b01152b0000
<IP_ADDRESS>.<IP_ADDRESS>.2.1|4:subprocess|echo hexvalue=07e30307001b01152b0000

The last example doesn't result in an error, but it ends up passing a hexflified value for the whole 'hexvalue=07e30307001b01152b0000' string which doesn't produce the desired outcome.  I don't believe hexvalue is supported for subprocess as it's not mentioned in the docs.
I can reproduce the issue on versions 0.4.6 and 0.4.7 on RHEL Python 3.6/3.7.
UPDATED:  It works when running snmpsim on Python 2.7.
Is there anything to be done to help it along in Python 3?
Thanks!
Pieter

Thank you for raising this and sorry for it takes time!
There is a fix in the release candidate as well as in master to address this problem.


Be able to override :base_url

These days one codebase usually uses more than one OpenAI compatible API provider at the same time.
This PR provides the ability to override the base URL.
Example usage:
msgs = [%{role: :user, content: "Hello!"}]

ExOpenAI.Chat.create_chat_completion(msgs, "hf:mistralai/Mistral-7B-Instruct-v0.3",
  base_url: "https://cheapai.local",
  openai_api_key: "1234"
)

Solves https://github.com/dvcrn/ex_openai/issues/24

Thanks for the PR! Looking good!
I'll try to get this released within the next few days ❤

Released in 1.7 - https://github.com/dvcrn/ex_openai/releases/tag/1.7.0


Naming inconsistencies

Is there any reason why for some countries you need the nations full name, such as "Tanzania, United Republic of" for getCode(), but for others the country is referred simply by its common name, like "Chad"

Those as the names as provided by the ISO standard. It seems reasonable for this package to follow the standard rather than attempt to make its own decisions about appropriate names.


lifelines: init at 2017-06-12-unstable

Motivation for this change
Adds lifelines command line genealogy tool. Using unstable because tag 3.1.1 will not build. Currently points at my repo, but will switch to upstream as soon as https://github.com/MarcNo/lifelines/pull/311 is merged.
Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

You can do hardeningDisable = [ "format" ] or NIX_CFLAGS_COMPILE = "-Wno-error=format-security".
More generally, having unstable after the date seems inappropriate; unstable is more akin to a namespace than a part of the version string.

Thanks for the review. I'll try that autotools thing. First autotools nixpkg I've worked on. As for the name, that semantic comes straight from the manual: https://nixos.org/nixpkgs/manual/#sec-package-naming. I'm contributing bug fixes and stuff upstream as well, so hopefully we can get a stable version tagged that builds on nixos soon.

Note that the manual recommends adding -unstable to the package name, not the version.
My suggestion of simply disabling the error flag obviates the need for pointing to your own fork, if that's the only reason to not use upstream.

My commit was just merged, so I switched to their repo. It's using fetchFromGithub now as well. I still can't build off a stable release because both previous stable releases (3.1.0 and 3.1.0) fail to compile on gcc because of conflicting function definitions (already fixed in upstream).

One thing to consider is that if you intend to drop the unstable suffix once upstream makes a new release, somebody who installed the unstable package would not receive the update via ordinary package upgrade, because they'll be considered different packages. It's probably more appropriate to use the pre-release naming pattern here. I think the intent behind unstable really is for situations where you'd carry both a stable and an unstable variant over time.

I'm hoping an upstream release will be soon and I can use that.

@disassembler How about versioning it as "<IP_ADDRESS>81013" ?

@disassembler any motivation to continue this PR?

I actually wanted to try this program out anyways... so I updated the PR to be a more recent unstable version.


*: Update to sigs.k8s.io/metrics-server latest

Pick up changes to 1.17 to custom-metrics-apiserver and the latest changes in metrics-server to allow us to show table results for podmetrics and nodemetrics. Fix import and interface changes as necessary.
The localvendor directory is an artifact of a change in sigs.k8s.io: sigs.k8s.io/metrics-server now requires this dependency in order to resolve, even though we do not use the scraper package.
go<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>reading k8s.io/kubernetes/pkg/kubelet/apis/stats/v1alpha1/pkg/kubelet/apis/stats/v1alpha1/go.mod at revision pkg/kubelet/apis/stats/v1alpha1/v0.0.0: unknown revision pkg/kubelet/apis/stats/v1alpha1/v0.0.0

@s-urbaniak

lgtm :+1:


appIcon uploaded

Fixed static/appIcon does not exist failure for AppInspect

Version 1.9.4: Fixed static/appIcon does not exist failure for AppInspect (for Splunk Cloud only)


FastCamelContext cannot be restarted after stop

In a CQ application if you do:
context.stop();
context.start();

Then you get:
java.lang.UnsupportedOperationException
	at org.apache.camel.quarkus.core.FastCamelContext.createRegistry(FastCamelContext.java:84)
	at org.apache.camel.impl.engine.AbstractCamelContext.getRegistry(AbstractCamelContext.java:2100)
	at org.apache.camel.impl.engine.AbstractCamelContext.doStartStandardServices(AbstractCamelContext.java:3808)
	at org.apache.camel.impl.engine.AbstractCamelContext.forceLazyInitialization(AbstractCamelContext.java:3773)
	at org.apache.camel.impl.engine.AbstractCamelContext.doInit(AbstractCamelContext.java:2849)
	at org.apache.camel.quarkus.core.FastCamelContext.doInit(FastCamelContext.java:172)
	at org.apache.camel.support.service.BaseService.init(BaseService.java:83)
	at org.apache.camel.impl.engine.AbstractCamelContext.init(AbstractCamelContext.java:2620)
	at org.apache.camel.support.service.BaseService.start(BaseService.java:111)
	at org.apache.camel.impl.engine.AbstractCamelContext.start(AbstractCamelContext.java:2639)
	at org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:255)

In general, it's not considered good practice to stop the CamelContext and start it again. But with CQ, it's not trivial to support, given that parts of the CamelContext are configured at build time, and there's no possibility of repeating those steps at runtime.
Should we detect the restart scenario and throw a friendlier exception? Or is there something else that could be done?

Yeah, I agree we should at least output a better exception on the second start.

+1 on throwing an Exception


pbr 1.0 breaks pyrax

Yesterday (March 18) pbr 1.0 was released. When doing a normal pip install pyrax with latest pip 6.1.1 it installs 1.0 which is conflicting with pyrax underlying libraries like 'oslo.i18n', 'python-keystoneclient', 'oslo.serialization', 'oslo.utils'.
Full error log we got on our system with a new virtualenv today:
Traceback (most recent call last):
  File "app_context_rqworker.py", line 25, in <module>
    app = create_app(run_as_server=False)
  File "/home/pybossa/pybossa/pybossa/core.py", line 39, in create_app
    setup_uploader(app)
  File "/home/pybossa/pybossa/pybossa/core.py", line 109, in setup_uploader
    uploader.init_app(app)
  File "/home/pybossa/pybossa/pybossa/uploader/rackspace.py", line 49, in init_app
    region=app.config['RACKSPACE_REGION'])
  File "/home/pybossa/pybossa/env/local/lib/python2.7/site-packages/pyrax/__init__.py", line 438, in _wrapped
    return fnc(*args, **kwargs)
  File "/home/pybossa/pybossa/env/local/lib/python2.7/site-packages/pyrax/__init__.py", line 504, in set_credentials
    connect_to_services(region=region)
  File "/home/pybossa/pybossa/env/local/lib/python2.7/site-packages/pyrax/__init__.py", line 626, in connect_to_services
    cloudservers = connect_to_cloudservers(region=region)
  File "/home/pybossa/pybossa/env/local/lib/python2.7/site-packages/pyrax/__init__.py", line 662, in connect_to_cloudservers
    _cs_auth_plugin.discover_auth_systems()
  File "/home/pybossa/pybossa/env/local/lib/python2.7/site-packages/novaclient/auth_plugin.py", line 40, in discover_auth_systems
    auth_plugin = ep.load()
  File "/home/pybossa/pybossa/env/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2344, in load
    self.require(*args, **kwargs)
  File "/home/pybossa/pybossa/env/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2361, in require
    items = working_set.resolve(reqs, env, installer)
  File "/home/pybossa/pybossa/env/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line 838, in resolve
    raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (pbr 1.0.0 (/home/pybossa/pybossa/env/lib/python2.7/site-packages), Requirement.parse('pbr!=0.7,<1.0,>=0.6'), set(['oslo.i18n', 'python-keystoneclient', 'oslo.serialization', 'oslo.utils']))

We had to pin pbr to a version like 0.11 which is below <1.0 to keep pyrax running.

This is not pyrax itself, but several of its dependencies.  The following outlines the version requirements and the packages that specify the version:
ContextualVersionConflict: (pbr 1.0.0 (/home/pybossa/pybossa/env/lib/python2.7/site-packages), Requirement.parse('pbr!=0.7,<1.0,>=0.6'), set(['oslo.i18n', 'python-keystoneclient', 'oslo.serialization', 'oslo.utils']))

no but it is serious problem for pyrax. I already tried to make a PR for a two line change in openstack/python-novaclient but they want me to sign a contributor agreement and get used to gerrit which is a littlebit much for a two lines change IMHO. Either you pin a version range in your library or somebody else may contribute that  changes to python-novaclient or the oslo libraries. It's a shame that a simple 1.0 change can break so much stuff.

We have the same issue. Only now it's pbr 1.0.1. Things were fine for weeks. Deployed tonight, have this issue popping up.
Does pinning pbr to 0.11 actually provide a usable work-around here?

@petersanchez yes pinning the version to the last version 0.11.0 before 1.0 is exactly what we have done at PyBossa to keep pyrax working. https://github.com/PyBossa/pybossa/commit/73179e71cd1ba62fa902ed5272cc2b961403f907

I've submitted a bug report upstream to python-novaclient at https://bugs.launchpad.net/python-novaclient/+bug/1457100

FWIW, there were several upstream issues with pbr 1.0, too: http://lists.openstack.org/pipermail/openstack-dev/2015-May/064362.html

I was confounded by the OpenStack git repo until I found the GitHub mirror. Sharing my code snip for checkout and install of the 0.11.0 version:
$ git clone git@github.com:openstack-dev/pbr.git
$ cd pbr
$ git checkout tags/0.11.0
$ python2.7 setup.py install

Thanks @dandye, the code snippet you shared sorted the problem for me perfectly!

An easy solution via pip is to just pip install -I pbr==0.11.0  Additionally, based on testing, something like the following works too:  pip install -U oslo.utils as oslo.utils will cause pbr 0.11.0 to be installed.
I'm still following up with the python-novaclient project to see about getting this fixed.  The error is actually triggered when you have a novaclient extension installed, causing pbr to trigger a dependency check.

A commit[1] has just been merged into python-novaclient that addresses the issue.  A release has not been cut yet.  I will follow up once a new release of python-novaclient has been released with this fix.
[1] https://bugs.launchpad.net/python-novaclient/+bug/1457100/comments/9

As of about 30 minutes ago, python-novaclient 2.26.0 was released that includes the fix for this issue.  As such I am closing this issue.


Forum messages are slow to update, especially compared to Legacy

I've been using the FSM MSP Working Group forum this morning and updates are slow to appear on my screen. I don't think this is an issue with latency in the network. Is there a way to speed up forum updates?

There are no real time updates at this point. Best to refresh the browser.

But they do appear eventually with refreshing. I’ll let them know that they should refresh. --Will McClintockNational Center for Ecological Analysis and SynthesisUniversity of California Santa Barbara, CA 93101On Jan 24, 2023, at 12:31 PM, Chad Burt @.***> wrote:
There are no real time updates at this point. Best to refresh the browser.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

The topic list gets refreshed every 40 seconds, but it's polling-based rather than responding to actual activity. It's not a huge lift to add realtime updates but it's just not there yet.

Realtime updates tasks

[ ] Add subscription support to graphql server

[ ] new posts
[ ] new topics
[ ] updates to forum and topic stats

[ ] show new posts immediately in open topic
[ ] update topic list immediately
[ ] update forum and topic post counts


Undelivered Email

hello, I have a question for you.
We provide a software for cinemas which also involve tickets sale.
Many times customers enter a wrong e-mail address and as consequence we receive a mail from<EMAIL_ADDRESS>with title "Undelivered Mail Returned to Sender" and as attach the e-mail that the customer hasn't received.
As this attach also contains the cinema e-mail I would like to redirect those e-mails to the relatives cinemas and theaters.
Can you guide me through the steps to deploy this?
I couldn't find any tips about this subject on your Knowledgebase, neither on GitHub.
Thank you
https://sendgrid.com/docs/Glossary/undelivered_email.html

Hello @francesco1119,Thanks for your suggestion or question! In an attempt to clear out our backlog,                                              we are closing out issues over 90 days old.                                             If this is still an issue, please feel free to reopen it.                                             Team SendGrid DX-Docs


Update share-append-only-databases-with-hyperbee.md

Updated link to dict.json the pears documentation.

Thank you for the PR, issue solved in https://github.com/holepunchto/pear-desktop/pull/52


Merge sparse LU into develop

There seems to be a formatting issue? Perhaps something got changed in the merge.

There seems to be a formatting issue? Perhaps something got changed in the merge.

Not sure why, but my local pre-commit script no longer seems to be generating the same format expected by the CI.

Not sure why, but my local pre-commit script no longer seems to be generating the same format expected by the CI.

The CI expects clang-format from ROCm 4.3, but the hipSOLVER script uses whatever version happens to be installed. We could port over the script from rocSOLVER, as --get-clang-format will download the specific version required by the CI.


chore: Ignore .idea directory from git

Why do you ignore package.lock.json ?

Codecov Report

Merging #64 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #64   +/-   ##
=======================================
  Coverage   99.37%   99.37%
=======================================
  Files          14       14
  Lines         318      318
=======================================
  Hits          316      316
  Misses          2        2

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d4b69d7...719f49f. Read the comment docs.

@ert78gb I understand this is a tiny change but I don't think it's desirable to start adding lots of editor-specific files to the main .gitignore. Developers are free to add these in for their own configuration locally.
I'm not sure why package.lock.json is in there.

ok I accept it.

could I add .nvmrc file to the repo or is it same user settings?

Same as above I'm afraid.


configure: error: cannot run C compiled programs.

From @sahil912 on November 2, 2016 11:54
I am following this issue after upgrading to MacOS Seirra
brew config gives me the following details:

HOMEBREW_VERSION: 1.0.9-20-gf14a3a1
ORIGIN: https://github.com/Homebrew/brew.git
HEAD: f14a3a17decdcfd26fc9f2dc0958ee642241ea5a
Last commit: 17 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 0d689da84064b9ef99f766858a87fd22c8305488
Core tap last commit: 86 minutes ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_REPOSITORY: /usr/local/Homebrew
HOMEBREW_CELLAR: /usr/local/Cellar
HOMEBREW_BOTTLE_DOMAIN: https://homebrew.bintray.com
CPU: octa-core 64-bit haswell
Homebrew Ruby: 2.0.0-p648
Clang: 8.0 build 800
Git: 2.9.3 => /Applications/Xcode.app/Contents/Developer/usr/bin/git
Perl: /usr/bin/perl
Python: /usr/bin/python
Ruby: /Users/jsahil/.rvm/rubies/ruby-2.2.0/bin/ruby
Java: 1.8.0_25
macOS: 10.12-x86_64
Xcode: 8.1
CLT: <IP_ADDRESS>.1.1472435881
X11: N/A
MacPorts/Fink: /opt/local/bin/port

Could please help? How do I resolve this issue,
Copied from original issue: Homebrew/legacy-homebrew#50697

Sorry but you have not followed the requested steps on the Troubleshooting page
Please follow (all of) these steps and post the information here so we can help you with your problem.
Thanks!

Closing due to no response.

I have the same issue with latest Xcode 8.1 on Sierra. In my case I was cross-compiling protobuf for x86_64 iOS Simulator. All other architectures compiled fine however.
I have followed all of the troubleshooting, updated and upgraded brew, etc.
I reproduced the issue on two Macs (both on Sierra). The issue can be reproduced by using the protobuf build script from here: https://gist.github.com/palplus/5847a2ee0d4372926ea0
git clone https://gist.github.com/5847a2ee0d4372926ea0.git protobuild
cd protobuild
./build-protobuf.sh
You can turn off other targets in the build scripts to shorten build time, though you'll notice that all targets but x84_64 simulator build fine.
The build script was working for me previously. I think the only thing that changed on my syste, was an update to xcode, though I can't say for sure unfortunately (not unlikely that I built previous to upgradin to Sierra).

You don't seem to reference a Homebrew installation at all?

The same problem here! ✋

Try running xcode-select --install. This generally solves the "cannot run C compiled programs" error.

My problem was with capybara-webkit ruby gem, I fixed it from official documentation here


Can't create gateway for routed IPSEC on 20.1.x

Describe the bug
On OPNsense 20.1.4 when creating a routed IPSEC following the official documentation I can not create the gateway with the remote tunnel IP.
It says : "The following input errors were detected: Cannot add IPv4 Gateway Address because no IPv4 address could be found on the interface."
The issue doens't occur on OPNsense 20.1.3.
To Reproduce
Steps to reproduce the behavior:

Fresh 20.1 install (on VMware VM)
Update to 20.1.4
Create the IPSEC tunnel following documentation
Get stuck when manually creating the gateway

Expected behavior
Manually creating the gateway is mandatory for adding the proper routes.
Screenshots
N/A
Relevant log files
N/A
Additional context
Setting up a new OPNsense VM (20.1 -> 20.1.4) connecting via IPSEC to an existing one (20.1.3)
I reverted my new box from 20.1.4 back to 20.1 (VM snapshot) and I could mount the tunnel without issue.
Environment
OPNsense 20.1.4 (amd64, OpenSSL).

I can't see anything related to https://docs.opnsense.org/releases/20.1.html?highlight=release notes#april-08-2020 that would cause this. It likely wasn't 20.1.4.
You can always check by issuing:
# opnsense-revert -r 20.1.3 opnsense

Cheers,
Franco

Reverting to 20.1.3, 20.1.2, 20.1.1, 20.1 gives me the same error when editing the gateway.
I'm not sure if I was supposed to reboot each time (I did after reverting to 20.1)
What else could I check ?

I think I found a clue having a quick look at the code.
I guess the tunnel has to be up from an IPSEC point of view, so that the IPSEC interface will get it's VTI IP, before one can add/edit a gateway on top of the tunnel.
Can you confirm it ?
If so then a slight improvement could be to add to the error message stated above something like "If you are editing an IPSEC VTI gateway, make sure the tunnel (SA) is up", and also mention it in the documentation.
Thank you.

Tested again and confirmed it.
IPSEC tunnel has to be UP first (although you can't confirm that with a ping for example since routes and gateways are not set yet).

This is still hindering setup of routed IPsec VPNs as documented in https://docs.opnsense.org/manual/how-tos/ipsec-s2s-route.html.
I think it is an error/bug to hold up the configuration because of runtime status of the tunnel.
Moreover I don't see a workaround documented herein. IMO this bug should remain open,

But if you strictly follow the Docs it works? For me it was not reproduceable.

Hi,
I have put some time into this as I probably see the same problem, and I can reproduce it.
The result is that the created ipsec interface doesn't have an IP address, and then you can't create a gw.
I have observed that it depends only on the IP addresses specified in phase2.
The problem is related to the 'distance' between the two point-to-point addresses (tunnel_local, tunnel_remote); it looks like they can not be more than 31 apart.
examples:
remote       -  local
----------------------------------------------
<IP_ADDRESS>  - up to <IP_ADDRESS> works
<IP_ADDRESS>  - <IP_ADDRESS> doesn't work (ifconfig ipsec<n> has no 'inet' line)
<IP_ADDRESS> - up to <IP_ADDRESS> works
<IP_ADDRESS> - <IP_ADDRESS> doesn't work
<IP_ADDRESS> - <IP_ADDRESS> works (not in the same /27)
<IP_ADDRESS> - <IP_ADDRESS> doesn't work
<IP_ADDRESS> - <IP_ADDRESS> works (not in the same /27)

reproduce by editing phase2, save. apply and test with ifconfig ipsec
I have upgraded to 21.1.8.
Thanks

I have encountered the same problem.
The behaviour was exactly as described by GaardenZwerch.
I have OPNsense 21.7.1-amd64 in use.

I dont get it, this is Point to Point, if you use <IP_ADDRESS> and .2 like in the docs it works, correct?

I dont get it, this is Point to Point, if you use <IP_ADDRESS> and .2 like in the docs it works, correct?

It's not point-to-point, it's a link network. If, luckily, you use the usual, a /30 link network, then it will work, because it calculates the mask by

mask = 31 - (IPA - IPB)
however, if the difference is greater than 1, the result doesn't make any sense, and if it's greater than 31, it starts to be actively incorrect / not allowed.

In any case, the user should be able to select the mask manually, if only so that he realizes it's not actually P-t-P but a link network.

arrrg.
I am having this exact problem, seems like.
I suppose I should mention that both sides are behind NAT.
If I just set the "remote side" and "local side" to what I would normally set the remote id and local id to (ie: the public IPs used by the NAT) then the connection happens... but I cant then make a gateway.
If I instead use made-up names like the sample <IP_ADDRESS> .. it doesnt work.. because auth fails.
(I should mention that one side is not OPNsense but a meraki router)

What gets me is that the OTHER side seems to understand the situation just fine. It figures out that it can route packages through the link just fine with the "tunnel remote address" and local address being the remote and local ids of the two routers involved.
So pings make it all the way through to a machine behind the opnsense box. But opensense, doesnt have the sense to return the ICMP reply .

Wait.. why is this closed? Its still a bug? !!
Please reopen this issue.

What exactly is the issue and where does it happen? Jumping into a closed ticket with no template data is unhelpful. The netmask issue referenced by @bimbar in September was fixed in a 21.7.x release. Next is your „me too“ so I’m having a hard time understanding.

Ah.
well i was having exactly the same issue, so didnt think it neccessary to repeat the info.
The ticket seems to be closed with no justification. It's great to know it was fixed.
In this kind of situation, on other github projects, I'm used to seeing some kind of "closed, fixed in X.Y,Z" marker.

No version info, no steps to reproduce. I’m locking this thread in the hope you will open a ticket with the necessary data.


Was not able to do so and so

Preliminary checklist

[ ] I have searched the existing issues and confirm this issue has not been reported before.
[ ] I give permission for members of the PropMan team to access and test my project for the sole purpose of investigating this issue.

Current Behavior
This is dummy text

Expected Behavior
This is dummy text

Steps to Reproduce
This is dummy text

Environment
This is dummy text

Additional Context and Visual Documentation
This is dummy text

Bug Report Code (Required)
This is dummy text

Thanks will look into it.

df


updated params fields

Updated the playbook's parameters to use Azure Sentinel's log analytics workspace name and rg.
Fixes #
Proposed Changes

I think you have the default playbook name wrong in the arm template
"PlaybookName": {
"defaultValue": "Close-Incident-ASCAlert",
"type": "String"
},


Add customize_event on instance feature

I like this. 👍
BTW, LogStashLogger still targets Ruby 1.9, which doesn't support keyword arguments.

Codecov Report

Merging #113 into master will increase coverage by 0.05%.
The diff coverage is 94.44%.

@@            Coverage Diff             @@
##           master     #113      +/-   ##
==========================================
+ Coverage   91.49%   91.54%   +0.05%
==========================================
  Files          61       61
  Lines        1469     1479      +10
==========================================
+ Hits         1344     1354      +10
  Misses        125      125

Impacted Files
Coverage Δ

lib/logstash-logger/formatter.rb
96.87% <100%> (ø)
:white_check_mark:

lib/logstash-logger/logger.rb
85.96% <100%> (ø)
:white_check_mark:

spec/logger_spec.rb
100% <100%> (ø)
:white_check_mark:

lib/logstash-logger/formatter/base.rb
94.11% <80%> (-2.44%)
:x:

lib/logstash-logger/silenced_logging.rb
94.44% <0%> (+2.55%)
:white_check_mark:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 058dd28...fae99d5. Read the comment docs.

@CoolElvis I recently decided to drop support for Ruby < 2.2. And I liked the way you previously had it with keyword arguments. So I cherry picked your previous commit into master. This feature will go out in the next release. Thanks!

This has been released in 0.25.0. Thanks for the contribution!


added error handling functionality that is available in the original …

…fitnesse repo. When an exception with 'StopTest' contained in the exception name the running test will fail and all other tests will abort

@weswilliams I've added fitnesse stoptest error handler functionality with this PR. Can you review it and merge if happy?

Hi @bbmcguinness it looks ok, I will need to get this setup on my new computer. Were you able to run the ant or maven tests?

@weswilliams Maven tests all pass :)