-
-
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 test_utils.make_mocked_request
behaviour for empty payload
#7168
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #7168 +/- ##
=======================================
Coverage 98.28% 98.28%
=======================================
Files 107 107
Lines 34219 34221 +2
Branches 4057 4056 -1
=======================================
+ Hits 33631 33633 +2
Misses 415 415
Partials 173 173
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 #8969 🤖 @patchback |
(cherry picked from commit 8a525d9)
Backport to 3.11: 💚 backport PR created✅ Backport PR branch: Backported as #8970 🤖 @patchback |
(cherry picked from commit 8a525d9)
What do these changes do?
Fixes #7167
In case of empty payload when initialized, it now assigns the payload as
EMPTY_RESPONSE
instance ofEmptyStreamReader
available via aiohttp/streams.pyAre there changes in behavior for the user?
No
Related issue number
Checklist
CONTRIBUTORS.txt
CHANGES
folder<issue_id>.<type>
for example (588.bugfix)issue_id
change it to the pr id after creating the pr.feature
: Signifying a new feature..bugfix
: Signifying a bug fix..doc
: Signifying a documentation improvement..removal
: Signifying a deprecation or removal of public API..misc
: A ticket has been closed, but it is not of interest to users.