-
Notifications
You must be signed in to change notification settings - Fork 807
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
Bugfix/fix vfs folder state when remote move is forbidden #6717
Bugfix/fix vfs folder state when remote move is forbidden #6717
Conversation
d1aef86
to
7275b8a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like there are some unrelated changes from #6718
7275b8a
to
b058995
Compare
c9d76f7
to
9202dfd
Compare
Quality Gate failedFailed conditions See analysis details on SonarCloud Catch issues before they fail your Quality Gate with our IDE extension SonarLint |
9202dfd
to
91307ce
Compare
91307ce
to
3b8d021
Compare
3b8d021
to
80bf451
Compare
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]>
80bf451
to
7a6691f
Compare
AppImage file: nextcloud-PR-6717-7a6691f6e04a62fdbd0b9573ca5a2f59af7e8633-x86_64.AppImage |
Quality Gate failedFailed conditions See analysis details on SonarCloud Catch issues before they fail your Quality Gate with our IDE extension SonarLint |
/backport to stable-3.14 |
/backport to stable-3.13 |
/backport to stable-3.12 |
The backport to # Switch to the target branch and update it
git checkout stable-3.12
git pull origin stable-3.12
# Create the new backport branch
git checkout -b backport/6717/stable-3.12
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick da920f6d 7a6691f6
# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/6717/stable-3.12 Error: Failed to push branch backport/6717/stable-3.12: fatal: could not read Username for 'https://github.com': No such device or address Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
No description provided.