mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 06:35:59 +03:00
[GH-ISSUE #239] Folder #xxx[xxx] contains an nonexistent bookmark xxx #230
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#230
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 @CharlesCage on GitHub (Mar 15, 2019).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/239
Software versions
Steps to reproduce
Expected outcome
Sync success
Actual outcome
Receiving a variety of similar errors following the format described in issue header, ex: "Folder #281[Bikspo] contains an nonexistent bookmark 564."
When I review the debug log and find the specific bookmark causing the error, I find that it's listed once in the debug log but appears twice in the Nextcloud Bookmarks section. Removing one of these (or sometimes two) will allow floccus to complete the sync -- or sometimes find another similar error, in which case resolving all as described allows a complete sync. However, the issue appears again on its own over the course of 24-48 hours.
Debug log
@CharlesCage commented on GitHub (Mar 15, 2019):
floccus-3.2.8-2019-03-15.log
Apologies -- please find attached debug log.
@tomershvueli commented on GitHub (Mar 16, 2019):
I'm seeing this same issue as well. I'm on Vivaldi 2.3.1440.60 (Stable channel) (64-bit). Floccus version 3.2.8.
@marcelklehr commented on GitHub (Mar 16, 2019):
@CharlesCage mmh. The log you provided doesn't cover the incident, I'm afraid. Could download the log again, immediately after seeing the error?
@CharlesCage commented on GitHub (Mar 18, 2019):
Sure thing, and sorry for the delay.
Current specific error:
Folder #441[Video] contains an nonexistent bookmark 376
floccus-3.2.8-2019-03-18.log
Also, some additional information regarding my troubleshooting: I was able to make the issue go away by backing up bookmarks from one source, deleting all bookmarks, syncing deletions across all browsers, re-importing the bookmarks, and re-syncing across all browsers. However, the problem soon returned.
I think this is clearly related to sync. I wonder if it might have something to do with handling of lost connections during sync?
Thanks again for your work.
@marcelklehr commented on GitHub (Mar 19, 2019):
Mh. the log still doesn't contain the error :/ From what I could gather, the problem might have occured only recently, is that correct?
@marcelklehr commented on GitHub (Mar 19, 2019):
I've released a patch release that should take care of the duplicates (finally). Let's see if it takes care of the error as well.
@CharlesCage commented on GitHub (Mar 21, 2019):
Ok! To give it a clean slate I removed Floccus from all browsers. Exported bookmarks from Chrome instance. Deleted all bookmarks from Chrome instance. Deleted all bookmark data from Nextcloud. Updated Nextcloud Bookmarks app to 0.16.3. Installed 3.2.9 version of Floccus on Chrome instance and sync'd zero bookmarks (all good). Imported bookmarks to Chrome. Sync'd bookmarks to Nextcloud (long time, but all good). Deleted all bookmarks from Firefox instance. Installed Floccus 3.2.9 on Firefox instance, connected to Nextcloud, and sync'd (all good).
Setting an alarm to report back in a day or two with results.
Thanks again for your time and effort.
@CharlesCage commented on GitHub (Mar 22, 2019):
Follow-up: I believe we can close this. I haven't had any issues so far, and because it seemed sync-related I've purposely tried interrupting sync with closing browsers, hibernating and suspending systems, etc. Seems solid.
If anything comes up, I'll file a new issue.
Hey, really want to thank you for the patch--and Floccus in general.
@marcelklehr commented on GitHub (Mar 22, 2019):
Thank you for the feedback! :)
@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.