-
Notifications
You must be signed in to change notification settings - Fork 424
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
Handle shutdown sockets #2171
Handle shutdown sockets #2171
Conversation
b156b1c
to
1cb319e
Compare
Did you remove all the TCP handling stuff? I think that would still be good to keep. |
1cb319e
to
8d8c8d0
Compare
Done. I skipped quic and h3 since they don't seem to forward any meaningful error. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Thanks for the PR!
Would it be possible to have a patch release with this fix in it published? The socket closing cause us significant issues. For now we depend on the git repository, but we want to depend on a crates.io release if possible 🙏 |
Sorry for the slow respons -- @bluejekyll seems to be very busy right now -- not sure if he will be able to publish to crates.io (or give me access, maybe via a GitHub team)? If so we can probably make this happen. |
Hey @faern -- sorry for the delay in getting back to you. Apparently we should be able to release from the Actions workflow if I tag a release, so I can (try) to do it after all. Can you try a backport PR? I've pushed a |
Fix #2169. The server stops accepting connections if this fails due to an unrecoverable error. The list of "unrecoverable" errors might not be exhaustive.