Alert message shown regularly while websocket attempts to reconnect about y-websocket

[tommoor]

This message seems to be guarded by resyncInterval being enabled so I'm just disabling that option for now – it seems like the interval just needs to be cleared on socket close?

[dmonad]

I was working with someone who reported (and showed logs) that the first sync message went missing. This would mean that in some browsers the first message on the websocket protocol can get lost which is very disturbing.

The issue seems to happen when a client connects through a VPN to a different region. It was only happening to a non-developer and I wanted to confirm what is happening.

I haven't head back from that user. So I will remove the message.

resyncInterval should fix the issue anyway. I'm not sure what else I can do.

[tommoor]

Any truth in my observation that rsyncinterval should be cleared when the connection is closed?

[dmonad]

When the connection is closed then then ws object should be set to null (

y-websocket/src/y-websocket.js

Line 94 in 5a36d77

websocket.onclose = () => {

).

Then resyncInterval shouldn't do anything anymore.. (

y-websocket/src/y-websocket.js

Line 222 in 5a36d77

if (this.ws) {

)

So how do you have a closed connection and still have the resyncInterval send messages?

Do you overwrite the onclose property? Or is there an edge case I'm not aware of?

[tommoor]

Not overwriting anything. It was happening during the retry connection loop once the server is killed, so there might be an edge-case – If I pin it down I'll file another ticket/PR.

[dmonad]

That would be great, thanks!