-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix status not being set when ClientResponse.json raises ContentTypeError #8742
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #8742 +/- ##
=======================================
Coverage 98.14% 98.14%
=======================================
Files 107 107
Lines 34062 34064 +2
Branches 4029 4029
=======================================
+ Hits 33430 33432 +2
Misses 456 456
Partials 176 176
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Backport to 3.10: 💚 backport PR created✅ Backport PR branch: Backported as #8745 🤖 @patchback |
Backport to 3.11: 💚 backport PR created✅ Backport PR branch: Backported as #8746 🤖 @patchback |
What do these changes do?
Fix status not being set when ClientResponse.json raises ContentTypeError
Are there changes in behavior for the user?
The status will be set
Is it a substantial burden for the maintainers to support this?
no
Related issue number
fixes #8741