Smoke test

Docs Build status updates of commit d9949a4:
:warning: Validation status: warnings

File
Status
Preview URL
Details

:warning:Warning

Details

api/Microsoft.Azure.Cosmos.TransactionalBatchRequestOptions.ConsistencyLevel.yml
:warning:Warning
View
Details

api/overview/azure/core-readme.md
:white_check_mark:Succeeded
View

api/overview/azure/core.experimental-readme-pre.md
:white_check_mark:Succeeded
View

api/overview/azure/microsoft.core.newtonsoftjson-readme-pre.md
:white_check_mark:Succeeded
View

xml/FrameworksIndex/azure-dotnet-preview.xml
:white_check_mark:Succeeded

xml/FrameworksIndex/azure-dotnet.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Fluent/CompositeIndexDefinition`1.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Fluent/ConflictResolutionDefinition.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Fluent/ContainerBuilder.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Fluent/ContainerDefinition`1.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Fluent/CosmosClientBuilder.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Fluent/IndexingPolicyDefinition`1.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Fluent/PathsDefinition`1.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Fluent/SpatialIndexDefinition`1.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Fluent/UniqueKeyDefinition.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Linq/CosmosLinqExtensions.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Scripts/Scripts.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Scripts/StoredProcedureExecuteResponse`1.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Scripts/StoredProcedureProperties.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Scripts/StoredProcedureRequestOptions.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Scripts/StoredProcedureResponse.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Scripts/TriggerOperation.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Scripts/TriggerProperties.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Scripts/TriggerResponse.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Scripts/TriggerType.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Scripts/UserDefinedFunctionProperties.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Scripts/UserDefinedFunctionResponse.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/BoundingBox.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/Crs.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/CrsType.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/Geometry.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/GeometryParams.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/GeometryShape.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/GeometryType.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/GeometryValidationResult.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/LineString.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/LinearRing.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/LinkedCrs.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/MultiPolygon.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/NamedCrs.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/Point.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/Polygon.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/PolygonCoordinates.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/Position.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos/AccountConsistency.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos/AccountProperties.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos/AccountRegion.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos/BoundingBoxProperties.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos/ChangeFeedProcessor.xml
:white_check_mark:Succeeded

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

[Warning-DuplicateUids] Uid(azure.net.sdk.landingPage.services.EventHub.Client) has already been defined in api/overview/azure/EventHubs/V4.yml.
[Warning-DuplicateUids] Uid(azure.net.sdk.landingPage.services.EventHub.Client) has already been defined in api/overview/azure/EventHubs/V4.yml.

api/Microsoft.Azure.Cosmos.TransactionalBatchRequestOptions.ConsistencyLevel.yml

[Warning-UidNotFound] 1 invalid cross reference(s) "Microsoft.Azure.Cosmos.ConnectionPolicy".

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 9761561:
:warning: Validation status: warnings

File
Status
Preview URL
Details

api/overview/azure/microsoft.servicebus-readme.md
:warning:Warning
View
Details

:warning:Warning

Details

api/Microsoft.Azure.Cosmos.TransactionalBatchRequestOptions.ConsistencyLevel.yml
:warning:Warning
View
Details

api/overview/azure/core-readme.md
:white_check_mark:Succeeded
View

api/overview/azure/core.experimental-readme-pre.md
:white_check_mark:Succeeded
View

api/overview/azure/microsoft.core.newtonsoftjson-readme-pre.md
:white_check_mark:Succeeded
View

xml/FrameworksIndex/azure-dotnet-preview.xml
:white_check_mark:Succeeded

xml/FrameworksIndex/azure-dotnet.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Fluent/CompositeIndexDefinition`1.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Fluent/ConflictResolutionDefinition.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Fluent/ContainerBuilder.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Fluent/ContainerDefinition`1.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Fluent/CosmosClientBuilder.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Fluent/IndexingPolicyDefinition`1.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Fluent/PathsDefinition`1.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Fluent/SpatialIndexDefinition`1.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Fluent/UniqueKeyDefinition.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Linq/CosmosLinqExtensions.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Scripts/Scripts.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Scripts/StoredProcedureExecuteResponse`1.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Scripts/StoredProcedureProperties.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Scripts/StoredProcedureRequestOptions.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Scripts/StoredProcedureResponse.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Scripts/TriggerOperation.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Scripts/TriggerProperties.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Scripts/TriggerResponse.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Scripts/TriggerType.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Scripts/UserDefinedFunctionProperties.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Scripts/UserDefinedFunctionResponse.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/BoundingBox.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/Crs.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/CrsType.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/Geometry.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/GeometryParams.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/GeometryShape.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/GeometryType.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/GeometryValidationResult.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/LineString.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/LinearRing.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/LinkedCrs.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/MultiPolygon.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/NamedCrs.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/Point.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/Polygon.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/PolygonCoordinates.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos.Spatial/Position.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos/AccountConsistency.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos/AccountProperties.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos/AccountRegion.xml
:white_check_mark:Succeeded

xml/Microsoft.Azure.Cosmos/BoundingBoxProperties.xml
:white_check_mark:Succeeded

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

api/overview/azure/microsoft.servicebus-readme.md

Line 19: [Warning-hard-coded-locale] Link 'http://azure.microsoft.com/en-us/develop/net/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19: [Warning-insecure-link] Link 'http://azure.microsoft.com/en-us/develop/net/' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 31: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/dotnet/api/overview/azure/service-bus?view=azure-dotnet' 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/service-bus-messaging/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 35: [Warning-hard-coded-locale] Link 'http://azure.microsoft.com/en-us/downloads/?sdk=net' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 35: [Warning-insecure-link] Link 'http://azure.microsoft.com/en-us/downloads/?sdk=net' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 37: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-messaging-overview' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 51: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/resources/samples/?sort=0&service=service-bus&platform=dotnet' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 53: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 91: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 92: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/rest/api/servicebus/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 93: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/dotnet/api/overview/azure/service-bus?view=azure-dotnet' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

[Warning-DuplicateUids] Uid(azure.net.sdk.landingPage.services.EventHub.Client) has already been defined in api/overview/azure/EventHubs/V4.yml.
[Warning-DuplicateUids] Uid(azure.net.sdk.landingPage.services.EventHub.Client) has already been defined in api/overview/azure/EventHubs/V4.yml.

api/Microsoft.Azure.Cosmos.TransactionalBatchRequestOptions.ConsistencyLevel.yml

[Warning-UidNotFound] 1 invalid cross reference(s) "Microsoft.Azure.Cosmos.ConnectionPolicy".

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 481b026:
:warning: Validation status: warnings

File
Status
Preview URL
Details

api/overview/azure/microsoft.servicebus-readme.md
:warning:Warning
View
Details

api/Azure.Core.Serialization.yml
:warning:Warning
View
Details

api/Microsoft.Azure.Cosmos.TransactionalBatchRequestOptions.ConsistencyLevel.yml
:warning:Warning
View
Details

api/Azure.Core.Serialization.NewtonsoftJsonObjectSerializer.yml
:warning:Warning
View
Details

api/overview/azure/core-readme.md
:white_check_mark:Succeeded
View

api/overview/azure/core.experimental-readme-pre.md
:white_check_mark:Succeeded
View

api/overview/azure/microsoft.core.newtonsoftjson-readme-pre.md
:white_check_mark:Succeeded
View

xml/AspNetCore/Areas_MicrosoftIdentity_Pages_Account_AccessDenied.xml
:white_check_mark:Succeeded

xml/AspNetCore/Areas_MicrosoftIdentity_Pages_Account_Error.xml
:white_check_mark:Succeeded

xml/AspNetCore/Areas_MicrosoftIdentity_Pages_Account_SignedOut.xml
:white_check_mark:Succeeded

xml/AspNetCore/Areas_MicrosoftIdentity_Pages__ViewStart.xml
:white_check_mark:Succeeded

xml/Azure.Core.Cryptography/IKeyEncryptionKey.xml
:white_check_mark:Succeeded

xml/Azure.Core.Cryptography/IKeyEncryptionKeyResolver.xml
:white_check_mark:Succeeded

xml/Azure.Core.Diagnostics/AzureEventSourceListener.xml
:white_check_mark:Succeeded

xml/Azure.Core.Extensions/IAzureClientBuilder`2.xml
:white_check_mark:Succeeded

xml/Azure.Core.Extensions/IAzureClientFactoryBuilder.xml
:white_check_mark:Succeeded

xml/Azure.Core.Extensions/IAzureClientFactoryBuilderWithConfiguration`1.xml
:white_check_mark:Succeeded

xml/Azure.Core.Extensions/IAzureClientFactoryBuilderWithCredential.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoBoundingBox.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoCollection.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoJsonConverter.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoLine.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoLineCollection.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoObject.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoPoint.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoPointCollection.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoPolygon.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoPolygonCollection.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoPosition.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/BearerTokenAuthenticationPolicy.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpClientTransport.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpPipeline.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpPipelineBuilder.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpPipelinePolicy.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpPipelineSynchronousPolicy.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpPipelineTransport.xml
:white_check_mark:Succeeded

xml/Azure.Core.Serialization/IMemberNameConverter.xml
:white_check_mark:Succeeded

xml/Azure.Core.Serialization/JsonObjectSerializer.xml
:white_check_mark:Succeeded

xml/Azure.Core.Serialization/NewtonsoftJsonObjectSerializer.xml
:white_check_mark:Succeeded

xml/Azure.Core.Serialization/ObjectSerializer.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/CollectionGeometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/Geometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/LineGeometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/MultiLineGeometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/MultiPointGeometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/MultiPolygonGeometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/PointGeometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/PolygonGeometry.xml
:white_check_mark:Succeeded

xml/Azure.Core/AccessToken.xml
:white_check_mark:Succeeded

xml/Azure.Core/BinaryData.xml
:white_check_mark:Succeeded

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

api/overview/azure/microsoft.servicebus-readme.md

Line 19: [Warning-hard-coded-locale] Link 'http://azure.microsoft.com/en-us/develop/net/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19: [Warning-insecure-link] Link 'http://azure.microsoft.com/en-us/develop/net/' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 31: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/dotnet/api/overview/azure/service-bus?view=azure-dotnet' 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/service-bus-messaging/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 35: [Warning-hard-coded-locale] Link 'http://azure.microsoft.com/en-us/downloads/?sdk=net' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 35: [Warning-insecure-link] Link 'http://azure.microsoft.com/en-us/downloads/?sdk=net' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 37: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-messaging-overview' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 51: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/resources/samples/?sort=0&service=service-bus&platform=dotnet' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 53: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 91: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 92: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/rest/api/servicebus/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 93: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/dotnet/api/overview/azure/service-bus?view=azure-dotnet' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

api/Azure.Core.Serialization.yml

[Warning-UidNotFound] 1 invalid cross reference(s) "Newtonsoft.Json.JsonSerializer".

api/Microsoft.Azure.Cosmos.TransactionalBatchRequestOptions.ConsistencyLevel.yml

[Warning-UidNotFound] 1 invalid cross reference(s) "Microsoft.Azure.Cosmos.ConnectionPolicy".

api/Azure.Core.Serialization.NewtonsoftJsonObjectSerializer.yml

[Warning-UidNotFound] 1 invalid cross reference(s) "Newtonsoft.Json.JsonSerializer".

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 221106f:
:warning: Validation status: warnings

File
Status
Preview URL
Details

api/overview/azure/microsoft.servicebus-readme.md
:warning:Warning
View
Details

api/Azure.Core.Serialization.yml
:warning:Warning
View
Details

api/Azure.Core.Serialization.NewtonsoftJsonObjectSerializer.yml
:warning:Warning
View
Details

api/Microsoft.Azure.Cosmos.TransactionalBatchRequestOptions.ConsistencyLevel.yml
:warning:Warning
View
Details

api/overview/azure/core-readme.md
:white_check_mark:Succeeded
View

api/overview/azure/core.experimental-readme-pre.md
:white_check_mark:Succeeded
View

api/overview/azure/messaging.eventhubs-readme-pre.md
:white_check_mark:Succeeded
View

api/overview/azure/microsoft.core.newtonsoftjson-readme-pre.md
:white_check_mark:Succeeded
View

xml/AspNetCore/Areas_MicrosoftIdentity_Pages_Account_AccessDenied.xml
:white_check_mark:Succeeded

xml/AspNetCore/Areas_MicrosoftIdentity_Pages_Account_Error.xml
:white_check_mark:Succeeded

xml/AspNetCore/Areas_MicrosoftIdentity_Pages_Account_SignedOut.xml
:white_check_mark:Succeeded

xml/AspNetCore/Areas_MicrosoftIdentity_Pages__ViewStart.xml
:white_check_mark:Succeeded

xml/Azure.Core.Cryptography/IKeyEncryptionKey.xml
:white_check_mark:Succeeded

xml/Azure.Core.Cryptography/IKeyEncryptionKeyResolver.xml
:white_check_mark:Succeeded

xml/Azure.Core.Diagnostics/AzureEventSourceListener.xml
:white_check_mark:Succeeded

xml/Azure.Core.Extensions/IAzureClientBuilder`2.xml
:white_check_mark:Succeeded

xml/Azure.Core.Extensions/IAzureClientFactoryBuilder.xml
:white_check_mark:Succeeded

xml/Azure.Core.Extensions/IAzureClientFactoryBuilderWithConfiguration`1.xml
:white_check_mark:Succeeded

xml/Azure.Core.Extensions/IAzureClientFactoryBuilderWithCredential.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoBoundingBox.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoCollection.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoJsonConverter.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoLine.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoLineCollection.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoObject.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoPoint.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoPointCollection.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoPolygon.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoPolygonCollection.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoPosition.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/BearerTokenAuthenticationPolicy.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpClientTransport.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpPipeline.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpPipelineBuilder.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpPipelinePolicy.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpPipelineSynchronousPolicy.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpPipelineTransport.xml
:white_check_mark:Succeeded

xml/Azure.Core.Serialization/IMemberNameConverter.xml
:white_check_mark:Succeeded

xml/Azure.Core.Serialization/JsonObjectSerializer.xml
:white_check_mark:Succeeded

xml/Azure.Core.Serialization/NewtonsoftJsonObjectSerializer.xml
:white_check_mark:Succeeded

xml/Azure.Core.Serialization/ObjectSerializer.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/CollectionGeometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/Geometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/LineGeometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/MultiLineGeometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/MultiPointGeometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/MultiPolygonGeometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/PointGeometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/PolygonGeometry.xml
:white_check_mark:Succeeded

xml/Azure.Core/AccessToken.xml
:white_check_mark:Succeeded

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

api/overview/azure/microsoft.servicebus-readme.md

Line 19: [Warning-hard-coded-locale] Link 'http://azure.microsoft.com/en-us/develop/net/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19: [Warning-insecure-link] Link 'http://azure.microsoft.com/en-us/develop/net/' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 31: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/dotnet/api/overview/azure/service-bus?view=azure-dotnet' 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/service-bus-messaging/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 35: [Warning-hard-coded-locale] Link 'http://azure.microsoft.com/en-us/downloads/?sdk=net' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 35: [Warning-insecure-link] Link 'http://azure.microsoft.com/en-us/downloads/?sdk=net' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 37: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-messaging-overview' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 51: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/resources/samples/?sort=0&service=service-bus&platform=dotnet' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 53: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 91: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 92: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/rest/api/servicebus/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 93: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/dotnet/api/overview/azure/service-bus?view=azure-dotnet' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

api/Azure.Core.Serialization.yml

[Warning-UidNotFound] 1 invalid cross reference(s) "Newtonsoft.Json.JsonSerializer".

api/Azure.Core.Serialization.NewtonsoftJsonObjectSerializer.yml

[Warning-UidNotFound] 1 invalid cross reference(s) "Newtonsoft.Json.JsonSerializer".

api/Microsoft.Azure.Cosmos.TransactionalBatchRequestOptions.ConsistencyLevel.yml

[Warning-UidNotFound] 1 invalid cross reference(s) "Microsoft.Azure.Cosmos.ConnectionPolicy".

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 468a930:
:warning: Validation status: warnings

File
Status
Preview URL
Details

api/overview/azure/microsoft.servicebus-readme.md
:warning:Warning
View
Details

api/Azure.Core.Serialization.yml
:warning:Warning
View
Details

api/Microsoft.Azure.Cosmos.TransactionalBatchRequestOptions.ConsistencyLevel.yml
:warning:Warning
View
Details

api/Azure.Core.Serialization.NewtonsoftJsonObjectSerializer.yml
:warning:Warning
View
Details

api/overview/azure/core-readme.md
:white_check_mark:Succeeded
View

api/overview/azure/core.experimental-readme-pre.md
:white_check_mark:Succeeded
View

api/overview/azure/messaging.eventhubs-readme-pre.md
:white_check_mark:Succeeded
View

api/overview/azure/microsoft.core.newtonsoftjson-readme-pre.md
:white_check_mark:Succeeded
View

docs-ref-toc/top_level_toc.yml
:white_check_mark:Succeeded

xml/AspNetCore/Areas_MicrosoftIdentity_Pages_Account_AccessDenied.xml
:white_check_mark:Succeeded

xml/AspNetCore/Areas_MicrosoftIdentity_Pages_Account_Error.xml
:white_check_mark:Succeeded

xml/AspNetCore/Areas_MicrosoftIdentity_Pages_Account_SignedOut.xml
:white_check_mark:Succeeded

xml/AspNetCore/Areas_MicrosoftIdentity_Pages__ViewStart.xml
:white_check_mark:Succeeded

xml/Azure.Core.Cryptography/IKeyEncryptionKey.xml
:white_check_mark:Succeeded

xml/Azure.Core.Cryptography/IKeyEncryptionKeyResolver.xml
:white_check_mark:Succeeded

xml/Azure.Core.Diagnostics/AzureEventSourceListener.xml
:white_check_mark:Succeeded

xml/Azure.Core.Extensions/IAzureClientBuilder`2.xml
:white_check_mark:Succeeded

xml/Azure.Core.Extensions/IAzureClientFactoryBuilder.xml
:white_check_mark:Succeeded

xml/Azure.Core.Extensions/IAzureClientFactoryBuilderWithConfiguration`1.xml
:white_check_mark:Succeeded

xml/Azure.Core.Extensions/IAzureClientFactoryBuilderWithCredential.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoBoundingBox.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoCollection.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoJsonConverter.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoLine.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoLineCollection.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoObject.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoPoint.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoPointCollection.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoPolygon.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoPolygonCollection.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoPosition.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/BearerTokenAuthenticationPolicy.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpClientTransport.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpPipeline.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpPipelineBuilder.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpPipelinePolicy.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpPipelineSynchronousPolicy.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpPipelineTransport.xml
:white_check_mark:Succeeded

xml/Azure.Core.Serialization/IMemberNameConverter.xml
:white_check_mark:Succeeded

xml/Azure.Core.Serialization/JsonObjectSerializer.xml
:white_check_mark:Succeeded

xml/Azure.Core.Serialization/NewtonsoftJsonObjectSerializer.xml
:white_check_mark:Succeeded

xml/Azure.Core.Serialization/ObjectSerializer.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/CollectionGeometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/Geometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/LineGeometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/MultiLineGeometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/MultiPointGeometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/MultiPolygonGeometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/PointGeometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/PolygonGeometry.xml
:white_check_mark:Succeeded

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

api/overview/azure/microsoft.servicebus-readme.md

Line 19: [Warning-hard-coded-locale] Link 'http://azure.microsoft.com/en-us/develop/net/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19: [Warning-insecure-link] Link 'http://azure.microsoft.com/en-us/develop/net/' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 31: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/dotnet/api/overview/azure/service-bus?view=azure-dotnet' 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/service-bus-messaging/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 35: [Warning-hard-coded-locale] Link 'http://azure.microsoft.com/en-us/downloads/?sdk=net' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 35: [Warning-insecure-link] Link 'http://azure.microsoft.com/en-us/downloads/?sdk=net' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 37: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-messaging-overview' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 51: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/resources/samples/?sort=0&service=service-bus&platform=dotnet' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 53: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 91: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 92: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/rest/api/servicebus/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 93: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/dotnet/api/overview/azure/service-bus?view=azure-dotnet' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

api/Azure.Core.Serialization.yml

[Warning-UidNotFound] 1 invalid cross reference(s) "Newtonsoft.Json.JsonSerializer".

api/Microsoft.Azure.Cosmos.TransactionalBatchRequestOptions.ConsistencyLevel.yml

[Warning-UidNotFound] 1 invalid cross reference(s) "Microsoft.Azure.Cosmos.ConnectionPolicy".

api/Azure.Core.Serialization.NewtonsoftJsonObjectSerializer.yml

[Warning-UidNotFound] 1 invalid cross reference(s) "Newtonsoft.Json.JsonSerializer".

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 9ad4c07:
:warning: Validation status: warnings

File
Status
Preview URL
Details

api/overview/azure/extensions.aspnetcore.dataprotection.blobs-readme.md
:warning:Warning
View
Details

api/overview/azure/extensions.aspnetcore.dataprotection.keys-readme.md
:warning:Warning
View
Details

api/overview/azure/microsoft.servicebus-readme.md
:warning:Warning
View
Details

api/Azure.Core.Serialization.yml
:warning:Warning
View
Details

api/Azure.Core.Serialization.NewtonsoftJsonObjectSerializer.yml
:warning:Warning
View
Details

api/Microsoft.Azure.Cosmos.TransactionalBatchRequestOptions.ConsistencyLevel.yml
:warning:Warning
View
Details

api/overview/azure/core-readme.md
:white_check_mark:Succeeded
View

api/overview/azure/core.experimental-readme-pre.md
:white_check_mark:Succeeded
View

api/overview/azure/messaging.eventhubs-readme-pre.md
:white_check_mark:Succeeded
View

api/overview/azure/messaging.eventhubs.processor-readme-pre.md
:white_check_mark:Succeeded
View

api/overview/azure/microsoft.core.newtonsoftjson-readme-pre.md
:white_check_mark:Succeeded
View

docs-ref-toc/top_level_toc.yml
:white_check_mark:Succeeded

xml/AspNetCore/Areas_MicrosoftIdentity_Pages_Account_AccessDenied.xml
:white_check_mark:Succeeded

xml/AspNetCore/Areas_MicrosoftIdentity_Pages_Account_Error.xml
:white_check_mark:Succeeded

xml/AspNetCore/Areas_MicrosoftIdentity_Pages_Account_SignedOut.xml
:white_check_mark:Succeeded

xml/AspNetCore/Areas_MicrosoftIdentity_Pages__ViewStart.xml
:white_check_mark:Succeeded

xml/Azure.Core.Cryptography/IKeyEncryptionKey.xml
:white_check_mark:Succeeded

xml/Azure.Core.Cryptography/IKeyEncryptionKeyResolver.xml
:white_check_mark:Succeeded

xml/Azure.Core.Diagnostics/AzureEventSourceListener.xml
:white_check_mark:Succeeded

xml/Azure.Core.Extensions/IAzureClientBuilder`2.xml
:white_check_mark:Succeeded

xml/Azure.Core.Extensions/IAzureClientFactoryBuilder.xml
:white_check_mark:Succeeded

xml/Azure.Core.Extensions/IAzureClientFactoryBuilderWithConfiguration`1.xml
:white_check_mark:Succeeded

xml/Azure.Core.Extensions/IAzureClientFactoryBuilderWithCredential.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoBoundingBox.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoCollection.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoJsonConverter.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoLine.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoLineCollection.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoObject.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoPoint.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoPointCollection.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoPolygon.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoPolygonCollection.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoPosition.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/BearerTokenAuthenticationPolicy.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpClientTransport.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpPipeline.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpPipelineBuilder.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpPipelinePolicy.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpPipelineSynchronousPolicy.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpPipelineTransport.xml
:white_check_mark:Succeeded

xml/Azure.Core.Serialization/IMemberNameConverter.xml
:white_check_mark:Succeeded

xml/Azure.Core.Serialization/JsonObjectSerializer.xml
:white_check_mark:Succeeded

xml/Azure.Core.Serialization/NewtonsoftJsonObjectSerializer.xml
:white_check_mark:Succeeded

xml/Azure.Core.Serialization/ObjectSerializer.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/CollectionGeometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/Geometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/LineGeometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/MultiLineGeometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/MultiPointGeometry.xml
:white_check_mark:Succeeded

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

api/overview/azure/extensions.aspnetcore.dataprotection.blobs-readme.md

Line 31: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-introduction#containers' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 77: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/aspnet/core/security/data-protection/introduction' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

api/overview/azure/extensions.aspnetcore.dataprotection.keys-readme.md

Line 31: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/general/overview' 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/key-vault/quick-create-portal#create-a-vault' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 34: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/quick-create-powershell#create-a-key-vault' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 34: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/quick-create-cli#create-a-key-vault' 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/aspnet/core/security/data-protection/introduction?view=aspnetcore-3.1' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

api/overview/azure/microsoft.servicebus-readme.md

Line 19: [Warning-hard-coded-locale] Link 'http://azure.microsoft.com/en-us/develop/net/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19: [Warning-insecure-link] Link 'http://azure.microsoft.com/en-us/develop/net/' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 31: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/dotnet/api/overview/azure/service-bus?view=azure-dotnet' 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/service-bus-messaging/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 35: [Warning-hard-coded-locale] Link 'http://azure.microsoft.com/en-us/downloads/?sdk=net' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 35: [Warning-insecure-link] Link 'http://azure.microsoft.com/en-us/downloads/?sdk=net' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 37: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-messaging-overview' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 51: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/resources/samples/?sort=0&service=service-bus&platform=dotnet' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 53: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 91: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 92: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/rest/api/servicebus/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 93: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/dotnet/api/overview/azure/service-bus?view=azure-dotnet' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

api/Azure.Core.Serialization.yml

[Warning-UidNotFound] 1 invalid cross reference(s) "Newtonsoft.Json.JsonSerializer".

api/Azure.Core.Serialization.NewtonsoftJsonObjectSerializer.yml

[Warning-UidNotFound] 1 invalid cross reference(s) "Newtonsoft.Json.JsonSerializer".

api/Microsoft.Azure.Cosmos.TransactionalBatchRequestOptions.ConsistencyLevel.yml

[Warning-UidNotFound] 1 invalid cross reference(s) "Microsoft.Azure.Cosmos.ConnectionPolicy".

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 9d75590:
:warning: Validation status: warnings

File
Status
Preview URL
Details

api/overview/azure/extensions.aspnetcore.dataprotection.blobs-readme.md
:warning:Warning
View
Details

api/overview/azure/extensions.aspnetcore.dataprotection.keys-readme.md
:warning:Warning
View
Details

api/overview/azure/microsoft.servicebus-readme.md
:warning:Warning
View
Details

api/Microsoft.Azure.Cosmos.TransactionalBatchRequestOptions.ConsistencyLevel.yml
:warning:Warning
View
Details

api/Azure.Core.Serialization.yml
:warning:Warning
View
Details

api/Azure.Core.Serialization.NewtonsoftJsonObjectSerializer.yml
:warning:Warning
View
Details

api/overview/azure/core-readme.md
:white_check_mark:Succeeded
View

api/overview/azure/core.experimental-readme-pre.md
:white_check_mark:Succeeded
View

api/overview/azure/messaging.eventhubs-readme-pre.md
:white_check_mark:Succeeded
View

api/overview/azure/messaging.eventhubs.processor-readme-pre.md
:white_check_mark:Succeeded
View

api/overview/azure/microsoft.core.newtonsoftjson-readme-pre.md
:white_check_mark:Succeeded
View

docs-ref-toc/top_level_toc.yml
:white_check_mark:Succeeded

xml/AspNetCore/Areas_MicrosoftIdentity_Pages_Account_AccessDenied.xml
:white_check_mark:Succeeded

xml/AspNetCore/Areas_MicrosoftIdentity_Pages_Account_Error.xml
:white_check_mark:Succeeded

xml/AspNetCore/Areas_MicrosoftIdentity_Pages_Account_SignedOut.xml
:white_check_mark:Succeeded

xml/AspNetCore/Areas_MicrosoftIdentity_Pages__ViewStart.xml
:white_check_mark:Succeeded

xml/Azure.Core.Cryptography/IKeyEncryptionKey.xml
:white_check_mark:Succeeded

xml/Azure.Core.Cryptography/IKeyEncryptionKeyResolver.xml
:white_check_mark:Succeeded

xml/Azure.Core.Diagnostics/AzureEventSourceListener.xml
:white_check_mark:Succeeded

xml/Azure.Core.Extensions/IAzureClientBuilder`2.xml
:white_check_mark:Succeeded

xml/Azure.Core.Extensions/IAzureClientFactoryBuilder.xml
:white_check_mark:Succeeded

xml/Azure.Core.Extensions/IAzureClientFactoryBuilderWithConfiguration`1.xml
:white_check_mark:Succeeded

xml/Azure.Core.Extensions/IAzureClientFactoryBuilderWithCredential.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoBoundingBox.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoCollection.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoJsonConverter.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoLine.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoLineCollection.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoObject.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoPoint.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoPointCollection.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoPolygon.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoPolygonCollection.xml
:white_check_mark:Succeeded

xml/Azure.Core.GeoJson/GeoPosition.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/BearerTokenAuthenticationPolicy.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpClientTransport.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpPipeline.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpPipelineBuilder.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpPipelinePolicy.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpPipelineSynchronousPolicy.xml
:white_check_mark:Succeeded

xml/Azure.Core.Pipeline/HttpPipelineTransport.xml
:white_check_mark:Succeeded

xml/Azure.Core.Serialization/IMemberNameConverter.xml
:white_check_mark:Succeeded

xml/Azure.Core.Serialization/JsonObjectSerializer.xml
:white_check_mark:Succeeded

xml/Azure.Core.Serialization/NewtonsoftJsonObjectSerializer.xml
:white_check_mark:Succeeded

xml/Azure.Core.Serialization/ObjectSerializer.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/CollectionGeometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/Geometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/LineGeometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/MultiLineGeometry.xml
:white_check_mark:Succeeded

xml/Azure.Core.Spatial/MultiPointGeometry.xml
:white_check_mark:Succeeded

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

api/overview/azure/extensions.aspnetcore.dataprotection.blobs-readme.md

Line 31: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-introduction#containers' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 77: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/aspnet/core/security/data-protection/introduction' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

api/overview/azure/extensions.aspnetcore.dataprotection.keys-readme.md

Line 31: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/general/overview' 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/key-vault/quick-create-portal#create-a-vault' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 34: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/quick-create-powershell#create-a-key-vault' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 34: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/key-vault/quick-create-cli#create-a-key-vault' 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/aspnet/core/security/data-protection/introduction?view=aspnetcore-3.1' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

api/overview/azure/microsoft.servicebus-readme.md

Line 19: [Warning-hard-coded-locale] Link 'http://azure.microsoft.com/en-us/develop/net/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 19: [Warning-insecure-link] Link 'http://azure.microsoft.com/en-us/develop/net/' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 31: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/dotnet/api/overview/azure/service-bus?view=azure-dotnet' 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/service-bus-messaging/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 35: [Warning-hard-coded-locale] Link 'http://azure.microsoft.com/en-us/downloads/?sdk=net' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 35: [Warning-insecure-link] Link 'http://azure.microsoft.com/en-us/downloads/?sdk=net' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 37: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-messaging-overview' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 51: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/resources/samples/?sort=0&service=service-bus&platform=dotnet' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 53: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 91: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/service-bus-messaging/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 92: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/rest/api/servicebus/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 93: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/dotnet/api/overview/azure/service-bus?view=azure-dotnet' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

api/Microsoft.Azure.Cosmos.TransactionalBatchRequestOptions.ConsistencyLevel.yml

[Warning-UidNotFound] 1 invalid cross reference(s) "Microsoft.Azure.Cosmos.ConnectionPolicy".

api/Azure.Core.Serialization.yml

[Warning-UidNotFound] 1 invalid cross reference(s) "Newtonsoft.Json.JsonSerializer".

api/Azure.Core.Serialization.NewtonsoftJsonObjectSerializer.yml

[Warning-UidNotFound] 1 invalid cross reference(s) "Newtonsoft.Json.JsonSerializer".

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 1923c06:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.
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


Deprecation warning for util._extend

Checks

[X] I understand project setup issues should be asked on StackOverflow or in GitHub Discussions.
[X] I updated to latest http-proxy-middleware.

Describe the bug (be clear and concise)
In Node v22 they started showing a deprecation warning for usage of util._extend, which is used in a dependency of this library.
(node:27864) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.
    at ProxyServer.<anonymous> (\node_modules\http-proxy\lib\http-proxy\index.js:50:26)
    at HttpProxyMiddleware.middleware (\node_modules\http-proxy-middleware\dist\http-proxy-middleware.js:22:32)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

There is a PR for that dependency:

https://github.com/http-party/node-http-proxy/pull/1666

Once that is merged and a new version is released, http-proxy-middleware will need to update the dependency to stop receiving the deprecation warning in Node v22+.
I'm mainly making this issue to encourage prioritization of the linked PR.
Step-by-step reproduction instructions
1. Use library with Node 22+

Expected behavior (be clear and concise)
No deprecation warnings
How is http-proxy-middleware used in your project?
<EMAIL_ADDRESS>C:\internal-app
`--<EMAIL_ADDRESS>  `--<EMAIL_ADDRESS>deduped
| +--<EMAIL_ADDRESS>
What http-proxy-middleware configuration are you using?
N/A

What OS/version and node/version are you seeing the problem?
Node v22.3.0 - All OS

Additional context (optional)
No response

Thanks for the report.
With semver, if http-proxy releases a new minor of patch version, there is no need to update this project.
You can just update your package lock file to retrieve updated http-proxy dependency.
https://github.com/chimurai/http-proxy-middleware/blob/82aaf0aefaeb341b87fcd5b0e27a15deb030e57e/package.json#L90
Closing this issue
(since no update to http-proxy-middleware is needed when http-proxy releases a minor/patch update)

Hello. I am getting "Deprecation warning for util._extend", when using http-proxy-middleware with Express.
My code:
// 3rd party:
import { createProxyMiddleware } from 'http-proxy-middleware';
// Express:
import express from 'express';

export function serve(
  port: number,
  filename: string,
  dir: string
): Promise<void> {
  const app = express();

  app.use(
    createProxyMiddleware({
      target: `http://localhost:5173`,
      ws: true,
    })
  );

  return new Promise<void>((resolve, reject) => {
    app.listen(port, resolve).on('error', reject);
  });
}

My package.json:
{
  "version": "1.0.0",
  "description": "",
  "main": "dist/index.js",
  "types": "dist/index.d.ts",
  "type": "module",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "dev": "tsc --watch --preserveWatchOutput"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "@types/cors": "^2.8.17",
    "@types/express": "^4.17.21",
    "cors": "^2.8.5",
    "express": "^4.19.2",
    "http-proxy-middleware": "^3.0.0"
  }
}

My error:
(node:26057) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.
    at ProxyServer.<anonymous> (.../node_modules/.pnpm/http-proxy@1.18.1_debug@4.3.5/node_modules/http-proxy/lib/http-proxy/index.js:50:26)
    at HttpProxyMiddleware.middleware (.../node_modules/.pnpm/http-proxy-middleware@3.0.0/node_modules/http-proxy-middleware/dist/http-proxy-middleware.js:22:32)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Thanks for the report.
With semver, when http-proxy releases a new minor of patch version, there is no need to update this project.
You can just update your package lock file to retrieve updated http-proxy dependency.

https://github.com/chimurai/http-proxy-middleware/blob/82aaf0aefaeb341b87fcd5b0e27a15deb030e57e/package.json#L90
Closing this issue (since no update to http-proxy-middleware is needed when http-proxy releases a minor/patch update)
You can read more about semver: https://semver.org

<EMAIL_ADDRESS>is already the latest version, and hasn't been updated for 4 years. And is still using util._extend

@chimurai please reopen this issue again. Facing the same deprecation warning with the lastest version :/

You can take a look at vitejs. They patched the http-proxy package to solve this issue

same problem

Getting this issue.

Why was this closed? This is still an issue. You have a dead dependency then called http-proxy which haven't been updated in 5 years. So there wont be any update there. Please replace your dependency to them and fix this issue. Getting this since angular uses http-proxy-middleware as a dependency so can't really be fixed elsewhere. Please reopen.
Having the same issue with node 22.11.0

There seem to be something in the work here https://github.com/http-party/node-http-proxy/pull/1666  at http-proxy but ye still no release for those tracking this issue .


Act 583

What is the Purpose?
Correct dropdown styling issue in objectives listing page
What was the approach?
Replace the default select component
Are there any concerns to addressed further before or after merging this PR?
The code is not easily resusable. We have to create a proper custom component
Mentions?
@ninetteadhikari @IvyMMutiso
Issue(s) affected?
ACT-583

Codecov Report

Merging #347 into dev will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #347   +/-   ##
=======================================
  Coverage   50.18%   50.18%
=======================================
  Files          91       91
  Lines        8242     8242
=======================================
  Hits         4136     4136
  Misses       4106     4106

Continue to review full report at Codecov.

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

Tested locally and this works for the Parent objective and Programs field on the Objective create modal but not sure if this should also be working in other places like the Target period field on the Result create modal (see screenshot):

Hey @andrewtpham. I only implemented in the "new objectives modal". It's not a reusable component yet. So all other select tags don't have the styling yet.

Ok thanks @michaelbukachi. Then this card is considered done. We can create a separate card on how to make this a reusable component

Hey @ninetteadhikari, on it.


Prevents authentication with empty user/pass if both are empty on opts

Fixes #12

LGTM! Thanks for this @fabioxgn.


allowing the user to authenticate to retrieve private repos

Describe what this PR does and why we need it:
Fixes issue 448
Changes proposed in this pull request

Set basic auth on retrieval of the bearer token for the registry service.

Which issue this PR fixes (This will close that issue when PR gets merged)
fixes 448

Manually tested this successfully, fixes https://github.com/openshift/ansible-service-broker/issues/448

This is making a direct call, needs moar apiserver integration


upgrade dependencies + support for include-all-sources

see https://github.com/gotwarlost/istanbul/issues/112

thanks for your work. i released your work.


bug(ErrorStateMatcher): Not able to configure globally ErrorStateMatcher

Reproduction
StackBlitz link for reproduction: https://stackblitz.com/edit/components-issue-enshvf
Steps to reproduce:

Pay your attention that CoreModule has declaration for ErrorStateMatcher provider with class ShowOnDirtyErrorStateMatcher. CoreModule imported into AppModule in the same way as FeatureModule.
Try to focus/blur example "Favorite Food" input and note that ShowOnDirtyErrorStateMatcher was not applied.

In big enterprise applications we should have clean modular structure without any SharedModule or MaterialModule to be imported into each feature module.
MatInputModule has hardcoded ErrorStateMatcher provider and when we import that module into our feature modules – our global ErrorStateMatcher provider is overwritten.
I suppose this issue related with PR #18962, but I believe this issue describes another problem with ErrorStateMatcher
Expected Behavior
ErrorStateMatcher can be defined globally
Actual Behavior
ErrorStateMatcher overwrites with each MatInputModule import
Environment

Angular: 9+
CDK/Material: 9+

We should follow the same pattern as in the MatDateSelectionModel when providing the default ErrorStateMatcher so that any higher-level defaults are picked up.

We should follow the same pattern as in the MatDateSelectionModel (SkipSelf + Optional) when providing the default ErrorStateMatcher so that any higher-level defaults are picked up.

Do you need my help with fixing this?

Yes this would be very helpfull cause right now you cannot override the default you can pass it using inputs but that creates a lot of boilerplate

is this still an issue? any updates? does it make sense to create a MR for this?


Move syntax highlighting to web worker

This should eliminate page freezes when loading big files/diff. highlightBlock is needed to preserve our existing HTML nodes when highlighting and for that, highlight.js needs access to the DOM API so I added a DOM implementation to make it work, which adds around 300kB to the output file size of the lazy-loaded highlight.js chunk.

It might be worth removing RequireHighlightJS from template context and let the decision be done in JS alone. I'm just not sure if it's going to break anything like here.

Regardin removal of .RequireHighlightJS: I guess it cannot be done without breaking the example here which seems to piggy-back on the variable for detection of rendered Markdown.

Fixed on race condition that happened with multiple outstanding highlight requests by adding a index to the data submitted to the worker. This should work reliably as every call to highlight will instantiate their own worker (the chunk is still only downloaded once).

Codecov Report

Merging #11017 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #11017      +/-   ##
==========================================
- Coverage   43.43%   43.41%   -0.02%
==========================================
  Files         597      597
  Lines       84628    84628
==========================================
- Hits        36754    36741      -13
- Misses      43344    43352       +8
- Partials     4530     4535       +5

Impacted Files
Coverage Δ

modules/indexer/stats/queue.go
62.50% <0.00%> (-18.75%)
:arrow_down:

modules/indexer/stats/db.go
40.62% <0.00%> (-9.38%)
:arrow_down:

modules/git/utils.go
65.67% <0.00%> (-4.48%)
:arrow_down:

modules/git/command.go
86.95% <0.00%> (-2.61%)
:arrow_down:

services/pull/check.go
51.21% <0.00%> (-1.83%)
:arrow_down:

modules/git/repo.go
47.28% <0.00%> (-0.84%)
:arrow_down:

services/pull/pull.go
34.70% <0.00%> (-0.30%)
:arrow_down:

