SmokeTest -> Master

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

File
Status
Preview URL
Details

:x:Error

Details

[Error-PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/azure-docs-sdk-python, working directory: W:\hvxg-s, target branch: master, target branch commit: 146539dfdf13601a3eddb2a208d2124fc6b3f545, source commit: 592f8fdf9988527d97f4d5b0ccd30089b9709508.

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 813f7e5:
:clock10: Full build: the average full build time is 140 min(s) 50 sec(s), this is based on the last 342 build(s) for this repository.

Docs Build status updates of commit 813f7e5:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2020_06_01.models.OSProfile.yml
:warning:Warning
View (azure-python)
Details

docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2020_06_01.models.VirtualMachineScaleSetOSProfile.yml
:warning:Warning
View (azure-python)
Details

docs-ref-services/appconfiguration-readme.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/core-tracing-opencensus-readme-pre.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/core-tracing-opentelemetry-readme-pre.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/eventhub-checkpointstoreblob-aio-readme.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/eventhub-checkpointstoreblob-readme.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/eventhub-readme-pre.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/identity-readme-pre.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/identity-readme.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/keyvault-certificates-readme-pre.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/keyvault-certificates-readme.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/keyvault-keys-readme-pre.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/keyvault-keys-readme.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/keyvault-secrets-readme-pre.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/keyvault-secrets-readme.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/search-documents-readme-pre.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/servicebus-readme.md
:warning:Warning
View (azure-python)
Details

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2015_06_15.models.OSProfile.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2015_06_15.models.VirtualMachineScaleSetOSProfile.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2016_03_30.models.OSProfile.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2016_03_30.models.VirtualMachineScaleSetOSProfile.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2016_04_30_preview.models.HardwareProfile.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2016_04_30_preview.models.OSProfile.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2016_04_30_preview.models.VirtualMachineScaleSetOSProfile.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2016_04_30_preview.models.VirtualMachineSizeTypes.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2016_04_30_preview.models.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2017_03_30.models.OSProfile.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2017_03_30.models.VirtualMachineScaleSetOSProfile.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2017_12_01.models.OSProfile.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2017_12_01.models.VirtualMachineScaleSetOSProfile.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2018_04_01.models.OSProfile.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2018_04_01.models.VirtualMachineScaleSetOSProfile.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2018_06_01.models.OSProfile.yml
:warning:Warning
View (azure-python-preview)
Details

docs-ref-autogen/azure-eventhub/azure.eventhub.aio.CheckpointStore.yml
:warning:Warning
View (azure-python)
Details

preview/docs-ref-autogen/overview/azure/VirtualMachines/Management.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/overview/azure/Storage/Management.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/overview/azure/Resources/Management.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/overview/azure/Monitoring/Management.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/overview/azure/KeyVault/Management.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/overview/azure/EventHubs/Management.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/overview/azure/VirtualMachines.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/overview/azure/Storage.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/overview/azure/Resources.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/overview/azure/Other.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/overview/azure/Monitoring.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-mgmt-resource/azure.mgmt.resource.resources.ResourceManagementClient.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-mgmt-resource/azure.mgmt.resource.resources.aio.ResourceManagementClient.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-mgmt-resource/azure.mgmt.resource.ResourceManagementClient.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-mgmt-resource/azure.mgmt.resource.PolicyClient.yml
:warning:Warning
View (azure-python-preview)
Details

This comment lists only the first 50 files in the pull request.

docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2020_06_01.models.OSProfile.yml

[Warning-UidNotFound] 5 invalid cross reference(s) "<xref:mailto:abc@123>", "<xref:mailto:P@$$w0rd>", "<xref:mailto:P@ssw0rd>", "<xref:mailto:P@ssword123>", "<xref:mailto:pass@word1>".

docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2020_06_01.models.VirtualMachineScaleSetOSProfile.yml

[Warning-UidNotFound] 5 invalid cross reference(s) "<xref:mailto:abc@123>", "<xref:mailto:P@$$w0rd>", "<xref:mailto:P@ssw0rd>", "<xref:mailto:P@ssword123>", "<xref:mailto:pass@word1>".

docs-ref-services/appconfiguration-readme.md

Line 24: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/azure-app-configuration/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 41: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/services/app-configuration/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

docs-ref-services/core-tracing-opencensus-readme-pre.md

Line 95: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/python/api/azure-core/azure.core.exceptions?view=azure-python' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

docs-ref-services/core-tracing-opentelemetry-readme-pre.md

Line 97: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/python/api/azure-core/azure.core.exceptions?view=azure-python' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

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

Line 20: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/event-hubs/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 20: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/storage/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 27: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 29: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 31: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-create-account-block-blob' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

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

Line 22: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/event-hubs/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 22: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/storage/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 29: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 31: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 33: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-create-account-block-blob' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

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

Line 23: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-about' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 32: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/event-hubs/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 43: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 62: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-get-connection-string' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 78: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-get-connection-string#get-connection-string-from-the-portal' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 124: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-features' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 347: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/storage/common/storage-quickstart-create-account?tabs=azure-portal' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 348: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/storage/blobs/storage-quickstart-blobs-portal#create-a-container' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 398: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-messages-read-builtin' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

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

Line 23: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 24: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/overview' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 30: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 111: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/services-support-managed-identities' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 287: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/develop/reference-aadsts-error-codes' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 32: [Suggestion-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning around July 2020.
Line 69: [Suggestion-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning around July 2020.
Line 155: [Suggestion-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning around July 2020.
Line 272: [Suggestion-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning around July 2020.
Line 290: [Suggestion-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning around July 2020.
Line 308: [Suggestion-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning around July 2020.

docs-ref-services/identity-readme.md

Line 22: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-service-principals' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 23: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/overview' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 29: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 110: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/services-support-managed-identities' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 286: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/develop/reference-aadsts-error-codes' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 31: [Suggestion-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning around July 2020.
Line 68: [Suggestion-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning around July 2020.
Line 154: [Suggestion-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning around July 2020.
Line 271: [Suggestion-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning around July 2020.
Line 289: [Suggestion-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning around July 2020.
Line 307: [Suggestion-multiple-h1s] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning around July 2020.

docs-ref-services/keyvault-certificates-readme-pre.md

Line 27: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 238: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/key-vault-ovw-soft-delete' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 240: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/key-vault-ovw-soft-delete' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

docs-ref-services/keyvault-certificates-readme.md

Line 27: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 238: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/key-vault-ovw-soft-delete' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 240: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/key-vault-ovw-soft-delete' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

docs-ref-services/keyvault-keys-readme-pre.md

Line 29: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 157: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/about-keys-secrets-and-certificates#key-vault-keys' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 231: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/key-vault-ovw-soft-delete' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 233: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/key-vault-ovw-soft-delete' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

docs-ref-services/keyvault-keys-readme.md

Line 28: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 156: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/about-keys-secrets-and-certificates#key-vault-keys' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 230: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/key-vault-ovw-soft-delete' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 232: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/key-vault-ovw-soft-delete' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

docs-ref-services/keyvault-secrets-readme-pre.md

Line 29: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 157: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/about-keys-secrets-and-certificates#key-vault-secrets' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 237: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/key-vault-ovw-soft-delete' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 238: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/key-vault-ovw-soft-delete' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

docs-ref-services/keyvault-secrets-readme.md

Line 28: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 156: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/about-keys-secrets-and-certificates#key-vault-secrets' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 236: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/key-vault-ovw-soft-delete' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 237: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/key-vault-ovw-soft-delete' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

docs-ref-services/search-documents-readme-pre.md

Line 21: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/search/search-what-is-azure-search' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 39: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/search/search-create-service-portal' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 49: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/search/search-sku-tier' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 54: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/search/search-security-api-keys' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 65: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/search/search-create-service-portal#get-a-key-and-url-endpoint' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 66: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/search/search-security-api-keys' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 83: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/search/search-create-service-portal#get-a-key-and-url-endpoint' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 84: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/search/search-security-api-keys' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 98: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/search/search-create-service-portal#get-a-key-and-url-endpoint' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 99: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/search/search-security-api-keys' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 131: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/rest/api/searchservice/index-operations' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 132: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/rest/api/searchservice/document-operations' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 133: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/rest/api/searchservice/indexer-operations' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 134: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/rest/api/searchservice/indexer-operations' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 135: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/rest/api/searchservice/skillset-operations' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 136: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/rest/api/searchservice/synonym-map-operations' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 291: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/search/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

docs-ref-services/servicebus-readme.md

Line 52: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-create-namespace-portal' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 94: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-messaging-overview#queues' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 96: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-messaging-overview#topics' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 98: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-queues-topics-subscriptions#topics-and-subscriptions' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2015_06_15.models.OSProfile.yml

[Warning-UidNotFound] 5 invalid cross reference(s) "<xref:mailto:abc@123>", "<xref:mailto:P@$$w0rd>", "<xref:mailto:P@ssw0rd>", "<xref:mailto:P@ssword123>", "<xref:mailto:pass@word1>".

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2015_06_15.models.VirtualMachineScaleSetOSProfile.yml

[Warning-UidNotFound] 5 invalid cross reference(s) "<xref:mailto:abc@123>", "<xref:mailto:P@$$w0rd>", "<xref:mailto:P@ssw0rd>", "<xref:mailto:P@ssword123>", "<xref:mailto:pass@word1>".

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2016_03_30.models.OSProfile.yml

[Warning-UidNotFound] 5 invalid cross reference(s) "<xref:mailto:abc@123>", "<xref:mailto:P@$$w0rd>", "<xref:mailto:P@ssw0rd>", "<xref:mailto:P@ssword123>", "<xref:mailto:pass@word1>".

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2016_03_30.models.VirtualMachineScaleSetOSProfile.yml

[Warning-UidNotFound] 5 invalid cross reference(s) "<xref:mailto:abc@123>", "<xref:mailto:P@$$w0rd>", "<xref:mailto:P@ssw0rd>", "<xref:mailto:P@ssword123>", "<xref:mailto:pass@word1>".

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2016_04_30_preview.models.HardwareProfile.yml

[Warning-UidNotFound] 3 invalid cross reference(s) "<xref:virtualmachines-list-sizes-availability-set.md>", "<xref:virtualmachines-list-sizes-region.md>", "<xref:virtualmachines-list-sizes-for-resizing.md>".

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2016_04_30_preview.models.OSProfile.yml

[Warning-UidNotFound] 5 invalid cross reference(s) "<xref:mailto:abc@123>", "<xref:mailto:P@$$w0rd>", "<xref:mailto:P@ssw0rd>", "<xref:mailto:P@ssword123>", "<xref:mailto:pass@word1>".

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2016_04_30_preview.models.VirtualMachineScaleSetOSProfile.yml

[Warning-UidNotFound] 5 invalid cross reference(s) "<xref:mailto:abc@123>", "<xref:mailto:P@$$w0rd>", "<xref:mailto:P@ssw0rd>", "<xref:mailto:P@ssword123>", "<xref:mailto:pass@word1>".

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2016_04_30_preview.models.VirtualMachineSizeTypes.yml

[Warning-UidNotFound] 3 invalid cross reference(s) "<xref:virtualmachines-list-sizes-availability-set.md>", "<xref:virtualmachines-list-sizes-region.md>", "<xref:virtualmachines-list-sizes-for-resizing.md>".

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2016_04_30_preview.models.yml

[Warning-UidNotFound] 3 invalid cross reference(s) "<xref:virtualmachines-list-sizes-availability-set.md>", "<xref:virtualmachines-list-sizes-region.md>", "<xref:virtualmachines-list-sizes-for-resizing.md>".

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2017_03_30.models.OSProfile.yml

[Warning-UidNotFound] 5 invalid cross reference(s) "<xref:mailto:abc@123>", "<xref:mailto:P@$$w0rd>", "<xref:mailto:P@ssw0rd>", "<xref:mailto:P@ssword123>", "<xref:mailto:pass@word1>".

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2017_03_30.models.VirtualMachineScaleSetOSProfile.yml

[Warning-UidNotFound] 5 invalid cross reference(s) "<xref:mailto:abc@123>", "<xref:mailto:P@$$w0rd>", "<xref:mailto:P@ssw0rd>", "<xref:mailto:P@ssword123>", "<xref:mailto:pass@word1>".

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2017_12_01.models.OSProfile.yml

[Warning-UidNotFound] 5 invalid cross reference(s) "<xref:mailto:abc@123>", "<xref:mailto:P@$$w0rd>", "<xref:mailto:P@ssw0rd>", "<xref:mailto:P@ssword123>", "<xref:mailto:pass@word1>".

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2017_12_01.models.VirtualMachineScaleSetOSProfile.yml

[Warning-UidNotFound] 5 invalid cross reference(s) "<xref:mailto:abc@123>", "<xref:mailto:P@$$w0rd>", "<xref:mailto:P@ssw0rd>", "<xref:mailto:P@ssword123>", "<xref:mailto:pass@word1>".

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2018_04_01.models.OSProfile.yml

[Warning-UidNotFound] 5 invalid cross reference(s) "<xref:mailto:abc@123>", "<xref:mailto:P@$$w0rd>", "<xref:mailto:P@ssw0rd>", "<xref:mailto:P@ssword123>", "<xref:mailto:pass@word1>".

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2018_04_01.models.VirtualMachineScaleSetOSProfile.yml

[Warning-UidNotFound] 5 invalid cross reference(s) "<xref:mailto:abc@123>", "<xref:mailto:P@$$w0rd>", "<xref:mailto:P@ssw0rd>", "<xref:mailto:P@ssword123>", "<xref:mailto:pass@word1>".

preview/docs-ref-autogen/azure-mgmt-compute/azure.mgmt.compute.v2018_06_01.models.OSProfile.yml

[Warning-UidNotFound] 5 invalid cross reference(s) "<xref:mailto:abc@123>", "<xref:mailto:P@$$w0rd>", "<xref:mailto:P@ssw0rd>", "<xref:mailto:P@ssword123>", "<xref:mailto:pass@word1>".

docs-ref-autogen/azure-eventhub/azure.eventhub.aio.CheckpointStore.yml

[Warning-UidNotFound] 1 invalid cross reference(s) "<xref:azure.eventhub.EventData>".

preview/docs-ref-autogen/overview/azure/VirtualMachines/Management.yml

[Warning-GitInfoNotFound] Failed to extract file creator information from git history.

preview/docs-ref-autogen/overview/azure/Storage/Management.yml

[Warning-GitInfoNotFound] Failed to extract file creator information from git history.

preview/docs-ref-autogen/overview/azure/Resources/Management.yml

[Warning-GitInfoNotFound] Failed to extract file creator information from git history.

preview/docs-ref-autogen/overview/azure/Monitoring/Management.yml

[Warning-GitInfoNotFound] Failed to extract file creator information from git history.

preview/docs-ref-autogen/overview/azure/KeyVault/Management.yml

[Warning-GitInfoNotFound] Failed to extract file creator information from git history.

preview/docs-ref-autogen/overview/azure/EventHubs/Management.yml

[Warning-GitInfoNotFound] Failed to extract file creator information from git history.

preview/docs-ref-autogen/overview/azure/VirtualMachines.yml

[Warning-GitInfoNotFound] Failed to extract file creator information from git history.

preview/docs-ref-autogen/overview/azure/Storage.yml

[Warning-GitInfoNotFound] Failed to extract file creator information from git history.

preview/docs-ref-autogen/overview/azure/Resources.yml

[Warning-GitInfoNotFound] Failed to extract file creator information from git history.

preview/docs-ref-autogen/overview/azure/Other.yml

[Warning-GitInfoNotFound] Failed to extract file creator information from git history.

preview/docs-ref-autogen/overview/azure/Monitoring.yml

[Warning-GitInfoNotFound] Failed to extract file creator information from git history.

preview/docs-ref-autogen/azure-mgmt-resource/azure.mgmt.resource.resources.ResourceManagementClient.yml

[Warning-UidNotFound] 76 invalid cross reference(s) "<xref:azure.mgmt.resource.v2016_02_01.models>", "<xref:azure.mgmt.resource.v2016_09_01.models>", "<xref:azure.mgmt.resource.v2017_05_10.models>", "<xref:azure.mgmt.resource.v2018_02_01.models>", "<xref:azure.mgmt.resource.v2018_05_01.models>", "<xref:azure.mgmt.resource.v2019_05_01.models>", "<xref:azure.mgmt.resource.v2019_05_10.models>", "<xref:azure.mgmt.resource.v2019_07_01.models>", "<xref:azure.mgmt.resource.v2019_08_01.models>", "<xref:azure.mgmt.resource.v2019_10_01.models>", "<xref:azure.mgmt.resource.v2016_02_01.operations.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2016_09_01.operations.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2017_05_10.operations.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2018_02_01.operations.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2018_05_01.operations.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2019_05_01.operations.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2019_05_10.operations.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2019_07_01.operations.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2019_08_01.operations.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2019_10_01.operations.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2016_02_01.operations.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2016_09_01.operations.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2017_05_10.operations.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2018_02_01.operations.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2018_05_01.operations.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2019_05_01.operations.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2019_05_10.operations.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2019_07_01.operations.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2019_08_01.operations.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2019_10_01.operations.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2018_05_01.operations.Operations>", "<xref:azure.mgmt.resource.v2019_05_01.operations.Operations>", "<xref:azure.mgmt.resource.v2019_05_10.operations.Operations>", "<xref:azure.mgmt.resource.v2019_07_01.operations.Operations>", "<xref:azure.mgmt.resource.v2019_08_01.operations.Operations>", "<xref:azure.mgmt.resource.v2019_10_01.operations.Operations>", "<xref:azure.mgmt.resource.v2016_02_01.operations.ProvidersOperations>", "<xref:azure.mgmt.resource.v2016_09_01.operations.ProvidersOperations>", "<xref:azure.mgmt.resource.v2017_05_10.operations.ProvidersOperations>", "<xref:azure.mgmt.resource.v2018_02_01.operations.ProvidersOperations>", "<xref:azure.mgmt.resource.v2018_05_01.operations.ProvidersOperations>", "<xref:azure.mgmt.resource.v2019_05_01.operations.ProvidersOperations>", "<xref:azure.mgmt.resource.v2019_05_10.operations.ProvidersOperations>", "<xref:azure.mgmt.resource.v2019_07_01.operations.ProvidersOperations>", "<xref:azure.mgmt.resource.v2019_08_01.operations.ProvidersOperations>", "<xref:azure.mgmt.resource.v2019_10_01.operations.ProvidersOperations>", "<xref:azure.mgmt.resource.v2016_02_01.operations.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2016_09_01.operations.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2017_05_10.operations.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2018_02_01.operations.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2018_05_01.operations.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2019_05_01.operations.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2019_05_10.operations.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2019_07_01.operations.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2019_08_01.operations.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2019_10_01.operations.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2016_02_01.operations.ResourcesOperations>", "<xref:azure.mgmt.resource.v2016_09_01.operations.ResourcesOperations>", "<xref:azure.mgmt.resource.v2017_05_10.operations.ResourcesOperations>", "<xref:azure.mgmt.resource.v2018_02_01.operations.ResourcesOperations>", "<xref:azure.mgmt.resource.v2018_05_01.operations.ResourcesOperations>", "<xref:azure.mgmt.resource.v2019_05_01.operations.ResourcesOperations>", "<xref:azure.mgmt.resource.v2019_05_10.operations.ResourcesOperations>", "<xref:azure.mgmt.resource.v2019_07_01.operations.ResourcesOperations>", "<xref:azure.mgmt.resource.v2019_08_01.operations.ResourcesOperations>", "<xref:azure.mgmt.resource.v2019_10_01.operations.ResourcesOperations>", "<xref:azure.mgmt.resource.v2016_02_01.operations.TagsOperations>", "<xref:azure.mgmt.resource.v2016_09_01.operations.TagsOperations>", "<xref:azure.mgmt.resource.v2017_05_10.operations.TagsOperations>", "<xref:azure.mgmt.resource.v2018_02_01.operations.TagsOperations>", "<xref:azure.mgmt.resource.v2018_05_01.operations.TagsOperations>", "<xref:azure.mgmt.resource.v2019_05_01.operations.TagsOperations>", "<xref:azure.mgmt.resource.v2019_05_10.operations.TagsOperations>", "<xref:azure.mgmt.resource.v2019_07_01.operations.TagsOperations>", "<xref:azure.mgmt.resource.v2019_08_01.operations.TagsOperations>", "<xref:azure.mgmt.resource.v2019_10_01.operations.TagsOperations>".

preview/docs-ref-autogen/azure-mgmt-resource/azure.mgmt.resource.resources.aio.ResourceManagementClient.yml

[Warning-UidNotFound] 76 invalid cross reference(s) "<xref:azure.mgmt.resource.v2016_02_01.models>", "<xref:azure.mgmt.resource.v2016_09_01.models>", "<xref:azure.mgmt.resource.v2017_05_10.models>", "<xref:azure.mgmt.resource.v2018_02_01.models>", "<xref:azure.mgmt.resource.v2018_05_01.models>", "<xref:azure.mgmt.resource.v2019_05_01.models>", "<xref:azure.mgmt.resource.v2019_05_10.models>", "<xref:azure.mgmt.resource.v2019_07_01.models>", "<xref:azure.mgmt.resource.v2019_08_01.models>", "<xref:azure.mgmt.resource.v2019_10_01.models>", "<xref:azure.mgmt.resource.v2016_02_01.aio.operations_async.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2016_09_01.aio.operations_async.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2017_05_10.aio.operations_async.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2018_02_01.aio.operations_async.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2018_05_01.aio.operations_async.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2019_05_01.aio.operations_async.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2019_05_10.aio.operations_async.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2019_07_01.aio.operations_async.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2019_08_01.aio.operations_async.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2019_10_01.aio.operations_async.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2016_02_01.aio.operations_async.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2016_09_01.aio.operations_async.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2017_05_10.aio.operations_async.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2018_02_01.aio.operations_async.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2018_05_01.aio.operations_async.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2019_05_01.aio.operations_async.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2019_05_10.aio.operations_async.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2019_07_01.aio.operations_async.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2019_08_01.aio.operations_async.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2019_10_01.aio.operations_async.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2018_05_01.aio.operations_async.Operations>", "<xref:azure.mgmt.resource.v2019_05_01.aio.operations_async.Operations>", "<xref:azure.mgmt.resource.v2019_05_10.aio.operations_async.Operations>", "<xref:azure.mgmt.resource.v2019_07_01.aio.operations_async.Operations>", "<xref:azure.mgmt.resource.v2019_08_01.aio.operations_async.Operations>", "<xref:azure.mgmt.resource.v2019_10_01.aio.operations_async.Operations>", "<xref:azure.mgmt.resource.v2016_02_01.aio.operations_async.ProvidersOperations>", "<xref:azure.mgmt.resource.v2016_09_01.aio.operations_async.ProvidersOperations>", "<xref:azure.mgmt.resource.v2017_05_10.aio.operations_async.ProvidersOperations>", "<xref:azure.mgmt.resource.v2018_02_01.aio.operations_async.ProvidersOperations>", "<xref:azure.mgmt.resource.v2018_05_01.aio.operations_async.ProvidersOperations>", "<xref:azure.mgmt.resource.v2019_05_01.aio.operations_async.ProvidersOperations>", "<xref:azure.mgmt.resource.v2019_05_10.aio.operations_async.ProvidersOperations>", "<xref:azure.mgmt.resource.v2019_07_01.aio.operations_async.ProvidersOperations>", "<xref:azure.mgmt.resource.v2019_08_01.aio.operations_async.ProvidersOperations>", "<xref:azure.mgmt.resource.v2019_10_01.aio.operations_async.ProvidersOperations>", "<xref:azure.mgmt.resource.v2016_02_01.aio.operations_async.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2016_09_01.aio.operations_async.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2017_05_10.aio.operations_async.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2018_02_01.aio.operations_async.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2018_05_01.aio.operations_async.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2019_05_01.aio.operations_async.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2019_05_10.aio.operations_async.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2019_07_01.aio.operations_async.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2019_08_01.aio.operations_async.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2019_10_01.aio.operations_async.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2016_02_01.aio.operations_async.ResourcesOperations>", "<xref:azure.mgmt.resource.v2016_09_01.aio.operations_async.ResourcesOperations>", "<xref:azure.mgmt.resource.v2017_05_10.aio.operations_async.ResourcesOperations>", "<xref:azure.mgmt.resource.v2018_02_01.aio.operations_async.ResourcesOperations>", "<xref:azure.mgmt.resource.v2018_05_01.aio.operations_async.ResourcesOperations>", "<xref:azure.mgmt.resource.v2019_05_01.aio.operations_async.ResourcesOperations>", "<xref:azure.mgmt.resource.v2019_05_10.aio.operations_async.ResourcesOperations>", "<xref:azure.mgmt.resource.v2019_07_01.aio.operations_async.ResourcesOperations>", "<xref:azure.mgmt.resource.v2019_08_01.aio.operations_async.ResourcesOperations>", "<xref:azure.mgmt.resource.v2019_10_01.aio.operations_async.ResourcesOperations>", "<xref:azure.mgmt.resource.v2016_02_01.aio.operations_async.TagsOperations>", "<xref:azure.mgmt.resource.v2016_09_01.aio.operations_async.TagsOperations>", "<xref:azure.mgmt.resource.v2017_05_10.aio.operations_async.TagsOperations>", "<xref:azure.mgmt.resource.v2018_02_01.aio.operations_async.TagsOperations>", "<xref:azure.mgmt.resource.v2018_05_01.aio.operations_async.TagsOperations>", "<xref:azure.mgmt.resource.v2019_05_01.aio.operations_async.TagsOperations>", "<xref:azure.mgmt.resource.v2019_05_10.aio.operations_async.TagsOperations>", "<xref:azure.mgmt.resource.v2019_07_01.aio.operations_async.TagsOperations>", "<xref:azure.mgmt.resource.v2019_08_01.aio.operations_async.TagsOperations>", "<xref:azure.mgmt.resource.v2019_10_01.aio.operations_async.TagsOperations>".

preview/docs-ref-autogen/azure-mgmt-resource/azure.mgmt.resource.ResourceManagementClient.yml

[Warning-UidNotFound] 76 invalid cross reference(s) "<xref:azure.mgmt.resource.v2016_02_01.models>", "<xref:azure.mgmt.resource.v2016_09_01.models>", "<xref:azure.mgmt.resource.v2017_05_10.models>", "<xref:azure.mgmt.resource.v2018_02_01.models>", "<xref:azure.mgmt.resource.v2018_05_01.models>", "<xref:azure.mgmt.resource.v2019_05_01.models>", "<xref:azure.mgmt.resource.v2019_05_10.models>", "<xref:azure.mgmt.resource.v2019_07_01.models>", "<xref:azure.mgmt.resource.v2019_08_01.models>", "<xref:azure.mgmt.resource.v2019_10_01.models>", "<xref:azure.mgmt.resource.v2016_02_01.operations.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2016_09_01.operations.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2017_05_10.operations.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2018_02_01.operations.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2018_05_01.operations.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2019_05_01.operations.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2019_05_10.operations.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2019_07_01.operations.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2019_08_01.operations.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2019_10_01.operations.DeploymentOperationsOperations>", "<xref:azure.mgmt.resource.v2016_02_01.operations.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2016_09_01.operations.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2017_05_10.operations.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2018_02_01.operations.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2018_05_01.operations.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2019_05_01.operations.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2019_05_10.operations.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2019_07_01.operations.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2019_08_01.operations.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2019_10_01.operations.DeploymentsOperations>", "<xref:azure.mgmt.resource.v2018_05_01.operations.Operations>", "<xref:azure.mgmt.resource.v2019_05_01.operations.Operations>", "<xref:azure.mgmt.resource.v2019_05_10.operations.Operations>", "<xref:azure.mgmt.resource.v2019_07_01.operations.Operations>", "<xref:azure.mgmt.resource.v2019_08_01.operations.Operations>", "<xref:azure.mgmt.resource.v2019_10_01.operations.Operations>", "<xref:azure.mgmt.resource.v2016_02_01.operations.ProvidersOperations>", "<xref:azure.mgmt.resource.v2016_09_01.operations.ProvidersOperations>", "<xref:azure.mgmt.resource.v2017_05_10.operations.ProvidersOperations>", "<xref:azure.mgmt.resource.v2018_02_01.operations.ProvidersOperations>", "<xref:azure.mgmt.resource.v2018_05_01.operations.ProvidersOperations>", "<xref:azure.mgmt.resource.v2019_05_01.operations.ProvidersOperations>", "<xref:azure.mgmt.resource.v2019_05_10.operations.ProvidersOperations>", "<xref:azure.mgmt.resource.v2019_07_01.operations.ProvidersOperations>", "<xref:azure.mgmt.resource.v2019_08_01.operations.ProvidersOperations>", "<xref:azure.mgmt.resource.v2019_10_01.operations.ProvidersOperations>", "<xref:azure.mgmt.resource.v2016_02_01.operations.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2016_09_01.operations.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2017_05_10.operations.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2018_02_01.operations.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2018_05_01.operations.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2019_05_01.operations.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2019_05_10.operations.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2019_07_01.operations.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2019_08_01.operations.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2019_10_01.operations.ResourceGroupsOperations>", "<xref:azure.mgmt.resource.v2016_02_01.operations.ResourcesOperations>", "<xref:azure.mgmt.resource.v2016_09_01.operations.ResourcesOperations>", "<xref:azure.mgmt.resource.v2017_05_10.operations.ResourcesOperations>", "<xref:azure.mgmt.resource.v2018_02_01.operations.ResourcesOperations>", "<xref:azure.mgmt.resource.v2018_05_01.operations.ResourcesOperations>", "<xref:azure.mgmt.resource.v2019_05_01.operations.ResourcesOperations>", "<xref:azure.mgmt.resource.v2019_05_10.operations.ResourcesOperations>", "<xref:azure.mgmt.resource.v2019_07_01.operations.ResourcesOperations>", "<xref:azure.mgmt.resource.v2019_08_01.operations.ResourcesOperations>", "<xref:azure.mgmt.resource.v2019_10_01.operations.ResourcesOperations>", "<xref:azure.mgmt.resource.v2016_02_01.operations.TagsOperations>", "<xref:azure.mgmt.resource.v2016_09_01.operations.TagsOperations>", "<xref:azure.mgmt.resource.v2017_05_10.operations.TagsOperations>", "<xref:azure.mgmt.resource.v2018_02_01.operations.TagsOperations>", "<xref:azure.mgmt.resource.v2018_05_01.operations.TagsOperations>", "<xref:azure.mgmt.resource.v2019_05_01.operations.TagsOperations>", "<xref:azure.mgmt.resource.v2019_05_10.operations.TagsOperations>", "<xref:azure.mgmt.resource.v2019_07_01.operations.TagsOperations>", "<xref:azure.mgmt.resource.v2019_08_01.operations.TagsOperations>", "<xref:azure.mgmt.resource.v2019_10_01.operations.TagsOperations>".

preview/docs-ref-autogen/azure-mgmt-resource/azure.mgmt.resource.PolicyClient.yml

[Warning-UidNotFound] 33 invalid cross reference(s) "<xref:azure.mgmt.resource.v2015_10_01_preview.models>", "<xref:azure.mgmt.resource.v2016_04_01.models>", "<xref:azure.mgmt.resource.v2016_12_01.models>", "<xref:azure.mgmt.resource.v2017_06_01_preview.models>", "<xref:azure.mgmt.resource.v2018_03_01.models>", "<xref:azure.mgmt.resource.v2018_05_01.models>", "<xref:azure.mgmt.resource.v2019_01_01.models>", "<xref:azure.mgmt.resource.v2019_06_01.models>", "<xref:azure.mgmt.resource.v2019_09_01.models>", "<xref:azure.mgmt.resource.v2015_10_01_preview.operations.PolicyAssignmentsOperations>", "<xref:azure.mgmt.resource.v2016_04_01.operations.PolicyAssignmentsOperations>", "<xref:azure.mgmt.resource.v2016_12_01.operations.PolicyAssignmentsOperations>", "<xref:azure.mgmt.resource.v2017_06_01_preview.operations.PolicyAssignmentsOperations>", "<xref:azure.mgmt.resource.v2018_03_01.operations.PolicyAssignmentsOperations>", "<xref:azure.mgmt.resource.v2018_05_01.operations.PolicyAssignmentsOperations>", "<xref:azure.mgmt.resource.v2019_01_01.operations.PolicyAssignmentsOperations>", "<xref:azure.mgmt.resource.v2019_06_01.operations.PolicyAssignmentsOperations>", "<xref:azure.mgmt.resource.v2019_09_01.operations.PolicyAssignmentsOperations>", "<xref:azure.mgmt.resource.v2015_10_01_preview.operations.PolicyDefinitionsOperations>", "<xref:azure.mgmt.resource.v2016_04_01.operations.PolicyDefinitionsOperations>", "<xref:azure.mgmt.resource.v2016_12_01.operations.PolicyDefinitionsOperations>", "<xref:azure.mgmt.resource.v2017_06_01_preview.operations.PolicyDefinitionsOperations>", "<xref:azure.mgmt.resource.v2018_03_01.operations.PolicyDefinitionsOperations>", "<xref:azure.mgmt.resource.v2018_05_01.operations.PolicyDefinitionsOperations>", "<xref:azure.mgmt.resource.v2019_01_01.operations.PolicyDefinitionsOperations>", "<xref:azure.mgmt.resource.v2019_06_01.operations.PolicyDefinitionsOperations>", "<xref:azure.mgmt.resource.v2019_09_01.operations.PolicyDefinitionsOperations>", "<xref:azure.mgmt.resource.v2017_06_01_preview.operations.PolicySetDefinitionsOperations>", "<xref:azure.mgmt.resource.v2018_03_01.operations.PolicySetDefinitionsOperations>", "<xref:azure.mgmt.resource.v2018_05_01.operations.PolicySetDefinitionsOperations>", "<xref:azure.mgmt.resource.v2019_01_01.operations.PolicySetDefinitionsOperations>", "<xref:azure.mgmt.resource.v2019_06_01.operations.PolicySetDefinitionsOperations>", "<xref:azure.mgmt.resource.v2019_09_01.operations.PolicySetDefinitionsOperations>".

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Add support for multiple copies of operators and an MPI event loop

This allows multiple copies of operators to run either on the local node or on separate remote nodes. Running multiple operators on a single node with rank != 0 is not currently supported, but would be easy to add in the future.
This also adds an MPI event loop that grabs tasks from the queue and sends them to the remote operators for them to
work on.
This also removes some of the previously needed location stuff.
To do:

[x] Figure out why display class is receiving mismatched x and y when using MPI
[ ] Figure out why I'm having some MPI issues on cori (including why more than 5 nodes causes some communication issues)

We are thinking to merge this and iterate on improvements in the future.

To follow up on this, I figured out that this MPI example on Cori is having issues because the highest level of thread support is MPI_THREAD_SERIALIZED, but I thought it was MPI_THREAD_MULTIPLE.


[Migration] Oauth apps are not accessible after migration

Describe the issue:
The Oauth apps are not accessible from the Console after migration from WSO2IS-5.10.0 to WSO2IS-5.11.0.
The Console is calling the REST API https://localhost:9443/api/server/v1/applications/a69137ae-5711-4578-bd14-a68f2006e850/inbound-protocols/openid to load the Oauth configs. The correct endpoint should be https://localhost:9443/api/server/v1/applications/a69137ae-5711-4578-bd14-a68f2006e850/inbound-protocols/oidc
How to reproduce:

Register a service provider with OAuth/OpenID Connect Configuration in WSO2IS 5.10.0
Do the migration from 5.10.0 to 5.11.0
Login to the console app and try to access the registered service provider

The root cause for this issue is tracked as a separate task in https://github.com/wso2/product-is/issues/9620.


Extension crashing - no usable version of libssl was found

When using the extension on a machine running Arch Linux, the following messages are shown in the output tab:
No usable version of libssl was found
[Info  - 17:51:55] Connection to server got closed. Server will restart.

This repeats 5 times until The server will not be restarted shows up (referring to the 'Avalonia Preview Language Server') and the extension fails.
I have OpenSSL installed to the latest version:
$ openssl version
OpenSSL 3.0.8 7 Feb 2023 (Library: OpenSSL 3.0.8 7 Feb 2023)

Hello,
try this option https://github.com/rstm-sf/view-avalonia-preview-vscode/actions/runs/4525983634
I upgraded .net from version 3 to 6. The problem seems to be gone https://github.com/rstm-sf/view-avalonia-preview-vscode/pull/15

I can confirm the crashes no longer occur on my end either. Thanks for the quick response!


Use TextEditor.transact

This fixes #57 and (probably) atom/vim-mode#703.
Apparently, using TextBuffer's history checkpoints caused problems with undoing, both through vim-mode's u or through core's Ctrl-Z.

Bump @lloeki

Sorry for the delay, things are a bit bumpy here and will be for a month or two.


Create mode where incorrect assignments trigger errors

Would it be possible to create a version of uint such that
a = -10
results in the program terminating with ERROR STOP?

I think it's probably possible and wouldn't be a bad idea to make one.
If you don't mind, could you give me an example of a situation where this ERROR STOP is particularly necessary?

This feature added in the version 0.1.
cf. README.md#forbid-assignment-of-negative-numbers


MINOR: update docs with regard to KIP-123

Missed some changes in #3194
Call for review @bbejeck @dguy @enothereska @miguno @guozhangwang

Updated

Updated again.

LGTM!


Final fixes plus portfolio pages

There are a few thing here that I'd like to iterate on, but considering the deadline, we'll have to address them later.  :shipit:


is there any way to get .schematic files not .SCHEM

Lite2Edit does not provide a way to get old .schematic files. You can use this resource instead: https://puregero.github.io/SchemToSchematic/


lanzaboote-tool: init at 0.3.0

Description of changes
Split of #231951 for ease of review and getting this done, as requested by reviewers.

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

The tests fail on aarch64-linux. Should we just mark it as a bad platform for now to get this merged?

The tests fail on aarch64-linux. Should we just mark it as a bad platform for now to get this merged?

That makes sense, yes.

The tests fail on aarch64-linux. Should we just mark it as a bad platform for now to get this merged?

I adopted rather an allow-list than a block-list because every other architecture won't work with lanzaboote for now.
In the future, we should adopt the badPlatforms = [ lib.systems.inspect.patterns.hasEfi ]; mechanism, in my opinon.
So we filter out any platform that is not known to possess UEFI for that specific variant of the lanzatool which will anyway be UEFI-only.


install: does not remove path from files

While compiling python3 in nixpkgs I noticed that install does not properly work:
Python uses the similar commands to the following command autogenerated by autoconf to install files:
/store/7rj52iy8gvdwkrca5k35a7i4hhdgf90c-uutils-coreutils-0.0.4/bin/install -c -m 644 ./Lib/unittest/runner.py /nix/store/bg19k3h973swd0745mhhp5snzijz7hx3-python3-3.8.8/lib/python3.8/unittest

but install converts that to a wrong path and then prints that the directory does not exist:
install: error: cannot install './Lib/unittest/runner.py' to '/nix/store/bg19k3h973swd0745mhhp5snzijz7hx3-python3-3.8.8/lib/python3.8/unittest/./Lib/unittest/runner.py': the source path is not an existing regular file

A minimal reproduce is:
mkdir -p Lib/unittest lib/unittest
touch Lib/unittest/runner.py
install ./Lib/unittest/runner.py lib/unittest
install: error: cannot install './Lib/unittest/runner.py' to 'lib/unittest/./Lib/unittest/runner.py': No such file or directory (os error 2)

High-five @DoBi, we were in sync 😄

High-five @DoBi, we were in sync smile

Yeah, I just noticed that.
I took a look at cp, because with it the copying works. I tried to use the some of the logic from there.
And I also added a test. But your solution looks more clean. Just a few lines instead of my bigger changes. :smile:

@DoBi mind if I merge your test into my PR? I have to add one

@DoBi mind if I merge your test into my PR? I have to add one

Feel free to use it ;)


multimodal data modeling in MIL

Feature

Not sure if it's already in the plan but it'd be great if we can incorporate multimodal data in MIL just like the regular train() dose.
Pitch

Incorporating multimodal data in image processing is increasingly important as clinical studies routinely collect multiple data types. It should help to improve the model's performance.
Alternatives

Additional context

Thank you, this is a great idea. I will add it to the feature list. It will get included in 2.1 or 2.2.

Perfect! Thanks for considering it.

So we're not quite ready for multimodal integration with clinical variables, but in version 2.2 we did just release a multimodal MIL strategy that allows you to train models at multiple magnification levels simultaneously (see here). This has laid the groundwork for future expansion into other types of mode integration (such as clinical variables, gene expression etc). Multimodal integration with non-pathology modalities is our next priority - stay tuned!

It's nice to see the progress. Thank you for your efforts, James!


When given any permission to any object, ensure that has_read is also granted.

If a group is granted any permissions to any namespaced object, they will need has_read. It makes little sense to delete or patch objects one can't read, and creating things you can't see may have a niche use, but... No.

Fixed in https://github.com/terjekv/hubuum/commit/0945bb227f02ac1f4cbc35e8a769c33871dc620a if one uses POST to the endpoint /namespace/<namespaceid>/groups/<groupid>.


use context to react to signal interrupts from the user

If the user hits CTL-C mid command, sherlock needs take care of open files and more importantly unwritten data which might only be in-memory.
Each sherlock.Func must receive the ctx context.Background() as a first parameter and handle cancelation.

@KonstantinGasser I'm trying to figure out what are the problems in existing code-base; Because the files opened in code for writes or reads are closed via defer f.Close()
Also, another part which I'm also confused about is: what part of command execution is leaving the data in-memory? Because the code is using afero.FS and that should do clean-up of in-memory traces of opened files. In afero code, for e.g. WriteFile function, it is opening & doing read/write to the file & closing it, so consumer of afero wouldn't get any handle to clean-up in-memory data brought-in or written by afero's local File f instance.
It would be helpful for me to understand which of the commands is leaving traces behind? Do you have any flow that leaves remnants of unwritten data. Thanks!

Hi @amit-pub thanks for that threat, it made me walkthrough the code again checking on the things you described. And I agree there is no obvious place in which it could happen.
I guess the worries I have are with the io.Copy (e.x in fs.CreateGroup) func which if an error occurs returns the number of bytes written along with the error and therefore could cause a partial write to the file. But yes using a context would not fix that.


Fast Youtube Downloader with aria2c

Download youtube videos parallel with threads using aria2c

Thank you for you contribution to the repo and the community
On 10 Feb 2017, at 19:18, Yash Ladha<EMAIL_ADDRESS>wrote:

Download youtube videos parallel with threads using aria2c
You can view, comment on, or merge this pull request online at:
https://github.com/geekcomputers/Python/pull/123
Commit Summary
Meme Generator Python
fast youtube downloader with aria2c
fast youtube downloader with aria2c
File Changes
M README.md (2)
A meme_maker.py (47)
A youtube-downloader fast.py (18)
Patch Links:
https://github.com/geekcomputers/Python/pull/123.patch
https://github.com/geekcomputers/Python/pull/123.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


1D-2D Code Extractor

Description of the new feature / enhancement
similar to the text extractor, but aimed at decoding common 1D (C128, i2o5,..)  or 2D (Datamatrix, QR, ...) codes on screen.
Scenario when this would be used?
Documents or pictures may contain machine readable codes - most users will grab their phone to take a picture of the screen, then send the result back to the pc via chat or mail clients.
Code Extractor would directly place the decoded content on the clipboard for and / or offer calling hyperlinks in the default browser.
Supporting information
No response

/dup https://github.com/microsoft/PowerToys/issues/4859


Improve README

The shields' centering doesn't work for now, I'll turn this PR to draft until I fix this

I'm more in favor of merging this PR now and having another PR later to center the badges. IMHO, it's not as important as correcting the logo size or the link.

Sounds reasonable, merging!


chore(main): release 0.8.3

:robot: I have created a release beep boop
0.8.3 (2024-10-05)
Bug Fixes

fix Release Me tagging strategy (#39) (21a182b)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.8.3
:sunflower:


alert repeatedly in chrome and opera

Expected behaviour
I thought that it can show a tooltip saying 'Copy success!' in clipboard.on() method.
Actual behaviour
According to the following way. in chrome or opera,if i clicked to copy button one time,alert the 'Copied!' message one time. if i clicked two times,alert two times. And so on,it can alert a lot of times message if you clicked a lot of times
Steps to reproduce
1,by onClick method to invoke clipboard.
2,in clipboard.on('success') function to alert message.
html:
<button class="btn" onClick="copy();" data-clipboard-action="copy" data-clipboard-target="#foo">Copy</button>
js:
`
function copy(){
var clipboard = new Clipboard(".btn");
clipboard.on('success', function(e) {
    console.log(e);
    alert(' copy success');
    clipboard.destory();
});

clipboard.on('error', function(e) {
    console.log(e);
    alert('copy fail');
});

`
please help analyze it. thanks

Clipboard.js already adds a click listener for you, you don't need to add another one. Please see the demos to better understand how the API works.


Constant variable as temporary storage for active memory

using Enzyme;

function model(a)
    b = a
    c = a .* 2
    return b, c
end;

function objective(x, a, loss, m)
    b, c = m(a)
    loss[1] = sum(x) + sum(b)
end;

x = rand(2);
dx = zero(x);
a = rand(2);
loss = [0.0];
dloss = [1.0];
Enzyme.autodiff(Enzyme.Reverse, objective,  Enzyme.Duplicated(x, dx),
                                            Enzyme.Const(a),
                                            Enzyme.Duplicated(loss, dloss),
                                            Enzyme.Const(model)
                                            );

I don't know what's going on here.
ERROR: Enzyme execution failed.
Mismatched activity for:   store {} addrspace(10)* %1, {} addrspace(10)** %.repack, align 8, !dbg !177, !noalias !178 const val: {} addrspace(10)* %1
Type tree: {[-1]:Pointer, [-1,0]:Pointer, [-1,0,-1]:Float@double, [-1,8]:Integer, [-1,9]:Integer, [-1,10]:Integer, [-1,11]:Integer, [-1,12]:Integer, [-1,13]:Integer, [-1,14]:Integer, [-1,15]:Integer, [-1,16]:Integer, [-1,17]:Integer, [-1,18]:Integer, [-1,19]:Integer, [-1,20]:Integer, [-1,21]:Integer, [-1,22]:Integer, [-1,23]:Integer, [-1,24]:Integer, [-1,25]:Integer, [-1,26]:Integer, [-1,27]:Integer, [-1,28]:Integer, [-1,29]:Integer, [-1,30]:Integer, [-1,31]:Integer, [-1,32]:Integer, [-1,33]:Integer, [-1,34]:Integer, [-1,35]:Integer, [-1,36]:Integer, [-1,37]:Integer, [-1,38]:Integer, [-1,39]:Integer}
You may be using a constant variable as temporary storage for active memory (https://enzyme.mit.edu/julia/stable/#Activity-of-temporary-storage). If not, please open an issue, and either rewrite this variable to not be conditionally active or use Enzyme.API.runtimeActivity!(true) as a workaround for now

Stacktrace:
 [1] model
   @ ~/minimal_example.jl:6

Stacktrace:
 [1] throwerr(cstr::Cstring)
   @ Enzyme.Compiler ~/.julia/packages/Enzyme/Z027x/src/compiler.jl:3016

Sorry, the minimal example is wrong.
b = a

is a constant variable used as temporary storage...


Ignore annots and comments so they don't disrupt the lilypond input code

Depending on where an <annot> occurs, it might currently disrupt the Lilypond input code as its content might be copied by <apply-templates>. Comments are likely not a problem, but it doesn't hurt to ignore them explicitly.

Great. Could you split them and put them to the "excluded elements" section?

Done and understood.


Error on creating RCyjs object

I attempted to construct an RCyjs object in R 4.2 in order to submit my graphnel to the browser and obtain coordinates, but I received the following error (I was surprised to see the same error on the package help run example):
"Error in sprintf("port not available: %d", port): invalid format '%d'; use format %s for character objects"
It is crucial to note that the code was functioning prior to the upgrading of my system (R, R studio, and packages).
The code that I was running is the following:
 g <- simpleDemoGraph()   rcy <- RCyjs(title="rcyjs demo", graph=g)
Thank you

Version number, please?

On Apr 13, 2023, at 12:51 PM, caligarimga @.***> wrote:
I attempted to construct an RCyjs object in R 4.2 in order to submit my graphnel to the browser and obtain coordinates, but I received the following error (I was surprised to see the same error on the package help run example):
"Error in sprintf("port not available: %d", port): invalid format '%d'; use format %s for character objects"
It is crucial to note that the code was functioning prior to the upgrading of my system (R, R studio, and packages).
The code that I was running is the following:
g <- simpleDemoGraph() rcy <- RCyjs(title="rcyjs demo", graph=g)
Thank you
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

The issue is with RCyjs and BrowserViz version 2.20.0.
I examined the code and compared it to version 2.16.
The function BrowserViz was altered in 2.20.0 to add the "host" parameter, which was missing in 2.16, however the call from .RCyjs was not updated to incorporate the new argument.

Very helpful.  I’ll tend to this later today, tomorrow for sure.

Paul

On Apr 14, 2023, at 11:25 AM, JFMSilva @.***> wrote:
The issue is with RCyjs and BrowserViz version 2.20.0.
I examined the code and compared it to version 2.16.
The function BrowserViz was altered in 2.20.0 to add the "host" parameter, which was missing in 2.16, however the call from .RCyjs was not updated to incorporate the new argument.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

fixed in RCyjs 2.21.1,  in Bioconductor.
Thanks for the bug report, and sorry for the trouble.

Thank you, Paul


KubernetesApplicationResource cannot find kubeconfig secret

What happened?
I was going through Wordpress AWS tutorial on master branch: https://crossplane.io/docs/master/workloads/aws/wordpress-aws.html
All the managed resources are created. An EKS cluster is created and its CR in crossplane-system namespace is as the following:
apiVersion: compute.aws.crossplane.io/v1alpha1
kind: EKSCluster
metadata:
  creationTimestamp: "2019-07-18T14:07:52Z"
  finalizers:
  - finalizer.eks.compute.aws.crossplane.io
  generation: 7
  name: kubernetescluster-6e9d0373-a965-11e9-b71a-b2d7db51bd10
  namespace: crossplane-system
  ownerReferences:
  - apiVersion: compute.crossplane.io/v1alpha1
    kind: KubernetesCluster
    name: wordpress-demo-cluster
    uid: 6e9d0373-a965-11e9-b71a-b2d7db51bd10
  resourceVersion: "22199"
  selfLink: /apis/compute.aws.crossplane.io/v1alpha1/namespaces/crossplane-system/eksclusters/kubernetescluster-6e9d0373-a965-11e9-b71a-b2d7db51bd10
  uid: 6e9e5466-a965-11e9-b71a-b2d7db51bd10
spec:
  claimRef:
    apiVersion: compute.crossplane.io/v1alpha1
    kind: KubernetesCluster
    name: wordpress-demo-cluster
    namespace: complex
    uid: 6e9d0373-a965-11e9-b71a-b2d7db51bd10
  classRef:
    apiVersion: core.crossplane.io/v1alpha1
    kind: ResourceClass
    name: standard-cluster
    namespace: crossplane-system
    uid: f27883f4-a940-11e9-b71a-b2d7db51bd10
  providerRef:
    name: aws-provider
    namespace: crossplane-system
  reclaimPolicy: Delete
  region: us-east-1
  roleARN: arn:aws:iam::950045500142:role/monus-eks-role
  securityGroupIds:
  - sg-0bc557c98cbb2521d
  subnetIds:
  - subnet-0fa207eb75bc9fcff
  - subnet-01fcfecfc0d81d151
  - subnet-038f899cf5140a46e
  vpcId: vpc-07406739e139a36d0
  workerNodes:
    clusterControlPlaneSecurityGroup: sg-0bc557c98cbb2521d
    keyName: monus-keypair
    nodeAutoScalingGroupMaxSize: 1
    nodeAutoScalingGroupMinSize: 1
    nodeGroupName: demo-nodes
    nodeInstanceType: m3.medium
  writeConnectionSecretToRef:
    name: 6e9d0373-a965-11e9-b71a-b2d7db51bd10
status:
  bindingPhase: Bound
  cloudformationStackId: arn:aws:cloudformation:us-east-1:950045500142:stack/eks-6e9e5466-a965-11e9-b71a-b2d7db51bd10/84579a10-a967-11e9-bb52-124d1eab42ba
  conditions:
  - lastTransitionTime: "2019-07-18T14:09:17Z"
    reason: Successfully reconciled managed resource
    status: "True"
    type: Synced
  - lastTransitionTime: "2019-07-18T14:29:33Z"
    reason: Managed resource is available for use
    status: "True"
    type: Ready
  endpoint: https://C85CED3CB0B32BECA30917AF2E228CC8.gr7.us-east-1.eks.amazonaws.com
  resourceName: eks-6e9e5466-a965-11e9-b71a-b2d7db51bd10
  state: ACTIVE

The KubernetesCluster claim that wanted it is the following in the complex namespace:
apiVersion: compute.crossplane.io/v1alpha1
kind: KubernetesCluster
metadata:
  creationTimestamp: "2019-07-18T14:07:52Z"
  finalizers:
  - finalizer.resourceclaim.crossplane.io
  generation: 2
  labels:
    app: wordpress-demo
    provider: aws
  name: wordpress-demo-cluster
  namespace: complex
  resourceVersion: "22200"
  selfLink: /apis/compute.crossplane.io/v1alpha1/namespaces/complex/kubernetesclusters/wordpress-demo-cluster
  uid: 6e9d0373-a965-11e9-b71a-b2d7db51bd10
spec:
  classRef:
    name: standard-cluster
    namespace: crossplane-system
  resourceRef:
    apiVersion: compute.aws.crossplane.io/v1alpha1
    kind: EKSCluster
    name: kubernetescluster-6e9d0373-a965-11e9-b71a-b2d7db51bd10
    namespace: crossplane-system
  writeConnectionSecretToRef: {}
status:
  bindingPhase: Bound
  conditions:
  - lastTransitionTime: "2019-07-18T14:29:33Z"
    reason: Managed resource is available for use
    status: "True"
    type: Ready
  - lastTransitionTime: "2019-07-18T14:07:52Z"
    reason: Successfully reconciled managed resource
    status: "True"
    type: Synced

You might notice that the former has spec.writeConnectionSecretToRef populated and pointing to the secret, but the latter doesn't. Even if it did, it would point to a wrong secret since that field is a LocalObjectReference, meaning the object it refers to has to exist in the same namespace. However, the secret resides in crossplane-system namespace and KubernetesCluster CR is in complex namespace.
See https://github.com/crossplaneio/crossplane/blob/master/pkg/apis/core/v1alpha1/resource.go#L89
Due to this field being empty, I see the following error in all 3 KubernetesApplicationResources:
- lastTransitionTime: "2019-07-18T14:12:24Z"
    message: 'cannot create Kubernetes client configuration: cannot get secret complex/:
      Secret "" not found'
    reason: Encountered an error during managed resource reconciliation
    status: "False"
    type: Synced

Hence nothing is deployed to the EKS cluster that is created.
How can we reproduce it?
Follow https://crossplane.io/docs/master/workloads/aws/wordpress-aws.html
What environment did it happen in?
Crossplane commit: 22978895d42ae84c42caa78ef653dd8013e528d6
K8s: Minikube 1.13.1

Fixed by https://github.com/crossplaneio/crossplane/pull/811


[HTTP V2] Asynchronous inference support

Have a look here. You are using resize() instead of np.resize()
This is fixed in #1227 by this commit.


Fixes #1983: Failure on creation of a schema history table on an empty database

A transaction should be rolled back after an error if autoCommit mode is set to false. Every error spoils the transaction.

Hi @axelfontaine,
Should I do anything else to get this commit merged in version 5.1.0?

@axelfontaine, I have the same problem and hope the PR will be merged soon.

Thanks for the PR. We ended up fixing this differently.


Don't fail the gradle task if the baseline file doesn't exist

Related with #3024 (this one is probably a prerequisite)
Expected Behavior
If a baseline is configured in gradle but the file doesn't exist the task should not fail
Current Behavior
It fails.
Context
This is how we have it configured:
    @get:InputFile
    @get:Optional
    @get:PathSensitive(PathSensitivity.RELATIVE)
    val baseline: RegularFileProperty = project.objects.fileProperty()

and it seems that @get:InputFile forces the file to exist. And if it doesn't exist it fails. I tried to fix it but I know little about gradle.
I created the test already if someone want to use it: https://github.com/detekt/detekt/tree/baseline-doesnt-exist

https://docs.gradle.org/current/userguide/more_about_tasks.html#sec:task_input_output_validation Yes @InputFile requires the property to have a value and the file to exist.
Why would we want the task detekt to succeed? Do we expect users to run detektBaseline first?

https://docs.gradle.org/current/userguide/more_about_tasks.html#sec:task_input_output_validation Yes @InputFile requires the property to have a value and the file to exist.
Why would we want the task detekt to succeed? Do we expect users to run detektBaseline first?

Each time that I create a new module I need to create the baselines files again (two because main and debug). A new module doesn't have debt so it should not need baseline.
And there's nearly no problem with miss configuration. If you miss configure your baseline you are going to find out it because of all the issues.

Each time that I create a new module I need to create the baselines files again (two because main and debug). A new module doesn't have debt so it should not need baseline.
And there's nearly no problem with miss configuration. If you miss configure your baseline you are going to find out it because of all the issues.

We could use the following workaround:
    if (file("$projectDir/detekt/baseline.xml").exists()) {
        baseline = file("$projectDir/detekt/baseline.xml")
    }

We could use the following workaround:
    if (file("$projectDir/detekt/baseline.xml").exists()) {
        baseline = file("$projectDir/detekt/baseline.xml")
    }

I like the way Android Lint handles baseline files - there's no task required to create baselines, instead it will create the baseline file if it's configured but the file doesn't exist yet, and reads it when running the lint task.
I've always thought this would be a good model for detekt to adopt. It would also help detekt-compiler-plugin remain "taskless", since there's no need for the createBaseline task.

I like the way Android Lint handles baseline files - there's no task required to create baselines, instead it will create the baseline file if it's configured but the file doesn't exist yet, and reads it when running the lint task.
I've always thought this would be a good model for detekt to adopt. It would also help detekt-compiler-plugin remain "taskless", since there's no need for the createBaseline task.

I like the way Android Lint handles baseline files - there's no task required to create baselines, instead it will create the baseline file if it's configured but the file doesn't exist yet, and reads it when running the lint task.
I've always thought this would be a good model for detekt to adopt. It would also help detekt-compiler-plugin remain "taskless", since there's no need for the createBaseline task.

I like the way Android Lint handles baseline files - there's no task required to create baselines, instead it will create the baseline file if it's configured but the file doesn't exist yet, and reads it when running the lint task.
I've always thought this would be a good model for detekt to adopt. It would also help detekt-compiler-plugin remain "taskless", since there's no need for the createBaseline task.

The concern is gradle cacheability, if the baseline file content gets changed (even we shouldn't, but sometimes it does), we should fail the up-to-date. Supporting this issue requires manually performing upToDate checks, which could be an overhead in the long run.

The concern is gradle cacheability, if the baseline file content gets changed (even we shouldn't, but sometimes it does), we should fail the up-to-date. Supporting this issue requires manually performing upToDate checks, which could be an overhead in the long run.

I think the mentioned workaround from @chao2zhang is a good idea. Hence, I second that.

I think the mentioned workaround from @chao2zhang is a good idea. Hence, I second that.

docs.gradle.org/current/userguide/more_about_tasks.html#sec:task_input_output_validation Yes @InputFile requires the property to have a value and the file to exist.

I believe our case is an exception. From the paragraph just below: https://docs.gradle.org/current/userguide/more_about_tasks.html#sec:task_input_output_validation
You will occasionally want to disable some of this validation, specifically when an input file may validly not exist. That’s why Gradle provides the @Optional annotation: you use it to tell Gradle that a particular input is optional and therefore the build should not fail if the corresponding file or directory doesn’t exist.

Hence I belive we should be able to update the Gradle logic to follow the same as Android lint:

No baseline specified => Do nothing with baselines
Baseline specified AND file missing => Create the baseline (delegate to the @TaskAction of detektBaseline).
Baseline specified AND file existing => Read and use the baseline.

docs.gradle.org/current/userguide/more_about_tasks.html#sec:task_input_output_validation Yes @InputFile requires the property to have a value and the file to exist.

I believe our case is an exception. From the paragraph just below: https://docs.gradle.org/current/userguide/more_about_tasks.html#sec:task_input_output_validation
You will occasionally want to disable some of this validation, specifically when an input file may validly not exist. That’s why Gradle provides the @Optional annotation: you use it to tell Gradle that a particular input is optional and therefore the build should not fail if the corresponding file or directory doesn’t exist.

Hence I belive we should be able to update the Gradle logic to follow the same as Android lint:

No baseline specified => Do nothing with baselines
Baseline specified AND file missing => Create the baseline (delegate to the @TaskAction of detektBaseline).
Baseline specified AND file existing => Read and use the baseline.

But we do have the Optional annotation already and the task fails before we can run our own code.

But we do have the Optional annotation already and the task fails before we can run our own code.

But we do have the Optional annotation already and the task fails before we can run our own code.

Seems like there is an open issue for exactly this on Gradle's end https://github.com/gradle/gradle/issues/2016

But we do have the Optional annotation already and the task fails before we can run our own code.

Seems like there is an open issue for exactly this on Gradle's end https://github.com/gradle/gradle/issues/2016

Nice! There are some workaround there that I'll try. Thanks!!

Nice! There are some workaround there that I'll try. Thanks!!

We should also consider changing @get:InputFile to @get:Input as we'll be using the Path rather than the file content for task avoidance.

We should also consider changing @get:InputFile to @get:Input as we'll be using the Path rather than the file content for task avoidance.

We should also consider changing @get:InputFile to @get:Input as we'll be using the Path rather than the file content for task avoidance.

But, if the content of the baseline changes we want to rerun the task because the output of detekt can change, right? I think that we should keep using @get:InputFile

We should also consider changing @get:InputFile to @get:Input as we'll be using the Path rather than the file content for task avoidance.

But, if the content of the baseline changes we want to rerun the task because the output of detekt can change, right? I think that we should keep using @get:InputFile

But, if the content of the baseline changes we want to rerun the task because the output of detekt can change, right?

Agree. Though we're forced to specify a valid file (we can't just create it if it's missing).

But, if the content of the baseline changes we want to rerun the task because the output of detekt can change, right?

Agree. Though we're forced to specify a valid file (we can't just create it if it's missing).

I wonder if the baseline could be generated as a report and dropped in the reports directory? That would mean separate parameters are used for task input and output for the baseline file which makes it simple to solve the original issue.
If the file is generated by default the flow would be:

Run detekt
Copy baseline file from report output directory to a location of user's choice
Configure the input file location to be used for the check task(s)

There's nothing happening implicitly here which is nice in some respects but it would be awkward when the baseline changes often because of the manual copy/paste.

I wonder if the baseline could be generated as a report and dropped in the reports directory? That would mean separate parameters are used for task input and output for the baseline file which makes it simple to solve the original issue.
If the file is generated by default the flow would be:

Run detekt
Copy baseline file from report output directory to a location of user's choice
Configure the input file location to be used for the check task(s)

There's nothing happening implicitly here which is nice in some respects but it would be awkward when the baseline changes often because of the manual copy/paste.

Run detekt
Copy baseline file from report output directory to a location of user's choice
Configure the input file location to be used for the check task(s)

True, but this is as manual as:

Run detektBaseline
Configure the input file location to be used for the check task(s)
Run detekt

That is our status quo so probably not really worth to pursue.

Run detekt
Copy baseline file from report output directory to a location of user's choice
Configure the input file location to be used for the check task(s)

True, but this is as manual as:

Run detektBaseline
Configure the input file location to be used for the check task(s)
Run detekt

That is our status quo so probably not really worth to pursue.

Configure the input file location to be used for the check task(s)

That depends on whether https://github.com/detekt/detekt/issues/1260 is addressed or not - if it is, this middle step could be removed (which is really another point in leaving the process as is, just thought I'd mention that other fairly stale issue).

Configure the input file location to be used for the check task(s)

That depends on whether https://github.com/detekt/detekt/issues/1260 is addressed or not - if it is, this middle step could be removed (which is really another point in leaving the process as is, just thought I'd mention that other fairly stale issue).


Extract code blocks early

Since will look at allowing latex, the curly braces in code blocks (e.g. in types in Julia) would clash.
These should be extracted early and potentially fed back in just before the HTML parsing which handles block codes just fine.

can do it just after extraction of definitions based on whether hascode=true


How can I return Object instead of JSON String from Squiggly API

Instead of returning a Simple JSON String, using Squiggly.stringify how can I return an Java Object after ObjectMapper objectMapper = Squiggly.init(new ObjectMapper(), filter); as been performed on the filter variables.

You can convert your object to a Map:
Map converted = objectMapper.convertValue(someObject, Map.class);

or a list of maps
CollectionType collectionType = objectMapper.getTypeFactory().constructCollectionType(List.class, Map.class);
        List<Map> converted = objectMapper.convertValue(someList, collectionType);

However, I'd like to learn more about your use case.  Using Squiggly.init with a static filter is usually only useful for demonstration purposes.  Most people are using Squiggly in a web application.


Edit hdinsight-use-pig.md

Edit complete: Also sending this info to Larry:
Line 43: You just talked about UDFs, so I think that is what you mean here. Please check to be sure.
Azure Blob storage: I don’t think this is the correct term. We can refer to “blobs in Azure Storage” or “Blob storage in Azure.” I started making these changes, but decided to leave it to you. In addition to the Azure style guide, for a reference, check this out:
http://azure.microsoft.com/en-us/documentation/articles/storage-introduction/#blob-storage
Lines 55-61: You reference WASB (Windows Azure Storage Blob)…remember that we are no longer using “Windows Azure.” Fix that where you can.
Line 88: Can you update “for now”?

Hi @ClarityQueen, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (v-diree). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, or work for Microsoft Open Technologies, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

looks good, thanks.


Using Nix for these scripts

Maybe it would be a cool idea to use Nix for all these scripts, considering it would make them completely reproducible independently of whatever distro someone uses, or what packages they have on their systems... They also could be bundled into a OCI image with all required dependencies to run them if that would be better!

Interesting idea. How much of Nix do you have to ship to take a single binary with you? like neovim for example?

It shouldnt be too much of a hassle, to package these scripts we just need their dependencies and write some functions and thats it, we dont even need to change the scripts in any way. Im going to make a PR showcasing that later today

nix bundle nixpkgs#duf creates a file called duf which is a symlink to a file in the nix store. copy that file and rename it to duf and put it in your path on a machine without nix and it works perfectly.
Nix creates self-executing archive files. arx format, which is new to me. It contains the binary and all deps in one file. works the same as a regular executable, but the first invocation was a little slower than usual.
So you're onto something @tulilirockz - this could be awesome.
Next step would be to build a wrapper around the whole process that takes a nix reference and outputs a sysext. build-from-nix nixpkgs#duf
I'm curious if there are any hidden gotchas or negatives to this, other than the binaries being kind of on the fatter side since they're static+deps all bundled together.

inside a nixos/nix container you run this:
nix bundle nixpkgs#hello --extra-experimental-features nix-command flakes

Pretty sure there shouldnt be any gotchas from that, considering that these bundled nix packages, without a sandbox, are pretty much just statically compiled programs. It would be pretty awesome to just have a flake that has all the scripts in it, then use Github Action with nix to bundle them, and release with "gh release"

Also, an update on this nix packaging situation. Im currently writing a PR for Blincus that does just that, it would be so awesome to just distribute these scripts without needing a compiled language or anything like that!

The only thing I got a bit caught up on was that the function that I'm using to package these scripts symlinkJoin, adds them to their relative PATHs, that might generate some kind of conflict depending on what is the name of the script. E.g.: When packaging Blincus as a nix package, I ran into a infinite recursion because the script install called itself indefinitely, instead of running GNU Install.

Although there are some drawbacks listed on https://github.com/matthewbauer/nix-bundle, namely the slow startup... That might be an issue

This could be even cooler considering NixOS has some other bundlers like "toRPM"... that generates RPM packages! It would be amazing to just distribute that to everyone, like, as easily as that!

see commit https://github.com/ublue-os/sysext/commit/3638ec2c7eb98d812e6089f847d861596de09fc3
the just albafetch recipe builds a nix generic container, then calls nix_bundle_sysext.sh which takes a flakeref (can be nixpkgs#hello format or a URL format), runs the nix bundle, creates the extension.

❯ albafetch
          /:-------------:\            bjk@beast
       :-------------------::          ---------
     :-----------/shhOHbmp---:\        Uptime: 13h 54m
   /-----------omMMMNNNMMD]  ---:      ---------------
  :-----------sMMMMNMNMP.    ---:      OS: Fedora Linux 39.20240115.0 (Bluefin) x86_64
 :-----------:MMMdP-------    ---\     Kernel: 6.6.9-200.fc39.x86_64
,------------:MMMd--------    ---:     Desktop: GNOME
:------------:MMMd-------    .---:     Shell: nix-user-chroot
:----    oNMMMMMMMMMNho     .----:     Terminal: xterm-256color
:--     .+shhhMMMmhhy++   .------/     ------------------------
:-    -------:MMMd--------------:      Host: XPS 8950
:-   --------/MMMd-------------;       CPU: Intel Core i7-12700 @ 0.8 GHz (20)
:-    ------/hMMMy------------:        GPU: TU104 [GeForce RTX 2080
:-- :dMNdhhdNMMNo------------;         Memory: 11292 MiB / 64016 MiB (17%)
:---:sdNMMMMNds:------------:
:------:://:-------------::
:---------------------://

Moved to #3


Finish mappings

fixed all item mappings except for Bundles (still 248)
mapped all candles to sea pickles, with correct waterlog/quantity
mapped cake candles to full cakes

Added the correct map for potted azalea. It can't be mapped to a different potted variant in the mappings because everything potted is just mapped to flower_pot, so I guess it will have to be a Geyser thing.


Team assignment scheduling

when a team member is discovered to have been previously infected, all his contacts are put in isolation.
What is needed is a scheduling system which sets up personnel schedules so that the number of infected co-workers is minimized, while still allowing some flexibility in rescheduling.
a secondary problem is with hospital experts which come to consult on cases, and also stand the risk of being sent to isolation, potentially robbing the hospital of that specialty.

waiting for specific details. a team is in standby.