Repository navigation
test(web): cover untagged and post-drop relay messages in the binding transport (#231) - #233
Merged
Merged
Conversation
V3RON
marked this pull request as ready for review
October 14, 2026 09:44
V3RON
changed the title
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.
Follow-up to #257, which fixed #231.
What changed
#257 and this PR's first commits fixed the same stale-relay-message bug in parallel, so the fix itself is already on main. This PR now only adds what #257 left out:
idreaches the active socket formessageas well asopen.attachPageclosing the page's socket.No behaviour change.
Checklist
CHANGELOG.md: not user-visible, tests and a comment onlyindex.ts; no new directnode:*I/O outside an adapter