-
Notifications
You must be signed in to change notification settings - Fork 2
server: disconnect lightway in case of TCP shutdown or other fatal failures #183
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ilures. Note that it is possible, disconnect has been called in `conn.handle_outside_data_error` already in case of fatal error case. It is still fine to call it again, since `disconnect` call is idempotent and no-op if it is already disconnected But we need this disconnect in case of TCP connection shutdown. Otherwise Server::Connection will be leaking.
df129ea
to
db3d430
Compare
Code coverage summary for db3d430:
✅ Region coverage 54% passes |
xv-thomas-leong
approved these changes
Apr 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Disconnect lightway in case of TCP shutdown or other fatal failures.
Note that it is possible, disconnect has been called in
conn.handle_outside_data_error
already in case of fatal error case. It is still fine to call it again, sincedisconnect
call is idempotent and no-op if it is already disconnectedBut we need this disconnect in case of TCP connection shutdown. Otherwise Server::Connection will be leaking.
Motivation and Context
TCP connections are not getting closed in some servers
How Has This Been Tested?
Verified in running prod server
Types of changes
Checklist:
main