Open juliusknorr opened 1 year ago
Actually seems like after the reconnect the step is not pushed at all so we have a diverging state between both clients
Failing step:
First successful push after reconnect:
https://github.com/nextcloud/text/pull/5082 was an attempt but unclear how it could have an effect, needs further debugging.
Idea:
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.