Line 280, Column 398: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/architecture/patterns/circuit-breaker' will be broken in isolated environments. Replace with a relative link.
Line 292, Column 74: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/computer-vision/home' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/cognitiveservices-vision-face-readme.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'face'.
Line 21, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Usage') are not allowed. You can only have one top-level heading.
Line 29, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Provide Feedback') are not allowed. You can only have one top-level heading.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 26, Column 24: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/python/api/overview/azure/cognitive-services' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/cognitiveservices/bing-custom-image-search-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 8, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs-ref-services/latest/cognitiveservices/bing-custom-search-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 8, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs-ref-services/latest/cognitiveservices/bing-entity-search-api-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 8, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs-ref-services/latest/cognitiveservices/bing-image-search-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 8, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs-ref-services/latest/cognitiveservices/bing-news-search-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 8, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs-ref-services/latest/cognitiveservices/bing-video-search-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 8, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs-ref-services/latest/cognitiveservices/bing-visual-search-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 8, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs-ref-services/latest/cognitiveservices/bing-web-search-api-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 8, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs-ref-services/latest/cognitiveservices/face-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 8, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 10, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'face-api'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 27, Column 24: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/face/overview' will be broken in isolated environments. Replace with a relative link.
Line 27, Column 114: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/face/quickstarts/client-libraries' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/commerce.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 12, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.

docs-ref-services/latest/common-readme.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'core'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs-ref-services/latest/communication-chat-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'communication'.
Line 22, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Getting started') are not allowed. You can only have one top-level heading.
Line 100, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Key concepts') are not allowed. You can only have one top-level heading.
Line 172, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Examples') are not allowed. You can only have one top-level heading.
Line 571, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Troubleshooting') are not allowed. You can only have one top-level heading.
Line 575, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Next steps') are not allowed. You can only have one top-level heading.
Line 579, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Contributing') are not allowed. You can only have one top-level heading.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 18, Column 46: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/communication-services/overview' will be broken in isolated environments. Replace with a relative link.
Line 20, Column 346: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/communication-services/' will be broken in isolated environments. Replace with a relative link.
Line 27, Column 63: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/communication-services/quickstarts/create-communication-resource?tabs=windows&pivots=platform-azp' will be broken in isolated environments. Replace with a relative link.
Line 27, Column 217: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/powershell/module/az.communication/new-azcommunicationservice' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/communication-identity-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'communication'.
Line 22, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Getting started') are not allowed. You can only have one top-level heading.
Line 34, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Key concepts') are not allowed. You can only have one top-level heading.
Line 112, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Troubleshooting') are not allowed. You can only have one top-level heading.
Line 115, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Next steps') are not allowed. You can only have one top-level heading.
Line 124, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Contributing') are not allowed. You can only have one top-level heading.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 19, Column 392: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/communication-services/quickstarts/access-tokens?pivots=programming-language-python' will be broken in isolated environments. Replace with a relative link.
Line 26, Column 63: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/communication-services/quickstarts/create-communication-resource?tabs=windows&pivots=platform-azp' will be broken in isolated environments. Replace with a relative link.
Line 26, Column 217: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/powershell/module/az.communication/new-azcommunicationservice' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/communication-phonenumbers-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'communication'.
Line 19, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Getting started') are not allowed. You can only have one top-level heading.
Line 156, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Troubleshooting') are not allowed. You can only have one top-level heading.
Line 159, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Next steps') are not allowed. You can only have one top-level heading.
Line 168, Column 1: [Warning-multiple-h1s] Multiple H1s(H1 'Contributing') are not allowed. You can only have one top-level heading.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 23, Column 63: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/communication-services/quickstarts/create-communication-resource?tabs=windows&pivots=platform-azp' will be broken in isolated environments. Replace with a relative link.
Line 23, Column 217: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/powershell/module/az.communication/new-azcommunicationservice' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/communication-sms-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'communication'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 18, Column 46: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/communication-services/overview' will be broken in isolated environments. Replace with a relative link.
Line 20, Column 367: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/communication-services/quickstarts/telephony-sms/send?pivots=programming-language-python' will be broken in isolated environments. Replace with a relative link.
Line 29, Column 63: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/communication-services/quickstarts/create-communication-resource?tabs=windows&pivots=platform-azp' will be broken in isolated environments. Replace with a relative link.
Line 29, Column 217: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/powershell/module/az.communication/new-azcommunicationservice' will be broken in isolated environments. Replace with a relative link.
Line 138, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/communication-services/quickstarts/telephony-sms/send?pivots=programming-language-python' will be broken in isolated environments. Replace with a relative link.
Line 139, Column 102: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/communication-services/quickstarts/telephony-sms/handle-sms-events' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/consumption.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 12, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 6, Column 12: [Suggestion-ms-author-invalid] Invalid value for 'ms.author', 'sttramer' is not a valid Microsoft alias.

docs-ref-services/latest/container-registry.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 12, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 6, Column 12: [Suggestion-ms-author-invalid] Invalid value for 'ms.author', 'sttramer' is not a valid Microsoft alias.

docs-ref-services/latest/containerinstance.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 12, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.

docs-ref-services/latest/core-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'core'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs-ref-services/latest/cosmos-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'cosmos'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 26, Column 114: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/' will be broken in isolated environments. Replace with a relative link.
Line 28, Column 28: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/sql-query-getting-started' will be broken in isolated environments. Replace with a relative link.
Line 28, Column 146: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/introduction' will be broken in isolated environments. Replace with a relative link.
Line 35, Column 9: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/account-overview' will be broken in isolated environments. Replace with a relative link.
Line 38, Column 71: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 96, Column 49: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/databases-containers-items' will be broken in isolated environments. Replace with a relative link.
Line 109, Column 100: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/how-to-write-stored-procedures-triggers-udfs' will be broken in isolated environments. Replace with a relative link.
Line 168, Column 39: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/analytical-store-introduction' will be broken in isolated environments. Replace with a relative link.
Line 168, Column 192: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/synapse-link' will be broken in isolated environments. Replace with a relative link.
Line 301, Column 77: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/how-to-sql-query' will be broken in isolated environments. Replace with a relative link.
Line 348, Column 34: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/time-to-live' will be broken in isolated environments. Replace with a relative link.
Line 357, Column 1: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/rest/api/cosmos-db/http-status-codes-for-cosmosdb' will be broken in isolated environments. Replace with a relative link.
Line 404, Column 68: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/data-lake-analytics.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 12, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 120, Column 1: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/data-lake-analytics/data-lake-analytics-manage-use-python-sdk' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/data-lake-store.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 12, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 6, Column 12: [Suggestion-ms-author-invalid] Invalid value for 'ms.author', 'sttramer' is not a valid Microsoft alias.

docs-ref-services/latest/data-nspkg-readme.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs-ref-services/latest/data-tables-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'tables'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 21, Column 62: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/python/api/overview/azure/data-tables-readme-pre?view=azure-python-preview' will be broken in isolated environments. Replace with a relative link.
Line 21, Column 62: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/python/api/overview/azure/data-tables-readme-pre?view=azure-python-preview
Line 29, Column 10: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/storage/common/storage-account-create?tabs=azure-portal' will be broken in isolated environments. Replace with a relative link.
Line 30, Column 10: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/create-cosmosdb-resources-portal' will be broken in isolated environments. Replace with a relative link.
Line 33, Column 48: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/storage/common/storage-account-create?tabs=azure-portal' will be broken in isolated environments. Replace with a relative link.
Line 33, Column 93: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/storage/common/storage-account-create?tabs=azure-powershell' will be broken in isolated environments. Replace with a relative link.
Line 33, Column 149: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/storage/common/storage-account-create?tabs=azure-cli' will be broken in isolated environments. Replace with a relative link.
Line 34, Column 59: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/scripts/cli/table/create' will be broken in isolated environments. Replace with a relative link.
Line 34, Column 99: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/create-cosmosdb-resources-portal' will be broken in isolated environments. Replace with a relative link.
Line 46, Column 293: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/storage/common/storage-account-overview#storage-account-endpoints' will be broken in isolated environments. Replace with a relative link.
Line 59, Column 121: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/storage/common/storage-account-overview#storage-account-endpoints' will be broken in isolated environments. Replace with a relative link.
Line 68, Column 19: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/rest/api/storageservices/authorize-with-shared-key' will be broken in isolated environments. Replace with a relative link.
Line 68, Column 161: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/storage/common/storage-account-overview#storage-account-endpoints' will be broken in isolated environments. Replace with a relative link.
Line 86, Column 140: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/storage/common/storage-account-overview#storage-account-endpoints' will be broken in isolated environments. Replace with a relative link.
Line 99, Column 10: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/storage/common/storage-sas-overview' will be broken in isolated environments. Replace with a relative link.
Line 99, Column 229: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/rest/api/storageservices/create-service-sas' will be broken in isolated environments. Replace with a relative link.
Line 268, Column 143: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/rest/api/storageservices/table-service-rest-api' will be broken in isolated environments. Replace with a relative link.
Line 268, Column 263: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/rest/api/storageservices/table-service-error-codes' will be broken in isolated environments. Replace with a relative link.
Line 334, Column 64: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/table-introduction' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/datafactory.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 11, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.

docs-ref-services/latest/devtest-labs.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 12, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.

docs-ref-services/latest/digitaltwins-core-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'digitaltwins'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 23, Column 549: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/digital-twins/overview' will be broken in isolated environments. Replace with a relative link.
Line 25, Column 90: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/digital-twins/tutorial-code' will be broken in isolated environments. Replace with a relative link.
Line 25, Column 213: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/digital-twins/tutorial-command-line-app' will be broken in isolated environments. Replace with a relative link.
Line 25, Column 566: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/digital-twins/tutorial-end-to-end' will be broken in isolated environments. Replace with a relative link.
Line 45, Column 36: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/dotnet/api/azure.core.tokencredential?view=azure-dotnet' will be broken in isolated environments. Replace with a relative link.
Line 45, Column 36: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/azure.core.tokencredential?view=azure-dotnet
Line 45, Column 141: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/dotnet/api/microsoft.rest.serviceclientcredentials?view=azure-dotnet' will be broken in isolated environments. Replace with a relative link.
Line 45, Column 141: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/microsoft.rest.serviceclientcredentials?view=azure-dotnet
Line 46, Column 62: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/dotnet/api/azure.identity.defaultazurecredential?view=azure-dotnet' will be broken in isolated environments. Replace with a relative link.
Line 46, Column 62: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/dotnet/api/azure.identity.defaultazurecredential?view=azure-dotnet
Line 74, Column 58: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/digital-twins/' will be broken in isolated environments. Replace with a relative link.
Line 212, Column 68: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/digital-twins/concepts-query-language' will be broken in isolated environments. Replace with a relative link.
Line 215, Column 45: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/digital-twins/how-to-query-graph#query-limitations' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/dns.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 12, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 6, Column 12: [Suggestion-ms-author-invalid] Invalid value for 'ms.author', 'sttramer' is not a valid Microsoft alias.

docs-ref-services/latest/event-hub.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 12, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 6, Column 12: [Suggestion-ms-author-invalid] Invalid value for 'ms.author', 'sttramer' is not a valid Microsoft alias.
Line 19, Column 503: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-hubs/event-hubs-about' will be broken in isolated environments. Replace with a relative link.
Line 33, Column 76: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/python/api/overview/azure/eventhub-readme?view=azure-python' will be broken in isolated environments. Replace with a relative link.
Line 33, Column 76: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/python/api/overview/azure/eventhub-readme?view=azure-python
Line 34, Column 113: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/python/api/overview/azure/eventhub-checkpointstoreblob-readme?view=azure-python' will be broken in isolated environments. Replace with a relative link.
Line 34, Column 113: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/python/api/overview/azure/eventhub-checkpointstoreblob-readme?view=azure-python
Line 35, Column 121: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/python/api/overview/azure/eventhub-checkpointstoreblob-aio-readme?view=azure-python' will be broken in isolated environments. Replace with a relative link.
Line 35, Column 121: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/python/api/overview/azure/eventhub-checkpointstoreblob-aio-readme?view=azure-python
Line 43, Column 82: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/python/api/azure-eventhub/?view=azure-python-previous' will be broken in isolated environments. Replace with a relative link.
Line 43, Column 82: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/python/api/azure-eventhub/?view=azure-python-previous
Line 51, Column 83: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/python/api/overview/azure/eventhubs/management?view=azure-python' will be broken in isolated environments. Replace with a relative link.
Line 51, Column 83: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: https://docs.microsoft.com/python/api/overview/azure/eventhubs/management?view=azure-python

docs-ref-services/latest/eventgrid-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'eventgrideventgrid'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 19, Column 119: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-grid/overview' will be broken in isolated environments. Replace with a relative link.
Line 25, Column 127: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-grid/custom-event-quickstart-portal' will be broken in isolated environments. Replace with a relative link.
Line 25, Column 365: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-grid/custom-event-quickstart' will be broken in isolated environments. Replace with a relative link.
Line 25, Column 459: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 92, Column 251: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-grid/get-access-keys' will be broken in isolated environments. Replace with a relative link.
Line 109, Column 5: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-grid/concepts#topics' will be broken in isolated environments. Replace with a relative link.
Line 112, Column 12: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-grid/event-domains' will be broken in isolated environments. Replace with a relative link.
Line 112, Column 340: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-grid/event-domains' will be broken in isolated environments. Replace with a relative link.
Line 117, Column 6: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-grid/concepts#events' will be broken in isolated environments. Replace with a relative link.
Line 122, Column 45: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-grid/input-mappings' will be broken in isolated environments. Replace with a relative link.
Line 122, Column 226: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-grid/event-schema' will be broken in isolated environments. Replace with a relative link.
Line 125, Column 263: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-grid/cloud-event-schema' will be broken in isolated environments. Replace with a relative link.
Line 146, Column 5: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-grid/system-topics' will be broken in isolated environments. Replace with a relative link.
Line 149, Column 56: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-grid/system-topics' will be broken in isolated environments. Replace with a relative link.
Line 151, Column 65: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-grid/concepts' will be broken in isolated environments. Replace with a relative link.
Line 155, Column 359: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-grid/kubernetes/overview' will be broken in isolated environments. Replace with a relative link.
Line 434, Column 63: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-grid/overview' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/eventhub-checkpointstoreblob-aio-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'eventhubs'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 22, Column 421: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-hubs/' will be broken in isolated environments. Replace with a relative link.
Line 22, Column 501: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/storage/' will be broken in isolated environments. Replace with a relative link.
Line 31, Column 251: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-hubs/event-hubs-create' will be broken in isolated environments. Replace with a relative link.
Line 33, Column 189: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/storage/blobs/storage-blob-create-account-block-blob' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/eventhub-checkpointstoreblob-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'eventhubs'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 22, Column 400: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-hubs/' will be broken in isolated environments. Replace with a relative link.
Line 22, Column 480: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/storage/' will be broken in isolated environments. Replace with a relative link.
Line 31, Column 251: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-hubs/event-hubs-create' will be broken in isolated environments. Replace with a relative link.
Line 33, Column 189: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/storage/blobs/storage-blob-create-account-block-blob' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/eventhub-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'eventhubseventhubs'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 21, Column 25: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-hubs/event-hubs-about' will be broken in isolated environments. Replace with a relative link.
Line 30, Column 310: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-hubs/' will be broken in isolated environments. Replace with a relative link.
Line 41, Column 5: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-hubs/event-hubs-create' will be broken in isolated environments. Replace with a relative link.
Line 59, Column 111: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-hubs/event-hubs-get-connection-string' will be broken in isolated environments. Replace with a relative link.
Line 63, Column 84: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-hubs/event-hubs-get-connection-string#get-connection-string-from-the-portal' will be broken in isolated environments. Replace with a relative link.
Line 79, Column 17: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-hubs/authorize-access-azure-active-directory' will be broken in isolated environments. Replace with a relative link.
Line 102, Column 47: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-hubs/event-hubs-features' will be broken in isolated environments. Replace with a relative link.
Line 337, Column 4: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/storage/common/storage-quickstart-create-account?tabs=azure-portal' will be broken in isolated environments. Replace with a relative link.
Line 338, Column 7: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/storage/blobs/storage-quickstart-blobs-portal#create-a-container' will be broken in isolated environments. Replace with a relative link.
Line 388, Column 61: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/iot-hub/iot-hub-devguide-messages-read-builtin' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/graph-rbac.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 12, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.

