mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 22:55:59 +03:00
[GH-ISSUE #267] Folder #xxx[xxx] contains an nonexistent bookmark xxx #254
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#254
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 @linux0uid on GitHub (Apr 17, 2019).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/267
Software versions
Expected outcome
I have try make sync from firefox and chromium. And even if first sync finished successfully after some time I had this error. On server side I did find the logging errors related to this issue. I have do sync from screech (removed flocuss from all browsers, remove all bookmarks on server) several times without success. I have run sync with both browsers together and with each of them alone. All the time sooner or later I have the same error.
Debug log
https://cloud.steli-horizon.com.ua/s/34jeHoQWMGidAXJ
@tkurbad commented on GitHub (Apr 25, 2019):
I'm seeing the same. Also, when trying to sync FF and Chromium concurrently.
@marcelklehr commented on GitHub (Apr 29, 2019):
This is an artifact of two sync runs happening at the same time from two different browsers. This leads to one client observing an inconsistent server state and stopping with the above message. This should no longer happen with sparse tree syncing as introduced by the upcoming v3.3.0 (see #269 )
@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.