Track disconnects initiated by the client#2893
Merged
Merged
Conversation
Centril
approved these changes
Jun 25, 2025
Contributor
Centril
left a comment
Centril
left a comment
There was a problem hiding this comment.
Looks mostly good. Some minor tweaks and I think this will be good to merge.
joshua-spacetime
force-pushed
the
joshua/track-ws-close-frame
branch
from
a76b726 to
177e38e
Compare
joshua-spacetime
added a commit
that referenced
this pull request
Jul 1, 2025
joshua-spacetime
added a commit
that referenced
this pull request
Jul 1, 2025
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
2 participants
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 of Changes
When a client connection ends, we want to know who initiated the disconnect - the client or the server.
API and ABI breaking changes
None
Expected complexity level and risk
0
Testing