modules/queue/unique_queue_disk_channel.go
55.76% <0.00%> (+1.92%)
:arrow_up:

models/unit.go
44.44% <0.00%> (+2.46%)
:arrow_up:

Continue to review full report at Codecov.

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

Make lgtm work


About unsandboxed custom extensions

How to obtain and modify variables and lists in unsandboxed custom extensions

Scratch.vm.runtime.getTargetForStage().lookupVariableByNameAndType('variable name').value = 3;
Scratch.vm.runtime.getTargetForStage().lookupVariableByNameAndType('list name', 'list').value = [1, 2, 3];

Is there a method to obtain the names of all variables and lists?

从根本上说，它只是
Scratch.vm.runtime.getTargetForStage().lookupVariableByNameAndType('variable name').value = 3;
Scratch.vm.runtime.getTargetForStage().lookupVariableByNameAndType('list name', 'list').value = [1, 2, 3];

您将不得不添加额外的逻辑来处理变量不存在等。

Is there a method to obtain the names of all variables and lists?

you can find the information you desire in .variables on either the stage (global variables) or any other target (local variables)
console.log(Scratch.vm.runtime.getTargetForStage().variables)

fundamentally it's just
Scratch.vm.runtime.getTargetForStage().lookupVariableByNameAndType('variable name').value = 3;
Scratch.vm.runtime.getTargetForStage().lookupVariableByNameAndType('list name', 'list').value = [1, 2, 3];

you will have to add extra logic for dealing with when the variable does not exist etc.
After modifying the list using this method,need to hide and then display the list to see if the modified list.

fundamentally it's just
Scratch.vm.runtime.getTargetForStage().lookupVariableByNameAndType('variable name').value = 3;
Scratch.vm.runtime.getTargetForStage().lookupVariableByNameAndType('list name', 'list').value = [1, 2, 3];

you will have to add extra logic for dealing with when the variable does not exist etc.

After modifying the list using this method,need to hide and then display the list to see if the modified list.


feat: [wip] new client workflow

Using a forked repo to confirm the workflow works correctly before merging this

I expect this pull request comes earlier than "Start to migrate new-client.py to sdk-platform-java". Once new-client.py moves to sdk-platform-java, we'll add "git clone" command in one of the steps to get.

When creating a pull request, can you try to use the identify of the person who run the job?

I should write that this might not work.

I tried github workflow dispatch to use GITHUB_TOKEN (https://github.com/suztomo/troubleshoot-bazel-repo-rule/blob/main/.github/workflows/create-pull-request.yaml) but it never becomes the token of the person who invokes the workflow. It seems my memory was incorrect.

Once it creates a pull request in your forked repository (Java-shopping-css is a good example.), add the URL of the generated pull request in the description of this pull. Run diff with the merged pull request for java-shopping-css.

(I forgot to mention this) Release managers occasionally make mistakes in input values and often have to re-run the new client generation script. (I believe you have seen cases yourself as a release manager.) Please take that into account.
In other words, avoid "You can run this job only once for one new client API request and no way to recover from mistakes."

(I forgot to mention this) Release managers occasionally make mistakes in input values and often have to re-run the new client generation script. (I believe you have seen cases yourself as a release manager.) Please take that into account.
In other words, avoid "You can run this job only once for one new client API request and no way to recover from mistakes."

@suztomo I changed the logic to add a random string to the branch name to avoid errors when creating an already existing branch

Once it creates a pull request in your forked repository (Java-shopping-css is a good example.),

add the URL of the generated pull request in the description of this pull request. I want to see the input parameters values are there.
Run diff with the merged pull request for java-shopping-css.

@suztomo the diff is too big, but I think there was a manual modification in this library https://github.com/googleapis/google-cloud-java/pull/10212/commits/5c1946a244ad1e410a3be341feb85b8e30c3690e
The diff shows those google/api protos and it's way too big to be meaninful.
The two main differences:

owlbot postprocessor changes (update versions/readme/pom)
https://github.com/googleapis/google-cloud-java/pull/10212/commits/5c1946a244ad1e410a3be341feb85b8e30c3690e#diff-7fd17abddc80e0bb38670083b845847becd79f363444e1005ca7913a0a942f4e that removes google/api protos

Yes, that's right. I forgot about the manual deletion in java-shopping-css. Exclude that part of diff.

Yes, that's right. I forgot about the manual deletion in java-shopping-css. Exclude that part of diff.

@suztomo
This is the diff between the two branches.  Can you add the URL for the example pull request for java-shopping-css in this pull request description?

It's "chore:" prefix because this change does not affect how customers use client libraries.

https://github.com/googleapis/google-cloud-java/actions/runs/7560449025/job/20586498055?pr=10179
Cloning googleapis-gen...
  File "/opt/hostedtoolcache/Python/3.9.18/x64/lib/python3.9/site-packages/click/core.py", line 11[30](https://github.com/googleapis/google-cloud-java/actions/runs/7560449025/job/20586498055?pr=10179#step:11:31), in __call__
    return self.main(*args, **kwargs)
  File "/opt/hostedtoolcache/Python/3.9.18/x64/lib/python3.9/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/opt/hostedtoolcache/Python/3.9.18/x64/lib/python3.9/site-packages/click/core.py", line 1657, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/opt/hostedtoolcache/Python/3.9.18/x64/lib/python3.9/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/opt/hostedtoolcache/Python/3.9.18/x64/lib/python3.9/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/home/runner/work/google-cloud-java/google-cloud-java/generation/new_client/new-client.py", line 280, in generate
    subprocess.check_call(["git", "clone", "-q", googleapis_gen_url, "./gen/googleapis-gen"], cwd=workdir)
  File "/opt/hostedtoolcache/Python/3.9.18/x64/lib/python3.9/subprocess.py", line [37](https://github.com/googleapis/google-cloud-java/actions/runs/7560449025/job/20586498055?pr=10179#step:11:38)3, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['git', 'clone', '-q', '***github.com/googleapis/googleapis-gen.git', './gen/googleapis-gen']' returned non-zero exit status 128.

https://github.com/googleapis/google-cloud-java/actions/runs/7560449054/job/20586498855?pr=10179
remote: Permission to googleapis/google-cloud-java.git denied to github-actions[bot].
fatal: unable to access 'https://github.com/googleapis/google-cloud-java.git/': The requested URL returned error: 403
Error: Process completed with exit code 12[8](https://github.com/googleapis/google-cloud-java/actions/runs/7560449054/job/20586498855?pr=10179#step:7:9).


feat: add ProblemState

Checklist

[ ] Appropriate tests were added
[ ] Any code changes were done in a way that does not break public API
[ ] All documentation related to code changes were updated
[ ] The new code follows the
contributor guidelines, in particular the SciML Style Guide and
COLPRAC.
[ ] Any new documentation only uses public API

Additional context
Add any other context about the problem here.

Docs won't build till MTK is tagged


[beta] In jQuery challenges: bootstrap, jquery and animate.css aren't loaded in

Duplicate of #9957 Please search existing issues. :sweat:


raidboss: call tower or spread during beat 2

During Beat 2, two of the players who started with zero hearts will be
marked by spread indicators which drop a puddle AOE. The two players who
get this marker need to spread away, while the remaining two players who
started with zero hearts need to grab towers.
Instead of using a simple canned spread response, collect the matches
for the spread markers. Once they're collected, check if any match the
current player to call spread.
If none match, then instead check whether the player started beat 2 with
one heart, and call towers instead. This informs the player more
appropriately what to do.
Signed-off-by: Jacob Keller<EMAIL_ADDRESS>

During Beat 2, two of the players who started with zero hearts will be
marked by spread indicators which drop a puddle AOE. The two players who
get this marker need to spread away, while the remaining two players who
started with zero hearts need to grab towers.

This description is incorrect.
0-heart players either get the repeated baited puddles, or the 4-heart stack markers.
1-heart players either get the spread marker, or have to soak towers.
I think the code as written is probably correct but can't test right now, just pointing out that the description is incorrect.

During Beat 2, two of the players who started with zero hearts will be
marked by spread indicators which drop a puddle AOE. The two players who
get this marker need to spread away, while the remaining two players who
started with zero hearts need to grab towers.

This description is incorrect.
0-heart players either get the repeated baited puddles, or the 4-heart stack markers.
1-heart players either get the spread marker, or have to soak towers.
I think the code as written is probably correct but can't test right now, just pointing out that the description is incorrect.

Yea, I realized i had it backwards when writing the code. Will fix.

I updated this PR to use a separate collect trigger as requested, and updated the callout to "Spread -- Avoid Towers". I thought about trying to add a response or generic output here, but I ended up not doing that. I did notice that a bunch of places could benefit from an avoidTowers output, but they likely didn't want "Spread -- Avoid Towers" like this mechanic.


Command line option to enable/disable the plugin

On my CI I want to lint only the diff lines, but when I run lint locally I want to be able to scan my whole project.
Is it possible to add a command line option, for example eslint src/** --disable-diff to restore the default behaviour?

That's a great idea! I'll look into it in the next few days.

@n-studio I've release a pre-release of this feature. It's pre-released as version 2.0.2-0 and if you like, you could try it out right now. It's completely automatic, so you don't have to specify if you're running in CI or not.
Please note: There's no new command-line option (ESLint doesn't allow that), but since I added auto-detection instead, it should work by simply changing your config from "plugin:diff/diff" to "plugin:diff/ci".


MIM-124: Filter resources by resource group

Looks good, but when I'm testing it locally I get this error when trying to save a request after adding a "Resurs".

@lalmqvist Should work now! One thing I noticed is that opening an old ticket where the resource is not part of the resource group will cause an error, maybe that should be fixed too...


Bump edition to 2021

This is non-breaking as editions are private, but allows breaking improvements to the language. No changes were required for this crate, but it may improve closure codegen and array iteration.

Bumping the edition looks fine to me. Do you have any link about the codegen improvements?

I was mostly referring to https://doc.rust-lang.org/edition-guide/rust-2021/disjoint-capture-in-closures.html

I doubt this is going to change anything for us. Probably still a sensible change.
I did publish version 0.11.1 with the previous changes, which should fix your issue.

Probably, it's just nice. No problem getting this change out, I'm now just waiting on darling to publish a new version and this whole thing is resolved.


angle: libmesa-dev is now libgl1-mesa-dev

Update the package name suggestion: libmesa-dev was replaced by libgl1-mesa-dev
Describe the pull request
Only updates the outdated instructions.

Ping @wrobelda for response.

Closing this PR since it seems that no progress is being made. Please reopen if work is still being done.


ActivatedRoute data is not present in AOT build

I'm submitting a ...  (check one with "x")
[ x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see use [gitter](https://gitter.im/mgechev/angular2-seed) or [stackoverflow](https://stackoverflow.com/questions/tagged/angular2)

Current behavior

Currently Angular's ActivatedRoute data is not present in the component in AOT build although it is present in JIT.
Expected behavior

ActivatedRoute data should be visible in both builds.
Minimal reproduction of the problem with instructions

Add data property to the HomeComponent path in home-routing.module.ts
npm run start -> try to console.log ActivatedRoute snapshot data (eg. {foo: 'bar'}) in HomeComponent, data should be present
npm run serve.prod ->  try to console.log ActivatedRoute snapshot data (eg. {foo: 'bar'}) in HomeComponent, data is not present and is undefined

Also during the build.bundles.app.rollup.aot there is a warning from rollup.

What is the motivation / use case for changing the behavior?

Route data should be present in both builds
Please tell us about your environment:

Operating system : Mac osx 10.13.6
IDE: WebStorm 2018.2.1
package manager: npm v5.6.0

Angular Seed Version: 6abf152
Angular seed version 9314d596c88a29b8f30e3a6fcbfc5c480ec3849c

Node: node --version = 8.11.3

Also when you remove the data property from the route, the error will be gone.

@vyakymenko any help regarding this :(?

It would be great to get an update on this - AOT performance benefits are great but right now cannot be used due to this issue!

@AlekseiPinchuk @lucadeangeli this seed is no longer under active maintenance, you should migrate to Angular CLI.

@aamir1995 thank you, my issue is in fact with Angular CLI, I will post on there


Experimental DSP build for testing CNL

Just for testing recent changes in DSP library

I think you've created a pull request to merge hbe72/dsp into johnmcfarlane/cnl. dsp is now a different repository from cnl. You would want to merge it into johnmcfarlane/dsp but if you are going to me the main developer, it should probably be your clone which receives pull requests and not the other way around (I think: I'm a bit new at cross-repo PRs myself.)

I leveraged your test system to test my changes to DSP branch. Do not merge or integrate this to CNL.
I will remove the pull request.


Add/build nydus-snapshotter container image

So that users can easily deploy and run it.

Fixed by #11


Latest release doesn't adhere to naming convention

Current release:
8.0.1-beta
last release
v8.0.0-beta
Please can this be made consistent?

Shoot, this is sloppy stuff. I don't want to break anybody who added a reference to "8.0.1-beta" (even though tools like glide probably make this largely irrelevant.) I can add a second tag "v8.0.1-beta" which should help ease the situation.

Alright, even better, I was able to update the Release Name while keeping both tags.

Thanks so much :)


ts: Migrate settings_ui.js to typescript.

This PR addresses the migration of file web/src/settings_ui.js to typescript.
Fixes:

Screenshots and screen captures:

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

settings_ui.js was migrated to TypeScript in 446aea41b3106f06a60af752283b8a2e1ebd2d5b. Thanks for working on this @xoldyckk!


Indicator has unnecessary omitObject

Which package has an issue?
@yamada-ui/react
Package Version
1.3.7
Description
Integrate omitObject handling with omitThemeProps.
let {
  className,
  inline = false,
  placement = "top-right",
  offset = 0,
  label,
  overflowCount = 99,
  showZero = true,
  children,
  isDisabled,
  containerProps,
  ping,
  pingColor = "var(--ui-ping)",
  pingDuration = "1.4s",
  pingCount = "infinite",
  pingScale = 1.8,
  ...rest
- } = omitThemeProps(mergedProps)
+ } = omitThemeProps(mergedProps, ["withBorder"])

<ui.div
  ref={ref}
  className={cx("ui-indicator__icon", className)}
  __css={css}
-  {...omitObject(rest, ["withBorder"])}
+  {...rest}
>

Link to Reproduction
No response
Steps to Reproduce

Go to '...'
Click on '...'
Scroll down to '...'
See error

Browser
None
Operating System

[ ] macOS
[ ] Windows
[ ] Linux

Do you know how to fix the issue?
Yes
Are you willing to participate in fixing this issue and create a pull request with the fix?
None
Additional Information
No response

I would like to challenge this issue.

@sacky3105
Hi, thanks for the comment!
Yes, pls.
I'll assign this issue to you. Good luck!!


[Automation] Fix intermittent failure in patient search tests

The barcode handler was auto selecting intermittently because the timing of events wasn't lining up. These changes disable autoselection for an entire test rather than on a search by search basis

Disable the social tests until the refactor PR is checked in which fixes the searching on the social page.

Coverage remained the same at 64.204% when pulling 5f0234a9d54aeaad395b45d476fb80e736b96f7b on drryanjames:master into cf1b7ecd0b4d6e9a8716eb65ba5a259510877c00 on esaude:master.


internal/images: staticcheck

Closing this, see my comment here:

https://github.com/perkeep/perkeep/pull/1405#issuecomment-894727096


Support all CmdStan arguments and subarguments

Currently, not all CmdStan arguments are supported by StataStan (version 1.2.1), and the 'variational' method has yet to be implemented. However, the standard Stata syntax, used in stan.ado, would require one Stata option for every CmdStan (sub)argument, which is a lot of work.
With nonstandard syntax though any number of arguments can be treated as one string, which StataStan could simply pass to CmdStan. In Stata, we need only convert the Stata-ish "arg1(val1) arg2(val2) ..." to "arg1=val1 arg2=val2 ...". So switching to nonstandard syntax would give StataStan users access to all of CmdStan.

It's a tradeoff between being natural for the user of Stata
vs. easy to support.  I'm OK either way and agree it would be
nice to get all the Stan features out.  But then it's also
a matter of reading the outputs back in, as they're not all the
same across sampling, optimization, and variational inference.

Bob

On Jul 7, 2016, at 2:56 PM, Felix Leung<EMAIL_ADDRESS>wrote:
Currently, not all CmdStan arguments are supported by StataStan (version 1.2.1), and the 'variational' method has yet to be implemented. However, the standard Stata syntax, used in stan.ado, would require one Stata option for every CmdStan (sub)argument, which is a lot of work.
With nonstandard syntax though any number of arguments can be treated as one string, which StataStan could simply pass to CmdStan. In Stata, we need only convert the Stata-ish "arg1(val1) arg2(val2) ..." to "arg1=val1 arg2=val2 ...". So switching to nonstandard syntax would give StataStan users access to all of CmdStan.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hmm.. I should have said standard/nonstandard syntax parsing. To clarify, by nonstandard I meant nonstandard in the way the programmer chooses to parse the arguments, and not in the sense that the user might find the syntax unnatural.
As an example, this might be considered very Stata-ish: command varlist, option1 option2 .... To write such a command using what Stata calls the standard syntax would parse option1 and option2 in two local variables. Using nonstandard syntax parsing, I could have "option1 option2 ..." treated as a long string. For the user, the syntax is identical.
I have written an intro here. There are three equivalent ways to run CmdStan from Stata (See methods 1-3). Equivalent in the sense that they would send identical commands to the shell; they call the same functions. Stata users should find methods 1 and 2 natural; method 3 is very close to CmdStan syntax, making it easy to just run the examples from the CmdStan guide.

This all sounds absolutely great. I like the idea of getting the Stata code closer to the Stan code so that users can follow the examples without much mental translation. If I'm slow responding, it's because my wife and I are (literally) about to have a baby. But I am very supportive of this!

Congrats on your baby~ Hope everything went well.
Good to hear you like the idea. I'll work on it later this week.
On Mon, Jul 11, 2016 at 6:52 PM Robert Grant<EMAIL_ADDRESS>wrote:

This all sounds absolutely great. I like the idea of getting the Stata
code closer to the Stan code so that users can follow the examples without
much mental translation. If I'm slow responding, it's because my wife and I
are (literally) about to have a baby. But I am very supportive of this!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/statastan/issues/15#issuecomment-231677125,
or mute the thread
https://github.com/notifications/unsubscribe/AEycOSpY1VGuaZo-Xw_vs4oPERWv4HEBks5qUgRTgaJpZM4JHZGA
.


Poudriere stuck forever if call to usr/bin/limits return error message

Prerequisites

[X] Have you checked for an existing issue describing your problem?
[x] Are you running the latest version?
[X] Is your ports tree recent?
[X] Is your FreeBSD Host on a supported release?

Describe the bug
Poudriere hang forever when call to /usr/bin/limits return error message
How to reproduce
Steps to reproduce the behavior:

host system need to be older than "3458bbd39778 - kernel: add RLIMIT_PIPEBUF"
jail need to be newer than  "f54f41403d14 - usr.bin/limits: support RLIMIT_PIPEBUF".

Now start a clean build of any ports, it will hang forever at the first build (ports-mgmt/pkg) in starting phase.
Log of this port will show:
$ cat /usr/local/poudriere/data/logs/bulk/generator-default/2024-09-26_21h36m07s/logs/pkg-1.21.3.log
[00:00:00] =>> Building ports-mgmt/pkg
[00:00:00] limits: setrlimit pipebuf: Invalid argument

Commenting those lines in /usr/local/share/poudriere/common.sh is a quick workaround:
${JEXEC_LIMITS+/usr/bin/limits} \
 ${MAX_MEMORY_BYTES:+-v ${MAX_MEMORY_BYTES}} \
  ${MAX_FILES:+-n ${MAX_FILES}} \

Whoops I tried building 3458bbd to reproduce, but I missed the "need to be older than" part.
3458bbd doesn't build successfully anyways, so now I'm going to try to build 0ecbb28 "vm_map: add vm_map_find_locked(9)" which is the parent of 3458bbd.
May take another day to build though ;-;

It's semantics but this isn't a bug.
if [ ${JAIL_OSVERSION} -gt ${HOST_OSVERSION} ]; then
        echo
        echo
        echo
        echo "!!! Jail is newer than host. (Jail: ${JAIL_OSVERSION}, Host: ${HOST_OSVERSION}) !!!"
        echo "!!! This is not supported. !!!"
        echo "!!! Host kernel must be same or newer than jail. !!!"
        echo "!!! Expect build failures. !!!"
        echo
        echo
        echo
fi

I think it's reasonable to consider addressing the issue but there are countless more problems that can happen when the jail is newer than the kernel.
About the issue, it would be quite surprising if a limit was ignored? So what would the right fix be here? I don't think this is fixable.


Remove webpack from peerDependencies

Modification Proposal
We are using postcss-loader with rsbuild. This means, we don't use webpack directly anymore / don't have it installed. postcss-loader still works fine with the setup, but when doing a yarn install, yarn complains about not having webpack listed in our dependencies.

➤ YN0002: │ my-awesome-rsbuild-webapp doesn't provide webpack (p1ea2d), requested by postcss-loader.

As postcss-loader doesn't use webpack directly, I think it's ok to just remove it from the peerDependencies array.
Expected Behavior / Situation
The loader will behave the same, but in the context of rsbuild won't add a warning in the install logs.
Actual Behavior / Situation
A warning in the install logs:

➤ YN0002: │ my-awesome-rsbuild-webapp doesn't provide webpack (p1ea2d), requested by postcss-loader.

https://github.com/webpack-contrib/css-loader/issues/1567#issuecomment-1911926011


Update polling logic

ping @matskiv @laurafitzgerald

@laurafitzgerald I dont believe that is actually a problem because we are usiing the until condition as the fail case and when the container starts that should pass regardless of the environment

after discussion with @PhilipGough the comments I left above are resolved.

Look good, verifying on OSM1 ATM.


Examples using  don't use art direction

http://scottjehl.github.io/picturefill/ - the picture example uses the same assets as the sizes example. For people who don't read but just copies examples, this is confusing.
I think the page could do a better job overall by explaining and showcasing the use case and the markup that goes with it instead of having the same image assets for all use cases and sizes="" value that doesn't even reflect the breakpoints in the CSS.

I’ll get this today.


Automatically update vertex normals when morphing

Is your feature request related to a problem? Please describe.
As far as I know, the Filament would not update vertex normal(tangent) when morphing animation, it only calculate the normal at first loading, the dynamic normal can make more effect at avatar emoticon animation
Describe the solution you'd like
A API or solution which can update vertex normal at morphing
Describe alternatives you've considered
/
OS and backend
Android OpenGLES
Any suggestion? Thanks in advance.

I don't understand the problem. Filament does update the normals when morphing if they are supplied in the MorphTargetBuffer.


Fixed threshold docs

The documentation for the ThresholdMeanExt trait appeared to be copy-n-pasted from the ThresholdOtsuExt trait. I thought I would take this opportunity to also clean up the doc comments and fix some formatting, too. PR submitted with appreciate from all contributors and developers for the implementation and crate. Thank you!

Thanks for that :+1:


About train_lgbm.py

When I run the train_lgbm.py, I got a warning——[LightGBM] [Warning] No further splits with positive gain, best gain: -inf
Could you tell me how to solve it？？

Not sure, but this warning might be just informational as long as you get correct model.


Black screen on computer browser

Hi,
First, thanks for this integration!
It's working on my mobile phone, but it's not working on regular browser (same wifi), only black screen with RTP
I checked different browser, tried to debug as much as I can.
Debug logs:
2023-08-30 08:13:16.162 ERROR (MainThread) [homeassistant] Error doing job: Fatal read error on STARTTLS transport
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/aioopenssl/__init__.py", line 493, in _read_ready
    data = self._sock.recv(self.MAX_SIZE)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/OpenSSL/SSL.py", line 2056, in recv
    self._raise_ssl_error(self._ssl, result)
  File "/usr/local/lib/python3.11/site-packages/OpenSSL/SSL.py", line 1794, in _raise_ssl_error
    raise ZeroReturnError()
OpenSSL.SSL.ZeroReturnError
2023-08-30 08:13:38.001 DEBUG (MainThread) [custom_components.webrtc] New client: {'authSig': 'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiIzNmNhMDljZmE1YjM0NDEwYjg1YWY5NmRjYTRlNzdkZCIsInBhdGgiOiIvYXBpL3dlYnJ0Yy93cyIsInBhcmFtcyI6W10sImlhdCI6MTY5MzM3NjAxNywiZXhwIjoxNjkzMzc2MDQ3fQ.aWCS6PVE8HIdSq5MA9Gmj7QB6qmZTYIc2vOo4K5seIw', 'url': 'rtsp://<IP_ADDRESS>/ch0_0.h264'}

I don't know if OpenSSL.SSL.ZeroReturnError comes from this integration.
Camera is on different vlan, just fyi.
Any thoughts?

camera resetted itself and switched to H.265. Sorry for bothering