docs-ref-services/latest/identity-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 24, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/active-directory/' will be broken in isolated environments. Replace with a relative link.
Line 62, Column 18: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 116, Column 1: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/active-directory/managed-identities-azure-resources/overview' will be broken in isolated environments. Replace with a relative link.
Line 118, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/active-directory/managed-identities-azure-resources/how-to-use-vm-token' will be broken in isolated environments. Replace with a relative link.
Line 119, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/app-service/overview-managed-identity?tabs=dotnet' will be broken in isolated environments. Replace with a relative link.
Line 120, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/aks/use-managed-identity' will be broken in isolated environments. Replace with a relative link.
Line 121, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cloud-shell/msi-authorization' will be broken in isolated environments. Replace with a relative link.
Line 122, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/azure-arc/servers/managed-identity-authentication' will be broken in isolated environments. Replace with a relative link.
Line 123, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/service-fabric/concepts-managed-identity' will be broken in isolated environments. Replace with a relative link.
Line 317, Column 1: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/active-directory/develop/reference-aadsts-error-codes' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/iot.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 12, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 6, Column 12: [Suggestion-ms-author-invalid] Invalid value for 'ms.author', 'sttramer' is not a valid Microsoft alias.

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


feat(ci/cd): add running gossip + benchmarks

running gossip for N seconds and then shutting down [x]
run benchmarks [x]
unused imports check [x]

the CI will now run only on review request AND every review submitted (instead on every commit of a pull request) - due to the increased time it will run i didnt want to run it for long
sample run: https://github.com/Syndica/sig/actions/runs/9390446592/job/25860335747

note: decided to not include accounts-db because of the uncertainty of how long to let it run to download a snapshot and didnt want to introduce too many changes in CI in one go

What is the downside of running it on every commit? It's nice to get feedback for each commit.

What is the downside of running it on every commit? It's nice to get feedback for each commit.

spinning up gossip to interact with the network and send packets seems wasteful imo - feels like we would only want to run these checks before we have it reviewed (to save reviewer time) or before we merge to main (to ensure theres no bugs) - if you want it every commit, you can always run it locally?

spinning up gossip to interact with the network and send packets seems wasteful

What resource are we wasting though? Is there an actual cost?
I feel that it is useful to understand whether my recent change broke anything. While I could run the checks locally, I might forget, or I might want to use my computer for something else that it interferes with. Also, the historical record of runs provides an audit trail that can be useful to diagnose issues that might have been overlooked.

good point - if you find it useful we can try it

If there are no other outstanding contentions, I'd like for this to get merged.


Create new issues for api routes after MongoDB Models have been created

All API routes needed for the models

@jman2476 @shannontice -- Once all the models are made you'll know what routes to make(e.g. route to get all the user's entries by id, route to return a light/heavy prompt etc.)


[request] please add sensor: Solarman - Daily Total Consumption to match the value in energy dashboard and Solarman App

Hi David,
could you please add a sensor that shows exactly the same value for the “Daily total consumption” as the value in the energy dashboard?
The KWh value in the official Solarman App, Deye App and Energy Ease App for mobile devices show the same value for Daily total consumption as the Energy dashboard in Home Assistant.
The already available “Daily Load Consumption” doesn’t match wit the “Daily total consumption”. This value is slightly lower.
Adding this sensor would be highly appreciated. Alternatively could you make it available as a template sensor? I have no clue how generate the code for it.
Joe

Hi again,
these values confuse me:
Daily consumption from Energy Ease App:

Daily consumption from HA energy dashnoard:

Daily load consumption from Solarman Modbus:

I thought that the load consumption with the battery discharge added leads to the right value, but it doesn’t:

Hope you know what I mean now.
I want a sensor that is exactly the same.
if it is not possible because of your discription above, never mind.
Anyway, thx for helping and trying to pimp the integration to max it out.
Joe

To be clear, the integration don't make up any values, nor it calculates them in this particular example, it takes the data from the inverter, and presents them for you. If there are any errors in that regard it has to be due to some misconfiguration.
That being said to debug this issue... Could you please provide again the same screenshots from the same time, obviously and also add data from inverter display itself? From the screen where is visible Today Load Consumption (It should be under house icon).
Have fun.

Hi David,
Thy for explaining.
Closed

I think I finally figured out what this was all about. So the mentioned sensor 'X Load Consumption' only shows the load consumption of the house. But what Energy dashboard or Solarman App shows you is load consumption of the house + what inverter consumed + all the other potential losses! In the yaml for SG04LP3 are additional sensors which also provides information about those losses! 😉
Have fun and stay sharp!

Yes I think you probably got it.
I never understood why there is no sensor that shows the same value as the one in the energy dashboard. I understand that your integration is just reading modbus registers and can‘t add calculated values.
Thanks for picking up my comment for another explanation. 😄
You are IT Kram diskutieren über übers Hecken von dem Wechselrichter unten im Keller, der baut

The Energy dashboard just sums up Exported/Bought energy and Produced energy and then shows you the Consumed amount. It does not even look at Load Consumption because it does not have to. 😉
But I also wanted to see this losses as an sensor so what I did is:
Total losses = Total Energy Exported/Bought + Total Produced + Total Battery Discharge - Total Energy Imported/Sold - Total Battery Discharge - Total Load Consumption
And the same for daily/today:
Daily losses = Daily Energy Exported/Bought + Daily Produced + Daily Battery Discharge - Daily Energy Imported/Sold - Daily Battery Discharge - Daily Load Consumption
This will give you all the energy consumed by the inverter itself + also all the losses by AC/DC conversions (Battery charging/discharging).
What I don't understand is why those are not provided by the inverter itself. 😄
Or maybe I do understand, they probably don't want to directly show how inefficient the inverter is. 😄
You welcome, I'm always trying to be as helpful as possible. 😉

