Catch utf8 decoding errors explicitly to fix py310 test failure #2
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.
The failing test in graphql-python#574 is
test_http_multipart_invalid_utf8.utf8 decoding errors bubbled up into a
JSONDecodeError, which triggered a bug under py310 specifically:\xff\xfe) in the multipart responsepart.text()raises aUnicodeDecodeErrorUnicodeDecodeError, onlyJSONDecodeErrorUnicodeDecodeError, the exceptiongroup package in py310 hit an internal bug:Catching the utf8 decoding error specifically does actually improve error handling anyway since it gives a more specific warning to the user imo.