New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebSocket
client reliability
#6686
Comments
Unsure, but is this also related? |
Is this something that is planned to be fixed in the near future? |
This makes it impossible for me to adopt bun at the moment. An approximate ETA would be very appreciated. |
Yeh its definitely a unexpected partial blocker for us, but there is https://github.com/Vexcited/tcp-websocket that might be worth exploring as a work around |
You can test these fixes right now if you run |
You guys rock! Looking forward to try this! |
I can confirm the wevm/viem#1342 and #6189 are no longer an issue with the latest version. Great job guys! |
still an issue for me when using ethers v6 and bun v1.0.29 I just subscribed to Mempool like this:
|
It's possible this could be another bug, could you open another issue? |
There are various issues with Bun's
WebSocket
client that have to do with parsing frames properly. We need to add the Autobahn to our tests and start fixing the bugs inwebsocket_http_client.zig
.Note: this is not to be confused with Bun's
WebSocket
server, which is implemented by uWebSockets which uses the Autobahn test suite.The text was updated successfully, but these errors were encountered: