-
Notifications
You must be signed in to change notification settings - Fork 668
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
Quick change in folder hierarchy causes sync errors #6694
Comments
Moving the folders back into their original hierarchy, resolves the error state: |
@ogoffart Should there be a ticket to track the larger underlying problem? |
Linux Mint tara; testpilotcloud-client-2.5.0daily20181016@ckamm is your fix merged in the 2.5 branch already? BAD Debug window says
|
Linux build done from unmerged branch filerename-to-virtual-6718 (build 10079) does not show the issue! |
@jnweiger it was merged at 11:00 yesterday But as the discussion on the PR states, this is only a partial fix. More complicated changes such as this one: You have folders Other complicated scenario that involve 3 level directory where each of them is moved will also not work. Edit: Changed milestone to 2.6 as this is a too complex problem to be fixed in 2.5 and is not a regression. |
The discovery in 2.6 should fix the problem. The step to reproduce are in the description. |
Works as expected in 2.6.0alpha2 (build 12128), macOS 10.14.5 |
Revert the hierarchy of two enabled folders quickly
mv Documents/Empty . ; mv Documents Empty
BAD:
Error message in client log
6 Aug 2018 15:22:36, Documents/Empty, testpilotcloud2,Error transferring https://demo.owncloud.org/remote.php/dav/files/demo/Empty/Documents/Empty - server replied:
Error message in server log
Almost good:
Do the same slowly
mv Documents/Empty . ; sleep 10; mv Documents Empty # sufficient sleep so that a sync run completes.
Syncs without errors, but the new toplevel folder called "Empty" is reported with (0B), which is no longer correct, as the Empty/Documents folder contains ca. 35Kb
The text was updated successfully, but these errors were encountered: