-
Notifications
You must be signed in to change notification settings - Fork 91
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
Reconnect handling #4943
Labels
Comments
8 tasks
#5082 was an attempt but unclear how it could have an effect, needs further debugging.
|
Idea:
|
This was referenced Dec 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I noticed when testing #4938 that there seems to be a case when a connection is offline long enough that the reconnect is not working as expected.
When trying to address the issue there by dropping the disconnected websocket provider with the following patch I noticed that after reconnecting the offline client would no longer send changes while still picking up the ones from the other clients.
The text was updated successfully, but these errors were encountered: