Skip to content
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

Merged
merged 1 commit into from
Mar 16, 2024
Merged

Conversation

dlon
Copy link
Contributor

@dlon dlon commented Mar 12, 2024

Fix #2169. The server stops accepting connections if this fails due to an unrecoverable error. The list of "unrecoverable" errors might not be exhaustive.

@djc
Copy link
Collaborator

djc commented Mar 12, 2024

Did you remove all the TCP handling stuff? I think that would still be good to keep.

@dlon
Copy link
Contributor Author

dlon commented Mar 13, 2024

Did you remove all the TCP handling stuff? I think that would still be good to keep.

Done. I skipped quic and h3 since they don't seem to forward any meaningful error.

Copy link
Member

@bluejekyll bluejekyll left a 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!

@bluejekyll bluejekyll merged commit d2e64d8 into hickory-dns:main Mar 16, 2024
18 checks passed
@faern
Copy link
Contributor

faern commented Mar 22, 2024

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 🙏

@dlon dlon deleted the handle-shutdown-sockets branch March 22, 2024 18:59
@djc
Copy link
Collaborator

djc commented Apr 4, 2024

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.

@djc
Copy link
Collaborator

djc commented Apr 12, 2024

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 release/0.24 branch which the PR can target which I started from the v0.24.0 tag. Feel free to include any semver-compatible commits in your branch.

@djc djc mentioned this pull request Apr 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Handle sockets that have been shut down
4 participants