Skip to content

Conversation

@backportbot-nextcloud
Copy link

Backport of #5126

During a network disconnect
Yjs-websocket notices missing awareness messages and closes the connection.
In this case the remaining steps can also not be send out and the request fails.
Preserve the queue so we can use it once the network is back up.

Signed-off-by: Max <[email protected]>
When yjs does not receive awareness updates
it will close and reopen the websocket.
Keep the content of the queue, i.e. the outgoing steps
so they can be send out once the connection is back.

Signed-off-by: Max <[email protected]>
Change the content of `queue` with `queue.splice`
rather than setting `queue` to another array.

Signed-off-by: Max <[email protected]>
Also add a unit test for the websocket polyfill

Signed-off-by: Max <[email protected]>
avoids the old provider leaking error events.

Signed-off-by: Max <[email protected]>
@backportbot-nextcloud backportbot-nextcloud bot added the bug Something isn't working label Dec 18, 2023
@backportbot-nextcloud backportbot-nextcloud bot added this to the Nextcloud 28.0.1 milestone Dec 18, 2023
This was referenced Dec 21, 2023
@juliusknorr juliusknorr merged commit db52a6d into stable28 Dec 21, 2023
@juliusknorr juliusknorr deleted the backport/5126/stable28 branch December 21, 2023 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

4. to release bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants