mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-27 07:05:59 +03:00
[GH-ISSUE #423] Erorr012 after folder moving #323
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#323
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @piotr5151 on GitHub (Dec 24, 2019).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/423
After cleaning and moving some folders on my laptop I switched to my desktop PC and I've received Error012.
My laptop still syncs perfectly, but desktop doesn't.
I tried to investigate the conditions of the Error012 and I've found that floccus is comparing number of folder's children locally with server.
This is something I don't understand. After cleaning and moving folders of course I've change the numer and order of children. Does it means that removing folders aren't allowed ?
How can I fix it ? And how to avoid such problem in the future ?
@marcelklehr commented on GitHub (Dec 24, 2019):
Hello @piotr5151
Thanks for your feedback! I take it you are using the WebDAV backend?
The error you are seeing is more intricate than a mere mismatch of local vs. server folder length, it's a mismatch between the ordering matrix and the current state of the folder in the cache, which is actually a bug in the code. Would you be amendable to providing debug logs at the following share: https://klehranlage.net/index.php/s/7nn82NSBsfQKdsJ
@marcelklehr commented on GitHub (Mar 2, 2020):
This should be resolved in version 4.0.0, please shout if you feel it isn't :)
@github-actions[bot] commented on GitHub (Mar 21, 2023):
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.