[Storage] Fix ranged download for client-side encryption #25522
Merged
+829
−22
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jalauzon-msft
requested review from
annatisch and
vincenttran-msft
as code owners
ghost
added
the
vincenttran-msft
approved these changes
Aug 3, 2022
|
API change check APIView has identified API level changes in this PR and created following API reviews. |
|
/azp run python - storage - ci |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Running just blob Live tests here: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1756885&view=results |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change addresses a couple of issues with a ranged blob download (specifying
offsetandlength) with client-side encryption enabled that can occur in rare circumstances. There is one fix for V1 and a separate fix for V2.