Conversation
|
🔥 Run benchmarks comparing feb0d4a against gh workflow run bench.yaml -f pr_number=63Note: this comment will update with each new commit. |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #63 +/- ##
==========================================
+ Coverage 92.87% 96.68% +3.81%
==========================================
Files 2 2
Lines 491 573 +82
==========================================
+ Hits 456 554 +98
+ Misses 28 14 -14
+ Partials 7 5 -2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
benchstats: 13f5e8b...77719b1View full benchmark output on the workflow summary. |
mccutchen
added a commit
that referenced
this pull request
Oct 5, 2025
Slightly more thorough tests to complement #63.
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.
This somewhat messy change adds support for properly closing websocket connections via the closing handshake, where the peer that initiates a close waits for a reply before actually closing the TCP connection.
This fixes #47, which notes a mystery:
I now think that's because most/all of the closing scenarios tested by autobahn are for edge cases where it's appropriate for the server to immediately close the connection without waiting for a reply. As noted in a comment below, see section 7.1.7 of the RFC and search for "Fail the" in the RFC to see all the scenarios where immediately closing the connection is the correct/recommended/required behavior.
AFAICT the "full" closing handshake is mostly going to be useful if/when application code wants to signal errors.