6/15/2021 Publish

Docs Build status updates of commit 590897e:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-services/latest/ai-textanalytics-readme.md
:warning:Warning
View (azure-java-stable)
Details

docs-ref-services/latest/core-amqp-readme.md
:warning:Warning
View (azure-java-stable)
Details

docs-ref-services/latest/cosmos-readme.md
:warning:Warning
View (azure-java-stable)
Details

docs-ref-services/latest/data-appconfiguration-readme.md
:warning:Warning
View (azure-java-stable)
Details

docs-ref-services/latest/data-tables-readme.md
:warning:Warning
View (azure-java-stable)
Details

docs-ref-services/latest/messaging-eventhubs-checkpointstore-blob-readme.md
:warning:Warning
View (azure-java-stable)
Details

docs-ref-services/latest/messaging-eventhubs-readme.md
:warning:Warning
View (azure-java-stable)
Details

docs-ref-services/latest/messaging-servicebus-readme.md
:warning:Warning
View (azure-java-stable)
Details

docs-ref-services/preview/containers-containerregistry-readme.md
:warning:Warning
View (azure-java-preview)
Details

docs-ref-services/preview/cosmos-encryption-readme.md
:warning:Warning
View (azure-java-preview)
Details

docs-ref-services/preview/media-videoanalyzer-edge-readme.md
:warning:Warning
View (azure-java-preview)
Details

