Uh oh!
There was an error while loading. Please reload this page.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Am I correct saying this would also reproduce for a regular
client.request()? If so, should we update this to…?(Also dropped the explicit
response.aclose()since the expected behavior is that exiting thestream()async context manager would do that for us, and fail with the proper exception.)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are correct. And the
await client.request()test is a worthy addition.You're the maintainer, so you are welcome to change to nix the
aclose()in the test ... but first, I'll explain my motivation.During debugging, I was surprised by #1464 -- a broken stream raises the "wrong" error on shutdown.
I imagine a reasonable
__aexit__()might handle an errno=104 error -- by doing nothing and raising nothing. So I aimed for an explicit test that avoids__aexit__().The change would be correct. But as a user, I find
__axit__()behavior confusing; so I wrote a more-explicit test.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, I like the way @adamhooper has approached the test case here, too.