abhishekpankaj54

Results 7 comments of abhishekpankaj54

[BUG]BlobServiceClientBuilder’s buildClient method does not return or terminate the thread.

I found the below results with below scenario: > 1 When I use the below versions of dependencies we got the error com.azure azure-storage-blob-batch 12.26.0 com.azure azure-core-http-netty and i do...

[BUG][JAVA SDK]We have observed that the listAvailablePrivateIPAddresses method, which we use to list the available IPs of a subnet, does not work when the subnet has only AddressPrefixes instead of a AddressPrefix.

@weidongxu-microsoft , Could you please have a look at it urgently? If you want more info please let me know.

[BUG][JAVA SDK]We have observed that the listAvailablePrivateIPAddresses method, which we use to list the available IPs of a subnet, does not work when the subnet has only AddressPrefixes instead of a AddressPrefix.

@weidongxu-microsoft Did you check this?

[BUG][JAVA SDK]We have observed that the listAvailablePrivateIPAddresses method, which we use to list the available IPs of a subnet, does not work when the subnet has only AddressPrefixes instead of a AddressPrefix.

@XiaofeiCao , Please update us as soon as possible, as our application is being impacted by this.

[BUG][JAVA SDK]We have observed that the listAvailablePrivateIPAddresses method, which we use to list the available IPs of a subnet, does not work when the subnet has only AddressPrefixes instead of a AddressPrefix.

@XiaofeiCao , Did you get a chance to look into this?

[BUG][JAVA SDK]We have observed that the listAvailablePrivateIPAddresses method, which we use to list the available IPs of a subnet, does not work when the subnet has only AddressPrefixes instead of a AddressPrefix.

@XiaofeiCao , Thanks for the Update, please update me once it is released.

[BUG][JAVA SDK]We have observed that the listAvailablePrivateIPAddresses method, which we use to list the available IPs of a subnet, does not work when the subnet has only AddressPrefixes instead of a AddressPrefix.

@XiaofeiCao , Will you be releasing a new version of the Azure Java SDK to address this fix? The latest version is 2.43.0 , so I assume a new version...