Skip to content

fix/no conflicts on sync - #9149

Merged
max-nextcloud merged 4 commits into
mainfrom
fix/no-conflicts-on-sync
Sep 2, 2026
Merged

fix/no conflicts on sync#9149
max-nextcloud merged 4 commits into
mainfrom
fix/no-conflicts-on-sync

Conversation

@max-nextcloud

Copy link
Copy Markdown
Collaborator

fix(sync): do not check for conflicts during sync

The document may be in the middle of getting saved.

When the file has been updated
but the metadata in the documents table has not
it may seem like the file was overwritten
even though text is saving the file.

This does not indicate an actual conflict.
Avoid triggering the conflict screen in that race condition.

  • Revert "fix(sync): do not mistake own save requests for outside changes"
  • fix(sync): do not check for conflicts during sync

@max-nextcloud
max-nextcloud force-pushed the fix/no-conflicts-on-sync branch 7 times, most recently from 51750af to ee78ca4 Compare September 2, 2026 03:20
@max-nextcloud
max-nextcloud marked this pull request as ready for review September 2, 2026 03:35
@max-nextcloud
max-nextcloud requested review from a team and blizzz September 2, 2026 03:44
@max-nextcloud max-nextcloud mentioned this pull request Sep 2, 2026
30 tasks
This reverts commit a4eeb24.

Signed-off-by: Max <max@nextcloud.com>
The document may be in the middle of getting saved.

When the file has been updated
but the metadata in the documents table has not
it may seem like the file was overwritten
even though text is saving the file.

This does not indicate an actual conflict.
Avoid triggering the conflict screen in that race condition.

Signed-off-by: Max <max@nextcloud.com>
We observed save requests that took longer than 30 seconds.
The lock needs to outlive those in order to prevent superfluous 409 responses.

Signed-off-by: Max <max@nextcloud.com>
Abort autosave if another save is still under way.

We observed save requests taking up to 30 seconds.
In this timespan autosave requests would still be processed
as the lastSavedTime in the database has not been updated yet.

Signed-off-by: Max <max@nextcloud.com>
@max-nextcloud
max-nextcloud force-pushed the fix/no-conflicts-on-sync branch from ee78ca4 to d331c8f Compare September 2, 2026 04:05

@AndyScherzinger AndyScherzinger left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

馃悩

@max-nextcloud
max-nextcloud merged commit dc47155 into main Sep 2, 2026
69 checks passed
@max-nextcloud
max-nextcloud deleted the fix/no-conflicts-on-sync branch September 2, 2026 05:14
@max-nextcloud

Copy link
Copy Markdown
Collaborator Author

/backport to stable35

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants