-
Notifications
You must be signed in to change notification settings - Fork 811
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/use file id to track renamed items #7334
Conversation
/backport to stable-3.12 |
/backport to stable-3.13 |
/backport to stable-3.14 |
6cf55b0
to
2cf7a0c
Compare
why one would not update the modification time when modifying a remote file during automated tests there is no reason to not update the modification time as this is what is done by the server Signed-off-by: Matthieu Gallien <[email protected]>
NEW/NEW conflicts could sometime be ignored and replaced by update metadata instructions we stop doing this and handle them like any other conflicts that would cause more download from the server those conflicts would be solved automatically in case this is not a real conflict but the client was missing the server reply with the updated metadata will enable more changes to improve MOVE detection from server side Signed-off-by: Matthieu Gallien <[email protected]>
orignally added by owncloud/client#6632 most probably a too strong assumption on the behavior of the Nextcloud server better check real item metadata like fileid, size or modification time Signed-off-by: Matthieu Gallien <[email protected]>
2cf7a0c
to
05b6db5
Compare
AppImage file: nextcloud-PR-7334-05b6db55c3da60366a05e00a7486309cdcdfc95e-x86_64.AppImage |
Quality Gate passedIssues Measures |
No description provided.