clients: explicitly shutdown connection when killing client#777
Merged
clients: explicitly shutdown connection when killing client#777
Conversation
There was a problem hiding this comment.
Pull request overview
This PR ensures that when a client is terminated (e.g., via kill/shutdown paths that drop the client tasks), the underlying Wayland connection is explicitly shutdown() to forcefully unblock pending read/write operations and accelerate teardown.
Changes:
- Add a drop-guard in the receive task to
shutdown(fd, SHUT_RD)when the receive future is dropped. - Add a drop-guard in the send task to
shutdown(fd, SHUT_WR)when the send future is dropped.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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
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.
No description provided.