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

[stable-3.1] Ensure a sync happens after a conflict resolution #2717

Merged
merged 1 commit into from
Dec 15, 2020

Conversation

backportbot-nextcloud[bot]
Copy link

backport of #2714

@camilasan
Copy link
Member

/rebase

You'd expect that after a conflict resolution the file watcher would
pick up the change and trigger a sync. For some reason it doesn't seem
to happen on at least some Ubuntu systems. In such cases the user would
then still have a stale conflict entry in the activity list and wouldn't
be able to do anything with it.

Signed-off-by: Kevin Ottens <[email protected]>
@github-actions github-actions bot force-pushed the backport/2714/stable-3.1 branch from 3e511a1 to 9774b6a Compare December 15, 2020 10:04
@nextcloud-desktop-bot
Copy link

AppImage file: Nextcloud-PR-2717-9774b6a429112545ad4bca04ae5788d21af225ce-x86_64.AppImage

To test this change/fix you can simply download above AppImage file and test it.

Please make sure to quit your existing Nextcloud app and backup your data.

@camilasan camilasan merged commit b391d88 into stable-3.1 Dec 15, 2020
@camilasan camilasan deleted the backport/2714/stable-3.1 branch December 15, 2020 10:18
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