-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Avoid calling update_cookies when there are no cookies #9470
Conversation
Calling update_cookies is ~4% of the client lifecycle time and we call it even with an empty dict of cookies
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## master #9470 +/- ##
=======================================
Coverage 98.59% 98.59%
=======================================
Files 105 105
Lines 35091 35092 +1
Branches 4178 4179 +1
=======================================
+ Hits 34597 34599 +2
Misses 329 329
+ Partials 165 164 -1
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 #9471 🤖 @patchback |
(cherry picked from commit 5bded30)
Backport to 3.11: 💚 backport PR created✅ Backport PR branch: Backported as #9472 🤖 @patchback |
(cherry picked from commit 5bded30)
…there are no cookies (#9471) Co-authored-by: J. Nick Koston <[email protected]>
…there are no cookies (#9472) Co-authored-by: J. Nick Koston <[email protected]>
What do these changes do?
Calling update_cookies is ~4% of the client lifecycle time and we call it even with an empty dict of cookies
Are there changes in behavior for the user?
no
Is it a substantial burden for the maintainers to support this?
no