docs-ref-services/latest/ai-textanalytics-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': 'textanalytics'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 25, Column 110: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/text-analytics/overview' will be broken in isolated environments. Replace with a relative link.
Line 30, Column 5: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/java/azure/jdk/?view=azure-java-stable' will be broken in isolated environments. Replace with a relative link.
Line 30, Column 5: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/java/azure/jdk/?view=azure-java-stable. Otherwise, remove the view parameter.
Line 32, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/cognitive-services-apis-create-account?tabs=multiservice%2Cwindows' will be broken in isolated environments. Replace with a relative link.
Line 35, Column 30: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/cognitive-services-apis-create-account?tabs=multiservice%2Cwindows' will be broken in isolated environments. Replace with a relative link.
Line 41, Column 15: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/cognitive-services-apis-create-account?tabs=multiservice%2Cwindows#create-a-new-azure-cognitive-services-resource' will be broken in isolated environments. Replace with a relative link.
Line 43, Column 15: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/cognitive-services-apis-create-account-cli?tabs=windows' will be broken in isolated environments. Replace with a relative link.
Line 86, Column 4: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure/cognitiveservices/account?view=azure-cli-latest#az-cognitiveservices-account-show' will be broken in isolated environments. Replace with a relative link.
Line 86, Column 4: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/cli/azure/cognitiveservices/account?view=azure-cli-latest#az-cognitiveservices-account-show. Otherwise, remove the view parameter.
Line 93, Column 33: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/cognitive-services-apis-create-account?tabs=multiservice%2Cwindows#get-the-keys-for-your-resource' will be broken in isolated environments. Replace with a relative link.
Line 137, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/authentication#assign-a-role-to-a-service-principal' 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/cognitive-services/authentication#assign-a-role-to-a-service-principal' will be broken in isolated environments. Replace with a relative link.
Line 147, Column 10: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/authentication#authenticate-with-azure-active-directory' will be broken in isolated environments. Replace with a relative link.
Line 168, Column 5: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/text-analytics/overview#data-limits' will be broken in isolated environments. Replace with a relative link.
Line 237, Column 74: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/text-analytics/how-tos/text-analytics-how-to-sentiment-analysis' will be broken in isolated environments. Replace with a relative link.
Line 250, Column 74: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/text-analytics/how-tos/text-analytics-how-to-language-detection' will be broken in isolated environments. Replace with a relative link.
Line 262, Column 74: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/text-analytics/how-tos/text-analytics-how-to-keyword-extraction' will be broken in isolated environments. Replace with a relative link.
Line 267, Column 17: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/Text-Analytics/named-entity-types' will be broken in isolated environments. Replace with a relative link.
Line 277, Column 74: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/text-analytics/how-tos/text-analytics-how-to-entity-linking' will be broken in isolated environments. Replace with a relative link.
Line 296, Column 74: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cognitive-services/text-analytics/how-tos/text-analytics-how-to-entity-linking' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/core-amqp-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'.
Line 24, Column 5: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/java/azure/jdk/?view=azure-java-stable' will be broken in isolated environments. Replace with a relative link.
Line 24, Column 5: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/java/azure/jdk/?view=azure-java-stable. Otherwise, remove the view parameter.

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': 'cosmosdbcosmosdb'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 18, Column 64: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/sql-api-sql-query' will be broken in isolated environments. Replace with a relative link.
Line 18, Column 92: [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 20, Column 115: [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 42, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/java/azure/jdk/' will be broken in isolated environments. Replace with a relative link.
Line 43, Column 391: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/local-emulator-export-ssl-certificates' will be broken in isolated environments. Replace with a relative link.
Line 80, Column 57: [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 86, Column 45: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/distribute-data-globally' will be broken in isolated environments. Replace with a relative link.
Line 91, Column 49: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/set-throughput' will be broken in isolated environments. Replace with a relative link.
Line 98, Column 39: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/request-units' will be broken in isolated environments. Replace with a relative link.
Line 105, Column 39: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/partitioning-overview' will be broken in isolated environments. Replace with a relative link.
Line 209, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/performance-tips-java-sdk-v4-sql?tabs=api-async' will be broken in isolated environments. Replace with a relative link.
Line 211, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/troubleshoot-java-sdk-v4-sql' will be broken in isolated environments. Replace with a relative link.
Line 253, Column 14: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/create-sql-api-java?tabs=sync' will be broken in isolated environments. Replace with a relative link.
Line 254, Column 3: [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.

docs-ref-services/latest/data-appconfiguration-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': 'appconfiguration'.
Line 22, Column 1: [Warning-table-syntax-invalid] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 23, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/azure-app-configuration' will be broken in isolated environments. Replace with a relative link.
Line 29, Column 5: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/java/azure/jdk/?view=azure-java-stable' will be broken in isolated environments. Replace with a relative link.
Line 29, Column 5: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/java/azure/jdk/?view=azure-java-stable. Otherwise, remove the view parameter.
Line 31, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/azure-app-configuration/quickstart-dotnet-core-app#create-an-app-configuration-store' will be broken in isolated environments. Replace with a relative link.
Line 47, Column 65: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 71, Column 9: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 108, Column 6: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/cli/azure' will be broken in isolated environments. Replace with a relative link.
Line 137, Column 30: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/azure-app-configuration/rest-api-authorization-azure-ad#roles' will be broken in isolated environments. Replace with a relative link.
Line 408, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/azure-app-configuration/quickstart-java-spring-app' will be broken in isolated environments. Replace with a relative link.

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 18, Column 1: [Warning-table-syntax-invalid] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 19, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/table-storage-overview' will be broken in isolated environments. Replace with a relative link.
Line 37, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/java/azure/jdk/' will be broken in isolated environments. Replace with a relative link.
Line 42, Column 45: [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 42, Column 94: [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 55, Column 57: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/create-table-java#create-a-database-account' will be broken in isolated environments. Replace with a relative link.
Line 55, Column 99: [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 222, Column 196: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/rest/api/storageservices/querying-tables-and-entities#supported-query-options' will be broken in isolated environments. Replace with a relative link.
Line 276, Column 212: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/rest/api/storageservices/querying-tables-and-entities#supported-query-options' will be broken in isolated environments. Replace with a relative link.
Line 305, Column 165: [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.

docs-ref-services/latest/messaging-eventhubs-checkpointstore-blob-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 21, Column 81: [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 28, Column 5: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/java/azure/jdk/?view=azure-java-stable' will be broken in isolated environments. Replace with a relative link.
Line 28, Column 5: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/java/azure/jdk/?view=azure-java-stable. Otherwise, remove the view parameter.
Line 33, Column 30: [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 35, Column 30: [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 53, Column 68: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/storage/common/storage-dotnet-shared-access-signature-part-1' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/messaging-eventhubs-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 38, Column 3: [Warning-bookmark-not-found] Cannot find bookmark '#azure-event-hubs-client-library-for-java' in 'docs-ref-services/latest/messaging-eventhubs-readme.md'.
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 33, Column 81: [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 60, Column 5: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/java/azure/jdk/?view=azure-java-stable' will be broken in isolated environments. Replace with a relative link.
Line 60, Column 5: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/java/azure/jdk/?view=azure-java-stable. Otherwise, remove the view parameter.
Line 65, Column 28: [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 88, Column 1: [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 128, Column 4: [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 167, 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 397, Column 1: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/event-hubs/event-hubs-messaging-exceptions' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/latest/messaging-servicebus-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': 'servicebus'.
Line 45, Column 2: [Warning-alt-text-missing] Missing alternate text for image 'http://azuredeploy.net/deploybutton.png'. Alt text is required for accessibility.
Line 160, Column 4: [Warning-bookmark-not-found] Cannot find bookmark '#receive-messages-and-renew-lock' in 'docs-ref-services/latest/messaging-servicebus-readme.md'.
Line 161, Column 4: [Warning-bookmark-not-found] Cannot find bookmark '#settle-messages' in 'docs-ref-services/latest/messaging-servicebus-readme.md', did you mean '#send-messages'?
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 20, Column 50: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/service-bus-messaging' will be broken in isolated environments. Replace with a relative link.
Line 30, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/service-bus-messaging' will be broken in isolated environments. Replace with a relative link.
Line 36, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/java/azure/jdk/?view=azure-java-stable' will be broken in isolated environments. Replace with a relative link.
Line 36, Column 3: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/java/azure/jdk/?view=azure-java-stable. Otherwise, remove the view parameter.
Line 41, Column 28: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/service-bus-messaging/service-bus-create-namespace-portal' will be broken in isolated environments. Replace with a relative link.
Line 68, Column 1: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/service-bus-messaging/service-bus-create-namespace-portal#get-the-connection-string' will be broken in isolated environments. Replace with a relative link.
Line 119, Column 10: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/service-bus-messaging/authenticate-application' will be broken in isolated environments. Replace with a relative link.
Line 139, Column 7: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/service-bus-messaging/service-bus-messaging-overview#queues' will be broken in isolated environments. Replace with a relative link.
Line 141, Column 7: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/service-bus-messaging/service-bus-messaging-overview#topics' will be broken in isolated environments. Replace with a relative link.
Line 143, Column 7: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/service-bus-messaging/service-bus-queues-topics-subscriptions#topics-and-subscriptions' will be broken in isolated environments. Replace with a relative link.
Line 234, Column 44: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/service-bus-messaging/service-bus-dead-letter-queues' will be broken in isolated environments. Replace with a relative link.
Line 241, Column 22: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/service-bus-messaging/message-sessions' will be broken in isolated environments. Replace with a relative link.
Line 278, Column 73: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/service-bus-messaging/service-bus-dead-letter-queues' will be broken in isolated environments. Replace with a relative link.
Line 367, Column 1: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/service-bus-messaging/service-bus-messaging-exceptions' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/preview/containers-containerregistry-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': 'containerregistry'.
Line 128, Column 3: [Warning-bookmark-not-found] Cannot find bookmark '#samples' in 'docs-ref-services/preview/containers-containerregistry-readme.md', did you mean '#examples'?
Line 129, Column 3: [Warning-bookmark-not-found] Cannot find bookmark '#samples' in 'docs-ref-services/preview/containers-containerregistry-readme.md', did you mean '#examples'?
Line 130, Column 3: [Warning-bookmark-not-found] Cannot find bookmark '#samples' in 'docs-ref-services/preview/containers-containerregistry-readme.md', did you mean '#examples'?
Line 131, Column 3: [Warning-bookmark-not-found] Cannot find bookmark '#samples' in 'docs-ref-services/preview/containers-containerregistry-readme.md', did you mean '#examples'?
Line 132, Column 3: [Warning-bookmark-not-found] Cannot find bookmark '#samples' in 'docs-ref-services/preview/containers-containerregistry-readme.md', did you mean '#examples'?
Line 136, Column 3: [Warning-bookmark-not-found] Cannot find bookmark '#samples' in 'docs-ref-services/preview/containers-containerregistry-readme.md', did you mean '#examples'?
Line 137, Column 3: [Warning-bookmark-not-found] Cannot find bookmark '#samples' in 'docs-ref-services/preview/containers-containerregistry-readme.md', did you mean '#examples'?
Line 138, Column 3: [Warning-bookmark-not-found] Cannot find bookmark '#samples' in 'docs-ref-services/preview/containers-containerregistry-readme.md', did you mean '#examples'?
Line 139, Column 3: [Warning-bookmark-not-found] Cannot find bookmark '#samples' in 'docs-ref-services/preview/containers-containerregistry-readme.md', did you mean '#examples'?
Line 140, Column 3: [Warning-bookmark-not-found] Cannot find bookmark '#samples' in 'docs-ref-services/preview/containers-containerregistry-readme.md', did you mean '#examples'?
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 26, Column 59: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/container-registry' will be broken in isolated environments. Replace with a relative link.
Line 32, Column 5: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/java/azure/jdk/?view=azure-java-stable' will be broken in isolated environments. Replace with a relative link.
Line 32, Column 5: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/java/azure/jdk/?view=azure-java-stable. Otherwise, remove the view parameter.
Line 34, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/container-registry/container-registry-get-started-azure-cli' will be broken in isolated environments. Replace with a relative link.
Line 52, Column 21: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/container-registry/container-registry-get-started-portal' will be broken in isolated environments. Replace with a relative link.
Line 72, Column 91: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/container-registry/container-registry-authentication' will be broken in isolated environments. Replace with a relative link.
Line 75, Column 38: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/active-directory/develop/authentication-national-cloud' will be broken in isolated environments. Replace with a relative link.
Line 102, Column 34: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/container-registry/container-registry-faq#how-do-i-enable-anonymous-pull-access' will be broken in isolated environments. Replace with a relative link.
Line 122, Column 33: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/container-registry/container-registry-concepts' will be broken in isolated environments. Replace with a relative link.
Line 272, Column 23: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/container-registry/container-registry-intro' will be broken in isolated environments. Replace with a relative link.

docs-ref-services/preview/cosmos-encryption-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 60, Column 3: [Warning-bookmark-not-found] Cannot find bookmark '#create-encryption-database' in 'docs-ref-services/preview/cosmos-encryption-readme.md'.
Line 61, Column 3: [Warning-bookmark-not-found] Cannot find bookmark '#create-encryption-container' in 'docs-ref-services/preview/cosmos-encryption-readme.md'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 17, Column 148: [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 40, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/java/azure/jdk/' will be broken in isolated environments. Replace with a relative link.
Line 41, Column 391: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/local-emulator-export-ssl-certificates' will be broken in isolated environments. Replace with a relative link.
Line 54, Column 57: [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 157, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/performance-tips-java-sdk-v4-sql?tabs=api-async' will be broken in isolated environments. Replace with a relative link.
Line 159, Column 3: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/troubleshoot-java-sdk-v4-sql' will be broken in isolated environments. Replace with a relative link.
Line 200, Column 41: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/azure/cosmos-db/create-sql-api-java?tabs=sync' will be broken in isolated environments. Replace with a relative link.
Line 201, Column 3: [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.

docs-ref-services/preview/media-videoanalyzer-edge-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': 'videoanalyzer'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

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


Extensions are missing

Extensions are missing after recreating VM in new VMSet. They are missing from extensions blade.

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

ID: 7eed234f-9a8d-4c1b-2368-fe4c8fbe8299
Version Independent ID: 876980d5-e42c-b070-c0a6-73ed3f2c91d1
Content: Change a VMs availability set
Content Source: articles/virtual-machines/windows/change-availability-set.md
Service: virtual-machines-windows
GitHub Login: @zr-msft
Microsoft Alias: zarhoads

@anandta Thanks for the feedback! We are currently investigating and will update you shortly.

Thank you Karishma. Specially concerned about JsonADDomain extension

Thank you Karishma. Specially concerned about JsonADDomain extension

@zr-msft It looks like the extensions are not retained after recreating VM with availability set.
@anandta has a CSS case open and he wants to confirm if this is a doc-bug or product issue so that he can take the next steps.

test


PCI DSS Tweaks

Amended PCI DSS content in line with Bryan Scaife email from 12 October 2017

Thanks Rory. I would keep referring to the external guidance for the SAQ A otherwise we'll have an additional maintenance overhead; happy to discuss if necessary.


[Task] how to batch export or import monitoring settings, batch tag or group settings

Description
This is a very good project. We want to test it in some scenarios and hope it can support

Support batch export or import monitoring settings

Support batch tag or group settings

Task List
-[1]  batch export or import monitoring settings
-[2]  batch tag or group settings

hi, weclome to use. These features not support now, but batch export or import monitoring would be added in roadmap!

hi, this feature has supported.


Remove unused imports

Thank you for the clean-up! Is this being done in the service of some larger objective or just because you noticed it and saw the chance to make it right?

Many of these are bog standard import removals.  However some of these imports may have side effects that I am not aware of.
I am especially unsure about whether these import six are needed, as I dont know it well enough to say it has no side effects that are needed by these modules.  From my reading of the six docs, its sys.modules and sys.meta_path hacks dont have relevant side effects.
I also dont know mock very well, but 4d020992b3 appears to have intentionally removed the use of mock when test code was moved, but the import was left behind.
And the tests all pass.

My objective is to fix the code quality of https://github.com/shazow/urllib3/blob/master/_travis/fetch_gae_sdk.py , so I am fixing the issues upstream; i.e. here.   #328 was part of that.  Happy to fix other issues while I am here.

If any of our imports have side effects of which we're not aware and removing those imports breaks us we are Bad People Who Deserve What We Get™. Any imports that are needed only for their side effects and our textually unused in the file in which they appear should be clearly commented as such, though of course it's better to have no such imports at all.
Thank you for running the tests. I intend to merge this after our Travis run turns green.
Glad to have you contributing improvements no matter the reason. :+1:

I can "confirm" that none of the imports have implicit behavior that oauth2client depends on.

Don't worry about the drop in coverage, it's just math:
(A - n) / (B - n) < A / B
<==>
(A - n) B < A (B - n)
<==>
- Bn < -An
<==>
A < B


updating default expansion for openshift toc

@sakthi-vetrivel Quick update to modify the default expansion so the Overview and Tutorial topics are shown. I think this just got overlooked, but if you feel differently please let me know.

#sign-off looks good to me!

@sakthi-vetrivel: I'm sorry - only the author of this article, @, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

I made a test PR in the private repo and the updated file renders OK on staging; merging.


radarr anime logo - text & mobile

radarr-anime-logo
I hope to find the .psd file used as the source, so I can upload it someday.

radarr-anime.png contains 900x292 .png file.
The version on a white background isn't great, but neither is the one for 4K.

radarr-anime-mobile.png contains 900x900 .png file.
Even here, the version on a white background isn't great, but mine is a bit better than the 4K one. 😅.

Please rebase to develop


Improve CQ Statements by :Name aliases

Copied issue from old internal github.
See https://github.com/influxdata/influxdb/issues/7332
The Idea is to use a influx-keyword to retain the original field name if you use a aggregate function like mean(*). Currently it appends a prefix everywhere, the only way to keep the old name is to manually place an alias behind each query: mean(cpu) as cpu.
This workarround is currently in place, but requires a lot of lines of code and makes the code way harder to maintenance. Once the Issue of influxdb is resolved, it should be quite easy to look into this again.
Until then: Blocked.
The requirement for the same naming are the different retention policies. To have the 90 day dashboard switch between 90 days and INF, it is required to have exactly the same field names. Otherwise another dashboard is required, which makes the Grafana dashboards even harder to update.

I've noticed that not every calculation is an exact rename. On some downsamples I've named them if using a sum function with the prefix sum_. This could create some issue when using the 90-days dashboard on INF scale.
This should not be an issue, if starting on the 14 day scale, since the 90 day dashboard only affects the 90/inf-RP where it would be the same.
If we start experience issues there I will have to remove the prefix from all downsamples 90 days to INF, where those names arn't exactly the same.

This feature is irrelevant for now, as tags and fields are named differently.
Not of importance, as it does not add any extra benefit.


Fix #210: matrix multiplication of array of vectors

I took at stab at fixing #210.  Not sure if I did it right, the variable names were confusing.  But I think I'm on to something.

Hi there @cspotcode
thank you for the help!
And kudos for getting behind the code I have written for the array class.
It's certainly not easy to read.
I tweaked your solution a little by moving the data pointers for each iteration of the outmost for-loop, instead of re-calculating the same operation for each iteration of the inner for-loop. This should be slightly more efficient.


FormFlow confirmation incorrect options

Bot Info

SDK Platform: .Net
SDK Version: 3.13.1
Active Channels: any
Deployment Environment: any

Issue Description
When I have a FormFlow with a confirmation question to which I answer "No", I get a correction dialog as displayed in the screenshot. It strikes me as odd that I get "No Preference" as the last choice. Shouldn't it be something to the effect of "Cancel" or "No changes"? Likewise, in German I get a very colloquial "Who cares?" (Egal). In Chinese I get "casual"?
While you're at it: I think there should also be a blank between the field to be changed and its current value.

Code Example
    public static IForm<WeightForm> BuildLocalizedForm()
    {
        var form = new FormBuilder<WeightForm>()
            .Message("Let's record your weight.")
            .Field(nameof(WeightQuantity))
            .Field(nameof(WeightUnit))
            .Confirm("Is it okay for me to record your weight as {WeightQuantity} {WeightUnit}? {||}")
            .Build();

        return form;
    }

I just tried to reproduce this and was unable, can you please include your whole form class.  Also if you see a fix please feel free to submit a pull request so that we can review the requested changes.

@JasonSowers here it comes, see the attachment. I have done some digging, and I think the culprit is the use and translation of the TemplateNoPreference resource in this built-in change dialog.
From a semantic standpoint, I am not sure what it is supposed to mean that I have "no preference" what I would like to change? That the bot is free to change whatever it pleases?
In my mind, the dialog should display:
What do you want to change?

Weight (85)
Weight Unit (lb)
No changes

WeightForm.zip
The German translation is a tricky cultural issue where your product management would probably have to define the target audience of your average bot. Right now, all the German translations are written in a language that targets a teenage to college age audience. "Egal" is what you would hear from your teenage kid when they have lost all interest in the world and want you to go away :-)

There is supposed to be a way to do this using the attribute [Template(TemplateUsage.NoPreference, "Your text")] on your class, but it is not working as expected for me. So we will be looking into this deeper and seeing if it is a bug or not.  Will let you know what we find

We are still looking into this, we think we found the reason this is not working.  The person that wrote formflow is out this week though, so we will have to wait for him to get back to come to a resolution.

FormConfiguration determines the NoPreference template.  As well as MatchNoPreference.  This can be found here: https://github.com/Microsoft/BotBuilder/blob/b7b2abbd089b0c0b91f367e4355743f7171dbc26/CSharp/Library/Microsoft.Bot.Builder/FormFlow/IFormBuilder.cs#L390
It can be overridden like:
public static IForm<WeightForm> BuildLocalizedForm()
{
    // TODO: Cache the localized forms as shown here: https://docs.microsoft.com/en-us/bot-framework/dotnet/bot-builder-dotnet-formflow-localize

    var form = new FormBuilder<WeightForm>()
        .Message("Let's record your weight.")
        .Field(nameof(WeightQuantity))
        .Field(nameof(WeightUnit))
        .Confirm("Is it okay for me to record your weight as {WeightQuantity} {WeightUnit}? {||}");

    var noPrefTemplate = form.Configuration.Templates.Find(t => t.Usage == TemplateUsage.NoPreference);
    noPrefTemplate.Patterns = new[] { "No Changes" };
    form.Configuration.NoPreference = new[] { "No Changes" };

    return form.Build();
}

Closing the issue assuming it as resolved. Please reopen a new issue if it still persists.


Mwpw 161560 remove html size

before: https://stage--dme-partners--adobecom.hlx.page/channelpartners/home/search/
after: https://MWPW-161560-remove-html-size--dme-partners--adobecom.hlx.page/channelpartners/home/search/?georouting=off

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 82.68%. Comparing base (641146a) to head (b6a3783).

Additional details and impacted files
@@           Coverage Diff           @@
##            stage     #119   +/-   ##
=======================================
  Coverage   82.68%   82.68%
=======================================
  Files          10       10
  Lines        3246     3246
=======================================
  Hits         2684     2684
  Misses        562      562

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


When installing with Docker, is there a way to pass host information to an external PVE as an environment variable?

When installing with Docker, I want to be able to call the API from an external Docker server without configuring PVE locally.
PVE_HOST: "https://<IP_ADDRESS>:8006" Even if I do this, the host information looks at localhost.
I wonder if there is a way to install only node_exporter in PVE and install prometheus-pve-exporter externally using docker.

From the README:

Visit http://localhost:9221/pve?target=<IP_ADDRESS>&cluster=1&node=1 where <IP_ADDRESS> is the IP of the Proxmox VE node to get metrics from. Specify the module request parameter, to choose which module to use from the config file.

hence, please point the target argument towards your PVE host. Also please take note of the example configurations at the bottom of the README. Especially take a look at Example config for PVE exporter running on Prometheus host. This example shows how to use relabelling in order to populate the target argument when scraping.


Outlines sometime not available

On some .py files I can see it, on others I cannot.
OSX 10.13.6
Atom 1.8.2 x64
ide-python 0.10.0 (downgraded because of the challenges brought up here https://github.com/lgeiger/ide-python/issues/119)
What more information can I provide?

Could you provide a minimal code sample where the outline isn't working?
Alternatively could you enable debug messages by executing atom.config.set('core.debugLSP', true) in the Developer Tools Console and post a screenshot of the console output when this issue occurs? You might need to restart Atom in order to see the debug messages.

I have the same issue here, it does not work for most of the files this is a sample file
class Test(object):
    """docstring for Test."""

    def __init__(self, arg):
        super(Test, self).__init__()
        self.arg = arg
    def test(self, arg):
        print("hy")

It says in the outline No Outline available Python Django files do not currently support outlines. Install and IDE package first
Auto-complete works well but not outline is available.
I have Ubuntu 18.04.2, atom 1.35.1 and latest IDE package.
I executed atom.config.set('core.debugLSP', true) and restarted atom but now output is displayed.

No Outline available Python Django files do not currently support outlines. Install and IDE package first

@mohsenSy It looks like you are using a django atom package that switches your syntax highlighting of python files to a custom django syntax. This means actually ide-python is not running since it doesn't recognize the custom django grammar. Could you try disabling the django specific atom packages and try again?

@lgeiger Thanks a lot it worked now. You think this bug is related to Django package??
However when I open a python file I get this error pylama provided path does not exist.
I am sure pylama is installed in /usr/bin/pylama I can use it in my terminal, how can I fix this?


Enable issues for RuleWorld/PyBioNetGen

I posted issues here because issues are not enabled for https://github.com/RuleWorld/PyBioNetGen. Enabling issues at https://github.com/RuleWorld/PyBioNetGen would encourage people to post issues there.

Didn't realize that was the case, I guess it's because it's under another username. It's enabled now.


Tyche - Redeem Fixes

@0xLienid Can you rebase off tyche?

@0xJem should be good to go

@0xLienid I think we discussed this today. I've asked Indigo whether we can roll back the mock sOHM changes. Can you get this up to date with tyche?

Not needed anymore https://github.com/OlympusDAO/olympus-frontend/pull/902 covers this.


Set HDF5_PLUGIN_PATH to a folder existing on GH CI

Fixes some failing tests from Maxwell due to the non-existence of the default HDF5_PLUGIN_PATH folder

@samuelgarcia can you merge this?


Python support for >=3.11?

I am trying to test turnkey-ml with https://huggingface.co/google/gemma-2-9b.
I am trying to do a pip install but got the following error:
ERROR: Ignored the following versions that require a different python version: 0.3.0 Requires-Python >=3.8, <3.11; 1.0.0 Requires-Python >=3.8, <3.11; 1.1.0 Requires-Python >=3.8, <3.11; 1.1.1 Requires-Python >=3.8, <3.11; 1.1.2 Requires-Python >=3.8, <3.11; 1.1.3 Requires-Python >=3.8, <3.11; 2.0.0 Requires-Python >=3.8, <3.11; 2.0.1 Requires-Python <3.11,>=3.8; 2.0.2 Requires-Python <3.11,>=3.8; 2.0.3 Requires-Python <3.11,>=3.8
Is Python>=3.11 supported?
@jeremyfowers

Hey Justin, sorry for the slow reply, I was on vacation. We just don't test with Python 3.11. Let me try making a branch and see if it works.

It looks like we have at least one dependency (scikitlearn 1.1.1) that isn't compatible with Python 3.11. I will take care of this as part of the bigger repo refresh I have been working on.


update maestro-shell

Update maestro-shell to include wifi support

@mray190 The previous PR did not update maestro-shell to the correct SHA. This PR will update it to latest dev branch of maestro-shell.

@psppalash need a fix to pass CI

@psppalash need a fix to pass CI

@mray190 Is the build failing?

@psppalash, take a look... seems CI failed.  Reach out if you need help figuring it out.

Thanks @mray190 @ryannowarm Looks like the build failed. The CI link was not working for me earlier so I didn't know what was wrong.
Will fix the build issue.

This PR will fix the build issue https://github.com/armPelionEdge/maestro-shell/pull/18

@mray190 I am not sure why the third check is stuck at "pending". An idea what is failing?

@mray190 This PR is ready to be merged now.


Add MIT license

https://github.com/brianamarie/10-git-problems/issues/2

Major thanks! 👏 Very appreciated, @eyarz.


Can not run tests when using preact compat alias

Describe the bug
When package tries to import react by alias, it picks CJS version of preact specific module, which leads to following error:
 FAIL  src/app.test.tsx > should render app
TypeError: Cannot read properties of undefined (reading '__H')
 ❯ l node_modules/preact/hooks/dist/hooks.js:1:201
 ❯ d node_modules/preact/hooks/dist/hooks.js:1:600
 ❯ Object.exports.useRef node_modules/preact/hooks/dist/hooks.js:1:2323
 ❯ d.BrowserRouter [as constructor] node_modules/react-router-dom/umd/react-router-dom.development.js:80:28
 ❯ d.O [as render] ../../../../../../../../../C:/Users/wight/Documents/preact-vitest-repro/node_modules/preact/dist/preact.mjs:1:8158
 ❯ j ../../../../../../../../../C:/Users/wight/Documents/preact-vitest-repro/node_modules/preact/dist/preact.mjs:1:5870
 ❯ w ../../../../../../../../../C:/Users/wight/Documents/preact-vitest-repro/node_modules/preact/dist/preact.mjs:1:2137
 ❯ j ../../../../../../../../../C:/Users/wight/Documents/preact-vitest-repro/node_modules/preact/dist/preact.mjs:1:6138
 ❯ P ../../../../../../../../../C:/Users/wight/Documents/preact-vitest-repro/node_modules/preact/dist/preact.mjs:1:8272
 ❯ ../../../../../../../../../C:/Users/wight/Documents/preact-vitest-repro/node_modules/@testing-library/preact/dist/esm/pure.mjs:52:7

Reproduction
https://github.com/wight554/preact-vitest-repro/
System Info
System:
    OS: Windows 10 10.0.22621
    CPU: (16) x64 AMD Ryzen 7 3700X 8-Core Processor
    Memory: 16.89 GB / 31.93 GB
  Binaries:
    Node: 16.14.0 - c:\program files\nodejs\node.EXE
    Yarn: 1.22.4 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 8.3.1 - c:\program files\nodejs\npm.CMD
  Browsers:
    Chrome: 103.0.5060.114
    Edge: Spartan (44.22621.290.0), Chromium (103.0.1264.49)
    Internet Explorer: 11.0.22621.1
  npmPackages:
    vite: ^3.0.0 => 3.0.0
    vitest: ^0.18.0 => 0.18.0

Used Package Manager
yarn
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I've checked https://github.com/preactjs/compat-alias-package, it seems to have proper exports. Can't really tell why this happens

I see that the error is coming from react-router-dom. Have you tried using deps.inline with it? Currently files inside node_modules are not processed by Vite. They are executed by Native Node without any transforming.

I see that the error is coming from react-router-dom. Have you tried using deps.inline with it? Currently files inside node_modules are not processed by Vite. They are executed by Native Node without any transforming.

This config:
    deps: {
      inline: ['react-router-dom'],
    }

Produces exactly the same error, with this config:
    deps: {
      inline: true,
    }

I get error:
 FAIL  src/app.test.tsx > should render app
Unknown Error: undefined
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯

Test Files  1 failed (1)
     Tests  1 failed (1)
      Time  2.13s (in thread 6ms, 35558.00%)

Other than react-router-dom I faced this error with styled components and recoil and probably other libraries that rely on react

Tried https://preactjs.com/guide/v10/getting-started#aliasing-in-rollup instead of alias package - this works in vite, but doesn't work in vitest even with https://github.com/vitest-dev/vitest/pull/1634

Tried https://preactjs.com/guide/v10/getting-started#aliasing-in-rollup instead of alias package - this works in vite, but doesn't work in vitest even with https://github.com/vitest-dev/vitest/pull/1634

Please, read again: Currently files inside node_modules are not processed by Vite. They are executed by Native Node without any transforming.
If it doesn't work, that it needs investigating. Aliasing WILL NOT WORK, if file is not processed by Vite.

One of the solutions from https://vitejs.dev/guide/ssr.html#ssr-externals:

If you have configured aliases that redirects one package to another, you may want to alias the actual node_modules packages instead to make it work for SSR externalized dependencies. Both Yarn and pnpm support aliasing via the npm: prefix.

One of the solutions from https://vitejs.dev/guide/ssr.html#ssr-externals:

If you have configured aliases that redirects one package to another, you may want to alias the actual node_modules packages instead to make it work for SSR externalized dependencies. Both Yarn and pnpm support aliasing via the npm: prefix.

tried all possible ways to add react or @preact/compat to deps.inline/ssr.noExternal, this doesn't work, tried these:
['@preact/compat', 'react', 'react-dom', "npm:@preact/compat"]
always same error

tried all possible ways to add react or @preact/compat to deps.inline/ssr.noExternal, this doesn't work, tried these: ['@preact/compat', 'react', 'react-dom', "npm:@preact/compat"] always same error

No, Vite recommends defining react inside package.json with npm prefix. Please, follow provided links to yarn or pnpm documentation.

Note: I understand deps.inline throws error, this is unrelated to aliasing.

If I add this to /node_modules/react-router/package.json, everything works fine:
  "exports": {
    ".": {
      "import": "./index.js"
    }
  }

This means that react-router doesn't package their library with Node ESM in mind. I checked they bundle ESM for browser, but it's incompatible with Node, as it doesn't have .mjs extension or package.json with type: module. See more here.
I wan't able to make your reproduction run, so I would recommend opening an issue in react-router package for now.

I wan't able to make your reproduction run

Weird, yarn install + npx vitest run works fine for me on several devices

I would recommend opening an issue in react-router

The thing is, there at least 4 more libraries in my main project with such issue and dealing with all of those this way takes ages to complete, would be way better to see some workaround (at least temporal)

Weird, yarn install + npx vitest run works fine for me on several devices

I mean, I wasn't able to fix it.

The thing is, there at least 4 more libraries in my main project with such issue and dealing with all of those this way takes ages to complete, would be way better to see some workaround (at least temporal)

I proposed several workarounds. The main problem with all of them I guess is the wrong package.json configuration. You can try and manually setup test.alias for your packages. PR https://github.com/vitest-dev/vitest/pull/1673 should help with the problem, but it won't fix it, if package has wrong package.json, and you will still need to add aliases. Until we merge the PR, alias will only be applied if files are inlined.

If I add this to /node_modules/react-router/package.json, everything works fine

tried doing this, getting this error:
 FAIL  src/app.test.tsx [ src/app.test.tsx ]Error: No "exports" main defined in C:\Users\wight\Documents\preact-vitest-repro\node_modules\react-router\package.json
 ❯ node_modules/react-router-dom/umd/react-router-dom.development.js:12:121
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯Serialized Error: {
  "code": "ERR_PACKAGE_PATH_NOT_EXPORTED",
}

Managed to fix most errors in main package codebase by patching package.json files in node_modules
8 files changed, but even this way some packages can not be patched,  e.g. this:
Error: No "exports" main defined in<EMAIL_ADDRESS> ❯ Object.<anonymous> node_modules/@mui/material/node/styles/adaptV4Theme.js:14:15

package.json of<EMAIL_ADDRESS>{
  "sideEffects": false,
  "module": "./index.js",
  "main": "../node/styles/index.js",
  "types": "./index.d.ts"
}

Upd. was able to force esm for most deps using alias and https://github.com/vitest-dev/vitest/pull/1673
But some dependencies can not into esm at all, e.g. styled-components, see
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Errors ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

Vitest caught 1 unhandled error during the test run. This might cause false positive tests.
Please, resolve all the errors to make sure your tests are not affected.

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Error ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
TypeError: Cannot read properties of null (reading 'context')
 ❯ Module.q ../../../../../../../../../C:/Users/wight/Documents/blog-template/node_modules/preact/hooks/dist/hooks.mjs:1:1014
 ❯ node_modules/styled-components/src/utils/interleave.js:1:18828
 ❯ O node_modules/styled-components/src/utils/interleave.js:1:19499
 ❯ d.t [as constructor] ../../../../../../../../../C:/Users/wight/Documents/blog-template/node_modules/preact/compat/dist/compat.mjs:1:1363
 ❯ d.O [as render] ../../../../../../../../../C:/Users/wight/Documents/blog-template/node_modules/preact/dist/preact.mjs:1:8158
 ❯ I node_modules/preact/dist/preact.js:1:5716
 ❯ b node_modules/preact/dist/preact.js:1:2103
 ❯ I node_modules/preact/dist/preact.js:1:5984
 ❯ b node_modules/preact/dist/preact.js:1:2103
 ❯ I node_modules/preact/dist/preact.js:1:5984

My changes: https://github.com/wight554/blog-template/pull/55/files#diff-6a3b01ba97829c9566ef2d8dc466ffcffb4bdac08706d3d6319e42e0aa6890dd
Is there any way I can force preact to be CJS @sheremet-va, tried aliasing but no luck? Unfortunately most react UI libraries aren't into supporting node native esm, they prefer bundlers to do they work

@wight554 yes, I also tried this MR agains your repro with no luck.

Is there any way I can force preact to be CJS

Unfortunately Vite's resolution algorithm is asynchronous, so it's not possible to reuse it. Maybe you can try and hijack require yourself, using node's module module? If it's successful we can try and find a way to integrate in inside Vitest, maybe under deps.cjs or something.

@wight554 yes, I also tried this MR agains your repro with no luck.

Is there any way I can force preact to be CJS

Unfortunately Vite's resolution algorithm is asynchronous, so it's not possible to reuse it. Maybe you can try and hijack require yourself, using node's module module? If it's successful we can try and find a way to integrate in inside Vitest, maybe under deps.cjs or something.

I was able to workaround it before by using TS CJS interop https://devblogs.microsoft.com/typescript/announcing-typescript-4-7-beta/#commonjs-interop
Used it for '@testing-library/preact', so it imported CJS version of preact https://github.com/vitest-dev/vitest/issues/747#issuecomment-1140225294
But it doesn't works since vite 3 version of vitest:
 FAIL  test/src/components/Header/Header.test.ts > Header > user is authenticated > user menu is opened > logout click > user service success > should set user state to null
 FAIL  test/src/components/Header/Header.test.ts > Header > user is authenticated > user menu is opened > logout click > user service error > should set snackbar state to error
TypeError: Cannot read properties of undefined (reading '__H')
 ❯ p ../../../../../../../../../C:/Users/wight/Documents/blog-template/node_modules/preact/hooks/dist/hooks.mjs:1:158
 ❯ Module._ ../../../../../../../../../C:/Users/wight/Documents/blog-template/node_modules/preact/hooks/dist/hooks.mjs:1:469
 ❯ y.RecoilObserver [as constructor] test/src/testUtils/components/RecoilObserver/RecoilObserver.ts:17:2
     15| }: RenderableProps<RecoilObserverProps<T>>) => {
     16|   const value = useRecoilValueLoadable(node);
     17|   useEffect(() => onChange(async ? value : value.contents), [onChange, async, value]);
       |  ^
     18|   return null;
     19| };
 ❯ y.M [as render] node_modules/preact/dist/preact.js:1:8004
 ❯ I node_modules/preact/dist/preact.js:1:5716
 ❯ b node_modules/preact/dist/preact.js:1:2103
 ❯ I node_modules/preact/dist/preact.js:1:5984
 ❯ b node_modules/preact/dist/preact.js:1:2103

❯ I node_modules/preact/dist/preact.js:1:5984
❯ b node_modules/preact/dist/preact.js:1:2103

Upd. was able to fix it by using cjs interop for all 'preact/hooks' (all packages with multiple version) imports and testing library
In my case I can fix it on transform stage (I'm using custom transformer), but I'd be happy to see some general solution, e.g. deps.cjsPackages flag that'll do some transforms for imports on vitest side

@wight554 cjs interop is the same as using const mod = require('path'), so I don't see why you really want to use it over simple require in this case. The syntax is hideous.
Using require bypasses Vitest entirely, and uses Native Node.js (note, that loader from #1673 will not work in this cases). Please, can you formulate more clearly what you expect from Vitest in this issue?

@wight554 cjs interop is the same as using const mod = require('path'), so I don't see why you really want to use it over simple require in this case. The syntax is hideous.
Using require bypasses Vitest entirely, and uses Native Node.js (note, that loader from #1673 will not work in this cases). Please, can you formulate more clearly what you expect from Vitest in this issue?

I wonder if it's possible to force configurable deps list to use require instead of import from vitest side
E.g. instead of doing changes I made higher I can add ['preact/hooks', '@testing-library/preact'] to some new configuration option like deps.forceCJS: ['preact/hooks', '@testing-library/preact']
i've seen nodejs createRequire, but idk how can I try to add it to vitest
https://nodejs.org/api/module.html#modulecreaterequirefilename

i've seen nodejs createRequire, but idk how can I try to add it to vitest https://nodejs.org/api/module.html#modulecreaterequirefilename

Vitest injects require in your files, you can use it directly.

Upd. was able to fix it by using cjs interop for all 'preact/hooks' (all packages with multiple version) imports and testing library In my case I can fix it on transform stage (I'm using custom transformer), but I'd be happy to see some general solution, e.g. deps.cjsPackages flag that'll do some transforms for imports on vitest side example: wight554/blog-template@e9c6659

managed to achieve same result with
    alias: [
      {
        find: 'preact/hooks',
        replacement: path.resolve(__dirname, './node_modules/preact/hooks/dist/hooks.js'),
      },
      {
        find: '@testing-library/preact',
        replacement: path.resolve(
          __dirname,
<EMAIL_ADDRESS>        ),
      },
    ],

this is way more DX friendly it is possible to cover this internally?

Upd. cleanest solution I was able to implement:
import { createRequire } from 'module';

const require = createRequire(import.meta.url);

    alias: [
      {
        find: 'preact/hooks',
        replacement: require.resolve('preact/hooks'),
      },
      {
        find: '@testing-library/preact',
        replacement: require.resolve('@testing-library/preact'),
      },
    ],

would be nicer to see smth like this in vitest itself

Vitest has both alias and test.alias config options, what else do you need? How users populate it is not Vitest authority.

would be nicer to see smth like this in vitest itself

Vitest has both alias and test.alias config options, what else do you need? How users populate it is not Vitest authority.

I meant having a separate option that'll use alias internally to simplify logic, but that's not really necessary

Just a note -> I got it to work with the solution from @wight554 🙏  - but only when combined with https://github.com/preactjs/compat-alias-package

@acapro got it working as well with the mixture of test.alias and compat alias package.
All my tests pass expect the ones testing custom hooks. Did you have any like that? am using @testing-library/react-hooks and get this error
[log]  ❯ Object.<anonymous> node_modules/@testing-library/react-hooks/lib/dom/pure.js:48:18
[error] Error: Package subpath './test-utils' is not defined by "exports" in node_modules/react-dom/package.json
[log]  ❯ getRenderer node_modules/@testing-library/react-hooks/lib/pure.js:54:12
[log]  ❯ Object.<anonymous> node_modules/@testing-library/react-hooks/lib/pure.js:70:5
[log]  ❯ Object.<anonymous> node_modules/@testing-library/react-hooks/lib/index.js:11:13

[log] Serialized Error: {
  "code": "ERR_PACKAGE_PATH_NOT_EXPORTED",
}

I'm facing similar issue with styled-components/native
Error: Cannot find module 'react-native'
Require stack:
- ./styled-components/native/dist/styled-components.native.cjs.js
Serialized Error: {
  "code": "MODULE_NOT_FOUND",
  "requireStack": [
    "./node_modules/styled-components/native/dist/styled-components.native.cjs.js",
  ],
}

styled-components/native internally uses require like so:
// inside styled-components.native.cjs.js
var reactNative = require('react-native');

I'm using an alias for react-native -> react-native-web, but adding test.alias or test.deps.inline didn't help. I guess vite can't transpile this? Manually patching the dependency solves the problem, but it would be nice if vite could override the require inside styled-components/native itself.
// inside styled-components.native.cjs.js
-var reactNative = require('react-native');
+var reactNative = require('react-native-web');

Here's my config:
export default defineConfig({
    plugins: [react()],
    resolve: {
        alias: {
            'react-native': 'react-native-web',
        },
    },
    test: {
        environment: 'jsdom',
        setupFiles: './tests/setup.ts',
    },
});

I guess vite can't transpile this?

Vitest doesn't support aliasing require calls, yes. There is an open issue: https://github.com/vitest-dev/vitest/issues/1910

I had a similar problem with a require("react") inside one of my dependencies. I was able to get around it by adding a Vitest setup script…
//vitest.config.ts
setupFiles: ['setup.js']

And then in the setup file I manually created an override for the library's React version by changing require.cache:
const modulePath = path.join('node_modules', 'react', 'index.js');
const source = path.resolve(__dirname, '..', '..', 'my-lib', modulePath);
const target = path.resolve(__dirname, '..', modulePath);
require.cache[source] = require.cache[target];


Pre-built binaries to remove the rustc dependency?

Have you considered uploading pre-built binaries so that users don't need rustc installed? I would be willing to contribute a patch.

I've been working on a set of rake tasks that make it easy for developers to do just that: https://github.com/malept/thermite (thanks for the kick in the pants to actually make it public).

I do like the idea.  As I understand it you will need to have a build for each OS type and maybe some variations of them?  Also the source of the binaries needs to be trusted.  So a trusted binary source with some gpg signatures?  What are your thoughts?  IMHO it's easier to trust the source code you get and see than the binaries packaged with/for it.

Might be a good use case for https://github.com/japaric/rust-everywhere to build your binaries which could give a decent value of trust.

As I understand it you will need to have a build for each OS type and maybe some variations of them?

I believe it should be built and linked not only for OS, but for OS+ruby_version, like
...
x86_64-apple-darwin + ruby 2.3.0
x86_64-apple-darwin + ruby 2.3.1

...
i686-apple-darwin + ruby 2.3.0
i686-apple-darwin + ruby 2.3.1
...

etc

I believe it should be built and linked not only for OS, but for OS+ruby_version

That is correct. I should update rusty_blank to do that.

However you should only need to build for minor ruby versions, not patch-level.

I'm not sure about pre-2.3 versions, for now I've tried with 2.3.0 and 2.3.1 (Mac OS X)
You can try to reproduce it locally.

Set ruby version to 2.3.0
Build extension
Set ruby version to 2.3.1
Run application

For me it fails with segfault :(

This is what I'm basing my statement on:
Several native Ruby extensions (like FFI and mysql2) provide binary gems for Windows Ruby builds. If  you look inside these gems, you'll see that it provides one native extension per minor Ruby version. In the case of mysql2-0.4.4-x64-mingw32.gem:
lib/mysql2/2.0/mysql2.so
lib/mysql2/2.1/mysql2.so
lib/mysql2/2.2/mysql2.so
lib/mysql2/2.3/mysql2.so

(I think the .so naming is a quirk of rake-compiler, but I'd have to check.)

@d-unseductable, @malept  As I understand it with RVM when you switch Ruby versions it will say that the gem isn't installed.  Installing the gem for the new Ruby patch version should recompile the asset.  See how current extensions are managed in RVM path on issue 71#comment .  RVM will have separate gems per minor patch versions and seeing a segfault as you've demonstrated @d-unseductable leads me to believe that there should be builds for all "supported" patch versions.
We should probably follow RVM's example for Ruby builds.  Check for binary if it's available and if not download the source and compile it. Although in our case we shouldn't need to download the source as it's already in the gem.
I'm not sure how other Ruby version managers handle gem storage but if segfaults are possible with patch versions I would seriously hope they keep them separate.

Currently in Thermite, the check is the other way: if cargo is available, compile the extension. Otherwise (if the project enabled it), look for a binary. If a binary isn't found (or searching for binaries is disabled), an error message is displayed saying "Install Rust to use this extension".

@malept I'm not against that.  That would save against server hosting usage (which I haven't considered yet).

@malept I've done what seems to be needed but I may need your help.  I've merged your Thermite PR and included the Github credentials.  Thermite output messages on Travis CI says it's building and deploying but the releases don't seem to be showing up.  Only the source code archives are there.
Since TravisCI isn't outputting any more information than:
Installing deploy dependencies
Successfully installed multipart-post-2.0.0
Successfully installed faraday-0.14.0
Successfully installed public_suffix-3.0.2
Successfully installed addressable-2.5.2
Successfully installed sawyer-0.8.1
Successfully installed octokit-4.6.2
6 gems installed
Successfully installed mime-types-2.99.3
1 gem installed

Logged in as Daniel P. Clark
Deploying to repo: danielpclark/faster_path
Current tag is: v0.3.0

Preparing deploy

Deploying application

Done. Your build exited with 0.

I don't really know where it could have gone wrong.

@danielpclark It looks like you need to call bundle exec rake thermite:tarball, either in script or after_success.

Okay, and the conditional environment flags will still apply?

Looks like it.


Refactor: use SecretStr for tongyi chat-model

@hwchase17 can this merged, thanks.

there was a big refactor to tongyi, may need to be merged in

@hwchase17 Sorry to bother you, can you review this PR?


ERC721 token not displayed

Describe the bug
ERC721 token (Cryptovoxels) not displayed
To Reproduce

Open https://gnosis-safe.io/app/#/safes/0xf5A07f885B9C2BC30e3766F5727E05bCE8b2B549/transactions
There is an incoming transfer of 1 CVPA
Go to assets-> Collectibles
No token

Expected behavior
I see the token
Additional context
The token is visible on Opensea: https://opensea.io/accounts/0xf5A07f885B9C2BC30e3766F5727E05bCE8b2B549
It also seems to me like it's a proper ERC721 token (https://etherscan.io/address/0x79986af15539de2db9a5086382daeda917a9cf0c#code)
Etherscan labels this as ERC20 token (Safe on Etherscan), so something fishy might be going on here. But since the backend captures it correctly for the tx list, I was wondering why it's not correct on the assets list.
Screenshots

Hi, Transfer event is not proper for an ERC721: event Transfer(address indexed _from, address indexed _to, uint256 _tokenId);, tokenId should be indexed. That's why it's not showed

Hi, Transfer event is not proper for an ERC721: event Transfer(address indexed _from, address indexed _to, uint256 _tokenId);, tokenId should be indexed. That's why it's not showed

.. and I thought I double checked that 🙄
Thanks for checking.

.. and I thought I double checked that 🙄
Thanks for checking.

.. and I thought I double checked that 🙄

No worries 😉

.. and I thought I double checked that 🙄

No worries 😉


Adding the has mortgage field to companyProfile document

[non-blocking, nice to have] not sure if it's mandatory field but if it is could we add it to something existing unit test even if it's the mocked return - will ensure it is accepted as part of the company profile document object


Parse-kv - DCR transformation error

I'm having issues with the parse-kv module when it comes to transform in a DCR.

Running this simple parse-kv module in the Log Analytics Workspace works very good, and it creates the column policy_id,
But when it comes to set this query in a Data Collection Rule, Azure raises an error :

If we look more closely to the parse and parse-kv modules, it seems that the DCR is mistaken the parse-kv and the parse module.
It asks for a parse-kv RawData with or so, but not using as and hence creating this error.
Could someone help me to fix this ?
Thank you !
See also

parse-kv doc
parse doc

@FormindMPO
Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can take a look at it accordingly.

#assign:cwatson-cat
#assign:yelevin
#assign:limwainstein

Hello
i tried again with this conf

Still having the issue with e306685f-9686-44f2-8e22-9a6cf1ecc889
But this uuid is valid, isn't it ? Plus it's working in other - already validated - taxii connectors

-> since it doesnt try to connect to test.com (i don't think that there is a taxii server here), i feel like it is a pre-validation test in the uuid verification...


Add Design Stripe under Illustrations.

Do you know is it possible to get these illustrations without signing up?

Its not.


GAIL could not work on Hopper-v2

Hello keiohta, I found that GAIL could not work in Hopper-v2 or Walker2d-v2. And SAC in this repository could not train a successful policy for Hopper-v2 too. I have checked the implementation of GAIL but failed to find out the reason why it does not work. In this failure caused by hyper-parameters or whether I need to fine-tune the parameters before training?

Hi @zhihaocheng , thanks for the report.
I reproduced the problem: SAC doesn't learn on Hopper-v2 and Walker2d-v2.
I don't think this problem is related to the hyper-parameters because it works on HalfCheetah-v2.
In the mean time, can you try with TD3? I confirmed TD3 works fine on both the two environments.

Hello @keiohta , thanks for your response.
I am trying to running TD3 and hope to work.
But it is still strange that SAC could not work on Hopper-v2 and Walker2d-v2, because it works well in other implementations. For example, https://spinningup.openai.com/en/latest/spinningup/bench.html. During my using of TF2RL, I found that both GAIL and SAC could not work on Hopper-v2 even though Hopper-v2 is almost the simplest continuous task. What's worse, GAIL uses DDPG, which is quite similar to SAC. So I guess whether there is something improper in terms of the implementation details of DDPG and SAC such that they could not work on Hopper-v2.

It would be perfect if the implementation here is able to work across various environments. On the other hand, I am very curious about why it does not work, because I did not find anything improper in the implementation.

I found a bug that caused the poor performance and fixed on this commit.
I confirmed SAC works as expected in this fixed version.
However, it has another error by introducing TensorFlow probability to remove custom distribution classes. So, I'll let you know once I merge this branch.
P.S.
Yeah, it would be good if I can guarantee that the performance of current implementation is similar to the one in the paper. I'll work on this.

I merged the branch. Can you try with the latest master?
pip install tf2rl==0.1.19
# or
pip install -U tf2rl

Thanks @keiohta, I will try the new version today. Also, I have checked your new commit and I think the reason that the past version did not work is due to the shape error during training? Is my understanding right?

Hello @keiohta , I tried but failed. I guess the newest TF2RL needs specific version of Tensorflow.
OS: CentOS Linux release 7.2 (Final).
Tensorflow: tensorflow-cpu 2.3.0.
tf2rl: 0.1.19.
Full error：
Traceback (most recent call last):
File "examples/run_sac.py", line 3, in
from tf2rl.algos.sac import SAC
File "/home/zhc/anaconda3/envs/dads-env/lib/python3.6/site-packages/tf2rl/algos/sac.py", line 7, in
from tf2rl.policies.tfp_gaussian_actor import GaussianActor
File "/home/zhc/anaconda3/envs/dads-env/lib/python3.6/site-packages/tf2rl/policies/tfp_gaussian_actor.py", line 3, in
import tensorflow_probability as tfp
File "/home/zhc/anaconda3/envs/dads-env/lib/python3.6/site-packages/tensorflow_probability/init.py", line 75, in
from tensorflow_probability.python import *  # pylint: disable=wildcard-import
File "/home/zhc/anaconda3/envs/dads-env/lib/python3.6/site-packages/tensorflow_probability/python/init.py", line 24, in
from tensorflow_probability.python import experimental
File "/home/zhc/anaconda3/envs/dads-env/lib/python3.6/site-packages/tensorflow_probability/python/experimental/init.py", line 34, in
from tensorflow_probability.python.experimental import auto_batching
File "/home/zhc/anaconda3/envs/dads-env/lib/python3.6/site-packages/tensorflow_probability/python/experimental/auto_batching/init.py", line 24, in
from tensorflow_probability.python.experimental.auto_batching import frontend
File "/home/zhc/anaconda3/envs/dads-env/lib/python3.6/site-packages/tensorflow_probability/python/experimental/auto_batching/frontend.py", line 44, in
from tensorflow.python.autograph.core import naming
ImportError: cannot import name 'naming'

Hi @zhihaocheng , this is caused by incompatibility in TensorFlow Probability version.
Please refer releases of tfp and install supported tfp version. I guess it will be 0.11.0.

Thank you @keiohta , after updating Tf Probalibity to 0.11.0, SAC is able to run and it will take some time to get the training results.

Hi @keiohta , I have tested the SAC here, and it do work on Hopper-v2.


DRM.NO_RECOGNIZED_KEY_SYSTEMS Error - Shaka player Fairplay

Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
v3.0.4
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from master?
Yes
Are you using the demo app or your own custom app?
Yes
If custom app, can you reproduce the issue using our demo app?
What browser and OS are you using?
Safari
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
IOS 13.3.1
What are the manifest and license server URIs?
You can find all files (.mpd, .m3u8, .js, .html) below :
https://drive.google.com/drive/folders/1KXfcL3k8A5ANZJvBU2u_9ShvLQ-beEGq?usp=sharing
What did you do?
We tried to play on safari but we got shaka player error .
You can find all files we used (.mpd, .m3u8, .js, .html) below :
https://drive.google.com/drive/folders/1KXfcL3k8A5ANZJvBU2u_9ShvLQ-beEGq?usp=sharing
What did you expect to happen?
Play without issues
What actually happened?
When trying to play, I'm gettting error below :
Error Code: 6000
"Shaka Error DRM.NO_RECOGNIZED_KEY_SYSTEMS ()"
"Error: Shaka Error DRM.NO_RECOGNIZED_KEY_SYSTEMS ()
at new shaka.util.Error (http://sawpcorneatabl/fairplay/shaka-player.compiled.debug.js:177:737)
at $jscomp.generator.Engine_.program_ (http://sawpcorneatabl/fairplay/shaka-player.compiled.debug.js:279:238)
at $jscomp.generator.Engine_.nextStep_ (http://sawpcorneatabl/fairplay/shaka-player.compiled.debug.js:36:105)
at $jscomp.generator.Engine_.next_ (http://sawpcorneatabl/fairplay/shaka-player.compiled.debug.js:32:234)
at $jscomp.generator.Generator_.next (http://sawpcorneatabl/fairplay/shaka-player.compiled.debug.js:37:73)
at http://sawpcorneatabl/fairplay/shaka-player.compiled.debug.js:45:230
at new Promise ()
at Object.$jscomp.asyncExecutePromiseGenerator (http://sawpcorneatabl/fairplay/shaka-player.compiled.debug.js:45:123)
at Object.$jscomp.asyncExecutePromiseGeneratorProgram (http://sawpcorneatabl/fairplay/shaka-player.compiled.debug.js:45:419)
at shaka.media.DrmEngine.queryMediaKeys_ (http://sawpcorneatabl/fairplay/shaka-player.compiled.debug.js:279:131)"

Shaka Player only supports FairPlay via native browser playback. That error suggests that Shaka Player is trying to play the content itself... but most iOS devices don't support MediaSource, so Shaka Player should be defaulting to native playback. Are you on an iPad? Supposedly MediaSource is available on those, though I don't have a real iPad to confirm that on.
Also, the files you shared are confusing me. An HLS stream is provided, but the code snippet is pointing to the link http://tableau.cornea.aero/fairplay/stream.mpd instead... which is a link that doesn't seem to work, and also doesn't make sense because I don't think MPEG-Dash streams can have FairPlay encryption at all. The stream.mpd file inside the drive, if that is what that link is, is encrypted with ClearKey encryption. Is this the actual code you are using?


New package: SDPNAL v0.0.1

Registering package: SDPNAL
Repository: https://github.com/JuliaOpt/SDPNAL.jl
Created by: @blegat
Version: v0.0.1
Commit: 1de6f4ba9cfc52454dcd13a900e5b668d4b25848
Reviewed by: @blegat
Reference: https://github.com/JuliaOpt/SDPNAL.jl/commit/1de6f4ba9cfc52454dcd13a900e5b668d4b25848#commitcomment-36601874

Name does not meet all of the following: starts with a capital letter, ASCII alphanumerics only, ends in lowercase

I have not chosen the name, this is the Julia wrapper of the SDPNAL solver written in matlab.

I was not able to install the package (i.e. import SDPNAL failed). See the CI logs for details.

This is expected as it requires MATLAB.jl


Added signal, message and node level attributes.

Changed whitespace handling and had to do minor whitespace tweaks to existing test files.
Corrected minor quirks such as "Vector_XXX" is not a valid node name. CANdb will remove it.
Or: Standard CAN ids outside of the 11bit range. CANdb++ will not accept that.
Sorry for putting all of that in one commit.

Coverage decreased (-0.4%) to 98.832% when pulling bdd03f61ffc6cb9729524548a7f161d66dc2202b on juleq:master into 2347d1a82002cf8827c5f29e1cf9db7a3b6d0659 on eerimoq:master.

I will work on the coverage. Any idea what I could do with the line ending issue that makes the Python 2 tests fail?

This might also be of interest for the poster of #27 and #38.

ENUM index resolving :).

My last commit was supposed to increase coverage. It did so for Python 2 but it did lower it for the Python 3 run. Do you see why?

Also, all members prefixed with and underscore should not be considered private and should not be used directly by the user. So I guess a we should create a property allowing the user access to attribute definitions, and other useful data if any.

I´ll work on the coverage, but you could already have a look.

I think it looks decent, but it's a lot of changes and it's hard to understand all implications of the changes. It would help my understanding if you could write an example and a few more tests.

Yes, I will do so. Maybe I can do the first commits tomorrow.
When I am done with this I could also tell you some findings that I made along the way. E.g. dbc files in the test folder that CanDb++ will not parse due to invalid order of contents (parser is sequence sensitive) or EV_ meaning Environment Variable and not Event. Regarding the whitespaces: I have corrected a few but have not caught every single strangeness their output logic yields. E.g. one space or one newline if a group or a field is missing. Will be a lottle mor trial and error in the dumpsters :).

Lovely! A DBC dump that actually is usable in other tools. =)

I am doing an example right now. I would want to add setters to various properties (in classes msg, sig...) of so that I can read in, manipulate without touching the _privates and dump out again. Objections against setters?

Should be ok.

Since the two methods get_message_by_name and get_message_by_frame_id use dictionary lookup, offering setters for message.name and message.frame_id will produce inconsistencies. An easy way around would to change the lookup to a search (like e.g. get_signal_by_name) and take a performance hit with large databases.
Another more complicated approach would be to make the lookup a class functionality of the message class. That way the setter could alter the dictionary when it is called.
The least invasive approach would be to just issue a warning as soon as the problematic setters are called. E.g. "Changing the frame id will make the results of database.get_message_by_frame_id inconsistent. Dumping and rereading will fix the dict again."
I think manipulation of these properties is quite a feature and I would really like to have that. I would be ok with the first approach (search instead of lookup). As a user, you can always save a reference for consecutive accesses or build your own dict.
What do you think?

Hmm. Just saw that the dicts are your primary way of accessing for encode/decode. I guess that makes it performance sensitive. I will think of another way.

Status update:

Regarding the message dict: I have chosen to do a search if lookup fails. If search is also failing, I raise the KeyError just like before. If I find something, I update the respective dictionary.
Regarding the dbc specifics containment: Have not done yet. I thought that you could give me feedback on the example first.
Regarding coverage: I have pushed to get a fresh coveralls result. I have tried a python coverage package to check coverage locally, but I was not able to produce comparable results. If you do local coverage testing, I would take a hint :)

I consider this push fully functional but I will add a test to increase coverage again.

Regarding coverage locally: Ok, I missed the --source switch. It is working now.

I do not run code coverage analysis locally.

I would consider this done if you have no objections. Can´t wait to see it pulled :).

Will continue tomorrow with styling. You are right, having them as class property did gain nothing. And I have not even thought about the multiple dbc use case...

I am not sure about the policy regarding blank lines: I have identified so far:

After local variable definition
Before and after if statements
Before return

I would further assume the following, but your feedback said otherwise:

Before and after local functions
Before and after for if it enhances readability or separates groups ( e.g. iterating nodes/messages/signals for the same purpose)

Could you clarify? Thanks.

I wrote a coding style guide in the documentation. It is by no means complete, but should be a good start.
http://cantools.readthedocs.io/en/latest/#coding-style

Let me know when you are ready and I'll merge. I can make the last coding style changes myself once merged.

I am ready. Thank you for that style guide. I would suggest including local functions and maybe a nested statement (for/if) as an example.

Sorry, I should have added that. I'll make the additions to the coding style rules and clean up the code =)

Only just seeing this -- thanks for implementing this juleq

@rjw245 Thank @eerimoq for his patience with me (and the heavy lifting)... :)


[RAML to Code] Support other versions of Spring MVC

Add a toggle and support for legacy versions of Spring MVC in the generation of Spring server endpoints

From Erreobi:
		SchemaMapper mapper = new SchemaMapper(new RuleFactory(config, new Jackson1Annotator(), schemaStore),
				new SchemaGenerator());

you can choose between Jackson1Annotator or Jackson2Annotator.

Ready to be released with 0.4.1.


issues with module_linux

I am having issues with a linux vendor box that doesn't like the way commands are found. the remote inventory script work fine on other linux boxes. however, when I run it against the vendor linux it drops the ssh connection.
the code in question is the way command are discovered.
commands = ['cat /dev/null',
'dmidecode -V',
'fdisk -V',
'find --version',
'grep -V',
'hdparm -V',
'hostname',
'id',
'ifconfig -V',
'ip -V',
'lshal -V'
'python2 -h',
'python3 -V',
'sort --version'
'sudo -V',
'wc --version']
It iterates though all the likely bin directories looking for a match? It is this trail and error which is I believe is causing the OS to drop the ssh connection.
def get_cmd_paths(self):
    search_paths = ['/usr/bin', '/bin', '/usr/local/bin', '/sbin', '/usr/sbin', '/usr/local/sbin']
    for cmd_to_find in commands:
        for search_path in search_paths:
            cmd_path = "%s/%s" % (search_path, cmd_to_find)
            data_out, data_err = self.execute(cmd_path, False)
            print "Here is data_out:%s, %s" %(data_out,data_err)
            if not data_err:
                self.paths.update({cmd_to_find.split()[0]: search_path})
                break
            if 'command not found' in data_err:
                if self.debug:
                    print '\t[-] Failed to find command "%s" at path "%s"' % (cmd_to_find, search_path)

Has anyone written this to use the "which" command for command discovery?

well thats not the issue, I am have written past that and still have the error. it must be something else?
(1, 'Administratively prohibited')

I am going to have to contact the vendor on this box. ssh works different.

Thanks David. We will leave it open for a few days. Please let us know if that is an issue within the codebase or you are able to resolve it with the vendor.

Yeah, it looks like if I slow down the execution of the commands I am able to get it work.
thanks
David


[WIP] Changed sloping_fault to use new subfault approach

Created fault module so that slip is specified more similar to dtopotools.  Also created a src/python/seismic directory that needs to be "linked" in clawpack/clawpack in order for all the paths to work correctly.  Not sure if the best way to do this is to start a "seismic" branch of clawpack/clawpack or leave it to the user for now to

create the symbolic link to $(CLAW)/seismic/src/python/seismic
add 'seismic' to the list in $(CLAW)/clawpack/init.py

I have been continuing to make improvements to a paper version of sloping fault, so any merge should be held off for now.

@rjleveque, suggest merging this in now unless you see conflicts... it's still technically has some WIP items, but also contains some refactoring that should be merged so that concurrent work doesn't become messy down the road.
Also suggest moving /2d/sloping_fault/process_gauges.py to /src/python/seismic/ and removing /2d/sloping_fault/plot_okada.py (as there is now a plot_okada function as part of the Fault class in /src/python/seismic/dtopotools_horiz_okada_and_1d)


[Restored] Bump Twilio Library to Version 5.x

Coverage increased (+6.5%) to 100.0% when pulling abf6f65e66592a307fc118d0d125eeafffb99e6a on next-gen into d137f12027b560678d37f82d5ed1c5799592d514 on master.

Coverage increased (+6.5%) to 100.0% when pulling 1314c64e8873def4acdb25129c38ed5f621d72d6 on next-gen into d137f12027b560678d37f82d5ed1c5799592d514 on master.

Coverage increased (+6.5%) to 100.0% when pulling 9a7ae397497dd8e33541f202b0d9752625dd5dab on next-gen into d137f12027b560678d37f82d5ed1c5799592d514 on master.

Coverage increased (+6.5%) to 100.0% when pulling 92bbf701744187f96bf3e5d651cd4635d6851d89 on next-gen into d137f12027b560678d37f82d5ed1c5799592d514 on master.

Coverage increased (+6.5%) to 100.0% when pulling 92bbf701744187f96bf3e5d651cd4635d6851d89 on next-gen into d137f12027b560678d37f82d5ed1c5799592d514 on master.


Cause RecallContextManagers to run when used without with

Closes #948.

I think this is subtle enough behavior to deserve a unit test, other than that LGTM