-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Revert: Close the socket if there's a failure in start_connection() #10464 #10656
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
Conversation
…10464 fixes #10617 alternative fix is MagicStack/uvloop#646
CodSpeed Performance ReportMerging #10656 will not alter performanceComparing Summary
|
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 #10656 +/- ##
==========================================
- Coverage 98.71% 98.71% -0.01%
==========================================
Files 125 125
Lines 37462 37439 -23
Branches 2076 2076
==========================================
- Hits 36980 36957 -23
Misses 335 335
Partials 147 147
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.11: 💚 backport PR created✅ Backport PR branch: Backported as #10657 🤖 @patchback |
…10464 (#10656) Reverts #10464 While this change improved the situation for uvloop users, it caused a regression with `SelectorEventLoop` (issue #10617) The alternative fix is MagicStack/uvloop#646 (not merged at the time of this PR) issue #10617 appears to be very similar to python/cpython@d5aeccf If someone can come up with a working reproducer for #10617 we can revisit this. cc @top-oai Minimal implementation that shows on cancellation the socket is cleaned up without the explicit `close` #10617 (comment) so this should be unneeded unless I've missed something (very possible with all the moving parts here) ## Related issue number fixes #10617 (cherry picked from commit 06db052)
Backport to 3.12: 💚 backport PR created✅ Backport PR branch: Backported as #10658 🤖 @patchback |
…10464 (#10656) Reverts #10464 While this change improved the situation for uvloop users, it caused a regression with `SelectorEventLoop` (issue #10617) The alternative fix is MagicStack/uvloop#646 (not merged at the time of this PR) issue #10617 appears to be very similar to python/cpython@d5aeccf If someone can come up with a working reproducer for #10617 we can revisit this. cc @top-oai Minimal implementation that shows on cancellation the socket is cleaned up without the explicit `close` #10617 (comment) so this should be unneeded unless I've missed something (very possible with all the moving parts here) ## Related issue number fixes #10617 (cherry picked from commit 06db052)
…'s a failure in start_connection() #10464 (#10657) **This is a backport of PR #10656 as merged into master (06db052).** Reverts #10464 While this change improved the situation for uvloop users, it caused a regression with `SelectorEventLoop` (issue #10617) The alternative fix is MagicStack/uvloop#646 (not merged at the time of this PR) issue #10617 appears to be very similar to python/cpython@d5aeccf If someone can come up with a working reproducer for #10617 we can revisit this. cc @top-oai Minimal implementation that shows on cancellation the socket is cleaned up without the explicit `close` #10617 (comment) so this should be unneeded unless I've missed something (very possible with all the moving parts here) ## Related issue number fixes #10617 Co-authored-by: J. Nick Koston <[email protected]>
Reverts #10464
While this change improved the situation for uvloop users, it caused a regression with
SelectorEventLoop
(issue #10617)The alternative fix is MagicStack/uvloop#646 (not merged at the time of this PR)
issue #10617 appears to be very similar to python/cpython@d5aeccf
If someone can come up with a working reproducer for #10617 we can revisit this.
cc @top-oai
Minimal implementation that shows on cancellation the socket is cleaned up without the explicit
close
#10617 (comment) so this should be unneeded unless I've missed something (very possible with all the moving parts here)Related issue number
fixes #10617