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

Documents out-of-sync if someone edited it on the desktop #2200

Closed
schiessle opened this issue Feb 24, 2022 · 2 comments
Closed

Documents out-of-sync if someone edited it on the desktop #2200

schiessle opened this issue Feb 24, 2022 · 2 comments
Labels
bug Something isn't working invalid

Comments

@schiessle
Copy link
Member

Tested on c.nc.com

I noticed this multiple times. I have a shread md file. Someone edits it on the desktop and sync it back. If i try to open the document later I get this:

grafik

with the option to either use the current version or use the saved version.

Also a hard refresh of the browser and re-open the document doesn't help. Maybe some server-side caching? I would expect that I always get the latest version from the storage. The only place where such a comparison makes sense to me is if you have a sync conflict because people edit the file at the same time in the browser and on the desktop. But that's probably also hard to detect...

@schiessle schiessle added the bug Something isn't working label Feb 24, 2022
@schiessle schiessle changed the title Documents out-of-sync if someone edited it in the desktop Documents out-of-sync if someone edited it on the desktop Feb 24, 2022
@luka-nextcloud
Copy link
Contributor

@schiessle I've shared the file and edited it anonymously. I can still access normally as the main user.
Please let me know if you are still able to reproduce the problem on the latest version.

@juliushaertl
Copy link
Member

This may still happen if the file is editing through the desktop but the editing sessions were not properly closed (and cleaned up yet by the background job) or some changes from the web have not been persisted.

Like got better since #2686 for unchanged files.

Other than that further improvements to avoid the conflict handling are tracked in #233

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working invalid
Projects
None yet
Development

No branches or pull requests

4 participants