Closed roy-work closed 1 month ago
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @jalauzon-msft @vincenttran-msft.
Hi @roy-work Roy, thanks for the report. Yes, you are correct that this is almost certainly caused by an invalid shared key, specifically one that cannot be properly base64 decoded. The long timeout is due to the automatic retry policy of the SDK retrying this error a few times. The fact that this type of error is retried is not correct and #36431 has been created to fix that issue.
We will also consider catching this error and adjusting the error message to hint at the fact this is probably an issue with the shared key.
azure-storage-blob
Describe the bug A call to
BlobClient.exists
fails after a huge delay with:To Reproduce Steps to reproduce the behavior:
"a"
.Expected behavior The error here needs to help me understand what's wrong; base64 padding has "nothing" to do with the API call here, and I had no idea at first what I'd done wrong, as I thought I had supplied a valid key.
The long timeout is equally weird; this should abort immediately … no?
The signature generation scheme here is to a user of the API an internal detail. I'm "lucky" in the sense that I've implemented it by hand before & know how it works (and that's what nudged me towards "maybe the key I supplied wasn't right?"), but a user who isn't familiar with how the signature scheme on the underlying API requests work is going to just be perplexed by this.
Screenshots N/A
Additional context I suspect this was previously reported here: https://github.com/Azure/azure-sdk-for-python/issues/35010