Skip to content
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

[stable28] fix(sync): reuse open connection #6059

Merged
merged 1 commit into from
Jul 24, 2024
Merged

Conversation

backportbot[bot]
Copy link

@backportbot backportbot bot commented Jul 18, 2024

@backportbot backportbot bot added bug Something isn't working 3. to review labels Jul 18, 2024
@backportbot backportbot bot added this to the Nextcloud 28.0.8 milestone Jul 18, 2024
Copy link
Member

@juliusknorr juliusknorr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Needs manual check for conflicts

Do not attempt to create a new connection
if there already is one and it is not closed.

If no messages are received for 30 seconds
yjs will open a new websocket.

Since we do not close the connection anymore from the websocket polyfill
we also do not need to open it.

If the network connection has gone down
creating a new connection will fail anyway.

Once it comes back we will know if the session is still valid.
Then we can either continue using it or reconnect.

This is part of #6050.

Signed-off-by: Max <max@nextcloud.com>
@mejo- mejo- marked this pull request as ready for review July 24, 2024 15:42
@mejo- mejo- merged commit 8315a63 into stable28 Jul 24, 2024
60 checks passed
@mejo- mejo- deleted the backport/6054/stable28 branch July 24, 2024 16:33
@Altahrim Altahrim mentioned this pull request Aug 8, 2024
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review bug Something isn't working
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

4 participants