update maven jar deployment doc with schema v2

Docs Build status updates of commit c351a8d:
:clock10: Full build: the average full build time is 70 min(s) 40 sec(s), this is based on the last 230 build(s) for this repository.
:warning: This is a FULL build due to the incremental build being disabled in configuration file (.openpublishing.publish.config.json in 'live' branch). For more detailed info, please click here.

Docs Build status updates of commit c351a8d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/spring-framework/deploy-spring-boot-java-app-with-maven-plugin.md
:white_check_mark:Succeeded
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 5095fd7:
:clock10: Full build: the average full build time is 70 min(s) 41 sec(s), this is based on the last 231 build(s) for this repository.
:warning: This is a FULL build due to the incremental build being disabled in configuration file (.openpublishing.publish.config.json in 'live' branch). For more detailed info, please click here.

Docs Build status updates of commit 5095fd7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/spring-framework/deploy-spring-boot-java-app-with-maven-plugin.md
:white_check_mark:Succeeded
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 726c467:
:clock10: Full build: the average full build time is 70 min(s) 43 sec(s), this is based on the last 240 build(s) for this repository.
:warning: This is a FULL build due to the incremental build being disabled in configuration file (.openpublishing.publish.config.json in 'live' branch). For more detailed info, please click here.

Docs Build status updates of commit 726c467:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-autogen/com.microsoft.azure.storage.blob.ServiceSASSignatureValues.yml
:warning:Warning
View (azure-java-stable)
Details

docs-ref-autogen/com.microsoft.azure.storage.blob.RequestRetryOptions.yml
:warning:Warning
View (azure-java-stable)
Details

docs-ref-autogen/com.microsoft.azure.storage.blob.ProgressReporter.yml
:warning:Warning
View (azure-java-stable)
Details

docs-ref-autogen/com.microsoft.azure.storage.blob.PipelineOptions.yml
:warning:Warning
View (azure-java-stable)
Details

docs-ref-autogen/com.microsoft.azure.storage.blob.PageBlobURL.yml
:warning:Warning
View (azure-java-stable)
Details

docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml
:warning:Warning
View (azure-java-stable)
Details

docs-ref-autogen/com.microsoft.azure.storage.blob.BlockBlobURL.yml
:warning:Warning
View (azure-java-stable)
Details

docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURLParts.yml
:warning:Warning
View (azure-java-stable)
Details

docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml
:warning:Warning
View (azure-java-stable)
Details

docs-ref-autogen/com.microsoft.azure.storage.blob.AppendBlobURL.yml
:warning:Warning
View (azure-java-stable)
Details

docs-ref-autogen/com.microsoft.azure.storage.blob.AccountSASSignatureValues.yml
:warning:Warning
View (azure-java-stable)
Details

docs-ref-autogen/com.microsoft.azure.storage.blob.StorageURL.yml
:warning:Warning
View (azure-java-stable)
Details

docs-ref-autogen/com.microsoft.azure.storage.blob.StorageException.yml
:warning:Warning
View (azure-java-stable)
Details

docs-ref-autogen/com.microsoft.azure.storage.blob.ServiceURL.yml
:warning:Warning
View (azure-java-stable)
Details

docs-ref-autogen/com.microsoft.azure.storage.blob.LoggingOptions.yml
:warning:Warning
View (azure-java-stable)
Details

docs-ref-autogen/com.microsoft.azure.storage.blob.TransferManager.yml
:warning:Warning
View (azure-java-stable)
Details

preview/docs-ref-autogen/com.microsoft.azure.storage.blob._storage_u_r_l.yml
:warning:Warning
View (azure-java-preview)
Details

preview/docs-ref-autogen/com.microsoft.azure.storage.blob._logging_options.yml
:warning:Warning
View (azure-java-preview)
Details

preview/docs-ref-autogen/com.microsoft.azure.storage.blob._storage_exception.yml
:warning:Warning
View (azure-java-preview)
Details

preview/docs-ref-autogen/com.microsoft.azure.storage.blob._transfer_manager.yml
:warning:Warning
View (azure-java-preview)
Details

preview/docs-ref-autogen/com.microsoft.azure.storage.blob._block_blob_u_r_l.yml
:warning:Warning
View (azure-java-preview)
Details

preview/docs-ref-autogen/com.microsoft.azure.storage.blob._blob_u_r_l_parts.yml
:warning:Warning
View (azure-java-preview)
Details

preview/docs-ref-autogen/com.microsoft.azure.storage.blob._blob_u_r_l.yml
:warning:Warning
View (azure-java-preview)
Details

preview/docs-ref-autogen/com.microsoft.azure.storage.blob._account_s_a_s_signature_values.yml
:warning:Warning
View (azure-java-preview)
Details

preview/docs-ref-autogen/com.microsoft.azure.storage.blob._service_s_a_s_signature_values.yml
:warning:Warning
View (azure-java-preview)
Details

preview/docs-ref-autogen/com.microsoft.azure.storage.blob._service_u_r_l.yml
:warning:Warning
View (azure-java-preview)
Details

preview/docs-ref-autogen/com.microsoft.azure.storage.blob._request_retry_options.yml
:warning:Warning
View (azure-java-preview)
Details

preview/docs-ref-autogen/com.microsoft.azure.storage.blob._pipeline_options.yml
:warning:Warning
View (azure-java-preview)
Details

preview/docs-ref-autogen/com.microsoft.azure.storage.blob._page_blob_u_r_l.yml
:warning:Warning
View (azure-java-preview)
Details

preview/docs-ref-autogen/com.microsoft.azure.storage.blob._container_u_r_l.yml
:warning:Warning
View (azure-java-preview)
Details

preview/docs-ref-autogen/com.microsoft.azure.storage.blob._append_blob_u_r_l.yml
:warning:Warning
View (azure-java-preview)
Details

docs-ref-conceptual/spring-framework/deploy-spring-boot-java-app-with-maven-plugin.md
:white_check_mark:Succeeded
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)

docs-ref-autogen/com.microsoft.azure.storage.blob.ServiceSASSignatureValues.yml

Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ServiceSASSignatureValues.yml'.

docs-ref-autogen/com.microsoft.azure.storage.blob.RequestRetryOptions.yml

Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.RequestRetryOptions.yml'.

docs-ref-autogen/com.microsoft.azure.storage.blob.ProgressReporter.yml

Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ProgressReporter.yml'.

docs-ref-autogen/com.microsoft.azure.storage.blob.PipelineOptions.yml

Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.PipelineOptions.yml'.

docs-ref-autogen/com.microsoft.azure.storage.blob.PageBlobURL.yml

Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.PageBlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.PageBlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.PageBlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.PageBlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.PageBlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.PageBlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.PageBlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.PageBlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.PageBlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.PageBlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.PageBlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.PageBlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.PageBlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.PageBlobURL.yml'.
Line 2: [Warning] Invalid file link:(~/azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java?name=page_from_url).
Line 2: [Warning] Invalid file link:(~/azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java?name=page_from_url).

docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml

Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ContainerURL.yml'.

docs-ref-autogen/com.microsoft.azure.storage.blob.BlockBlobURL.yml

Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlockBlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlockBlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlockBlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlockBlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlockBlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlockBlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlockBlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlockBlobURL.yml'.
Line 2: [Warning] Invalid file link:(~/azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java?name=block_from_url).
Line 2: [Warning] Invalid file link:(~/azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java?name=block_from_url).

docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURLParts.yml

Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURLParts.yml'.

docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml

Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.BlobURL.yml'.

docs-ref-autogen/com.microsoft.azure.storage.blob.AppendBlobURL.yml

Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.AppendBlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.AppendBlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.AppendBlobURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.AppendBlobURL.yml'.
Line 2: [Warning] Invalid file link:(~/azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java?name=append_from_url).
Line 2: [Warning] Invalid file link:(~/azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java?name=append_from_url).

docs-ref-autogen/com.microsoft.azure.storage.blob.AccountSASSignatureValues.yml

Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.AccountSASSignatureValues.yml'.

docs-ref-autogen/com.microsoft.azure.storage.blob.StorageURL.yml

Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.StorageURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.StorageURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.StorageURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.StorageURL.yml'.

docs-ref-autogen/com.microsoft.azure.storage.blob.StorageException.yml

Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.StorageException.yml'.

docs-ref-autogen/com.microsoft.azure.storage.blob.ServiceURL.yml

Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ServiceURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ServiceURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ServiceURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ServiceURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ServiceURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ServiceURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ServiceURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ServiceURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ServiceURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ServiceURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ServiceURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ServiceURL.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.ServiceURL.yml'.

docs-ref-autogen/com.microsoft.azure.storage.blob.LoggingOptions.yml

Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.LoggingOptions.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.LoggingOptions.yml'.

docs-ref-autogen/com.microsoft.azure.storage.blob.TransferManager.yml

Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.TransferManager.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'docs-ref-autogen/com.microsoft.azure.storage.blob.TransferManager.yml'.

Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._transfer_manager.yml'.

preview/docs-ref-autogen/com.microsoft.azure.storage.blob._block_blob_u_r_l.yml

Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._block_blob_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._block_blob_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._block_blob_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._block_blob_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._block_blob_u_r_l.yml'.

preview/docs-ref-autogen/com.microsoft.azure.storage.blob._blob_u_r_l_parts.yml

Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._blob_u_r_l_parts.yml'.

preview/docs-ref-autogen/com.microsoft.azure.storage.blob._blob_u_r_l.yml

Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._blob_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._blob_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._blob_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._blob_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._blob_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._blob_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._blob_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._blob_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._blob_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._blob_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._blob_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._blob_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._blob_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._blob_u_r_l.yml'.

Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._service_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._service_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._service_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._service_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._service_u_r_l.yml'.

Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._page_blob_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._page_blob_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._page_blob_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._page_blob_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._page_blob_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._page_blob_u_r_l.yml'.

preview/docs-ref-autogen/com.microsoft.azure.storage.blob._container_u_r_l.yml

Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._container_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._container_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._container_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._container_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._container_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._container_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._container_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._container_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._container_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._container_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._container_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._container_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._container_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._container_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._container_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._container_u_r_l.yml'.

preview/docs-ref-autogen/com.microsoft.azure.storage.blob._append_blob_u_r_l.yml

Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._append_blob_u_r_l.yml'.
Line 0: [Warning] Cannot resolve '../azure-storage-java/src/test/java/com/microsoft/azure/storage/Samples.java' relative to 'preview/docs-ref-autogen/com.microsoft.azure.storage.blob._append_blob_u_r_l.yml'.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@brunoborges  Could you please help review this?

Docs Build status updates of commit a756768:
:clock10: Full build: the average full build time is 70 min(s) 46 sec(s), this is based on the last 242 build(s) for this repository.
:warning: This is a FULL build due to the incremental build being disabled in configuration file (.openpublishing.publish.config.json in 'live' branch). For more detailed info, please click here.

Docs Build status updates of commit a756768:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.vscode/settings.json
:white_check_mark:Succeeded

docs-ref-conceptual/eclipse/media/azure-toolkit-for-eclipse-create-hello-world-web-app/deploy-app-service.png
:white_check_mark:Succeeded
View (azure-java-legacy) View (azure-java-preview) View (azure-java-stable)

docs-ref-conceptual/eclipse/media/azure-toolkit-for-eclipse-create-hello-world-web-app/dynamic-web-project-properties.png
:white_check_mark:Succeeded
View (azure-java-legacy) View (azure-java-preview) View (azure-java-stable)

docs-ref-conceptual/eclipse/media/azure-toolkit-for-eclipse-create-hello-world-web-app/select-app-service.png
:white_check_mark:Succeeded
View (azure-java-legacy) View (azure-java-preview) View (azure-java-stable)

docs-ref-conceptual/eclipse/media/azure-toolkit-for-intellij-sign-in-instructions/A03.png
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-conceptual/eclipse/media/azure-toolkit-for-intellij-sign-in-instructions/A04.png
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-conceptual/eclipse/media/azure-toolkit-for-intellij-sign-in-instructions/A05.png
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-conceptual/eclipse/media/azure-toolkit-for-intellij-sign-in-instructions/A06.png
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-conceptual/eclipse/media/azure-toolkit-for-intellij-sign-in-instructions/A08.png
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-conceptual/eclipse/media/azure-toolkit-for-intellij-sign-in-instructions/I03.png
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-conceptual/eclipse/media/azure-toolkit-for-intellij-sign-in-instructions/L02.png
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-conceptual/eclipse/media/azure-toolkit-for-intellij-sign-in-instructions/L03.png
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-conceptual/spring-framework/deploy-spring-boot-java-app-with-maven-plugin.md
:white_check_mark:Succeeded
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit bf422f3:
:clock10: Full build: the average full build time is 70 min(s) 48 sec(s), this is based on the last 243 build(s) for this repository.
:warning: This is a FULL build due to the incremental build being disabled in configuration file (.openpublishing.publish.config.json in 'live' branch). For more detailed info, please click here.

Docs Build status updates of commit bf422f3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/spring-framework/deploy-spring-boot-java-app-with-maven-plugin.md
:white_check_mark:Succeeded
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

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

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/Azure/azure-docs-sdk-java, working directory: W:\h1nz-s, target branch: master, target branch commit: 6782d62002a37f4b9b3b0a6e7d474b6381646948, source commit: 0fa85e342e20b7d4e316edf473c0bd301faaa277.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 045db31:
:clock10: Full build: the average full build time is 70 min(s) 57 sec(s), this is based on the last 249 build(s) for this repository.

Docs Build status updates of commit 045db31:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/spring-framework/deploy-spring-boot-java-app-with-maven-plugin.md
:white_check_mark:Succeeded
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 0fa85e3:
:clock10: Full build: the average full build time is 70 min(s) 57 sec(s), this is based on the last 250 build(s) for this repository.

Docs Build status updates of commit 0fa85e3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/spring-framework/deploy-spring-boot-java-app-with-maven-plugin.md
:white_check_mark:Succeeded
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 6efb846:
:clock10: Full build: the average full build time is 70 min(s) 57 sec(s), this is based on the last 251 build(s) for this repository.

Docs Build status updates of commit 6efb846:
:clock10: Full build: the average full build time is 70 min(s) 57 sec(s), this is based on the last 251 build(s) for this repository.

Docs Build status updates of commit 6efb846:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/spring-framework/deploy-spring-boot-java-app-with-maven-plugin.md
:white_check_mark:Succeeded
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@JasonFreeberg hey Jason, can you please review the note about the environment variable PORT contained in these changes?

Docs Build status updates of commit ec50d6c:
:clock10: Full build: the average full build time is 70 min(s) 58 sec(s), this is based on the last 253 build(s) for this repository.

Docs Build status updates of commit ec50d6c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/java-sdk-azure-get-started.md
:white_check_mark:Succeeded
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)

docs-ref-conceptual/spring-framework/deploy-spring-boot-java-app-with-maven-plugin.md
:white_check_mark:Succeeded
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 6efb846:
:clock10: Full build: the average full build time is 71 min(s), this is based on the last 255 build(s) for this repository.

Docs Build status updates of commit 6efb846:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/spring-framework/deploy-spring-boot-java-app-with-maven-plugin.md
:white_check_mark:Succeeded
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@brunoborges @yucwan --
I spoke to the Linux PM. The PORT variable is for Vnet, which is in preview. They will clean up the confusion between PORT and WEBSITE_PORT before VNet goes to GA.
It is best that developers configure their Java app to listen to port 80 when it is on App Service. That is the guidance in our Java dev guide and in the examples. They can set this in their production build profile.

@JasonFreeberg can you please clarify?

If user sets a custom PORT in the App Settings, is that taken into consideration?
Should the app run on whatever port is specified in PORT?
In what scenario the user needs to use, and/or set, WEBSITE_PORT?

// @Flanker32 we should perhaps hold this PR until we have clear understanding of the set up.

The app should run on port 80. I suggest developers configure their app to listen on 80 explicitly (by using a Maven/Gradle or Spring profile).
They can provide a value to WEBSITE_PORT, which will configure the container to route traffic to that given port, instead of 80. The config predates me so I don't know what scenario caused its creation originally.
I think we should expose them to as few App Service-isms as possible. "Configure your app to listen on port 80" is simpler than explaining WEBSITE_PORT.
PORT is there for VNet integration, which is in preview. I would disregard it for this situation.

The problem I see with Configure your app to listen on port 80 is that port 80 is below 1024 and in many cases, it is a troublesome for users during development because it is a reserved port range.
I feel that we are forcing users to have to configure profiles in Maven/Gradle or whatever tool or framework they have to produce a different build specifically configured for App Service nonetheless, and that to me is App Service-ism enough.
If there is a default port to be used instead of having to set WEBSITE_PORT, then that port should be anything but < 1024, and the environment variable WEBSITE_PORT should always be present with that value in case user apps reference it, while still allowing App Service Configuration to change its value.
Plus, it should be clear in the docs somewhere what PORT is used for because in many samples and articles out there, there are indications to bind the Java app to this environment variable instead of WEBSITE_PORT.

Yeah that's also a fair point. In my demos I often use Maven or Spring profiles to set the port because I already need to configure other values for test vs prod. If you want this article to use WEBSITE_PORT that works!
Do you still have those articles using PORT? I'll take those to the owner and get those ironed out.

I don't have a list out of my head, but it is something I definitely referenced myself in the integration-tests.
A key question: in the App Service environment - in all possible environments - is the WEBSITE_PORT variable always present with the default value (80) ?

@brunoborges @JasonFreeberg Regarding to this doc, I propose to stay the old way to configure the spring app to run on port 80 with -Dserver.port=80; while providing a link to Configure custom container in case they want to use other port. Thus we don't need to maintain that information here.

Closing this pr since content is now outdate


Resolve issue_140: remove Sybase from command-line and improve text

Signed-off-by: renee2468<EMAIL_ADDRESS>

resolved by PR #141


Use addFunction to add MultiMaterial to a scene

The function addMultiMaterial is affected by the observer or the _blockEntityCollection variable. This needs to be taken into account.
You can see a similar case with the Material class.
https://github.com/BabylonJS/Babylon.js/blob/master/packages/dev/core/src/Materials/material.ts#L922
And this is the problematic code. Even if _blockEntityCollection is set, MultiMaterial will still be added to the scene.
https://github.com/BabylonJS/Babylon.js/blob/master/packages/dev/loaders/src/glTF/1.0/glTFLoader.ts#L786

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.


fix(deps): update github.com/ibm-cloud/bluemix-go digest to b838ccd

This PR contains the following updates:

Package
Type
Update
Change

github.com/IBM-Cloud/bluemix-go
require
digest
eecebfb -> b838ccd

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 1.10.6 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


AttributeError: module 'auton_survival' has no attribute 'plot_kaplanmeier'

Here is the code (directly from the notebooks:
# Plot the phenogroup specific Kaplan-Meier survival estimate.
auton_survival.reporting.plot_kaplanmeier(outcomes, groups=phenotypes)

Here is the error message:

> ---------------------------------------------------------------------------
> AttributeError                            Traceback (most recent call last)
> [~\AppData\Local\Temp\ipykernel_20180\1703960961.py](https://file+.vscode-resource.vscode-cdn.net/c%3A/Users/Snehal%20Patel/OneDrive%20-%20SimBioSys/Hack-a-thon/Hack-a-thon%202023/Code_and_Data/~/AppData/Local/Temp/ipykernel_20180/1703960961.py) in
>       1 # Plot the phenogroup specific Kaplan-Meier survival estimate.
> ----> 2 auton_survival.reporting.plot_kaplanmeier(outcomes, groups=phenotypes)
>
> AttributeError: module 'auton_survival' has no attribute 'reporting'

I tried importing the function first, but I get the same error:
from auton_survival.reporting import plot_kaplanmeier

> ---------------------------------------------------------------------------
> ModuleNotFoundError                       Traceback (most recent call last)
> [~\AppData\Local\Temp\ipykernel_20180\4279169460.py](https://file+.vscode-resource.vscode-cdn.net/c%3A/Users/Snehal%20Patel/OneDrive%20-%20SimBioSys/Hack-a-thon/Hack-a-thon%202023/Code_and_Data/~/AppData/Local/Temp/ipykernel_20180/4279169460.py) in
> ----> 1 from auton_survival.reporting import plot_kaplanmeier
>
> ModuleNotFoundError: No module named 'auton_survival.reporting'

hmm are you using pip install to install the package? We don't support pip yet have you tried cloning the package and using directly?

Got it.  I did use pip, so I'll try cloning directly, as you suggested.  Thanks for propt reply!

hmm are you using pip install to install the package? We don't support pip yet have you tried cloning the package and using directly?

Just a heads up: we now support pip installs via pip install auton-survival
https://pypi.org/project/auton-survival/

Thanks for the heads up!  Really great to have the ability to pip install
:)
On Thu, Nov 9, 2023 at 9:44 AM Matteo Fordiani @.***>
wrote:

hmm are you using pip install to install the package? We don't support pip
yet have you tried cloning the package and using directly?
Just a heads up: we now support pip installs via pip install
auton-survival
https://pypi.org/project/auton-survival/
—
Reply to this email directly, view it on GitHub
https://github.com/autonlab/auton-survival/issues/126#issuecomment-1804077418,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGAPI634NNASRZO3S7HNWWDYDT26VAVCNFSM6AAAAAA3KLHQL6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBUGA3TONBRHA
.
You are receiving this because you authored the thread.Message ID:
@.***>


using 2 different AD servers, one as a fallback

Laravel Version: 6.1
Adldap2-Laravel Version: 10.2.3
PHP Version:7.2
LDAP Type: ActiveDirectory

Description:
We are trying to use 2 ldap servers we are required to maintain, where one is default and one is a fallback if authentication in the default fails.  What I have tried is

Create a new user provider that extends your DatabaseUserProvider
Create my second connection in ldap.php
In my user provider, use Resolver::setConnection() in my own ::retrieveByCredentials() and ::validateCredentials() methods to try to use my second ldap connection.
If authentication fails, let it fall back to the parent, which is your default DatabaseUserProvider class, which hopefully will use the default connection.

So far this doesn't seem to be working and I wanted to see if you see a flaw in my logic, I cannot tell what is failing right now.  I did notice though when I open up the laravel log file, even after authentication fails and the application is not running, the ldap library continues to log connection attempts in the log file, like it is running in the background, trying to connect to both ldap servers in a loop, it looks like it is stuck in some sort of loop.
Any help is appreciated.
Steps To Reproduce:

Hi @justageek, thanks so much for the sponsorship! ❤
This may be tricky since multi-domain support isn’t built in, but I’ll try to help as much as I can.
I’m tied up for bit of the night, but I’ll write up a response later and we can get try to get this working.

Hi @justageek, I'm ready to help tackle this with you.
Before you call Resolver::setConnection() I believe you should first attempt connecting to that server -- otherwise the Resolver::byCredentials() method will return null since the LDAP query will fail to run. I believe this may be a step that is missing.
Can you share your code along with where you are doing this logic during authentication?

@stevebauman , here is my custom user provider and the ldap_auth.php file so you can see how it is used.
AuditPortalUserProvider.php.zip
ldap_auth.php.zip

Ok great thanks!
So you have two options:

Set auto_connect to true in your config/ldap.php file for both of your LDAP connections
Attempt connecting to the LDAP connection prior to calling Resolver::byCredentials()

Do you have auto_connect enabled on your connections? This option will attempt to bind to your configured LDAP servers when the Resolver is called -- otherwise you have to connect manually.
Also, if you could post the logs that get generated upon login, that would help me debug with you.
You should only need to call Resolver::setConnection('audit-portal'); once in the providers retrieveByCredentials method.
However, I'm not seeing any kind of fallback logic here -- only one LDAP connection is being used.
I would suggest looping through your configured LDAP connections in the retrieveByCredentials method and setting the Resolver connection like so:
public function retrieveByCredentials(array $credentials)
{
    foreach (config('ldap.connections') as $name => $config) {
        Resolver::setConnection($name);

        if (!$user = parent::retrieveByCredentials($credentials) {
            continue;
        }

        return $user;
    }
}

Let me know if that works! 👍

Thanks again Steve, I have to admit I don't 100% follow the logic, we do have auto_connect set to true for both connections by default.  What do I call in order to do the following:
Attempt connecting to the LDAP connection prior to calling Resolver::byCredentials()
One thing that confused me is since ldap_auth.php has one single key/value for 'connection', it seems like every time you try to authenticate, it is going to try to use that connection value, maybe that doesn't matter.  So, the first time it tries to authenticate someone, it will use my custom user provider by try to use the default connection, since that is how ldap_auth.php is set up right now.  I will give your loop idea a try and see what happens.  Do I need to disable the "fallback" logic so if one authentication fails it doesnt' automatically try to fallback to the next?

Steve, I have sort of a mess, I am testing a user that should authenticate in the default ldap connection but should not in the second connection, and it looks like my code sees the failure in the second connection before it has a chance to see if the authentication worked in the default.  It is hard to tell.  You can see the user is found in the ldap server but then fails authentication because the code tries the second connection for the authentication and it fails there.
`
[2020-05-27 21:50:31] local.INFO: LDAP (ldaps://dc-cluster.cashexpressllc.com:636) - Connection: default - Operation: Binding - Username: CASHEXPRESSLLC\auditorportal
[2020-05-27 21:50:32] local.INFO: LDAP (ldaps://dc-cluster.cashexpressllc.com:636) - Connection: default - Operation: Bound - Username: CASHEXPRESSLLC\auditorportal
[2020-05-27 21:50:32] local.INFO: LDAP (ldaps://cashtn.com:636) - Connection: audit-portal - Operation: Binding - Username: CASHTN\svc_auditor_portal
[2020-05-27 21:50:33] local.INFO: LDAP (ldaps://cashtn.com:636) - Connection: audit-portal - Operation: Bound - Username: CASHTN\svc_auditor_portal
[2020-05-27 21:50:33] local.INFO: LDAP (ldaps://dc-cluster.cashexpressllc.com:636) - Connection: default - Operation: Search - Base DN: OU=CashExpressLLC,DC=cashexpressllc,DC=com - Filter: (&(objectclass=user)(objectcategory=person)(!(objectclass=contact))(samaccountname=matthew.pearce)) - Selected: (*,objectguid) - Time Elapsed: 274.63
[2020-05-27 21:50:33] local.INFO: User 'Matthew Pearce' has been successfully found for authentication.
[2020-05-27 21:50:33] local.INFO: User 'Matthew Pearce' is being synchronized.
[2020-05-27 21:50:33] local.INFO: User 'Matthew Pearce' has been successfully synchronized.
[2020-05-27 21:50:33] local.INFO: User 'Matthew Pearce' is authenticating with username: 'CN=Matthew Pearce,OU=Standard Users,OU=CashExpressLLC,DC=cashexpressllc,DC=com'
[2020-05-27 21:50:33] local.INFO: LDAP (ldaps://cashtn.com:636) - Connection: audit-portal - Operation: Attempting - Username: CN=Matthew Pearce,OU=Standard Users,OU=CashExpressLLC,DC=cashexpressllc,DC=com
[2020-05-27 21:50:33] local.INFO: LDAP (ldaps://cashtn.com:636) - Connection: audit-portal - Operation: Binding - Username: CN=Matthew Pearce,OU=Standard Users,OU=CashExpressLLC,DC=cashexpressllc,DC=com
[2020-05-27 21:50:34] local.WARNING: LDAP (ldaps://cashtn.com:636) - Connection: audit-portal - Operation: Failed - Username: CN=Matthew Pearce,OU=Standard Users,OU=CashExpressLLC,DC=cashexpressllc,DC=com - Reason: Invalid credentials
[2020-05-27 21:50:34] local.INFO: LDAP (ldaps://cashtn.com:636) - Connection: audit-portal - Operation: Binding - Username: CASHTN\svc_auditor_portal
[2020-05-27 21:50:34] local.INFO: LDAP (ldaps://cashtn.com:636) - Connection: audit-portal - Operation: Bound - Username: CASHTN\svc_auditor_portal
[2020-05-27 21:50:34] local.INFO: User 'Matthew Pearce' has failed LDAP authentication.
[2020-05-27 21:50:34] local.INFO: LDAP (ldaps://dc-cluster.cashexpressllc.com:636) - Connection: default - Operation: Binding - Username: CASHEXPRESSLLC\auditorportal
[2020-05-27 21:50:36] local.INFO: LDAP (ldaps://dc-cluster.cashexpressllc.com:636) - Connection: default - Operation: Bound - Username: CASHEXPRESSLLC\auditorportal
[2020-05-27 21:50:36] local.INFO: LDAP (ldaps://cashtn.com:636) - Connection: audit-portal - Operation: Binding - Username: CASHTN\svc_auditor_portal
[2020-05-27 21:50:36] local.INFO: LDAP (ldaps://cashtn.com:636) - Connection: audit-portal - Operation: Bound - Username: CASHTN\svc_auditor_portal
`

Steve, I have a weird mess here, my user is being found in the default ldap server, which is correct for my test, but then fails authentication because it looks like the code moves on to the second connection before it tries the authentication step.
User 'Matthew Pearce' has been successfully found for authentication.
[2020-05-27 21:50:33] local.INFO: User 'Matthew Pearce' is being synchronized.
[2020-05-27 21:50:33] local.INFO: User 'Matthew Pearce' has been successfully synchronized.
[2020-05-27 21:50:33] local.INFO: User 'Matthew Pearce' is authenticating with username:
I don't know why it moves on to the second connection after finding the user in the default ldap server.

Steve, thanks for your help , I am really close, I have the authentication working with your loop through the connections, however for some reason if I the login_fallback set to true, it connects and binds to the ldap server but never searches for and locates the user and then proceeds to authentication for some reason, it works if I set it to false.  I guess it falls back to fast to the Eloquent login credentials, which my test user doesn't have.

No problem @justageek! Sounds like we're getting close.

however for some reason if I the login_fallback set to true, it connects and binds to the ldap server but never searches for and locates the user and then proceeds to authentication for some reason, it works if I set it to false.

In your application, are you only wanting LDAP users to be able to authenticate? Or will your app support registering / creating local users that must be able to sign in as well?
The login fallback option is for the latter of the above (supporting sign in for local app users who do not exist in your LDAP servers).
If you wish to support this, we will need to override a bit more logic and I will help you with that once I know the direction you're looking to take in your app. Thanks!

Steve, so I don't know what to think, if I have login_fallback set to true, I cannot login with a user that is in the second Active Directory server.  But if I set it to false, the login for the default AD server doesn't work.

Ok -- let me make some patches here. Shouldn't take long. Once I'm done, I'll need you to perform a composer update. I'll post here again shortly!

ok

Ok -- now I'll need you to update your composer.json file with the following to receive the latest patch:
"adldap2/adldap2-laravel": "dev-master",

Then, run the following to download it:
composer update

Afterwards, in your customer provider, paste the following code:
/**
 * Whether to fallback to Eloquent authentication.
 *
 * @var bool
 */
protected $fallback = false;

public function retrieveByCredentials(array $credentials)
{
    foreach ($connections = config('ldap.connections', []) as $name => $config) {
        Resolver::setConnection($name);

        if ($user = parent::retrieveByCredentials($credentials)) {
            return $user;
        }

        end($connections);

        // Here we will determine if we are on the last connection. If
        // so, we will enable fallback to Eloquent authentication and
        // attempt to retrieve the local database user to fallback to.
        if ($name == key($connections)) {
            $this->fallback = true;

            return $this->eloquent->retrieveByCredentials($credentials);
        }
    }
}

protected function isFallingBack()
{
    return $this->fallback;
}

Once complete, try authenticating against both domains you have configured, and then a local database user.
Let me know if it works!

Hi Steve, I need to run a full set of tests, but I think it is going to work.  I cannot thank you enough for all the work on this, you are awesome for doing it for us!

Sounds good! And I’m happy to help and I will always support my sponsors 😄
Will wait for your update 👍


Modals: implement a system for reusing custom modals

Describe what feature you'd like. Pseudo-code, mockups, or screenshots of similar solutions are encouraged!
Currently users can call canned options like alerts, confirm, prompt with minimal config - just import the store and pass the appropriate settings. However, each time a custom modal is used it has to be imported, over and over again per page. Let's consider implementing a means to "register" these custom components one time - perhaps with or alongside the implementation of the <Modal /> itself in the root layout.
Users should then be able to call these just like the canned option with minimal effort.
What type of pull request would this be?
Enhancement
Any links to similar examples or other references we should review?
No response

View the discussion in this Discord thread:
https://discord.com/channels/1003691521280856084/1062822266032889937
In addition to the above change, we'll want to ensure styling is flexible for custom modals. We should have some way of triggering a "naked" state that's not affected by the standard modal window sizes, styles, etc. That is to say, no card background, shadow, no fixed width, etc.
This will allow for much more dynamic customization and better support for full screen sized modals.

Maybe the following fits in this PR as well. I noticed while using custom ModalComponent, that the following from the docs doesn't work:
const d: ModalSettings = {
	// ...
	backdropClasses: '!items-start'
	modalClasses: '!p-0 !bg-green-500 !max-w-[75%]'
};

Instead only classes: is available which is equivalent to modalClasses. Haven't found a way to style the backdrop classes yet. But I believe this PR is a great opportunity to fix this inconsistency.

Solved as part of: https://github.com/skeletonlabs/skeleton/issues/922
Closing this ticket. Please refer any further comments to the ticket linked above.


brew extract ends up with error "Error: no implicit conversion of nil into Array"

brew config output
brew config
HOMEBREW_VERSION: 3.2.10-69-gfaa56d2
ORIGIN: https://github.com/Homebrew/brew
HEAD: faa56d2118db315bba8415d1770c51f0c4a69adf
Last commit: 5 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 1bfe8dfd7f728a0b191900721d3759d76ed5326d
Core tap last commit: 2 hours ago
Core tap branch: master
HOMEBREW_PREFIX: /usr/local
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 12
Homebrew Ruby: 2.6.3 => /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3_2/bin/ruby
CPU: dodeca-core 64-bit kabylake
Clang: 12.0.0 build 1200
Git: 2.24.3 => /Applications/Xcode_12.4.app/Contents/Developer/usr/bin/git
Curl: 7.64.1 => /usr/bin/curl
macOS: 10.15.7-x86_64
CLT: <IP_ADDRESS>.1.1610135815
Xcode: 12.4 => /Applications/Xcode_12.4.app/Contents/Developer

brew doctor output
brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: Some installed kegs have no formulae!
This means they were either deleted or installed with `brew diy`.
You should find replacements for the following formulae:
<EMAIL_ADDRESS><EMAIL_ADDRESS>
Warning: Some installed formulae are deprecated or disabled.
You should find replacements for the following formulae:
  ilmbase

Warning: "config" scripts exist outside your system or Homebrew directories.
`./configure` scripts often look for *-config scripts to determine if
software packages are installed, and which additional flags to use when
compiling and linking.

Having additional scripts in your path can confuse software installed via
Homebrew if the config script overrides a system or Homebrew-provided
script of the same name. We found the following "config" scripts:
  /Library/Frameworks/Python.framework/Versions/3.6/bin/python3.6m-config
  /Library/Frameworks/Python.framework/Versions/3.6/bin/python3-config
  /Library/Frameworks/Python.framework/Versions/3.6/bin/python3.6-config
  /Library/Frameworks/Python.framework/Versions/3.6/bin/ansible-config

Warning: Unbrewed dylibs were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected dylibs:
  /usr/local/lib/libwkhtmltox.0.12.5.dylib

Warning: Unbrewed header files were found in /usr/local/include.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected header files:
  /usr/local/include/wkhtmltox/image.h
  /usr/local/include/wkhtmltox/pdf.h

Warning: You have unlinked kegs in your Cellar.
Leaving kegs unlinked can lead to build-trouble and cause formulae that depend on
those kegs to fail to run properly once built. Run `brew link` on these:
  telnet
<EMAIL_ADDRESS>
Warning: Some installed formulae are not readable:
<EMAIL_ADDRESS>undefined method `cxx11?' for #<BuildOptions:0x00007ffe94b93b70>

[X] I ran brew update and am still able to reproduce my issue.
[X] I have resolved all warnings from brew doctor and that did not fix my problem.

What were you trying to do (and why)?
I try to extract a previous version of cmake to my local tap. I did not fix all issues brew docotr found as I don't see how this could be related, also some outdated brews I still need for now to build up the tap with the old versions as homebrew doesn't have a better way to install old versions of a formula anymore.
What happened (include all command output)?
brew extract --version 1.18.4 cmake homebrew/lsyzrh
==> Searching repository history
Error: no implicit conversion of nil into Array
Please report this issue:
https://docs.brew.sh/Troubleshooting
/usr/local/Homebrew/Library/Homebrew/software_spec.rb:226:in concat' /usr/local/Homebrew/Library/Homebrew/software_spec.rb:226:in block in needs'
/usr/local/Homebrew/Library/Homebrew/software_spec.rb:225:in each' /usr/local/Homebrew/Library/Homebrew/software_spec.rb:225:in needs'
/usr/local/Homebrew/Library/Homebrew/formula.rb:2955:in block in needs' /usr/local/Homebrew/Library/Homebrew/formula.rb:2955:in each'
/usr/local/Homebrew/Library/Homebrew/formula.rb:2955:in needs' /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core/Formula/cmake.rb:23:in class:Cmake'
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-core/Formula/cmake.rb:1:in block in load_formula' /usr/local/Homebrew/Library/Homebrew/formulary.rb:78:in module_eval'
/usr/local/Homebrew/Library/Homebrew/formulary.rb:78:in block in load_formula' /usr/local/Homebrew/Library/Homebrew/ignorable.rb:44:in hook_raise'
/usr/local/Homebrew/Library/Homebrew/formulary.rb:88:in load_formula' /usr/local/Homebrew/Library/Homebrew/formulary.rb:385:in klass'
/usr/local/Homebrew/Library/Homebrew/formulary.rb:180:in get_formula' /usr/local/Homebrew/Library/Homebrew/formulary.rb:500:in from_contents'
/usr/local/Homebrew/Library/Homebrew/dev-cmd/extract.rb:229:in block in formula_at_revision' /usr/local/Homebrew/Library/Homebrew/dev-cmd/extract.rb:38:in with_monkey_patch'
/usr/local/Homebrew/Library/Homebrew/dev-cmd/extract.rb:229:in formula_at_revision' /usr/local/Homebrew/Library/Homebrew/dev-cmd/extract.rb:158:in block in extract'
/usr/local/Homebrew/Library/Homebrew/dev-cmd/extract.rb:138:in loop' /usr/local/Homebrew/Library/Homebrew/dev-cmd/extract.rb:138:in extract'
/usr/local/Homebrew/Library/Homebrew/brew.rb:129:in `'
What did you expect to happen?
I expect the version to be extract an being available in my local tap, but it only throws this error above
Step-by-step reproduction instructions (by running brew commands)
brew tap --force-auto-update homebrew/lsyzrh<EMAIL_ADDRESS>brew extract --version 1.18.4 cmake homebrew/lsyzrh

Are you sure you want version 1.18.4? As far as I can tell, the earliest version packaged by Homebrew is 2.6.3. (Trying to brew extract that is probably not going to work too well either.)

omg...thx for pointing this out....I guess it was already too late yesterday and I didn't see the obvious problem. I wanted to extract 3.18.4...but the blurry error message didn't gave me the right hint.

Let's see if we can get that error message fixed.


Failed to persist entry: API_ERROR: "params.entry" is required

Hi Im Using Netlify CMS local Proxy Server on my project....
Ive wanna update and add features to it , but
i keep getting error
Failed to persist entry: API_ERROR: "params.entry" is required
Prior months i dont have issue on this....
I dont know if there is a breaking changes that is not mentioned on the documentation....
or its me thats do something wrong...
so,  i keep rolling back to older commits and
reinstall node_modules
and re run server and the netlify cms proxy server
All instances of my rollback produces the same error...
I dont have any solution until now....
But my Production is Working Normal...
I think this is a bug on either the netify cms proxy server or the with the cdn
<EMAIL_ADDRESS>Someone please fix this messed

@codeitlikemiley this error shouldn't surface unless you are not using the latest version of the netlify-cms-proxy-server package. Not sure how you are setting up the proxy server,  according to docs  re-run npx  netlify-cms-proxy-server should setup the latest version of the proxy server package.
If a re-run of the netlify-cms-proxy-server package doesn't work, you would need to double-check whether a specific version of the server package is installed locally.

I vendor lock my netlify-cms-proxy-server in my package.json file....
totally make sense now what this is happening...
I know the only problem here is the proxy server since the production site is working smooth....
Its very important to version lock both proxy and the netlify-cms cdn both having same version...
i know the proxy server is on beta but it worth to note this topic since i think majority of proxy server user will face this issue
Problem is solved when i npm install again , i think the global proxy server is being over written by my per project installation of the proxy server...
@barthc is there a way i can use a local netify cms compiled version instead of using
<EMAIL_ADDRESS>i really need to make netlify cms work even with no internet connection...
and referencing this cdn link must be replace , can you sugguest a way how get the same compiled js
and if there is a big difference on using cdn and a compiled one thanks

Problem is solved when i npm install again , i think the global proxy server is being over written by my per project installation of the proxy server...

Upgrading the netlify-cms-proxy-server package to the latest version(1.3.6) in your package.json should be enough.

@barthc is there a way i can use a local netify cms compiled version instead of using
<EMAIL_ADDRESS>
You would have to compile it yourself, take a look at the manual initialization sample here https://www.netlifycms.org/docs/beta-features/#manual-initialization

I think using the compiled version litterally has some benefits in performance since you wont be reading any yml file?
Hope i can migrate 3k lines of code from my config.yml
can you suggest a service that can easily trans-pile yaml to json?
that would be a time saver...
thanks for help

Hi @codeitlikemiley, and thanks for responding @barthc.

Its very important to version lock both proxy and the netlify-cms cdn both having same version...
i know the proxy server is on beta but it worth to note this topic since i think majority of proxy server user will face this issue

The guarantee for netlify-cms-proxy-server is for it to be backwards compatible with older CMS versions, not forward compatible.
You can pin the CMS version by using<EMAIL_ADDRESS>for example or by installing from npm:
https://www.netlifycms.org/docs/add-to-your-site/#installing-with-npm
In both approaches the CMS will read you config yml, unless you switch to https://www.netlifycms.org/docs/beta-features/#manual-initialization
As for migrating your config - I would open a new issue for that since it is off topic for this one, or ask in our Slack https://www.netlifycms.org/chat
Closing this as resolved.


Create WarpInferType

This PR is to extend the function typeOf from InferType to work also with warp defined Nodes

It is already implemented in safeGetNodeType

It is already implemented in safeGetNodeType

Oh, ok, I didn't see that you already add it recently. I'll remove this PR then


UI 2.0: GenericView Base

Provide a GenericView base template that can be built on top of (see #3528) that provides breadcrumbs, top-menu, and attributes for defining tabs, page headings, buttons, etc:
See:

Implemented with #3626


Find a way to indicate disputed territories

http://en.wikipedia.org/wiki/List_of_states_with_limited_recognition
Using diagonal stripes as an SVG background pattern might work. Dashed borders would not work, because topojson eliminates redundancy of boundary lines.

Don't do this inside the library.


cmd/stackforms: add gen-doc subcommand

in this PR, we add stackforms in their dedicated package to introduce a stackforms command:
$ cy stackforms help
Manage the Cycloid stackforms

Usage:
  cy stackforms [command]

Aliases:
  stackforms, stackform, forms, form, f

Available Commands:
  gen-doc     generate a markdown file from stackforms
  validate    validate a .forms.yml file

[stackforms]
We also added a gen-doc subcommand to generate a markdown documentation from a stackforms spec file in order to automate a project documentation from a single source of truth: the .forms.yml file. It could also be part of a cy stack init boilerplate command.
NB: Currently, only string and integer are supported for the default values, IDK yet how we could render default map / slice.
Example of output:
## Usecase: default

### pipeline

#### Repos

| Parameter Name | Type | Default |
|----------------|------|---------|
| git_repository  | string | git@github.com:MyUser/code.git |

#### Terraform

| Parameter Name | Type | Default |
|----------------|------|---------|
| azure_subscription_id  | string | ((azure.subscription_id)) |
| azure_tenant_id  | string | ((azure.tenant_id)) |

### terraform

#### LogicApp

| Parameter Name | Type | Default |
|----------------|------|---------|
| app_action_body  | string | n/a |

#### VirtualMachines

| Parameter Name | Type | Default |
|----------------|------|---------|
| resource_group_name  | string | n/a |

_Generated by [cycloid-cli](https://github.com/cycloidio/cycloid-cli)_

My only comment is about the command name. Should we want to brand on StackForm name and be part of the root command or do we prefer to keep it inside stacks ?

My only comment is about the command name. Should we want to brand on StackForm name and be part of the root command or do we prefer to keep it inside stacks ?

@gaelL Good feedback. From a daily usage aspect, I guess it's better to centralize this commands under the stack subcommand in order to have something similar to the GUI !

My only comment is about the command name. Should we want to brand on StackForm name and be part of the root command or do we prefer to keep it inside stacks ?

@gaelL Good feedback. From a daily usage aspect, I guess it's better to centralize this commands under the stack subcommand in order to have something similar to the GUI !


[libzip] Update to 1.7.1

Fix #11914
Update libzip to the latest version 1.7.1
All features are tested successfully in the following triplets:

x86-windows

x64-windows

x64-windows-static

x64-uwp

Thank you!


Error on creating Asset

[ ] On adding maximum value it shows error toast but also it allows to create asset @akshay8551 Logic missing ideally it should not

[ ] Check on both coins and collectibles

[ ] Also created asset does not appears on home

https://github.com/user-attachments/assets/b61e7562-b10b-4071-9eee-53ac2b6d7ff6

@Deveshshankar ,
We check maximum value while user enter amount in input box. We're not allow to enter greater than max value. You can rethink about this issue if anything need to add/improve please let me know.
Thanks

Closing this for now if it will be reported by more people will close


Sync Java 17 changes with main

Purpose
Java 17 migration
Examples
Checklist

[ ] Linked to an issue
[ ] Updated the changelog
[ ] Added tests
[ ] Updated the spec
[ ] Checked native-image compatibility

Closing this since the same PR has been sent from the upstream branch.


Open terminal link in Incognito window

When cmd-click or ctrl-clicking a link from the terminal window, this opens in a standard window. A significant amount of times I need this to open an incognito window, for instance, when testing a password protected page. Example: I am editing a Shopify password page and it's quite painful as it logs me in instantly. A second link that allows incognito, with say option-click/alt-click, would be ideal.
The tooltip link doesn't allow you to copy - it disappears before you get a chance. Highlighting it and copying does not add it to the clipboard if you are quick enough. The text-based link goes over 2 lines in most cases, particularly when splitting terminals (see screenshot), so is broken up with || in the middle, forcing you to edit the link before you can use it.
I have seen this come and go in 2020 on issue #65136, but it's a big productivity issue for me right now. So I thought I should resurrect it.

This sort of thing would only be possible after https://github.com/microsoft/vscode/issues/216853 is done. So closing this out of scope but you might want to sub to that one.
In the meantime note you should be able to double click (or double click and drag) to quickly copy a link


[vite 3.0.0-alpha.5+] Cannot define with stringified object value

Describe the bug
Starting in alpha.5, it's no longer possible to have a config like:
export default defineConfig({
  define: {
    foo: JSON.stringify({ foo: true }),
  },
});

During build (but not dev), it will throw an error like:
Unexpected token (Note that you need plugins to import files that are not JavaScript)
file: /home/projects/vitejs-vite-bjukr5/node_modules/.vite/depsBuild/chunk-UC5OZ2ED.js?v=cf0d5223:11:13
 9: // <define:foo>
10: var init_define_foo = __esm({
11:   "<define:foo>"() {
                 ^
12:   }
13: });
error during build:
Error: Unexpected token (Note that you need plugins to import files that are not JavaScript)
    at error (file:///home/projects/vitejs-vite-bjukr5/node_modules/rollup/dist/es/shared/rollup.js:1888:30)
    at Module.error (file:///home/projects/vitejs-vite-bjukr5/node_modules/rollup/dist/es/shared/rollup.js:12452:16)
    at Module.tryParse (file:///home/projects/vitejs-vite-bjukr5/node_modules/rollup/dist/es/shared/rollup.js:12829:25)
    at Module.setSource (file:///home/projects/vitejs-vite-bjukr5/node_modules/rollup/dist/es/shared/rollup.js:12734:24)
    at ModuleLoader.addModuleSource (file:///home/projects/vitejs-vite-bjukr5/node_modules/rollup/dist/es/shared/rollup.js:22208:20)

This is currently what's breaking the storybook vite-builder in vite 3.
Reproduction
https://stackblitz.com/edit/vitejs-vite-bjukr5?file=package.json
System Info
n/a

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Seems to be caused by #8280 or #8281. I'm quite puzzled how this happens. When running npm run dev, you can see "<define:foo>"() { in one of the chunks in .vite/deps too


Error: UNKNOWN: unknown error, open '\..\games.txt'

Error: UNKNOWN: unknown error, open '\..\games.txt'
version<EMAIL_ADDRESS>nodejs: v10.
OS: Windows 10.15.3
Webpack config
{
  test: /node_modules[\/\\](iconv-lite)[\/\\].+/,
  resolve: {
    aliasFields: [ 'main' ]
  }
}

Gamedig is not usable in webpack / frontend applications. It's intended to be used only in a nodejs backend. Browsers cannot support sending the required udp packets for most query protocols.


Add --style arrows drawing style

Fix #3  Usage example: animate_bloch example x --style arrows

Agree, --style arrows sounds better than boolean --arrow-style. PTAL.

No problem. It is easy to update README. What kind of gif do you want to put in the Readme? Give me the command.
I think we can include the commands like Rx;0.5 there to illustrate it.

I found a bug while testing this.  I hope you don't mind that I fixed it and added the example.  Let me know what you think or if you want to make any other changes before I merge.

Thanks for fixing the bug. Just one minor comments in README, you have line
animate_bloch ~/Downloads/rx_gate_arrows --style arrows ry,0.666667 ry,0.666667 ry,0.666667.
Do you want to keep ~/Downloads/? Also, the name should be ry_gate_arrows instead of rx?

Good catch.  I need to review my own code.

Published in version 0.4.0.


Please support MSYS2 MINGW64

Do not have time to support such variety of compilers. If you managed to build it with MINGW, feel free to create a PR with build fixes


Add quill-cassandra dependency to build.sbt

Problem
When looking for instructions of how to set quill with Cassandra there is no instructions of how to set the project properly.
Solution
Modify CASSANDRA.cmd to  indicate the dependencies needed in build.sbt besides other requirements to make the examples run.
@getquill/maintainers

@vejeta Thanks for your contribution!
This document is actually just a comparison of cassandra libraries, this kind of instruction should be in README.md. What do you think about adding this link to CASSANDRA.md instead:
https://github.com/getquill/quill#cassandra-contexts

@fwbrasil: it sounds great. Let's close this PR.


Fix build validation when variant packages aren't in bootstrap

High Level Description
This prevents an exception from being raised when a treeinfo's bootstrap package list doesn't pull in a package listed in the treeinfo's package variants. A treeinfo with bootstrap_package_list is expected to produce a bootstrap tarball containing a subset of its complete set of packages, so it's not necessarily an error if a package variant isn't present within it.
Related Issues

DCOS-14070

Checklist for all PR's

[x] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

Here's proof that the test fails with the fix removed: https://teamcity.mesosphere.io/viewLog.html?buildId=575029&buildTypeId=DcosIo_Dcos_CodeQuality

@BenWhitehead @orsenthil Ready for review.


No tree view with id 'github:compareChanges' registered

I see this error often when I create a new PR:
workbench.desktop.main.js:sourcemap:747 Error: No tree view with id 'github:compareChanges' registered.
    at h.$getChildren (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:116:11884)
    at u.N (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:105:11239)
    at u.M (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:105:10957)
    at u.H (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:105:10044)
    at u.G (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:105:9179)
    at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:105:7810
    at m.invoke (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
    at b.deliver (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:63:2029)
    at d.fire (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:63:1667)
    at w.fire (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:72:14905)
    at /Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:121:15810
    at m.invoke (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
    at b.deliver (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:63:2029)
    at d.fire (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:63:1667)
    at w.fire (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:72:14905)
    at MessagePortMain.<anonymous> (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:121:13935)
    at MessagePortMain.emit (node:events:526:28)
    at Object.MessagePortMain._internalPort.emit (node:electron/js2c/utility_init:5:364)

Tried again to fix this here: https://github.com/microsoft/vscode/pull/170698


When I scroll to the last video on the list to load more videos it resets me to the start of the list

Basically, title.
When I'm looking for videos to watch and I get to the end of the list of currently loaded videos. It then resets me to the start of the list each time it tries to load more videos.  Will update when I have a solution.

This is still an issue.

am also having this issue on 1.5.2
a workaround is to watch the older videos on floatplane.com or ltt youtube channel

Is this resolved by now?

Apologies -- I still have eyes on this issue. With how busy I've been at work, I haven't had much motivation to touch anything aside from my Kindle to read at night as of late, but I should be around more once the holiday season is over. I'll tinker here and there in the meantime, but I can't promise much beyond that. 🤦♂