-
Notifications
You must be signed in to change notification settings - Fork 31
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 crashing with large updates #217
Comments
Thanks for reporting, Craig. When you say large updates, do you have a ballpark estimate of how large these updates are? (I can start by generating updates of that size to see if I can replicate it) |
So I got it to crash with roughly 10k keys updates, each key is a 36-lengthed string, and each value is a record holding 2 keys and 6 numbers as values. |
@paulgb I managed to get a simple repro for you : https://github.com/CraigFeldspar/ysweet-crash Steps :
I just added to the base color grid example this piece of code in
data.json is ~7Mb in size |
Thank you! Will take a look. |
Any updates? I have this issues too |
This is related to the websocket message size limit(1MiB) of Cloudflare durable object. |
Whenever using the test y-sweet endpoint, I often get the websocket to crash :
main.mjs:533 WebSocket connection to 'wss://y-sweet.net/p/....(url hidden)' failed: Close received after close
After that, no reconnection happens automatically, the page needs to be reloaded.
This happens usually with larger updates rather that short ones. Is there some message size limitation ? If yes, how can we gracefully handle these kind of errors in order to resend the updates more gradually ?
Also, if you need the full URL to analyze logs on your side, please let me know
The text was updated successfully, but these errors were encountered: