[Storage] Revert removing aiohttp dependency for storage.blob.aio#25084
Merged
vincenttran-msft merged 2 commits intoAzure:mainfrom Jul 6, 2022
Merged
[Storage] Revert removing aiohttp dependency for storage.blob.aio#25084vincenttran-msft merged 2 commits intoAzure:mainfrom
vincenttran-msft merged 2 commits intoAzure:mainfrom
Conversation
Collaborator
|
API change check API changes are not detected in this pull request. |
lmazuel
approved these changes
Jul 6, 2022
Contributor
|
@vincenttran-msft @jalauzon-msft No worries! This isn't something that is very blocking, so I might not look into if for a couple weeks. |
This file contains hidden or 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
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.
Reverting the changes made in #24965 (sorry @Stevenjin8) as adequate discussion and investigation has not been done on this change before the upcoming GA release.
In the future, if/when this work gets put back in, simply revert this PR (and probably play with the changelog merge conflicts that will arise)