Repository navigation
fix(core): read product sockets with the Bun.connect WebSocket client - #667
Merged
Merged
Conversation
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 57 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
klNuno
marked this pull request as ready for review
October 19, 2026 20:31
…heck upgrade answers and close codes
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.
Note
Clanker Claude Opus 5.5 is responding on behalf of meetsu
The agent browser on Windows, the
boitecommands and the group relay stop losing their connection when Bun's WebSocket client drops a frame.what changed
Bun.connectclient from test(e2e): speak CDP without Bun's WebSocket client and explain a shell page left blank #650 moves into the core, shared with the E2E harness, and gains headers,wss://, close reasons and permessage-deflate (packages/core/src/ws-client.ts)reportErrorand reading goes on; a closed socket drops its send queue (bufferedAmountshows it)UpgradeandConnectionor with an unoffered subprotocol, ends a forbidden close code with 1002 and text that is not UTF-8 with 1007client.tsagain clears the waiter and timer of a call whose params do not serializebrowser/cdp.ts,client.ts,group/relay.ts)new WebSocket((product-sockets.test.ts)projects.ts, failed Core Linux arm64 on this PR)to question
No test makes Bun's client fail: replays of #613's dumps and byte-cut sweeps passed on Bun 1.4.3. The evidence is the #650 and #662 loops and the 1011 closes of the core client on macOS arm64 (jobs 117880160622, 117938889719).
The #658 macOS hang does not use this client: macOS and Linux read DevTools over
--remote-debugging-pipe.verified
product-sockets.test.ts: the guard fails on main's sockets, 3 pass hereprojects-git.test.tscase fails on main'sprojects.tsand on a fix that only waits for the pending check, passes herews-client.test.ts, 2 inclient-timeout.test.ts) and pass herebun run checkpasses; Windows core suite 2704 pass,audio-sessions.test.tsflaky on main toobrowser.command: 4 sockets, 71 messages through the new clientBundle size
Core JavaScript grows about 10.7 KB:
ws-client.tsnow ships in the core.