-
### What task needs to be completed?
14.x changed the async implementation and has a different API.
In the transition period, we can either use the new implementation on 13.x (not sure how to en…
-
> Not sure either about that reconnecting-websocket.
Thanks for weighing in @jonespm! I think dealing with this is somewhat important, since WebSocket connections seem to be one of the areas where …
-
It would be really cool for the extension to also support websockets. If it is out of scope then it may serve as an idea for new extension ;-).
zdila updated
2 weeks ago
-
So far the architecture consists of basic client-server approach, where the client initiates protocol switch to websocket, thus creating new communication channel. Single game contains up to 4 persist…
-
We know that our async infrastructure is not the best. It has multiple processes and has some potential bugs, so I decided to spend some time to rewrite WebSocket client on Rust.
I should help to fix…
-
Full disclosure upfront: I'm pretty sure the root cause of this is a bug in Bun itself, which I've already filed [here](https://github.com/oven-sh/bun/issues/15247). However, I don't know how long tha…
-
## Bug Report
A WebSocket client instantiated in the Edge runtime will randomly drop incoming messages from the WedSocket server. In my test every 10th or so incoming message is dropped, but it pro…
-
from binance.websocket.spot.websocket_stream import SpotWebsocketStreamClient
def on_message(_, _message):
print(_message)
my_client = SpotWebsocketStreamClient(on_message=on_message)
my_c…
-
Ideally, the websocket could be closed both explicitly, with a `client.close()` method, and implicitly when the client goes out of scope.
The current implementation causes an issue in jest integrati…
-
Hi Andy,
as shown in the image, the websocket client have not close the websocket conenction, but my web…