mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 06:35:59 +03:00
[GH-ISSUE #803] Getting E12 for one-way sync. #508
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#508
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 @mmqmzk on GitHub (Jan 30, 2021).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/803
Describe the bug
Getting an E12 every three or four sync.
To Reproduce
Expected behavior
No errors.
Desktop:
Server:
Both have the issue.
I use the sync tabs feature, I put each my browser's tabs in separate XBEL files on a WebDAV server, then synchronize to separate folders in other browsers, there's only one writer for each XBEL file or folder, and I have chosen "Always revert upstream remote changes and push local changes" strategy, but the floccus account which uploads tabs frequent getting "E012: Folder ordering is missing some of the folder's children". So, I have to choose "Trigger sync from scratch", then the next sync shall be ok, of course.
Is it better to give an option overwrite local/remote rather than do a merge for one-way sync if users want to?
If I miss used this feature, please tell me.
@mmqmzk commented on GitHub (Feb 1, 2021):
This issue seems resolved by
932ef7f9d0.Thank you @marcelklehr !
@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.