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.14] Bugfix/fix vfs folder state when remote move is forbidden #7131

Merged
merged 2 commits into from
Sep 16, 2024

Conversation

backportbot[bot]
Copy link

@backportbot backportbot bot commented Sep 16, 2024

Backport of PR #6717

when remote move is forbidden, desktop client will move back the folder
to its original name

in such cases, we were forgetting to set VFS metadata in their proper
state (i.e. placeholder in sync)

so ensure that when a remote move fails, we still touch VFS metadata
when appropriate and handle errors

Signed-off-by: Matthieu Gallien <[email protected]>
when doing local discovery, it is possible that files or folders may be
discovered with VFS metadata not up to date (i.e. placeholder file not
set in sync)

in such case, generate a propagation instruction to set them in sync

Signed-off-by: Matthieu Gallien <[email protected]>
@backportbot backportbot bot added this to the 3.14.1 milestone Sep 16, 2024
@nextcloud-desktop-bot
Copy link

AppImage file: nextcloud-PR-7131-8131a00265bedd1fe9f5e74000df4ecbd653eb22-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.

Copy link

sonarcloud bot commented Sep 16, 2024

@mgallien mgallien merged commit e1285f3 into stable-3.14 Sep 16, 2024
11 of 15 checks passed
@mgallien mgallien deleted the backport/6717/stable-3.14 branch September 16, 2024 17:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants