NormSohl from OPS portal: Merge from master to live

:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:warning:Warning

Details

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

Details

msteams-platform/concepts/Cards/cards-reference.md
:warning:Warning

Details

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

Details

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

Details

msteams-platform/concepts/bots/bot-conversations/bots-cards.md
:warning:Warning

Details

msteams-platform/concepts/bots/bot-conversations/bots-conv-channel.md
:warning:Warning

Details

msteams-platform/concepts/bots/bot-conversations/bots-conv-personal.md
:warning:Warning

Details

msteams-platform/concepts/bots/bot-conversations/bots-conv-proactive.md
:warning:Warning

Details

msteams-platform/concepts/bots/bot-conversations/bots-conversations.md
:warning:Warning

Details

msteams-platform/concepts/bots/bot-conversations/bots-message-format.md
:warning:Warning

Details

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

Details

msteams-platform/concepts/bots/bots-notifications.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/bots/bots-text-formats.md
:warning:Warning

Details

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

Details

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

Details

msteams-platform/concepts/connectors.md
:warning:Warning

Details

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

Details

msteams-platform/concepts/tabs/tabs-configuration.md
:warning:Warning

Details

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

Details

msteams-platform/concepts/tabs/tabs-update-remove.md
:warning:Warning

Details

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

Details

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

Details

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

Details

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

Details

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

Details

msteams-platform/scenarios/scenarios.md
:warning:Warning

Details

msteams-platform/troubleshoot/troubleshoot.md
:warning:Warning

Details

msteams-platform/concepts/bots/bots-cards.md
:white_check_mark:Succeeded

msteams-platform/concepts/cards/cards-format.md
:white_check_mark:Succeeded

msteams-platform/concepts/outgoingwebhook.md
:white_check_mark:Succeeded

msteams-platform/includes/bots/message-format-cards.html
:white_check_mark:Succeeded

msteams-platform/redirects/bots1on1.md
:white_check_mark:Succeeded

msteams-platform/redirects/botsconversation.md
:white_check_mark:Succeeded

msteams-platform/redirects/botsinchannels.md
:white_check_mark:Succeeded

msteams-platform/scenarios/bots-channel-conversation.md
:white_check_mark:Succeeded

msteams-platform/scenarios/bots-personal-conversation.md
:white_check_mark:Succeeded

msteams-platform/scenarios/bots-personal-conversations.md
:white_check_mark:Succeeded

msteams-platform/TOC.yml

[Warning] Invalid file link:(~/resources/dev-preview/developer-preview-intro).
[Warning] Invalid file link:(~/concepts/authentication/auth-silent-AAD).
[Warning] Invalid file link:(~/resources/design/framework/search).
[Warning] Invalid file link:(~/resources/resource-overview).
[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/cards/cards).
[Warning] Invalid file link:(~/concepts/bots/bots-overview).
[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:(~/scenarios/scenarios).
[Warning] Invalid file link:(~/resources/design/framework/apps).
[Warning] Invalid file link:(~/concepts/outgoingwebhook).
[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/bots/bot-conversations/bots-conv-proactive).
[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:(~/concepts/apps/apps-package).
[Warning] Invalid file link:(~/concepts/authentication/auth-tab-AAD).
[Warning] Invalid file link:(~/get-started/get-started-tenant).
[Warning] Invalid file link:(~/resources/design/overview).
[Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-personal).
[Warning] Invalid file link:(~/resources/design/framework/cards).
[Warning] Invalid file link:(~/resources/design/framework/tabs).
[Warning] Invalid file link:(~/resources/dev-preview/developer-preview).
[Warning] Invalid file link:(~/resources/design/framework/bots).
[Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-channel).
[Warning] Invalid file link:(~/concepts/authentication/auth-bot-AAD).
[Warning] Invalid file link:(~/concepts/concepts-overview).
[Warning] Invalid file link:(~/troubleshoot/faq).
[Warning] Invalid file link:(~/concepts/tabs/tabs-update-remove).
[Warning] Invalid file link:(~/concepts/bots/bots-menus).
[Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-cards).
[Warning] Invalid file link:(~/get-started/get-started).
[Warning] Invalid file link:(~/concepts/bots/bots-create).
[Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-message-format).
[Warning] Invalid file link:(~/concepts/authentication/auth-configure).
[Warning] Invalid file link:(~/concepts/authentication/auth-flow-bot).
[Warning] Invalid file link:(~/get-started/get-started-nodejs).
[Warning] Invalid file link:(~/resources/design/components/fields).
[Warning] Invalid file link:(~/resources/design/framework/activity-feed).
[Warning] Invalid file link:(~/resources/design/framework/messaging-extensions).
[Warning] Invalid file link:(~/concepts/cards/cards-format).
[Warning] Invalid file link:(~/concepts/bots/bots-with-tabs).
[Warning] Invalid file link:(~/publishing/apps-publish).
[Warning] Invalid file link:(~/concepts/authentication/auth-flow-tab).
[Warning] Invalid file link:(~/resources/dev-preview/developer-preview-features).
[Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conversations).
[Warning] Invalid file link:(~/get-started/app-studio-component-library).
[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:(~/concepts/deep-links).
[Warning] Invalid file link:(~/resources/design/components/buttons).
[Warning] Invalid file link:(~/concepts/authentication/authentication).
[Warning] Invalid file link:(~/resources/design/components/dialogs).
[Warning] Invalid file link:(~/resources/general/requirements).
[Warning] Invalid file link:(~/concepts/cards/cards-reference).
[Warning] Invalid file link:(~/publishing/office-store-checklist).
[Warning] Invalid file link:(~/concepts/cards/cards-actions).
[Warning] Invalid file link:(~/concepts/messaging-extensions).
[Warning] Invalid file link:(~/.general/general-overview).
[Warning] Invalid file link:(~/overview).
[Warning] Invalid file link:(~/resources/design/components/themes).
[Warning] Invalid file link:(~/resources/general/debug).
[Warning] Invalid file link:(~/get-started/get-started-app-studio).
[Warning] Invalid file link:(~/get-started/get-started-dotnet).
[Warning] Invalid file link:(~/feedback).
[Warning] Invalid file link:(~/troubleshoot/troubleshoot).
[Warning] Invalid file link:(~/get-started/get-started-dotnet-in-azure).
[Warning] Invalid file link:(~/concepts/tabs/tabs-static).
[Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
[Warning] Invalid file link:(~/concepts/apps/apps-upload).
[Warning] Invalid file link:(~/concepts/bots/bots-context).

msteams-platform/concepts/Cards/cards-actions.md

Line 210: [Warning] Invalid file link:(~/concepts/authentication/auth-flow-bot).

msteams-platform/concepts/Cards/cards-reference.md

Line 41: [Warning] Invalid file link:(~/concepts/cards/cards-actions).
Line 45: [Warning] Invalid file link:(~/concepts/cards/cards-format).
Line 70: [Warning] Invalid file link:(~/concepts/cards/cards-format).
Line 219: [Warning] Invalid file link:(~/concepts/cards/cards-format).
Line 233: [Warning] Invalid file link:(~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk).
Line 319: [Warning] Invalid file link:(~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk).
Line 377: [Warning] Invalid file link:(~/concepts/authentication/auth-flow-bot).
Line 406: [Warning] Invalid file link:(~/concepts/cards/cards-format).

msteams-platform/concepts/Cards/cards.md

Line 9: [Warning] Invalid file link:(~/concepts/cards/cards-actions).
Line 19: [Warning] Invalid file link:(~/concepts/connectors).
Line 21: [Warning] Invalid file link:(~/concepts/connectors#access-existing-office-365-connectors-from-microsoft-teams).
Line 27: [Warning] Invalid file link:(~/concepts/cards/cards-reference).
Line 31: [Warning] Invalid file link:(~/concepts/cards/cards-reference).
Line 31: [Warning] Invalid file link:(~/concepts/messaging-extensions).
Line 35: [Warning] Invalid file link:(~/concepts/cards/cards-reference).

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

Line 19: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 20: [Warning] Invalid file link:(~/concepts/bots/bots-overview).
Line 21: [Warning] Invalid file link:(~/concepts/compose-extensions).
Line 29: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 30: [Warning] Invalid file link:(~/concepts/bots/bots-overview).
Line 30: [Warning] Invalid file link:(~/concepts/compose-extensions).
Line 31: [Warning] Invalid file link:(~/concepts/connectors).
Line 32: [Warning] Invalid file link:(~/concepts/compose-extensions).
Line 33: [Warning] Invalid file link:(~/concepts/custom-bot).

msteams-platform/concepts/bots/bot-conversations/bots-cards.md

Line 9: [Warning] Invalid file link:(~/concepts/cards/cards).
Line 11: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conversations).
Line 13: [Warning] Invalid file link:(~/concepts/cards/cards-reference).
Line 15: [Warning] Invalid file link:(~/concepts/cards/cards-actions).

msteams-platform/concepts/bots/bot-conversations/bots-conv-channel.md

Line 22: [Warning] Invalid file link:(~/concepts/apps/apps-overview).
Line 30: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conversations#teams-channel-data).
Line 45: [Warning] Invalid file link:(~/concepts/bots/bots-notifications#team-member-or-bot-addition).
Line 47: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-personal#starting-a-11-conversation).
Line 47: [Warning] Invalid file link:(~/concepts/bots/bots-context#fetching-the-team-roster).
Line 56: [Warning] Invalid file link:(~/resources/design/overview).
Line 112: [Warning] Invalid file link:(~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk).
Line 194: [Warning] Invalid file link:(~/concepts/bots/bots-context).

msteams-platform/concepts/bots/bot-conversations/bots-conv-personal.md

Line 9: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-channel).
Line 11: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-channel).
Line 27: [Warning] Invalid file link:(~/resources/design/overview).

msteams-platform/concepts/bots/bot-conversations/bots-conv-proactive.md

Line 21: [Warning] Invalid file link:(~/concepts/bots/bots-notifications#team-member-or-bot-addition).
Line 21: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-channel).
Line 21: [Warning] Invalid file link:(~/concepts/bots/bots-context#fetching-the-team-roster).

msteams-platform/concepts/bots/bot-conversations/bots-conversations.md

Line 17: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-channel).
Line 18: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-personal).
Line 24: [Warning] Invalid file link:(~/resources/schema/manifest-schema).
Line 38: [Warning] Invalid file link:(~/concepts/bots/bots-notifications).
Line 52: [Warning] Invalid file link:(~/concepts/cards/cards-reference).
Line 60: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-message-format).
Line 63: [Warning] Invalid file link:(~/concepts/bots/bots-text-formats).
Line 65: [Warning] Invalid file link:(~/concepts/cards/cards-format).
Line 85: [Warning] Invalid file link:(~/concepts/bots/bots-notifications#channel-updates).
Line 145: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-channel#mentions).
Line 155: [Warning] Invalid file link:(~/concepts/bots/bots-notifications#channel-updates).
Line 159: [Warning] Invalid file link:(~/concepts/bots/bots-notifications#team-name-updates).
Line 162: [Warning] Invalid file link:(~/concepts/bots/bots-notifications#channel-updates).
Line 199: [Warning] Invalid file link:(~/concepts/cards-actions).
Line 270: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-proactive#starting-11-conversations).
Line 271: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-proactive#creating-a-channel-conversation).
Line 273: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-proactive).

msteams-platform/concepts/bots/bot-conversations/bots-message-format.md

Line 48: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conversations#cards).
Line 72: [Warning] Invalid file link:(~/concepts/cards/cards-format).

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

Line 11: [Warning] Invalid file link:(~/get-started/get-started-nodejs).
Line 17: [Warning] Invalid file link:(~/get-started/get-started-app-studio).
Line 33: [Warning] Invalid file link:(~/resources/general/debug).
Line 37: [Warning] Invalid file link:(~/concepts/apps/apps-package).
Line 37: [Warning] Invalid file link:(~/concepts/apps/apps-upload).
Line 38: [Warning] Invalid file link:(~/concepts/apps/apps-overview#map-your-scenario-to-teams-capabilities).
Line 38: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 39: [Warning] Invalid file link:(~/publishing/apps-publish).

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

Line 17: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conversations).
Line 25: [Warning] Invalid file link:(~/concepts/bots/bots-notifications#team-member-or-bot-addition).
Line 26: [Warning] Invalid file link:(~/concepts/bots/bots-notifications#team-member-or-bot-removed).
Line 27: [Warning] Invalid file link:(~/concepts/bots/bots-notifications#team-name-updates).
Line 28: [Warning] Invalid file link:(~/concepts/bots/bots-notifications#channel-updates).
Line 29: [Warning] Invalid file link:(~/concepts/bots/bots-notifications#channel-updates).
Line 30: [Warning] Invalid file link:(~/concepts/bots/bots-notifications#channel-updates).
Line 31: [Warning] Invalid file link:(~/concepts/bots/bots-notifications#reactions).
Line 32: [Warning] Invalid file link:(~/concepts/bots/bots-notifications#reactions).
Line 44: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-channel#best-practice-welcome-messages-in-teams).
Line 126: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-personal#best-practice-welcome-messages-in-11-conversations).

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

Line 14: [Warning] Invalid file link:(~/concepts/outgoingwebhook).
Line 20: [Warning] Invalid file link:(~/references/resources/schema/manifest-schema).
Line 35: [Warning] Invalid file link:(~/references/resources/schema/manifest-schema).
Line 42: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 61: [Warning] Invalid file link:(~/get-started/get-started-app-studio).
Line 65: [Warning] Invalid file link:(~/concepts/outgoingwebhook).
Line 71: [Warning] Invalid file link:(~/get-started/get-started-nodejs).
Line 72: [Warning] Invalid file link:(~/get-started/design#designing-a-great-bot).
Line 72: [Warning] Invalid file link:(~/concepts/tabs/tabs-static).
Line 72: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 73: [Warning] Invalid file link:(~/concepts/bots/bots-create).
Line 74: [Warning] Invalid file link:(~/concepts/bots/bots-conversations).
Line 74: [Warning] Invalid file link:(~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk).
Line 75: [Warning] Invalid file link:(~/concepts/bots/bots-cards).
Line 76: [Warning] Invalid file link:(~/concepts/bots/bots-notifications).
Line 77: [Warning] Invalid file link:(~/concepts/bots/bots-context).
Line 78: [Warning] Invalid file link:(~/concepts/bots/bots-menus).
Line 79: [Warning] Invalid file link:(~/concepts/bots/bots-with-tabs).
Line 80: [Warning] Invalid file link:(~/concepts/bots/bots-test).
Line 81: [Warning] Invalid file link:(~/publishing/apps-publish).

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

Line 22: [Warning] Invalid file link:(~/concepts/apps/apps-package).
Line 22: [Warning] Invalid file link:(~/concepts/apps/apps-upload).
Line 24: [Warning] Invalid file link:(~/concepts/bots/bots-notifications).
Line 79: [Warning] Invalid file link:(~/publishing/apps-publish).

msteams-platform/concepts/bots/bots-text-formats.md

Line 28: [Warning] Invalid file link:(~/concepts/cards/cards-reference).
Line 49: [Warning] Invalid file link:(~/concepts/bots/bots-conversations#cards).

msteams-platform/concepts/cards-actions.md

Line 12: [Warning] Invalid file link:(~/concepts/cards-actions#hero-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 76: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conversations#message-format).
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).

msteams-platform/concepts/concepts-overview.md

Line 17: [Warning] Invalid file link:(~/concepts/apps/apps-overview).
Line 18: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 19: [Warning] Invalid file link:(~/concepts/bots/bots-overview).
Line 20: [Warning] Invalid file link:(~/concepts/cards/cards).
Line 21: [Warning] Invalid file link:(~/concepts/authentication).
Line 22: [Warning] Invalid file link:(~/concepts/activity-feed).
Line 23: [Warning] Invalid file link:(~/concepts/connectors).
Line 24: [Warning] Invalid file link:(~/concepts/messaging-extensions).
Line 25: [Warning] Invalid file link:(~/concepts/outgoingwebhook).
Line 26: [Warning] Invalid file link:(~/concepts/deep-links).

msteams-platform/concepts/connectors.md

Line 35: [Warning] Invalid file link:(~/concepts/cards/cards).
Line 189: [Warning] Invalid file link:(~/concepts/apps/apps-package).
Line 189: [Warning] Invalid file link:(~/publishing/apps-publish).
Line 189: [Warning] Invalid file link:(~/overview#apps-in-microsoft-teams).
Line 196: [Warning] Invalid file link:(~/publishing/apps-publish).
Line 200: [Warning] Invalid file link:(~/concepts/apps/apps-package#icons).
Line 265: [Warning] Invalid file link:(~/publishing/apps-publish).

msteams-platform/concepts/messaging-extensions.md

Line 26: [Warning] Invalid file link:(~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk).
Line 32: [Warning] Invalid file link:(~/concepts/bots/bots-create).
Line 38: [Warning] Invalid file link:(~/resources/schema/manifest-schema#composeextensions).
Line 137: [Warning] Invalid file link:(~/concepts/apps/apps-upload).
Line 203: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conversations#receiving-messages).
Line 272: [Warning] Invalid file link:(~/concepts/cards-actions).
Line 272: [Warning] Invalid file link:(~/concepts/connectors#using-office-365-connector-cards-in-microsoft-teams).
Line 410: [Warning] Invalid file link:(~/resources/schema/manifest-schema#validdomains).

msteams-platform/concepts/tabs/tabs-configuration.md

Line 9: [Warning] Invalid file link:(~/concepts/apps/apps-package).
Line 80: [Warning] Invalid file link:(~/resources/general/requirements).
Line 90: [Warning] Invalid file link:(~/concepts/tabs/tabs-context).
Line 90: [Warning] Invalid file link:(~/concepts/authentication/authentication).
Line 98: [Warning] Invalid file link:(~/concepts/tabs/tabs-content).
Line 102: [Warning] Invalid file link:(~/concepts/deep-links).
Line 103: [Warning] Invalid file link:(~/concepts/tabs/tabs-content).
Line 103: [Warning] Invalid file link:(~/concepts/tabs/tabs-update-remove).
Line 106: [Warning] Invalid file link:(~/resources/general/cross-domain).
Line 106: [Warning] Invalid file link:(~/resources/schema/manifest-schema).
Line 110: [Warning] Invalid file link:(~/concepts/tabs/tabs-update-remove#removing-a-tab).
Line 122: [Warning] Invalid file link:(~/troubleshoot/troubleshoot).

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

Line 14: [Warning] Invalid file link:(~/references/resources/schema/manifest-schema).
Line 33: [Warning] Invalid file link:(~/concepts/tabs/tabs-configuration).
Line 34: [Warning] Invalid file link:(~/concepts/tabs/tabs-update-remove).
Line 35: [Warning] Invalid file link:(~/concepts/tabs/tabs-content).
Line 36: [Warning] Invalid file link:(~/concepts/tabs/tabs-update-remove#removing-a-tab).
Line 37: [Warning] Invalid file link:(~/concepts/deep-links).
Line 43: [Warning] Invalid file link:(~/concepts/tabs/tabs-static).
Line 44: [Warning] Invalid file link:(~/concepts/tabs/tabs-content).
Line 52: [Warning] Invalid file link:(~/concepts/tabs/tabs-content).
Line 53: [Warning] Invalid file link:(~/concepts/authentication/auth-flow-tab).
Line 54: [Warning] Invalid file link:(~/resources/general/cross-domain).
Line 55: [Warning] Invalid file link:(~/resources/design/components/themes).
Line 58: [Warning] Invalid file link:(~/resources/general/requirements).

msteams-platform/concepts/tabs/tabs-update-remove.md

Line 13: [Warning] Invalid file link:(~/concepts/tabs/tabs-configuration).
Line 13: [Warning] Invalid file link:(~/resources/schema/manifest-schema).
Line 24: [Warning] Invalid file link:(~/concepts/tabs/tabs-configuration).
Line 26: [Warning] Invalid file link:(~/concepts/tabs/tabs-context).
Line 81: [Warning] Invalid file link:(~/resources/general/requirements).
Line 92: [Warning] Invalid file link:(~/concepts/tabs/tabs-context).
Line 92: [Warning] Invalid file link:(~/concepts/authentication/authentication).

msteams-platform/get-started/design.md

Line 10: [Warning] Invalid file link:(~/resources/design/overview).
Line 48: [Warning] Invalid file link:(~/concepts/bots/bots-notifications).

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

Line 15: [Warning] Invalid file link:(~/get-started/get-started-with-nodejs).

msteams-platform/resources/design/framework/messaging-extensions.md

Line 39: [Warning] Invalid file link:(~/concepts/deep-links).

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

Line 10: [Warning] Invalid file link:(~/resources/schema/manifest-schema-migrate).
Line 10: [Warning] Invalid file link:(~/resources/schema/manifest-schema).

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

Line 11: [Warning] Invalid file link:(~/resources/schema/manifest-schema-migrate).
Line 166: [Warning] Invalid file link:(~/concepts/bots/bots-create).
Line 218: [Warning] Invalid file link:(~/concepts/apps/apps-package#icons).
Line 280: [Warning] Invalid file link:(~/concepts/bots/bots-menus).

msteams-platform/scenarios/scenarios.md

Line 15: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-channel).
Line 16: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-personal).
Line 22: [Warning] Invalid file link:(~/feedback).

msteams-platform/troubleshoot/troubleshoot.md

Line 16: [Warning] Invalid file link:(~/resources/schema/manifest-schema#validdomains).
Line 48: [Warning] Invalid file link:(~/concepts/authentication/authentication).
Line 60: [Warning] Invalid file link:(~/get-started/get-started-tenant).
Line 64: [Warning] Invalid file link:(~/concepts/apps/apps-upload).
Line 72: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-channel#mentions).
Line 89: [Warning] Invalid file link:(~/resources/schema/manifest-schema#developer).

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.


Fix condition to create a new db directory

Current create condition has two problems.

When .create(false) is set, cask always tries to create a new db directory.
When .create(true) and directory already exists, cask fails to start due to file already exist error.

This patch fixes these conditions.

Aright, updated.

Thanks 👍.


cannot get accurate position using meter offset in scatterplot

I used the below to plot using METER_OFFSET. Results are quite good until the points are very far from the Origin, where they start moving away from their positions plotted using LNGLAT. Any idea to get it more accurate with the lnglat positions?
class Layer extends ScatterplotLayer {
    constructor(props) {
        super(props)
    }

    calculateInstancePositions(attribute) {
        const { data, getPosition, projectionMode, positionOrigin } = this.props
        const { viewport } = this.context
        const { value } = attribute
        let i = 0
        for (const point of data) {
            let position = getPosition(point)
            if (projectionMode === COORDINATE_SYSTEM.METER_OFFSETS) {
                const lngLatDelta = [
                    position[0] - positionOrigin[0],
                    position[1] - positionOrigin[1]
                ]
                position = viewport.lngLatDeltaToMeters(lngLatDelta)
                if (
                    (lngLatDelta[0] < 0 && position[0] > 0) ||
                    (lngLatDelta[0] > 0 && position[0] < 0)
                ) {
                    position[0] *= -1
                }
                if (
                    (lngLatDelta[1] < 0 && position[1] < 0) ||
                    (lngLatDelta[1] > 0 && position[1] > 0)
                ) {
                    position[1] *= -1
                }
            }
            value[i++] = get(position, 0)
            value[i++] = get(position, 1)
            value[i++] = get(position, 2) || 0
        }
    }
}

Hi @huaruiwu
I'd assume METER_OFFSET will only give you high precision for positions near the center.
If all your coordinates are in LNGLAT, you can try the LATLNG mode and enable fp64.
(if you don't have a lot of points, performance should not be an issue with fp64)

This is expected behavior of the METER_OFFSET mode, as the mercator projection is non-linear. Just curious,  how large an area does your data cover? a few thousand kilometers?

Thanks for the quick response! It's an area of 333,000km2, and over 500,000 points so I cannot use fp64.

333,000km2
~600km * 600km, this is larger than a regular city range.

may I ask if you need to visualize every single point at a low zoom level?
would you consider doing some pre-aggregation / sampling when viewing a larger geo-range, and filtering points out of bound when zooming in to get a closer view?

@huaruiwu In that case, projectionPixelsPerUnit needs to be an attribute. Depending on the distance between the center point, each vertex would need to be projected using a different projectionPixelsPerUnit
Currently, projectionPixelsPerUnit is calculated around the center point and fixed for all points.

@gnavvy I would like to visualize each point at a radius of 1 at low zoom levels.
@shaojingli That makes sense. I will try that and see what happens!

This is a case (huge amount of lng lat points over a wide area) where pre-projecting the points (either in JavaScript or using transform feedback) would make a lot of sense. We don't have support for that mode yet but it would be an interesting addition.

By pre-projecting I mean pre-resolving the flat non-linear mercator projection.

Tried to just add projectionPixelsPerUnit as an attribute but it's difficult to get it working because it also depends on the zoom.

You can also try dividing the area into horizontal strips and render each slice on a scatterplotlayer with its own projection center. The error should be smaller that way.

Just looked at the uniform calculation. We are using the viewport center instead of projection center to calculate the scales. This should be a bug? @ibgreen @shaojingli

It's always been like that... this has been mentioned by @heshan0131 before the launch of v4. I agree that the center for pixelperunit calculation should be the positionOrigin instead of map center

Just looked at the uniform calculation. We are using the viewport center instead of projection center to calculate the scales. This should be a bug?

There are (at least) two aspects to this:

(regardless of projection mode) there is the general idea that we should be able to work in "meters" in shaders - just specifying relative sizes in your geometry in meters.

To do that we need to provide the shaders with a linear meter scale. The "best" linear approximation of a meter we can give at any given time is the linear distance scale of the mercator viewport is the scale at the viewport center.
Changing this would mean the size of a meter would be dependent on whether positionOrigin is supplied or not, and would be increasingly wrong as the user panned away from positionOrigin.

Then there is METER_OFFSETS mode. It is suppose to be used only for small scales where the meter approximation stays correct.

I agree that this mode should benefit from a fixing the meter scale, although it has never been a visible issue in small scale visualizations we do.

Preliminary conclusion, it is either a tradeoff, or we need to pass two meter scales to the shaders.
It is all really complicated. I think it would be really valuable to do a full spec of the project shader module before starting to patch it, or we risk getting into a game of "whack-a-mole" where fixing one bug causes another to pop up on the side.

Changing this would mean the size of a meter would be dependent on whether positionOrigin is supplied or not, and would be increasingly wrong as the user panned away from positionOrigin.

@ibgreen, calculating the size of a meter dependent on positionOrigin sounds like a reasonable approximation. But even so, how to get this value for data provided in lat/lon mode is the problem, we won't have positionOrigin in that mode. I believe it's not a good idea to have lat/lon mode and meter offset mode behave differently with regard to our meters calculation

I believe it's not a good idea to have lat/lon mode and meter offset mode behave differently with regard to our meters calculation

Yes agreed, I share this concern, it would make the system even more complicated and surprising for the user.
Also, I believe that any changes we make here will not help the original issue. If you have data points that are far enough apart the linear distance scale approximation will not work and the question of which center we use is moot. It will be difficult to make a METER_OFFSET solution that works well for larger scales.
I have been playing with a LNGLAT_OFFSETS mode idea for some time that I think could work and provide big performance improvements for this case (it would use 64 bit calculations only for initial offset subtractions, but not for matrix multiplication). Just a matter of finding the time to implement it.
Then we could start recommending the METER_OFFSET mode only for small data sets that are actually specified in meters.

Great ideas. I think a LNGLAT_OFFSETS with good performance would be really useful.

I'm currently abusing the METER_OFFSETS mode in way which may be of interest here. I perform the non-linear part of the projection once in JS to effectively get coordinates on the zoom-0 Mapbox tile. I then use METER_OFFSETS as projection mode with one small change. In the draw call of the layer, I override projectionPixelsPerUnit with a value that only depends on zoom, not position of the viewport.
This is only a few lines as is, but maybe we could turn this into a LINEAR_OFFSETS mode as a feature, with the scale factor passed as a prop. In my case I need to project the points myself anyway, so having access to a direct mode like this would be useful. Maybe I'm missing something and this is also achievable with IDENTITY and web-mercator-viewport.
The modified non-linear projection code: (from web-mercator-viewport)
const PI = Math.PI
const PI_4 = PI / 4
const DEGREES_TO_RADIANS = PI / 180

export default function projectFlatUnscaled(lng, lat) {
  const lambda2 = lng * DEGREES_TO_RADIANS
  const phi2 = lat * DEGREES_TO_RADIANS
  const x = (lambda2 + PI) / (2 * PI)
  const y = (PI - Math.log(Math.tan(PI_4 + phi2 * 0.5))) / (2 * PI)
  return [x, y] // This is passed as position to deck.gl layer
}

Uniform override example: (based on point-cloud-layer)
  draw({ uniforms }) {
    const { radiusPixels } = this.props
    const p = uniforms.projectionScale * WORLD_SCALE
    const projectionPixelsPerUnit = [p, p, p]
    this.state.model.render(Object.assign({}, uniforms, {
      radiusPixels,
      projectionPixelsPerUnit,
    }))
  }

Interesting. I haven't had a chance to try this. I just ended up dividing the area into horizontal strips like @Pessimistress suggested

This is only a few lines as is, but maybe we could turn this into a LINEAR_OFFSETS mode as a feature,

@tehwalris  Apologies for slow replies, looks like I missed your remark here at the end of this long issue. Your use is interesting and similar to something I have been thinking about:

Add a COORDINATE_SYSTEM.WEB_MERCATOR_TILE_ZERO mode. It would allow the app to preproject lng/lats in JavaScript to numbers between 0-512. The shader already knows the scale so it could apply it without the app having to modify distance scales.

Implementing this mode is easy. I mainly want to make sure there is a use case for these modes before we add more complexity to the framework.
The main advantage I see would be somewhat faster rendering (no need for vertex shader to reproject lng/lats every frame).
But note that the precision advantages only comes when we use offsets instead of absolute coordinates, so this mode would need to support fp64.
Maybe we would also add a COORDINATE_SYSTEM.WEB_MERCATOR_TILE_ZERO_OFFSETS mode? But that makes things ever more complex to describe...

Only way I found that got around this whole problem was to bin the data. This was not enough though, because WebMercatorViewport uses latitude and longitude to calculate distance scales.
So I had to also add a projectionOrigin prop to WebMercatorViewport.
WebMercatorViewport :
       const distanceScales = calculateDistanceScales({
            latitude: projectionOrigin ? projectionOrigin[1] : latitude,
            longitude: projectionOrigin ? projectionOrigin[0] : longitude,
            scale
        })

Bin data :
                const aoiCenter = turf.center(
                    wellknown(nextProps.selectedAOI.get('boundary_wkt'))
                )
                let bins = {}
                measuredGeometry.features.forEach(f => {
                    const lat = f.geometry.coordinates[1]
                    const key = lat.toFixed(2)
                    if (!bins[key]) {
                        bins[key] = [f]
                    } else {
                        bins[key].push(f)
                    }
                })
                const scatterplotLayers = Object.keys(bins).map(key => {
                    const bin = bins[key]
                    return {
                        id: 'measurements points ' + key,
                        data: bin,
                        opacity: 1,
                        radiusMinPixels: 1,
                        getPosition: d => {
                            return d.geometry.coordinates
                        },
                        getRadius: d => 0.5,
                        getColor: d => [OI_GREEN.r, OI_GREEN.g, OI_GREEN.b],
                        fp64: false,
                        projectionMode: COORDINATE_SYSTEM.METER_OFFSETS,
                        positionOrigin: [
                            aoiCenter.geometry.coordinates[0],
                            Number(key + '5')
                        ]
                    }
                })

@ibgreen

But note that the precision advantages only comes when we use offsets instead of absolute coordinates, so this mode would need to support fp64.

That depends. Preprojecting does reduce "jiggle" for me. It's somewhere between fp32 and fp64 shader quality. As far as I understand, the improvement is because sin/cos then use JS numbers - so better than fp32 shader sin/cos.

Need to evaluate the use case.

Collecting early thoughts on improved projection modes in this RFC


regarding logo

add logo in one folder

Any particular reason you would like to have all logos in one folder?
In the future also please open issues using one of the provided templates.

It will be more organized


SQL reference shows incorrect "Tables" for RPC methods

Now that https://github.com/iasql/iasql-engine/pull/1756 is merged we can close this.


Self-hosted vs. Systemd

Hey @nhlfr! @blixtra pointed me here and I am wondering what the direction of this would be. We've done a lot of systemd/kubernetes in the past although we are slowly moving away from this. So I am happy to share some thoughts about this.
Obviously I don't know much about the scope of this tool so please ignore any false assumptions.
I'll try to list a few options to Integrate with systemd here:

generating the units to run a kubernetes on systemd. using either go binaries or rkt/runc to start container images with kubernetes binaries. using systemd-run to run those units right away.
using systemd-nspawn to start os images on a host that then use kubeadm to create a cluster
using systemd to start a kubelet and then start a self-hosted cluster rendered with something like bootkube. There is not much need to have something else than a kubelet if you go for the self-hosted kubernetes and that is what we do nowadays more or less.

You see I am just guessing and curious. Can you tell me more about your plans? And maybe we can help finding a good direction that is useful for the community.
Also pinging the kubeadm developers in case you haven't talked to them before @errordeveloper @lukemarsden @pires

To me the main question is – what would be the outcome, e.g. are we looking to have a quick way for spinning up test clusters of size N locally (may be even nested) or something else?

Hey @teemow, the goal of this project is exactly what you described in option 2.
We are going to run N systemd-nspawn containers and then use kubeadm to create a kubernetes cluster. I would like to focus mostly on setting up kubernetes both from locally built source code, so this tool is addressed mostly for developers of kubernetes and is going to be an alternative for:

vagrant provider - which is very problematic for developers, doesn't work well on all distros (for me personally, it doesn't work at all...)
https://github.com/sttts/kubernetes-dind-cluster or https://github.com/Mirantis/kubeadm-dind-cluster - in my opinion, Docker isn't a very good tool for simulating a cluster node, since its an application container engine, not an operating system container engine (like systemd-nspawn or lxc); also, the second project isn't fully working ATM

We may try to give a possibility to set up stable versions of k8s (from packages) as well, but the use case for developers is IMO more important ATM.
@errordeveloper Yes, the main reason behind creating this project is that we would like to have a quick way to deploy a kubernetes cluster (from source) and minimize the difference between "deployment on production" and "deployment from code I modified on my laptop".
I'm not sure what do you mean by "nested clusters", for now we want to treat systemd-nspawn containers as nodes, and run Docker daemon inside them to be used by kubernetes.
I will to put the info above (maybe with some details I possibly forgot about) into README/wiki soon.

@nhlfr ack. sounds great! I've used docker in nspawn too and that worked very well for me. The old code is here:

https://github.com/teemow/conair
https://github.com/teemow/conair-coreos

Do you want to keep this issue open as a reminder to add stuff to the readme? Feel free to close otherwise.


MultiplayerPeerExtension Missing _GetPacket and _PutPacket functions.

Tested versions

Reproducible in 4.2

System information
Godot v4.2.stable.mono - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3070 (NVIDIA; <IP_ADDRESS>01) - AMD Ryzen 7 3700X 8-Core Processor (16 Threads)
Issue description
When extending the MultiplayerPeerExtension class in C#, the _GetPacket methods and the _Put Packet Methods are not defined and cannot be overriden.
Steps to reproduce
Extend the MultiplayerPeerExtension
Attempt to override Either the _GetPacket or the _PutPacket methods.
It will not be possible.
Minimal reproduction project (MRP)
public partial class CustomMultiplayerPeer : MultiplayerPeerExtension
{
    public override Error _PutPacket(byte[] buffer) // compilation error, no suitable method to override.
    {
        return Error.Ok;
    }
}

Does the same equivalent GDScript code work?

Does the same equivalent GDScript code work?

yes.

Additionally for the C# version i cannot for the life of me get _GetPacketScript or PutPacketScript to fire even though there are RPC's running.

_put_packet and _get_packet are meant for GDExtensions, and use pointers (they won't work in GDScript either, and C# is likely complaining because you are using the wrong parameters for _put_packet in any case).
Use _put_packet_script and _get_packet_script to implement the functionality via scripting language (i.e. using Variants).


Fixed Linux support.

While trying to use a portion of ffi-stat on a linux box I noticed that a lot of the constants were assumed to be in Hex but they're actually Octal; also the non-data-structure support was absent; and the data structure was missing some tail padding which caused fun memory problems.

Yeah, when I started this project I had no idea what I was doing, haha. Thanks for fixing it!


Fix missing documentation for using Llama_cpp

What kind of change does this PR introduce? Docs update.

Why was this change needed? Explains how to use Llama_cpp as the selected LLM, resolves #466.

Other information: N/A

Sure thing. From the looks of it, they only need to download that model if they haven't run setup.sh and are just editing the env config, right?

Yep, exactly!

Alright, should be up-to-date. Let me know if it makes sense.

@holopin-bot @mnickrogers Thank you!


fix: Redirect to incorrect place after click on collection on navbar

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR type

[x] Bugfix
[ ] Feature
[ ] Refactoring

What's new?

[x] PR closes #4133

Screenshot

[x] My fix has changed something on UI; a screenshot is best to understand changes for others.

pay 30

pay 30

pay 30 usd

pay 30 usd

pay 30 usd
seems webhooks or something is slowing down bot 👀

pay 30 usd
seems webhooks or something is slowing down bot 👀

Hey, I did not put the payment link there. It's a small fix.

By the way, could you pls check this issue?  @yangwao
https://github.com/kodadot/nft-gallery/pull/4048#issuecomment-1276897606

Hey, I did not put the payment link there. It's a small fix.

lmao, I'm going too fast ;D


Want to change the UI of Tic Tac Toe game

Project name
Tic-Tac-Toe
Project link
(Provide project link over here)](https://github.com/khushi-purwar/WebDev-ProjectKart/tree/master/Tic-Tac-Toe
Improvements suggested

Change the Whole UI of tic tac toe game
will add two new cards for win and loss

demo :-

Assigned to u @iamrahulmahato

@gurjeetsinghvirdee The PR is made #1101 .


How to list and use ALSA's plughw: devices (env PA_ALSA_PLUGHW=1 already set)?

Hey everybody, first of all, thank you for the library and the amount of examples!
I wonder, if its possible to use ALSA's plugins to appear in 'list-devices' and to use those in the audiostream callback. Concretely, I'm using a Unix-based setup with ALSA and as cross-plattform audio library libportaudio2 installed via pip. According to PortAudio (which can be found in portaudio/src/hostapi/alsa/pa_linux_alsa.c, l. 1669: static PaError AlsaOpen), you just need to set a variable to list and use the plughw devices. I've set PA_ALSA_PLUGHW=1 it in both the user-based ~/.bashrc and the system-wide /etc/profile configuration files - however, under sounddevice it does not seem to be recognized (it still just shows the hw: devices).
I've also checked that PortAudio is installed in the latest release: dpkg -l |grep portaudio, shows v19.
Sure, it can be an issue with PortAudio, but before I'm going to debug using and compiling the PA code, I wanted to ask you in case someone knows a solution. Btw. PortAudio provides a debug logger - does someone know how to track those, when calling the C++ lib from a python code?

When I tried it (Debian Linux, using Pulse Audio) there was a little change in the device names and in the number of channels:
$ python3 -m sounddevice
   0 HDA Intel PCH: ALC269VC Analog (hw:0,0), ALSA (2 in, 2 out)
   1 HDA Intel PCH: HDMI 0 (hw:0,3), ALSA (0 in, 8 out)
   2 HDA Intel PCH: HDMI 1 (hw:0,7), ALSA (0 in, 8 out)
   3 HDA Intel PCH: HDMI 2 (hw:0,8), ALSA (0 in, 8 out)
   4 HDA Intel PCH: HDMI 3 (hw:0,9), ALSA (0 in, 8 out)
   5 sysdefault, ALSA (128 in, 128 out)
   6 front, ALSA (0 in, 2 out)
   7 surround40, ALSA (0 in, 2 out)
   8 surround51, ALSA (0 in, 2 out)
   9 surround71, ALSA (0 in, 2 out)
  10 hdmi, ALSA (0 in, 8 out)
  11 dmix, ALSA (0 in, 2 out)
* 12 default, ALSA (32 in, 32 out)
  13 /dev/dsp, OSS (16 in, 16 out)
$ export PA_ALSA_PLUGHW=1
$ python3 -m sounddevice
   0 HDA Intel PCH: ALC269VC Analog (plughw:0,0), ALSA (128 in, 128 out)
   1 HDA Intel PCH: HDMI 0 (plughw:0,3), ALSA (0 in, 128 out)
   2 HDA Intel PCH: HDMI 1 (plughw:0,7), ALSA (0 in, 128 out)
   3 HDA Intel PCH: HDMI 2 (plughw:0,8), ALSA (0 in, 128 out)
   4 HDA Intel PCH: HDMI 3 (plughw:0,9), ALSA (0 in, 128 out)
   5 sysdefault, ALSA (128 in, 128 out)
   6 front, ALSA (0 in, 2 out)
   7 surround40, ALSA (0 in, 2 out)
   8 surround51, ALSA (0 in, 2 out)
   9 surround71, ALSA (0 in, 2 out)
  10 hdmi, ALSA (0 in, 8 out)
  11 dmix, ALSA (0 in, 2 out)
* 12 default, ALSA (32 in, 32 out)
  13 /dev/dsp, OSS (16 in, 16 out)

So setting the environment variable definitely has some effect, but I don't know if this helps in your case?
I don't know anything about the debug logger, how would you use it from C++ code?

Very Good!
So the conclusion is,


After auth it throws me to a 404 page

After going through the auth on: http://<IP_ADDRESS>:3456
uname/pass and then putting in the code from my phone....it then throws me to a 404 page:
http://<IP_ADDRESS>:3456/www.amazon.com/404
Going back to node-red it doesn't show auth'ed and wants to repeat steps.
Also: for filepath how can I confirm it has the correct permissions and correct?

For anyone having the issue i had the same and opened a browser session in incognito and that worked.

In fact the real solution is described here: https://github.com/Apollon77/alexa-remote/#issues-when-getting-the-cookie-and-tokens-initially
Such a 404 or other starnge errors during cookie process is caused by old OTP/2FA settings. Update them and all is fine

clearing cookies and switching my amazon to 2FA works.  Issue I am having now is when I click deploy in node-red it wants me to re-auth the account again.  Expected?
BTW When I did the login/2fa on my computer I did CHECK the box that says don't require 2fa on this device (was this right?)
Thanks.

Check which "FA/OTP method is active for your account, if still SMS based then Update to the current one. Then it should work

Thanks!


added is_network_error to error type

The issue wasn't very specific, on what exactly can be considered a network error, so I used this answer as a guideline.
The following errors can occur:

http::Error
hyper::Error
mime::FromStrError
url::ParseError
TlsIncompatible
native_tls::Error
io::Error (for dns)
io::Error (for io)
serde_urlencoded::ser::Error
serde_json::Error
TooManyRedirects
RedirectLoop
Status(StatusCode)
UnknownProxyScheme
Timer
BlockingClientInFutureContext

I narrowed the relevant errors down to

hyper::Error
native_tls::Error
io::Error (for dns)
io::Error (for io)

Because I don't know how you should match (idiomatically) against string errors, that are returned by native_tls::Error and the io::Error,
I only matched hyper::Errors.
closes #560

Sorry for the delay, I've changed the design of the Error struct drastically, I'm not sure it will be as easy to provide this.


Typo in MongoDB and Mongoose - Delete Many Documents with model.remove()

Describe your problem and - if possible - how to reproduce it
There is a typo in the first paragraph of 'MongoDB and Mongoose - Delete Many Documents with model.remove()' challenge page.  In the last sentence 'Pass to it a query ducument ...', 'ducument' should be 'document'.
Add a Link to the page with the problem
https://learn.freecodecamp.org/apis-and-microservices/mongodb-and-mongoose/delete-many-documents-with-model-remove
Tell us about your browser and operating system

Browser Name:
Browser Version:
Operating System:

If possible, add a screenshot here

Shouldn't this issue be closed? It is has already been fixed.
@raisedadead

@tingxuanz @hilliarj This issue is being closed as it has been resolved by the PR shown above.


Add React.Children.isRenderable

This RFC specifies a React.Children.isRenderable method which allows checking whether a child component (or it's children) return a node or doesn't return anything.
const MaybeWrapper = ({children}) =>
  React.Children.map(children, child) =>
    React.Children.isRenderable(child)
      ? <Wrapper>{child}</Wrapper>
      : child

Thanks for the RFC! I realize this is a pretty late review, see https://github.com/reactjs/rfcs/issues/182 on some discussion around that.
We'd like to not expand the React.Children namespace. While it's occasionally very useful, it's also a flawed feature. Unlike other React features, it doesn't allow composition. Specifically, components that use React.Children don't take well to, for example, wrapping a bunch of children into a single component. We're keeping it around because we don't have a better solution for these cases, but in general we don't plan to change React.Children and hope to eventually make it unnecessary.
Your RFC appears to be more ambitious — it would actually check children "deeply". This is not how any of the existing React.Children utilities work so it probably doesn't belong there. Regardless, there are some big questions about the design that are unsolved by this proposal. I will close it because it's not workable as is, but maybe somebody would open a follow-up.

A method takes a child component instance, finds it's corresponding fiber and checks whether it has a stateNode. If a stateNode exist, the method returns true, else it starts recursively repeat this process on a child fiber and it's siblings until it finds a non-empty stateNode containing a DOM node, otherwise it returns false.

I don't think this works. You're describing a check against the tree that already exists. But the code executes for the tree that is currently being rendered. That could be a completely different tree from the one that already exists — it could have different props or structure. So this implementation doesn't solve the problem and would be inconsistent. There is also a flaw in that it assumes you can get an internal instance (a fiber) based on a child. But that's not how React or JSX works — the child itself is only a description. It's the place into which you place it in the output — its position — that determines the associated internal instance.

This method accepts an instantiated component (a React element) and not a class or a function.

An element is not an "instantiated component", it's only an object like { type: Foo }. I hope this clarifies it. <Foo /> is not the result of executing Foo deeply — it is merely a description. React lazily descends the tree. This is why isRenderable(<Foo />) can't work unless it actually attempts to render Foo deeply which brings a whole suite of other questions:

How do you preserve context? It's normally determined by a place in the tree. If you do isRenderable(<Foo />) but then place it in a <Wrapper>, and Wrapper has a context provider in it, how do you ensure the <Foo /> execution during the check also gets the same context? It wasn't wrapped in the provider yet.
How do you reuse the rendered result? Elements like <Foo /> are stateless, they are merely descriptions. So how do you make it so that the result of the initial "deep render" of <Foo /> is actually being used in the output? You wouldn't want to render it twice.
How "deep" does this deep render go? Does it happen synchronously? This compromises on other features, like time slicing, where we try to distribute the work. We use the per-component boundary to check for interruptions, but this feature would have to be synchronous and recursive so that wouldn't work.
Checking for null specifically seems like a low return on investment for such an invasive feature. The request here is to add a "pierce-through" capability which has rippling implications on many other features. It doesn't seem worth it just to find out whether a component renders null. What are the other use cases that "pierce-through" capability would solve? This seems like a piece of a much more general proposal, but that proposal needs fleshing out.

I am not sure if I got the idea of call-return clearly (the video is not available anymore and all mentions lead to this video), and the use case doesn't seem obvious from the code.

Call/Return is our much earlier exploration of this idea. Here's roughly how it worked. A child component could return a special value, called a "return". E.g. return createReturn(10). And a parent component could return a special value, called a "call". E.g. return createCall(children, ...). The second argument there is a callback, in which the parent would receive collected "returns" from its children. For example if you have child  that renders createReturn(10) instead of JSX, and a child  that renders createReturn(20), their parent could render createCall(<></>, (returns) =>
{returns[0] + returns[1]}
) and that would become
30
. Crucially, you could extract <></> into a separate component like <MyChildren /> and it would still work. One way to look at this feature is that usually, child return values are opaque to the parent — they're just put into its JSX — but this feature let you actually "call" components and use their "returns".
This feature kind of worked but we thought it's pretty confusing (however, it did specify solutions to the problems outlined above). So we did not proceed with that API and ended up deleting it. But a future attempt to bring something like this back would probably need to similarly "powerful" but also much more usable.

I'll also add a comment from @sebmarkbage from when we were last discussing this feature internally:

There are many nuances to this problem space:

Whether you can do multiple passes over the same components and how you communicate that.
Whether you can use a different set of children in the first pass vs the second pass.
Whether you can reorder children between the passes.
Whether it leaks multiple levels or terminates at some predictable point.
Where state/error/context propagation happens.

Then there are implementation details like what's the overhead of these.
It's possible to do these in user space with hooks since hooks are composable.
function Foo({children}) {
  // synchronously reconciles against state stored in useState
  // enough if the tree is small and then rendering continues below
  let yields = useChildren(children);
  return
{doSomething(yields)}
;
}

The most natural way to do getDerivedStateFromCatch with hooks might be a generator form:
function *Foo({ children }) {
  let [showError, updateError] = useState(false);
  if (showError) {
    return <Error retry={() => updateError(false)} />;
  }
  try {
    return yield children;
  } catch (x) {
    updateError(true);
  }
}

This would also naturally perhaps provide a point for call/return.
function *Foo({children}) {
  let yields = yield children; // asynchronously reconciles
  return
{doSomething(yields)}
;
}

Those APIs alone doesn't allow for the multi-pass model perhaps depending on how we model it though.
It's a big space but I don't think we should bring back the model that we had.
I think the way the generator form would work is that we just reconcile the tree again every time it yields against the same children. When it returns, we know we’re done. That lets you do multiple passes against the same subtree until you stabilize. That might be a different use case than the model where the first and second pass touches different components.

I think what Seb meant by it being possible in userspace is that technically React Hooks are implemented using a "dispatcher" which we switch during runtime to the appropriate implementation. So a Hook like useChildren above could temporarily hijack the dispatcher to the one that provides "in-place" implementations of other Hooks. I haven't really thought about this, but in the spirit of transparency, that's the current thinking/feedback on this class of proposals.
I'll close this proposal, since in the current form it's very unlikely to happen.


Fix negative lookbehind matches on javascript

Bug: Regexes with more than one negative lookbehind resolves different matches than the C# implementation.
Solution: Those regexes are evaluated in two steps, first obtaining the matches without the negative lookbehind and then dropping those that also match with the negative lookbehind groups.

@enzocanoo,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


is there way , i can push tx directly and no wait for the peer to ask for it ?

instead of sending hash, send full tx hex directly to peer on the first attempt.?
like force feed.
thanks

No, there is currently no option for that. Feel free to add it.


[Feature Request] Add a way for spell circles to act independently from a player

Might be kind of a big change mechanically, but here are my thoughts on what would actually need to be done

Provide an "offhand" to spell circles, ex through a directix with a hopper-fed inventory
Add a specific impetus for this use case, for which mind's reflection will fail

Alternatively, allowing item stacks to spoof an offhand slot would enable such functionality through the cleric impetus, but would have more knock-on effects for hex casting in general (fex the use of CADs would broaden significantly)
Notes:

cartographer may be a good fit for either the impetus or the directix, as would librarian tho they're already used for akashic libraries

This would allow for the automation of more complex tasks ie through the use of place block, which is currently fairly limited in scope by my understanding

We are working on it. One of the planned changes for 1.0 is to abstract the
player out of the casting system.
So sit tight for now...
On Fri, Jun 17, 2022 at 4:57 PM Lucianna @.***> wrote:

Might be kind of a big change mechanically, but here are my thoughts on
what would actually need to be done

Provide an "offhand" to spell circles, ex through a directix with a
hopper-fed inventory
Add a specific impetus for this use case, for which mind's
reflection will fail

Alternatively, allowing item stacks to spoof an offhand slot would enable
such functionality through the cleric impetus, but would have more knock-on
effects for hex casting in general (fex the use of CADs would broaden
significantly)
Notes:
-cartographer may be a good fit for either the impetus or the directix, as
would librarian tho they're already used for akashic libraries
This would allow for the automation of more complex tasks ie through the
use of place block, which is currently very limited in scope by my
understanding
—
Reply to this email directly, view it on GitHub
https://github.com/gamma-delta/HexMod/issues/137, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHD6LUXOFNU4HFDBSZWLEHLVPTYF7ANCNFSM5ZDRBE3A
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

So yeah i guess i'll close this since i did technically address it


Export Babbage Model to Fiscal Data Package

Description
As babbage will power the first API we expose for OpenSpending Next, it can be useful to have an interface to export Fiscal Data Packages out of Babbage (and, the database babbage works from).
Question: Do we really need to export?
Tasks

[ ] Write a loader from Babbage Model to Fiscal Data Package
[ ] Decent unit test coverage, passing on Py 2.7, 3.3, 3.4, 3.5

#wontfix


no module nmap

Traceback (most recent call last):
File "isf.py", line 9, in
from icssploit.interpreter import IcssploitInterpreter
File "/root/Desktop/isf/icssploit/init.py", line 1, in
from icssploit.utils import (
File "/root/Desktop/isf/icssploit/utils/init.py", line 15, in
import nmap
ImportError: No module named nmap

Tried sudo apt-get install python-nmap?

Tried sudo apt-get install python-nmap?

same error on ubuntu 22.10
ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.
python-nmap for python3 is getting installed successfully but not for python2.7


Gtk-Message: Failed to load module "canberra-gtk-module"

Describe the bug
After clicking enter to open an issue in the browser "Gtk-Message: 16:09:48.965: Failed to load module "canberra-gtk-module" appears randomly on the screen. Switching between the issues by using the arrow keys removes it again
Please provide following details

JiraCLI Version:(Version="1.2.0", GitCommit="9d8a0afd75b68aa519367f93c240429117cc4090", CommitDate="2022-12-16T10:53:08+00:00", GoVersion="go1.18.3", Compiler="gc", Platform="linux/amd64")

Are you using Jira cloud or on-premise jira server?

    SERVER INFO
Version:         1001.0.0-SNAPSHOT
Build Number:    100213
Deployment Type: Cloud
Default Locale:  en_US

What operating system are you using? Also mention version.Ubuntu 22.10

What terminal are you using? Also mention version.Alacritty  0.12.0-dev

To Reproduce
Steps to reproduce the behavior:

Just open list of any issues: jira issue list
Click on a row to open the issue in the browser
See weird screenshot

Expected behavior
View is not destroyed by gtk messages
Screenshots

Additional context

Hi @khskekec, I am not sure about this. This looks something specific to your system. I will leave this open for now in case others have similar issues and could help.

When jira-cli opens a browser, it executes xdg-open on Linux, and it's up to the OS to know how to open a browser from that. In general, that means Firefox on Ubuntu.
This is a side effect of Firefox looking for a particular shared library when it starts up. It doesn't need the library.
Take a look at

How to fix error: Failed to load module "canberra-gtk-module"
Ubuntu 22.04 LTS: Starting firefox through terminal Error "cannot change mount " & Failed to load module "canberra-gtk-module", How to solve it?

for some things to try. This problem is outside of jira-cli's scope, tbh.

Closing as this seems to be system dependent and out of scope of this project.


Do you use predicted clip scores and ground-truth change points(segments) to generate video summary?

Wondering if you use ground-truth change points(segments) to generate video summary. So ur model just predicts scores of each extracted frame without segment splitting. This seems a little strange... Could you please explain? Correct me if I am wrong.
            cps = dataset[key]['change_points'][...]
            num_frames = dataset[key]['n_frames'][()]
            nfps = dataset[key]['n_frame_per_seg'][...].tolist()
            positions = dataset[key]['picks'][...]
            user_summary = dataset[key]['user_summary'][...]

            machine_summary = vsum_tools.generate_summary(probs, cps, num_frames, nfps, positions)

I think change_points are obtained by using KTS.
    ...
    def kts(self, n_frames, features):
        seq_len = len(features)
        picks = np.arange(0, seq_len) * self.sample_rate

        # compute change points using KTS
        kernel = np.matmul(features, features.T)
        change_points, _ = cpd_auto(kernel, seq_len - 1, 1, verbose=False)
        change_points *= self.sample_rate
        change_points = np.hstack((0, change_points, n_frames))
        begin_frames = change_points[:-1]
        end_frames = change_points[1:]
        change_points = np.vstack((begin_frames, end_frames - 1)).T

        n_frame_per_seg = end_frames - begin_frames
        return change_points, n_frame_per_seg, picks

    def run(self, video_path: PathLike):
        n_frames, features = self.get_features(video_path)
        cps, nfps, picks = self.kts(n_frames, features)
        return n_frames, features, cps, nfps, picks

@LvJC  Yes the segmentation algorithm is KTS. These are provided by the H5 files of datasets


Remove ContextInterface & rename forks and threads

This would remove ContextInterface completely, allowing the interfaces of forked process and threads to diverge as needed.
To make naming more short & sweet, ThreadContext is renamed to just Thread, with the previous Thread class renamed to InternalThread.
Forking is a verb, not a noun, so ForkContext is renamed to Process. The idea is that forking is really just the Unix way of creating a new process, so the naming matches up a little better this way. This is distinguished from exec(), since internally, executing a new process command essentially creates a new process with fork() and then runs another process in the current process space. As a side benefit, the naming matches 1:1 with processes in Erlang. (A freebie.)
If we want to remove ContextInterface, this will help us dump it cold turkey, and build off from there.

So good!


Remove discriminator from ActiveConfiguration and split activeconfiguraiton APIs to config level

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[x] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[x] SDK of .NET (need service team to ensure code readiness)
[x] SDK of Python
[x] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[x] PowerShell
[x] CLI
[x] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[ ] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[x] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@yanfa317, as this PR contains breaking changes, please follow the process in http://aka.ms/bcforapi to get it reviewed. thanks

@yanfa317 Fan Yang (AZURE) FTE, as this PR contains breaking changes, please follow the process in http://aka.ms/bcforapi to get it reviewed. thanks

While the changes seem fine from ARM perspective, you need to follow the breaking changes process mentioned by the openapi bot and by @lirenhe.

/azp run

  "commitType": "AdminSecurity"

sec admin

Refers to: specification/network/resource-manager/Microsoft.Network/preview/2021-02-01-preview/examples/NetworkManagerCommitPost.json:15 in b8b5ffb. [](commit_id = b8b5ffb98f52a89186871a0424a00ed0be904b00, deletion_comment = False)

    "/subscriptions/subscriptionC/resourceGroups/resoureGroupSample/providers/Microsoft.Network/networkManagers/testNetworkManager/securityConfigurations/SampleSecurityConfig"

SampleSecurityAdminConfig

Refers to: specification/network/resource-manager/Microsoft.Network/preview/2021-02-01-preview/examples/NetworkManagerCommitPost.json:13 in b8b5ffb. [](commit_id = b8b5ffb98f52a89186871a0424a00ed0be904b00, deletion_comment = False)

    "/subscriptions/subscriptionC/resourceGroups/resoureGroupSample/providers/Microsoft.Network/networkManagers/testNetworkManager/securityConfigurations/SampleSecurityConfig"

securityAdminConfigurations

Refers to: specification/network/resource-manager/Microsoft.Network/preview/2021-02-01-preview/examples/NetworkManagerCommitPost.json:13 in b8b5ffb. [](commit_id = b8b5ffb98f52a89186871a0424a00ed0be904b00, deletion_comment = True)

"title": "Post Azure Virtual Network Manager Commit",

Do we need a sample for connectivity and sec user?

Refers to: specification/network/resource-manager/Microsoft.Network/preview/2021-02-01-preview/examples/NetworkManagerCommitPost.json:2 in b8b5ffb. [](commit_id = b8b5ffb98f52a89186871a0424a00ed0be904b00, deletion_comment = True)

        "etag": "sadf-asdf-asdf-asdf",

This is not valid. I think we should list a valid guid here

Refers to: specification/network/resource-manager/Microsoft.Network/preview/2021-02-01-preview/examples/NetworkManagerListAll.json:15 in b8b5ffb. [](commit_id = b8b5ffb98f52a89186871a0424a00ed0be904b00, deletion_comment = True)

    "etag": "sadf-asdf-asdf-asdf",

.

Refers to: specification/network/resource-manager/Microsoft.Network/preview/2021-02-01-preview/examples/NetworkManagerPatch.json:21 in b8b5ffb. [](commit_id = b8b5ffb98f52a89186871a0424a00ed0be904b00, deletion_comment = True)

"title": "Patch Managed Network Tags",

Is the NM update?
We don't support NM, do we?
If not, we should remove this file.

Refers to: specification/network/resource-manager/Microsoft.Network/preview/2021-02-01-preview/examples/NetworkManagerPatch.json:2 in b8b5ffb. [](commit_id = b8b5ffb98f52a89186871a0424a00ed0be904b00, deletion_comment = True)

"title": "Patch Managed Network Tags",

Is the NM update?
We don't support NM, do we?
If not, we should remove this file.
Refers to: specification/network/resource-manager/Microsoft.Network/preview/2021-02-01-preview/examples/NetworkManagerPatch.json:2 in b8b5ffb. [](commit_id = b8b5ffb, deletion_comment = True

It is required APi, and we need to support it

@lirenhe , we still before public preview, do we need follow http://aka.ms/bcforapi ? Just wondering

In reply to: 884652089

Looks like All your list calls are modeled as POST!
Whereas for most control plane features as well as automated clients GET is what being used see guidance @ Azure Policy Guidelines | ARM Wiki
POST is applicable only when we would like to return secrets which needs to be hidden in GET by default.
Please confirm the reasoning for this design apart from following existing pattern (which may have issues and not to be continued)

Changes look ok. But please resolve breaking changes or get exception. See changelog above for details.

We have talked with @chiragg4u by mail, and have resolved his concerns. I think he has approved it already. thanks!


sha256 in relatedDependency seems to be wrong (holds that of parent dependency)

Describe the bug
<sha256> of <relatedDependency> seems wrong, looks like sha256 of the parent dependency.
Grep for 2c68e2803ce3c47eedb73b84abc002b5edc3be120b235a9f5e7a2bc4e17003e7 in this example, all sha256 the same.
But the other hashes are different (sha1 and md5).
Version of dependency-check used
7.1.0
Log file
see XML
    <dependency isVirtual="false">
      <fileName>jersey-guava-2.24.jar</fileName>
      <filePath>C:\dev\M3_REPO\org\glassfish\jersey\bundles\repackaged\jersey-guava\2.24\jersey-guava-2.24.jar</filePath>
      <md5>82a10834d0869967296093f7f09c7f56</md5>
      <sha1>df9d1fca9c5289097da6c0b8a3092c6d6eb48d87</sha1>
      <sha256>2c68e2803ce3c47eedb73b84abc002b5edc3be120b235a9f5e7a2bc4e17003e7</sha256>
      <description>Jersey Guava Repackaged</description>
      <license>http://glassfish.java.net/public/CDDL+GPL_1_1.html</license>
      <projectReferences>
        <projectReference>dws-client-sample-oidc:compile</projectReference>
      </projectReferences>
      <relatedDependencies>
        <relatedDependency>
          <fileName>jersey-apache-connector-2.24.jar</fileName>
          <filePath>C:\dev\M3_REPO\org\glassfish\jersey\connectors\jersey-apache-connector\2.24\jersey-apache-connector-2.24.jar</filePath>
          <sha256>2c68e2803ce3c47eedb73b84abc002b5edc3be120b235a9f5e7a2bc4e17003e7</sha256>
          <sha1>0dd7ed91cbe1b3fc364468015b1e63f47968da68</sha1>
          <md5>da3009f30862a690800ddf5c0cb63da0</md5>
          <identifiers>
            <package>
<EMAIL_ADDRESS>            </package>
          </identifiers>
        </relatedDependency>
        <relatedDependency>
          <fileName>jersey-client-2.24.jar</fileName>
          <filePath>C:\dev\M3_REPO\org\glassfish\jersey\core\jersey-client\2.24\jersey-client-2.24.jar</filePath>
          <sha256>2c68e2803ce3c47eedb73b84abc002b5edc3be120b235a9f5e7a2bc4e17003e7</sha256>
          <sha1>73af5ad94fed5ee61d27afaecbecb42c33ca0263</sha1>
          <md5>2688860d9a5143677bbaa4c76bd8ddb0</md5>
          <identifiers>
            <package>
<EMAIL_ADDRESS>            </package>
          </identifiers>
        </relatedDependency>

To Reproduce
Most projects should expose this problem.
Expected behavior
sha256 should contain the hash of the related dependency, not of the parent dependency?

There may even be bad follow-up effect due to this:
we are observing jars from wars that are ONLY listed as <relatedDependency> but never as <dependency>.
In the following example, spring-security-crypto (transitive dependency) is never listed as <dependency>, although it was directly found in the war!?
This again could have the effect, that possible CVEs from spring-security-crypto would never get listed?
    <dependency isVirtual="false">
      <fileName>MYPROJECT-soap-5.0.0.war: spring-security-core-5.6.3.jar</fileName>
      <filePath>C:\dev\M3_REPO\de\MYCOMPANY\MYPROJECT\MYPROJECT-soap\5.0.0\MYPROJECT-soap-5.0.0.war\WEB-INF\lib\spring-security-core-5.6.3.jar</filePath>
      <md5>530d76f8d8617f168f7bebbe54f7e59f</md5>
      <sha1>30174aca1818d0cd8e8ac932eb7c7c67f9243a84</sha1>
      <sha256>582e8f566391fb1e03ae9ac40879be734b7393b4543965ea1a7428d5a561e7a1</sha256>
      <projectReferences>
        <projectReference>MYPROJECT-var:compile</projectReference>
        <projectReference>MYPROJECT-server-test:compile</projectReference>
      </projectReferences>
      <relatedDependencies>
        <relatedDependency>
          <fileName>MYPROJECT-soap-5.0.0.war: spring-security-config-5.6.3.jar</fileName>
          <filePath>C:\dev\M3_REPO\de\MYCOMPANY\MYPROJECT\MYPROJECT-soap\5.0.0\MYPROJECT-soap-5.0.0.war\WEB-INF\lib\spring-security-config-5.6.3.jar</filePath>
          <sha256>582e8f566391fb1e03ae9ac40879be734b7393b4543965ea1a7428d5a561e7a1</sha256>
          <sha1>5e6d89757a826245b2c38868096387833258a390</sha1>
          <md5>394da82d1ee5edcdda1f05a03f6e5156</md5>
        </relatedDependency>
        <relatedDependency>
          <fileName>MYPROJECT-soap-5.0.0.war: spring-security-crypto-5.6.3.jar</fileName>
          <filePath>C:\dev\M3_REPO\de\MYCOMPANY\MYPROJECT\MYPROJECT-soap\5.0.0\MYPROJECT-soap-5.0.0.war\WEB-INF\lib\spring-security-crypto-5.6.3.jar</filePath>
          <sha256>582e8f566391fb1e03ae9ac40879be734b7393b4543965ea1a7428d5a561e7a1</sha256>
          <sha1>2233c052b2e92cfd4f4bd741f2bacd2721982606</sha1>
          <md5>f088d97c2e30f5262930c867cac86d2d</md5>
        </relatedDependency>
        <relatedDependency>
          <fileName>MYPROJECT-soap-5.0.0.war: spring-security-web-5.6.3.jar</fileName>
          <filePath>C:\dev\M3_REPO\de\MYCOMPANY\MYPROJECT\MYPROJECT-soap\5.0.0\MYPROJECT-soap-5.0.0.war\WEB-INF\lib\spring-security-web-5.6.3.jar</filePath>
          <sha256>582e8f566391fb1e03ae9ac40879be734b7393b4543965ea1a7428d5a561e7a1</sha256>
          <sha1>067db612f39c74268561fab887e2385f2b6cf324</sha1>
          <md5>71e95f30b3d7fc65418e7c2732914fce</md5>
        </relatedDependency>
      </relatedDependencies>

Which tool of DependencyCheck did you use, and what was the full tool configuration used?

Sorry that I forgot to mention. I am using the Maven Plugin 7.1.0 with the aggregate goal.

To answer one question - "This again could have the effect, that possible CVEs from spring-security-crypto would never get listed?"  No, this would not mask a CVE. For related dependencies to be bundled together the CPEs and CVEs must match. If they were different they would not be bundled.


Code sample : how to convert a DWG to a ASCII DXF and select the ACAF version

First, big thank you for your ACADSHARP.
I'm trying to use it to convert DWG to ASCII DXF...
I've use this code  :
const string _file = "../../../../samples/sample_AC1032.dwg";
const string _filedxf = "../../../../samples/sample_AC1032_mlc.dxf";
static void Main(string[] args)
{
CadDocument doc;
using (DwgReader reader = new DwgReader(_file))
{
doc = reader.Read();
}
//exploreDocument(doc);

using (DxfWriter writer = new DxfWriter(_filedxf, doc,false))
{
	writer.OnNotification += NotificationHelper.LogConsoleNotification;
	writer.Write();
}

}
The dxf created is ASCII one... how to select the ACAD version of DXF if I want one, Please ?
With best regards,
MLC

Hi @mlcvista,
If you want to save the document in a different version just change the version in the header:
//Example
doc.Header.Version = ACadVerson.AC1018;

Thanks for your support.


 This occurs regardless of the command I issue.
CLI output
➜  nanobox-python-sample git:(master) nanobox console
+> Resuming nanobox...
   - Booting virtual machine
   \ Starting nanobox serverA vagrant error occured (See /Users/danielkalen/.nanobox/apps/nanobox-python-sample/vagrant.log for details)
   - Starting nanobox server
A fatal Vagrant error occurred (See /Users/danielkalen/.nanobox/apps/nanobox-python-sample/vagrant.log for details). Exiting...

vagrant.log output
2016-06-23 15:26:55 INFO  ==> nanobox-python-sample: Booting VM...
2016-06-23 15:26:56 INFO  ==> nanobox-python-sample: Waiting for machine to boot. This may take a few minutes...
2016-06-23 15:26:57 INFO  nanobox-python-sample: SSH address: <IP_ADDRESS>:11812
2016-06-23 15:26:57 INFO  nanobox-python-sample: SSH username: docker
2016-06-23 15:26:57 INFO  nanobox-python-sample: SSH auth method: password
2016-06-23 15:27:01 INFO  nanobox-python-sample: Warning: Remote connection disconnect. Retrying...
2016-06-23 15:27:11 INFO  nanobox-python-sample: Warning: Remote connection disconnect. Retrying...
2016-06-23 15:27:21 INFO  nanobox-python-sample: Warning: Remote connection disconnect. Retrying...
2016-06-23 15:27:32 INFO  nanobox-python-sample: Warning: Remote connection disconnect. Retrying...
2016-06-23 15:27:42 INFO  nanobox-python-sample: Warning: Remote connection disconnect. Retrying...
2016-06-23 15:27:52 INFO  nanobox-python-sample: Warning: Remote connection disconnect. Retrying...
2016-06-23 15:27:55 INFO  ==> nanobox-python-sample: Machine booted and ready!
2016-06-23 15:27:55 INFO  ==> nanobox-python-sample: Running provisioner: shell...
2016-06-23 15:27:55 INFO  nanobox-python-sample: Running: inline script
2016-06-23 15:27:55 INFO  ==> nanobox-python-sample: Running provisioner: shell...
2016-06-23 15:27:55 INFO  nanobox-python-sample: Running: inline script
2016-06-23 15:27:55 INFO  ==> nanobox-python-sample: Waiting for nanobox server...
2016-06-23 15:27:55 INFO  ==> nanobox-python-sample: Running provisioner: shell...
2016-06-23 15:27:55 INFO  nanobox-python-sample: Running: inline script
2016-06-23 15:27:55 INFO  ==> nanobox-python-sample: Running provisioner: shell...
2016-06-23 15:27:55 INFO  nanobox-python-sample: Running: inline script
2016-06-23 15:27:55 INFO  ==> nanobox-python-sample: Killing eth1 dhcp...
2016-06-23 15:27:55 INFO  ==> nanobox-python-sample: /tmp/vagrant-shell: line 3: kill: (952) - No such process
2016-06-23 15:27:55 ERROR 2016-06-23 15:27:55 ERROR The SSH command responded with a non-zero exit status. Vagrant
2016-06-23 15:27:55 ERROR assumes that this means the command failed. The output for this command
2016-06-23 15:27:55 ERROR should be in the log above. Please read the output to determine what
2016-06-23 15:27:55 ERROR went wrong.
2016-06-23 15:27:55 FATAL [commands/resume] vagrant.Resume() failed - exit status 1
2016-06-23 15:27:55 *LOG* Closing log now

Thanks for finding this. The help is greatly appreciated!
Nanobox has been completely re-written from the ground up, and we just released v1 into beta this week. Nanobox no longer depends on Vagrant, and so this is no longer an issue. We would love to get your feedback on the new version. The new guides are still a WIP but should be usable within the next week. If you're interested, we'd love to talk with you on irc #nanobox or we can bring you into our slack channel as well.
Additionally, Nanobox and Nanobox Cloud have been merged into a unified process. If you would be interested in early access to the private beta please let me know and I can get you an access token.
Just reach out to<EMAIL_ADDRESS>and we can get you going.
I really appreciate your help on this. I'll go ahead and close this ticket and hope to hear from you directly.