-
Notifications
You must be signed in to change notification settings - Fork 310
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 port selection #1229
Fix port selection #1229
Conversation
@kevin-bates should we do something similar in |
The tornado util function appears to be more robust. |
…ver into fix-port-selection
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #1229 +/- ##
==========================================
+ Coverage 79.08% 79.12% +0.03%
==========================================
Files 68 68
Lines 8253 8252 -1
Branches 1603 1599 -4
==========================================
+ Hits 6527 6529 +2
+ Misses 1301 1299 -2
+ Partials 425 424 -1
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
I think this makes sense. Are we confident the |
Yeah, I don't think we need LINGER because we aren't actually sending any messages on this socket. We could always inline the method with attribution if we ever decide to move off of |
Actually, I don't think we need this logic in client, since we're asking the OS to give us a port, not attempting to use a specific one. |
Fixes #1170, by using the same
bind_sockets
function as is later used to start the http server.