Meanwhile I firured out how to match the values for "Daily Consumption" from Solarman APP with Solarman for Home Assistant.
To add a newly created template sensor, just copy this code into your configuration.yaml:
  # Sensor template for:
  # "Solarman Daily Energy Consumption" to match the value from Solarman APP
  # To install: Add lines to your "configuration.yaml" and restart
  # The sensor names match for: DEYE Hybrid Inverter "sg04lp3.yaml"
  # Code by PV-Joe (2024)
  - platform: template
    sensors:
      daily_energy_consumption:
        friendly_name: "Solarman Daily Energy Consumption"
        unique_id: solarman_daily_energy_used
        unit_of_measurement: 'kWh'
        device_class: "power"
        value_template: >
          {{
            (states('sensor.solarman_daily_production')|float(0) +
            states('sensor.solarman_daily_energy_bought')|float(0) +
            states('sensor.solarman_daily_battery_discharge')|float(0) -
            states('sensor.solarman_daily_energy_sold')|float(0) -
            states('sensor.solarman_daily_battery_charge')|float(0))
            | round(1)
          }}

Yes I calculate energy losses this way. You can even do this sensor from within inverter definition file in my integration I support simple math operation with registers. ;)

I like the way to have a sensor that adds up Load Consumption and Losses and in addition your seperated sensor for Losses values as well.
Your dashboard is brilliant. I love it!
Maybe you could share the configuration and the yaml code for your dashboard  in your Wiki.
I could imagine more people are interested in the professional look and feel of these amazing gauges.
Well done!

I like the way to have a sensor that adds up Load Consumption and Losses and in addition your seperated sensor for Losses values as well.

I understand.. cause you are also using InfluxDB and that means you don't have the value there... makes sense!

Your dashboard is brilliant. I love it!
Maybe you could share the configuration and the yaml code for your dashboard in your Wiki. I could imagine more people are interested in the professional look and feel of these amazing gauges.
Well done!

Thank you! It took a lot of effort so I'm glad you like it.
Anyway I have it planned in milestones here: Start Wiki 😉
Cheers!

I extended the wiki with those sensors for you: Today/Daily Consumption [kWh] and Total Consumption [kWh]

Dashboards 😉


build_emoji: Make sure emoji names are supported.

Oh weird, sorry about that.

You need to use git commit --amend --reset-author; it's still shown as written by Anders.


Logistics bots fly strangely on planets of non-normal sizes

On telluric planets smaller than vanilla size, bots fly in a tall arch to reach their destination. Have not tested on large planets though.

Shouldn't be a difficult fix, thanks

impossible fix unfortunately, they are all in shader too. I raised a suggestion in the dsp discord if you want to upvote it
https://discord.com/channels/750553061369577492/801263634164219924/1028934174675046441


dead link

https://github.com/EpistasisLab/pmlb/blob/d79bef5d4a822c2c0fde565dac22870399a1c890/datasets/adult/metadata.yaml#L5
the source links to http://mlr.cs.umass.edu/ml/datasets/Adult which is dead

Link rots are not fun 😭   I found this UCI link instead: https://archive.ics.uci.edu/ml/datasets/adult still unsure if the umass link is still out there somewhere.


Docs updates from Gitter

Updating docs to answer some questions we've received in our Gitter channel:

Can you execute SQL from a file? (fixes #276) @tschottdorf, please take a look at the updates to use-the-built-in-sql-client.md.
Does CockroachDB support cross-region communication? (fixes #273) @bdarnell, please take a look at the updates to configure-replication-zones.md.
Can you use CockroachDB as a kv store? (fixes #138) @vivekmenezes, please take a look at the question added to frequently-asked-questions.md.
What are the storage sizes for different data types? (fixes #214) @knz, please take a look at the changes to data-types.md, string.md, bytes.md, and decimal.md.

This change is

LGTM

Review status: 0 of 16 files reviewed at latest revision, 2 unresolved discussions.

frequently-asked-questions.md, line 138 [r5] (raw file):

## Can I use CockroachDB as a key-value store?

CockroachDB is a distributed SQL database built on a transactional and strongly-consistent key-value store. At this time, it is not possible to access the key-value store directly. As an alternative, you can [create a SQL table](create-table.html) with two columns, `k` and `v`, and set `k` as the primary key. This will map rather directly to the underlying key-value operations.

I'd take out the last sentence because it's not accurate and not really useful.

Comments from Reviewable

LGTM
Previously, bdarnell (Ben Darnell) wrote…
> LGTM

Review status: 0 of 16 files reviewed at latest revision, 2 unresolved discussions.

Comments from Reviewable

LGTM


ValueError: Object arrays cannot be loaded when allow_pickle=False on Linux

Hi,
I have an issue which might be related to this one, but the fix for that one did not work for me. I am also running Linux Mint and not Windows. I tried to use python 2.7.18 , python 3.8.10 and python 3.9.6.
My requirement versions are:
Cython          0.29.24 numpy           1.16.6 pandas          0.24.2 scipy           1.2.3
All of them installed via pip
The first error:
python run_detector.py
Import Error: No module named nms
please compile fast nms by running:
python setup.py build_ext --inplace
using slow nms in the meantime.
Processing         1 files
Input directory    wavs
Results directory  results

Traceback (most recent call last):
  File "run_detector.py", line 115, in <module>
    det = detector.CPUDetector(det_model_file, det_params_file)
  File "/home/arn/bats/batdetect/bat_eval/cpu_detection.py", line 36, in __init__
    self.weights = np.load(weight_file, encoding='latin1')
  File "/home/arn/.local/lib/python2.7/site-packages/numpy/lib/npyio.py", line 447, in load
    pickle_kwargs=pickle_kwargs)
  File "/home/arn/.local/lib/python2.7/site-packages/numpy/lib/format.py", line 696, in read_array
    raise ValueError("Object arrays cannot be loaded when "
ValueError: Object arrays cannot be loaded when allow_pickle=False

When I try to compile fast non maximum suppression:
python setup.py build_ext --inplace
Compiling nms.pyx because it changed.
[1/1] Cythonizing nms.pyx
/home/arn/.local/lib/python2.7/site-packages/Cython/Compiler/Main.py:369: FutureWarning: Cython directive 'language_level' not set, using 2 for now (Py2). This will change in a later release! File: /home/arn/bats/batdetect/bat_eval/nms.pyx
  tree = Parsing.p_module(s, pxd, full_module_name)
running build_ext
building 'nms' extension
creating build
creating build/temp.linux-x86_64-2.7
x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g -fdebug-prefix-map=/build/python2.7-QDqKfA/python2.7-2.7.18=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I/home/arn/.local/lib/python2.7/site-packages/numpy/core/include -I/usr/include/python2.7 -c nms.c -o build/temp.linux-x86_64-2.7/nms.o -fopenmp -ffast-math -msse -msse2 -msse3 -msse4 -s -std=c99
In file included from /home/arn/.local/lib/python2.7/site-packages/numpy/core/include/numpy/ndarraytypes.h:1822,
                 from /home/arn/.local/lib/python2.7/site-packages/numpy/core/include/numpy/ndarrayobject.h:12,
                 from /home/arn/.local/lib/python2.7/site-packages/numpy/core/include/numpy/arrayobject.h:4,
                 from nms.c:646:
/home/arn/.local/lib/python2.7/site-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:17:2: warning: #warning "Using deprecated NumPy API, disable it with " "#define NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
   17 | #warning "Using deprecated NumPy API, disable it with " \
      |  ^~~~~~~
x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g -fdebug-prefix-map=/build/python2.7-QDqKfA/python2.7-2.7.18=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-Bsymbolic-functions -Wl,-z,relro -Wdate-time -D_FORTIFY_SOURCE=2 -g -fdebug-prefix-map=/build/python2.7-QDqKfA/python2.7-2.7.18=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC build/temp.linux-x86_64-2.7/nms.o -o /home/arn/bats/batdetect/bat_eval/nms.so -fopenmp`

The error basically remains the same afterwards:
python run_detector.py
Processing         1 files
Input directory    wavs
Results directory  results

Traceback (most recent call last):
  File "run_detector.py", line 115, in <module>
    det = detector.CPUDetector(det_model_file, det_params_file)
  File "/home/arn/bats/batdetect/bat_eval/cpu_detection.py", line 36, in __init__
    self.weights = np.load(weight_file, encoding='latin1')
  File "/home/arn/.local/lib/python2.7/site-packages/numpy/lib/npyio.py", line 447, in load
    pickle_kwargs=pickle_kwargs)
  File "/home/arn/.local/lib/python2.7/site-packages/numpy/lib/format.py", line 696, in read_array
    raise ValueError("Object arrays cannot be loaded when "
ValueError: Object arrays cannot be loaded when allow_pickle=False

The "results" and "individual_results" folders are created but remain empty.
I have a feeling that this might be a beginner problem, which will hopefully make it easy to resolve for someone who knows what they are doing.

Hi there.
I haven't tested the code using the package versions you are using. If you have not already done so, try with the versions specified here:
https://github.com/macaodha/batdetect/tree/master/bat_eval#requirements
Hope this helps,
Oisin

I manged to downgrade the requirements to these versions:
Cython          0.24.1 numpy           1.16.6 pandas          0.24.2 scipy           0.19.0
run_detector.py does seem to work with these versions.
specifying the data directory via option does not seem to work as does the save_individual_results = False
But this is a minor problem since setting those in the file does work.
Thank you for your quick support.

Great, glad you got it working. In general the codebase, is old and we plan on having something new available in the next few months.


sequoia: 0.18.0 -> 0.19.0

Motivation for this change
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

From some reason I pushed a new version and GitHub won't update the PR.


Get BLE state

[x] Check if the device has BLE
[x] Get the state (On, Off, NotAvailable)
[x] Event that notifies about state changes
[x] add to sample app
[x] document feature
[ ] unauthorized state Android

Add this to IBluetoothLE.

Unauthorized state on Android has to be implemented with #22


Update implemention of SlowMo to its implementation in Fairscale

[ ] Was this discussed/approved via a Github issue? (no need for typos, doc improvements)
[x] Did you read the contributor guideline?
[x] Did you make sure to update the docs?
[x] Did you write any new necessary tests?

What does this PR do?
SlowMo is being moved to Fairscale. This commit updates the implementation of SlowMo to the Fairscale version. It also adds tests for SlowMo.
Note: This PR is currently for review. It will be merged at a later date once SlowMo has been updated to Fairscale. SlowMo is being merged to Fairscale as part of a PR. So, once that PR is merged to Fairscale, this PR on Fairseq will be ready for merge
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

Thanks for the review! I'll wait for SlowMo to be merged into Fairscale before going ahead with merging this PR.


Is this project dead?

The dependencies are definitely out of date

Not yet :). Updated dependencies and bump to v2.0.0


fix: extract_gender returns 'female' when no matches found for name

extract_gender function is always returns 'female' even for cases, when no name matches found (m_count = 0, f_count = 0).

Thanks for the PR! Merging.


Updated Base Pointer Controller Pointer Name Property  …

Overview

Added a backing field, in case the gameObject reference is destroyed when attempting to get the pointer name

isn't this hiding an issue? if the underlying gameobject has been destroyed, the pointer is no longer valid... how do you envision an app getting into this situation?

I've never had an issue setting the name, only getting it during shutdown because of the non-deterministic nature of unity's game loop. For example, if a GameObject get's destroyed before the MixedRealityToolkit ServiceLocator finished shutting down the InputSystem.

For example, if a GameObject get's destroyed before the MixedRealityToolkit ServiceLocator finished shutting down the InputSystem.

If the gameObject is destroyed, won't the pointer script also be destroyed? Does checking the pointer script reference for null before trying to access the name not work?

If the gameObject is destroyed, won't the pointer script also be destroyed? Does checking the pointer script reference for null before trying to access the name not work?

No it doesn't which is why we're getting the issue in the first place. 😅

Which line is causing the issue?

The gameObject can sometimes be null when exiting play mode in the editor because it is cleaned up before the system shuts down.

Right, that part is clear from this PR. I was asking if there's a line in the Toolkit asking the pointer for its name at a time when the gameObject is null.

When we're unregistering the pointers and removing it from the list. Under the hood the Remove function tries to get the hash code.  In our hash code override we access the property, which returns the gameObject.name instead of a backed field.

@StephenHodgson, that's a great description of the issue. Thanks for adding it. Makes the change much easier to understand.


Case Sensitivity

Fixes #904
Feature Summary and Justification
This allows Emoji to be treated case sensitively, per current Reddit spec. Also treats two emoji from the same name and different subreddits differently, per spec.

Awesome work! Thanks for the update.


update Servlet version in ServletContext.java

I am reading the Servlet spec and I found a number mismatched.
What I have changed:

Update a number from 4 to 5

Thank you, @zzk0 !


doc: fix ensuareAlpha alpha argument

1 is full-transparent

I'm unsure I understand this change as the current documentation is correct. Adding an alpha channel using a value of 0 produces a fully-transparent image.
The alpha channel relates to the ability to see whatever is behind the image. Perhaps you are thinking of a mask?

@lovell you're right, the output file must be png.
If I use jpg as output, like below, it outputs a black image, what caused it? This gets me confused.
await sharp('rgb.jpg')
  .ensureAlpha(0)
  .toFile('output.jpg')

JPEG images do not support an alpha channel.


[SMALLFIX] Update S3A directory suffix

Update the suffix for pseudo-directories in S3A to path separator.
Caveats when migrating from older versions:

1.4.0 directory breadcrumbs will show up as files
isDirectory will not recognize 1.4.0 empty directories
deleteDirectory will not delete 1.4.0 empty directories. Also performance could be impacted as UfsSyncChecker may falsely detect nested directory breadcrumbs as un-synced files

@calvinjia Please take a look. Thanks!

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15340/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15343/
Test FAILed.

Jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15344/
Test PASSed.

@madanadit Could you run the s3 test profile with s3a and ensure those pass?

@gpang Can you also take a look?

@madanadit Is there a restriction that directory names cannot end with the suffix?

@gpang there is no such restriction

@calvinjia Everything that ran passed. A couple timed out (seems unrelated to this PR)
FileInStreamIntegrationTest.remoteReadLargeFile
FileSystemMasterIntegrationTest.createFilePerf:295
FileSystemMasterIntegrationTest.listFiles:489
FileSystemMasterIntegrationTest.listStatus:515


Rework SaveConfig for web & multi sensors

Description
This PR intends to give more informations about which picture was taken (which sensor took it). It should also provide a better web support with the use of the cross_file package.

Instead of a FilePathBuilder, it now takes CaptureRequestBuilder

It takes a List<Sensor> as argument
It returns a either a SingleCaptureRequest or a MultipleCaptureRequest depending on the number of sensors required

SaveConfig has a default value for CaptureRequestBuilder. Medias will be saved at [temporary directory]/camerawesome/[time in millis].jpg
A CaptureRequest uses XFile instead of String to better support Web (e.g.: file property for a SingleCaptureRequest)
On Web, the files may be null since the XFile will be built by the camera implementation without a real path.
The MediaCapture object now contains a CaptureRequest instead of a path (String).

It it was a success, the file(s) it contains should not be null.

Since a CaptureRequest can either be a SingleCaptureRequest or a MultipleCaptureRequest, a when operator is introduced to deal with these without explicit casting on the dev side.
A dependency to XFile may be added to let users specify their own path in the SaveConfig with the current implementation. An alternative would be to create our own File class and convert it to XFile when we want to work with it.

Checklist
Before creating any Pull Request, confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).

[x] 📕 I read the Contributing page.
[x] 🤝 I match the actual coding style.
[x] ✅ I ran flutter analyze without any issues.

Breaking Change

[x] 🛠 My feature contain breaking change.

Introduction of the CaptureRequest concept to deal with multiple pictures and ease the CamerAwesome web implementation.

Nice refactor ! How can we force download to

custom path
download folder
application folder

Here is an example for the download folder, with a different name for each picture on multicam:
CameraAwesomeBuilder.awesome(
    saveConfig: SaveConfig.photoAndVideo(
      initialCaptureMode: CaptureMode.photo,
      photoPathBuilder: (sensors) async {
        final Directory? extDir = await getDownloadsDirectory();
        final testDir = await Directory(
          '${extDir!.path}/camerawesome',
        ).create(recursive: true);
        if (sensors.length == 1) {
          final String filePath =
              '${testDir.path}/${DateTime.now().millisecondsSinceEpoch}.jpg';
          return SingleCaptureRequest(XFile(filePath), sensors.first);
        } else {
          // Separate pictures taken with front and back camera
          return MultipleCaptureRequest({
            for (final sensor in sensors)
              sensor: XFile(
                '${testDir.path}/${sensor.position == SensorPosition.front ? 'front_' : "back_"}${DateTime.now().millisecondsSinceEpoch}.jpg',
              )
          });
        }
      },
    ),
);

One downside of this solution is that the app using CamerAwesome must also add a cross_file and a path_provider dependency to set a custom save path.

Maybe we could make this simpler ?


Property 'get' does not exist on type 'Lists'

I have created new webpart and installed @pnp/sp package.
I have tried to get lists from web but it is giving me error like "Property 'get' does not exist on type 'Lists'"
I have tried to get web title but still giving me error like "Property 'get' does not exist on type 'Web'"
Here is my code. I have created web part 2 days before with same code and which was working fine.
    var newWeb = new Web(WebUrl);
    return newWeb.lists.filter('Hidden eq false').get().then((data) => {
      this.RefreshPropertyPane();
    });

    var newWeb = new Web(WebUrl);
    return newWeb.select("title").get().then((data) => {
      return "";
    }).catch((exceptation) => {
     return "";
    });

Category

[ ] Question
[ ] Typo
[x ] Bug
[ ] Additional article idea

HI,
This issue was regarding PnP/SP package. Resolved by installing all PnP/sp packages in webpart using below command.
npm i @pnp/logging @pnp/common @pnp/odata @pnp/graph @pnp/nodejs


how to enable live reload

in flet docs i see code like this
appp(main,view=AppView.WEB_BROWSER,port=5050)
how to implement in you framework

LeftApp() launches the app - you use the flet_mode option to control how its deployed:
import flet as ft
LeftApp(
    ...
    flet_mode=ft.AppView.WEB_BROWSER)

Another way to control this (which I typically end up using as its more flexible), is to launch my program using the flet command line options.
# web, live reload, port 5000
flet -w -r -p 5000

# desktop, reload
flet -r

ok thx


Create a keyboard shortcut to close Preview.

Please Select if your Request is Either something new or an Enhancement

[ ] Enhancement of an existing Feature.
[X ] Request of a new feature.

Please select the area your request applys to. (Multiple selections are Possible)

[ ] Onboard. Initial vault setup and import/export pods
[X] Create. Note creation, lookup, snippets and templates
[ ] Retrieve. Backlinks, references, graph view
[ ] Structure. Refactoring, multi-vault and schemas
[ ] Publish. Sharing your repo with the world
[ ] Misc (Choose this if your not sure)

Is your feature request related to a problem? Please describe
Provide keyboard shortcuts to allow open and closing of HTML Markdown previews. Right now, I can type CTRL+K V, and the preview window will pop up. But if you then type CTRL+W it will close the note and not the preview window, unless you click on the preview window first.
Describe the solution you'd like
A keyboard shortcut that will always close the preview windows, regardless of where the cursor focus is.
Describe alternatives you've considered
I was trying to find  if I could set another keybinding and did not see one. Dendron: Show Preview  exists, but there is no Dendron: Hide Preview
Additional context
As I edit notes, I would like to pop open the Preview, see how it looks, and then close it and keep working without needing to take my hands off the keyboard.

Thanks @apastuszak for the suggestion - this seems like a useful command to add.  We'll prioritize against our backlog.

A dedicated Dendron keybinding to always close the preview regardless of what's focused would be great, but there are other ways to do it right now without taking your hands off the keyboard (maybe not as quick as a single shortcut though):

if you have just a single editor group, you can close the preview by Ctrl + 2 Ctrl + W; where Ctrl + 2 switches to the second editor group with the preview, and when the preview is closed, the focus goes back to the first editor group with your open note;
if you have just a single editor group, you can add a shortcut to the @command:workbench.action.closeEditorsInOtherGroups command to close the preview;
alternatively, you can do Ctrl + K Ctrl + Right Arrow Ctrl + W; where Ctrl + K Ctrl + Right Arrow focuses on the editor group to the right of the current one, which should be a preview. This is a bit longer than the first two sequences though;

IMO having toggle show/hide command is the most intuitive and convenient interface.

IMO having toggle show/hide command is the most intuitive and convenient interface.

I think the easiest way would be to have Dendron: Show Preview close the preview when called again. Maybe change the name to Dendron: Toggle Preview as well.

This issue is featured in this week's round of CROP voting on Dendron's Discord server.

This just got shipped in the 0.104 release.


application logs missing failed actions

Issue type
[ ] Feature request
[X] Bug report
[ ] Documentation
Environment

Python version:  3.5.2
NetBox version:  2.2.8

Description
The console/file log output of Netbox is limited to authentication events.
I'm currently trying to debug the API as used by NetboxClientRuby. I'm getting 403 errors where I don't think I should be when creating objects (the API token has full write privileges and my user can create objects in the web UI fine). Looking at the logs in /var/log/supervisor, all I see are my authentication events. Further, turning the logging up to DEBUG does not change the output.
403 Forbidden ({"detail"=>"You do not have permission to perform this action."})
I expect DEBUG level logging to include errors in object creation for any reason. Especially, 403s which should likely show up at INFO if not all the way up at ERROR.

I'd like to add another vote to this request.
Right now, I'm wiring a bunch of Python stuff to populate data in NetBox, but since I'm doing this via the API, there does not seem to be a good audit log for it.
I would argue that only the modify actions should be auditable, though, at DEBUG levels, where the implication of the performance impact is at least implied, even read APIs should be logged.

Still not clear on what you're asking for. Could you please provide example code that would accomplish what you're proposing?

@jeremystretch: Apologies. I am not a decent enough coder to actually do that.
I'll try to rephrase for more sanity. We are talking about taking, effectively, what is the "Recent Activity" feed and putting it out to a log (be it a file or SYSLOG). The change not currently there is also logging the API access(es).
Specifically, instead of:
2018-01-30 14:09 | Modified device server515
The log line would contain:
If modified via WebUI:
{"datetime":"2018-01-30T14:12:03-05:00", "user":"pm17788", "interface":"WebUI", "operation":"modify", "id":"dcim/devices/515", "data":{"name":"server515"}}
If modified via API:
{"datetime":"2018-01-30T14:12:03-05:00", "user":"pm17788", "interface":"API", "operation":"modify", "id":"dcim/devices/515", "data":{"name":"server515"}}
Basically, a full audit log of not only the operation performed, but what were the actual data items associated with the operation. If, for example, an Interface was created, then a full JSON of the data passed is what I'd expect in the logline.
It (probably) doesn't make sense to store this sort of an audit trail in a database - long-term storage requirements get silly, but IFF feasible, having more detail in the Recent Activity log would make sense for, say, past 7 days. If I want longer retention, I get to setup separate logging.
I hope this makes sense.

The UserAction stuff is slated to be overhauled entirely at some point (hopefully soon). #1127 has been open for a while now to convert it to use signals, but we need to go further than that. I might just expand that issue to cover this.

Cool! I would be quite willing to test, if that helps in any way.

Folding this into #1898


RC Test: Ratio and Proportion 1.2.0-rc.1

RC Test
Mentions: @emily-phet @terracoda @BLFiedler @jessegreenberg
Simulation links

github repository for issues
phet top level directory
sim: all_phet.html

Test Matrix

General Test Matrix

Features included

[x] Alternative Input
[x] UI Sound
[x] Sonification
[x] Description
[x] Voicing
[x] Camera input (please see https://github.com/phetsims/ratio-and-proportion/issues/488)

Focus and Special Instructions
Please note that we have dropped PhET-iO support for this release. Important features for testing are camera input: hands, and voicing, and especially how they interact together.

For QA...

General features

What to Test

Click every single button.
Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.

If there is sound, make sure it works.
Make sure you can't lose anything.
Play with the sim normally.
Try to break the sim.
Test all query parameters on all platforms. (See QA Book for a list of query parameters.)
Download HTML on Chrome and iOS.
Make sure the iFrame version of the simulation is working as intended on all platforms.
Make sure the XHTML version of the simulation is working as intended on all platforms.
Complete the test matrix.
Don't forget to make sure the sim works with Legends of Learning.
Test the Game Up harness on at least one platform.
Check this LoL
spreadsheet and notify AR or AM if it not there.
If this is rc.1 please do a memory test.
When making an issue, check to see if it was in a previously published version.
Try to include version numbers for browsers.
If there is a console available, check for errors and include them in the Problem Description.
As an RC begins and ends, check the sim repo. If there is a maintenance issue, check it and notify developers if there is a problem.
As the RC ends, please review the QA credits in the about dialog.  If the QA credits are complete and correct, please add a comment in the RC test issue indicating so.  If not, please open a new issue and specify what changes should be made.

Accessibility features

What to Test

Specific instructions can be found above.

Make sure the accessibility (a11y) feature that is being tested doesn't negatively affect the sim in any way. Here is
a list of features that may be supported in this test:

Alternative Input
Interactive Description
Sound and Sonification
Pan and Zoom
Mobile Description
Voicing

Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.
Test all keyboard navigation inputs (if applicable).
Test all forms of input with a screen reader (if applicable).

If this sim is not in this list or up to date there, make an
issue in website to ask if PhET research page links need updating. Please
assign to @terracoda and @emily-phet.

Screen Readers
This sim may support screen readers. If you are unfamiliar with screen readers, please ask Katie to introduce you to
screen readers. If you simply need a refresher on screen readers, please consult the
QA Book, which should have all of the information
you need as well as a link to a screen reader tutorial made by Jesse. Otherwise, look over the a11y view before opening
the simulation. Once you've done that, open the simulation and make sure alerts and descriptions work as intended.

Platforms and Screen Readers to Be Tested

Windows 10 + Latest Chrome + Latest JAWS
Windows 10 + Latest Firefox + Latest NVDA
macOS + Safari + VoiceOver
iOS + Safari + VoiceOver (only if specified in testing issue)

Critical Screen Reader Information
We are tracking known screen reader bugs in
here. If you find a
screen reader bug, please check it against this list.

Keyboard Navigation
This sim supports keyboard navigation. Please make sure it works as intended on all platforms by itself and with a
screen reader.
Magnification
This sim supports magnification with pinch and drag gestures on touch screens, keyboard shortcuts, and mouse/wheel controls. Please test magnfication and make sure
it is working as intended and well with the use cases of the simulation. Due to the way screen readers handle user input, magnification is NOT expected to
work while using a screen reader so there is no need to test this case.

FAQs for QA Members

There are multiple tests in this issue... Which test should I do first?
Test in order! Test the first thing first, the second thing second, and so on.

How should I format my issue?

We typically assign the developer who opened the issue in the QA repository.

My question isn't in here... What should I do?
You should:

Consult the QA Book.
Google it.
Ask Katie.
Ask a developer.
Google it again.
Cry.

Memory test

Sounds like a plan. Calling QA here.

Thanks! I think we are pretty close to a new RC, I'm hoping by the end of the week.


Create RSM HCD Nuget Organization

Create a new NuGet organization for RSM HCD. Name: rsm-hcd

Broken off from #52

Quick Q for discussion: What should we do with the old andculture NuGet org? Should we preserve the org or take it down? If we leave the org up, should we consider deprecating/unlisting the packages?

I'd say we leave as is.  Delisting, could potentially break anything that is currently depending on those versions.

Maybe we could deprecate the packages and point folks to the newer org, similar to what we're doing with GitHub?

If that's an option, let's go for it.

Added an organizational secret, NUGET_RSM_AUTH_TOKEN.  When the packages are updated in the repo and we are ready to publish, we can update the GH publish action to use the new token.


new Backups: VM IPs are not protected

Description
There is a possible race condition in the time window between the original VM termination and the instantiation of a new VM from the backup template.
To Reproduce
Restore VM Template from a backup
Terminate the original VM
Instantiate a new VM (for example, a new customer initiates a new VM from the same network pool)
Instantiate the Backup VM Template - it will fail because the IP is allocated to the VM that is instantiated before it.
Expected behavior
The Restored VM should have the same IP as the original one. The IP should not be allocated to another VM\
Details

Affected Component: [core]
Hypervisor: [KVM]
Version: [6.5.80]

Additional context
I think that the IPs are consumed on the first available basis from the Network pool. I think if this behaviour is changed somehow and the IPs are allocated sequentially. There is a better chance to request the same IP during instantiating. But some locking mechanism sounds much more promising.

Progress Status

[ ] Code committed
[ ] Testing - QA
[ ] Documentation (Release notes - resolved issues, compatibility, known issues)

I don't understand this one. This is the expected behavior, OpenNebula checks that there is only one IP in use; if another VM backup or not request it it will fail the allocation.
In case of a backup either, terminate the original VM or restore the template without IPs.
I don't see any missing functionality or bug here

Let's have a single network with one AR, <IP_ADDRESS>/24 size 200
User A creates a VM1 - it will get the first available IP <IP_ADDRESS>.
User A restore to a backup template VM1'. In the backup template, there is <IP_ADDRESS>.
User A terminate VM1 - then OpenNebula release the <IP_ADDRESS> to the AR, and it becomes as available
User B create a VM2 - OpenNebula will allocate <IP_ADDRESS> because it is the first available in the AR
User A instantiates VM1' from the backup VM' template - it will fail because the IP listed in the backup Template is already allocated to VM2.
AFAIK the ARs are related to the addresses defined in the VM metadata pool, not to the VM templates pool.

The solution is either, that the user makes a reservation so only she is able to use it. Using Network Templates is another option, so uses the self-service feature of VNETs
So this is not related specifically to backups but VNET multi-tenancy; which is covered by reservations and templates

Ahaa, but already allocated addresses could not be reserved? (they are reserved by the VMs)
Is there a solution to convert from a "flat" network allocation (I mean only VM allocations) to VM reservations?

Mmmmm not really the workflow is to make a Vnet reservation, (that will mark the IP/MAC as reserved) and then make the VMs to point to the VNET reservation.
Being able to add to a reservation an IP currently in use by an user is a nice feature though. We can add it to the backlog...
I'll reword this issue to address that feature if it covers the use case...

Definitely.
AFAIK there are a lot of old users where the VMs are not instantiated using this approach. So to use this backup workflow they need to be "migrated" somehow.
Also, I think the proposed feature https://github.com/OpenNebula/one/issues/6053 will elegantly mitigate this case. Or at least most of it?


Docker compose for fast start

ISA has many systems for works and will be cool to create Docker compose for start.

Please take a look on files
https://github.com/TinkoffCreditSystems/ISA/blob/master/build/docker-compose.yml
https://github.com/TinkoffCreditSystems/ISA/blob/master/scripts/docker.rebuild-and-run.cmd
Please feel free to reopen the issue if you need other tools and files.


Fixes #623 #170. Made Prewrite and scan iterators seek.  Added optimi…

…zation to remove Accumulo delete iterator.
This change required modifying how delete lock markers sorted.  The change to
delete lock markers was made to enable safely seeking over delete markers after
seeing the 1st delete lock marker.  The way delete lock markers sorted before
this change did not lend itself to safe seeking.
Also the timestamps used for delete lock markers was made much more consistent.
Tried to use the exact timestamp of the lock being deleted.

+1


Resizing rows in a ERD table freezes the app or does not work

Preflight Checklist

[ x] I agree to follow the Code of Conduct that this project adheres to.
[x ] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Describe the bug
I have a diagram with some ERD tables. I noticed the overall diagram was getting too big and that the default row height of the tables was a bit too high. So I resized the rows of one table colors from 30 to 20pt. No issues. Then I tried the next table color_types and when I selected a few rows and resized from 30 to 20pt the app either totally froze (repaints, but doesn't react to any input) or resized the table frame instead of the selected rows. You can not select rows without the table also being selected, so I guess that's related. No idea how it worked on the first table though.
After the resizing all arrows are wonky too, their "green magic points" have disappeared and it's no longer possible to get them to connect to the correct rows.
To Reproduce
Steps to reproduce the behavior:

Open attached diagram
Find table color_types
Try to resize one or more rows.
See the arrows coming to id of the color_types table. The magic connection points are gone from the entire table.

Expected behavior
The rows should resize to whatever I enter and the table itself should also resize to accommodate the new size(s) for the row(s). Arrows anchored to the row's green connectors should follow the resize operation and not randomly jump somewhere.
Screenshots
If applicable, add screenshots to help explain your problem.
draw.io version (In the Help->About menu of the draw.io editor):

draw.io version 13.9.9, desktop version

Desktop (please complete the following information):

OS: macOS Catalina
Browser: no browser, desktop version

database.drawio.zip

Does this still happen in latest build?


Add linting rules

Hey @gh0stwheel! Linting rules are here.
Summary:

Added linting rules
Fixed all errors, warnings, and format issues.
Updated the example's code to compile with the latest changes
Resolves: https://github.com/radicle-dev/drips-js-sdk/issues/22

Note: Code diff seems to be veeeery big but it's just the linting format rules applied that changed almost all lines in the relevant files. There are no "functional" changes 🤓
To validate the linting rules:

run npm install.
Break linting rules, for example in dripsClient.ts change a const to a let variable. and save (without formatting).
run npm run lint.
Validate that you see the relevant error in the console.
You can also run lint-and-fix and validate that it automatically fixes the errors.
(optional) To integrate linting with VSCode:

Install the Eslint extension.
Reload VSCode.
Repeat the first steps to break some linting rules.
Validate that you are seeing the errors in the editor like this:

VSCode also allows you to fix those errors from the editor.

To validate the formatting rules:

run npm install.
Break some code formatting, for example in dripsClient.ts break the indentation, remove some ";", etc. and save (without formatting)
run npx prettier --write .  .
Validate that dripsClient.ts was reformatted and saved.
(optional) To integrate prettier with VSCode:

Install the "Prettier - Code formatter" extension.
In your settings.json add the follwing:

"editor.formatOnSave": true
"editor.defaultFormatter": "esbenp.prettier-vscode",
"prettier.singleQuote": true,

Repeat the first steps and validate that the file is automatically formatted on save

@gh0stwheel OK this devil's package-lock.json file caused some weird issues 😜
It was faster to copy the changes into a new branch starting from a clean main.
 Is it okay to close this PR?

@jtourkos merged the changes from a different branch. So we're closing this now.


Display the inputted UoA Timetable

User Story
As a Student,
I want to see my inputted calendar displayed on TimeWeaver,
So that I can plan events and meetings.
Description
TimeWeaver after receiving calendar information after being parsed should be able to display those calendar values on the timetable.
Acceptance Criteria

[x] After inputting calendar I am able to view my calendar on TimeWeaver
[x] Display is visually pleasing

This is now complete 😄


GH-37148 [C++]: Explicitly list the integer values of the  Type::type enum

Rationale for this change
The enum type in C++ leaves the integer values implicitly defined and let the compiler assign the values to them automatically. This means an insertion of a new entry that is not a the end, causes implementations that rely on specific values (like R) to break with confusing error messages [1].
Assigning the values explicitly can communicate that these enum entry values are relied upon and can allow a more natural ordering of the list that is different from the numeric order the entries receive.
[1] https://github.com/apache/arrow/issues/37091
What changes are included in this PR?

Setting numeric values of the enum entries explicitly
Completing an equivalent enum on the R side

Are these changes tested?
N/A
Are there any user-facing changes?
No.

Closes: #37148

Would should we do about MAX_ID then?

Would should we do about MAX_ID then?

Leave it unset, so the compiler sets it to the maximum.

CI failures look to be a timeout and something with the dev script - I've re-triggered them both, but I think we can probably merge this once we're happy that's all they are?

@bkietz can you merge this?


charge-charge interaction

Is this pull request associated with an issue(s)?
No.
Description
Adds a module for computing the charge-charge interaction between two sets of point charges.
TODOs
None. R2g.

🚀 [bumpr] Bumped! New version:v0.0.5 Changes:v0.0.4...v0.0.5


Add a fix for mmc page allocation failures

The default maximum value for the number of segments in the MMC driver is too high. Set it to something more reasonable to avoid failing allocations under load.

@willnewton can we close this now since we have https://github.com/resin-os/resin-beaglebone/pull/105 and https://github.com/resin-os/resin-beaglebone/pull/106 which update the kernel to a version which has your patch included?


Broadcast notification

To test this with @cakesoft-shashank

Was not able to get a Push notification.
There was a notification in the notification panel nothing happened.
ideally, when a user clicks on a notification there should be a CTA  that should take the user to the play store to upgrade if the user wants.

created a new issue for this


It looks like a Clickup site change has broken the scraping in the plugin.

Hi,
It looks like a Clickup site change has broken the scraping in the plugin.
To fix:
function getSingleTaskDetails() {

const title = document.querySelector(".task-name__overlay").textContent;

const title = document.querySelector(".cu-task-title__overlay").textContent;
const [id] = location.pathname.split('/').reverse();
const link = location.href;

It works fine after that.
Cheers,
Casey

It works fine for my version of ClickUp 🤔
I think i'm just going to combine those selectors to support both worlds.

Are you on version 3.0 of the site? It may be a new layout.