starred/floccus

Fork 0

mirror of https://github.com/floccusaddon/floccus.git synced 2026-04-25 14:16:12 +03:00

[GH-ISSUE #598] Trying to remove a non-existing item from OrderTracker - moving subfolders around #416

New issue

Closed

opened 2026-02-25 22:37:04 +03:00 by kerem · 4 comments

kerem commented

2026-02-25 22:37:04 +03:00

Owner

Originally created by @maurerle on GitHub (Jul 10, 2020).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/598

Describe the bug
Sync failes. I have a folder which has another Folder in it and after I moved some links into a new top level folder and moved the new top level folder (Blogs) into another folder I get the error message

Trying to remove a non-existing item from OrderTracker: bookmark:372;37 Trying to insert an already existing item into OrderTracker: bookmark:Cf-GTOvBQ6Rj Trying to insert an already existing item into OrderTracker: bookmark:uj7YJd4aKTde Trying to insert an already existing item into OrderTracker: bookmark:K1k5b_DDZQlj

I already tried exporting the data from the bookmarks app and mak a fresh sync, which worked yesterday but today I get the error again.

It worked fine for a long time, so thank you!
Will try to investigate further but maybe you know more about this problem

Desktop (please complete the following information):

OS: Windows
Browser Firefox
Browser Version 78.0.2
Floccus version: 4.2.5
Floccus sync method: nextcloud folders

Server (please complete the following information):

OS: debian10
Nextcloud version: 18.0.6
Bookmarks app version: 3.2.4

Debug log
It is often useful to provide a debug log file along with the issue. You can obtain a debug log of the most recent sync runs by clicking 'Debug log' in the bottom right corner of the floccus panel in your browser.

Note: As your debug log usually contains large parts of your bookmark data, instead of attaching it publicly to the issue here, I recommend uploading it privately at the following URL https://klehranlage.net/index.php/s/7nn82NSBsfQKdsJ

[x ] Debug log provided
floccus-4.2.5-2020-07-10-maurerle

Additional context
Add any other context about the problem here.

Originally created by @maurerle on GitHub (Jul 10, 2020). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/598 **Describe the bug** Sync failes. I have a folder which has another Folder in it and after I moved some links into a new top level folder and moved the new top level folder (Blogs) into another folder I get the error message `Trying to remove a non-existing item from OrderTracker: bookmark:372;37 Trying to insert an already existing item into OrderTracker: bookmark:Cf-GTOvBQ6Rj Trying to insert an already existing item into OrderTracker: bookmark:uj7YJd4aKTde Trying to insert an already existing item into OrderTracker: bookmark:K1k5b_DDZQlj` I already tried exporting the data from the bookmarks app and mak a fresh sync, which worked yesterday but today I get the error again. It worked fine for a long time, so thank you! Will try to investigate further but maybe you know more about this problem **Desktop (please complete the following information):** - OS: Windows - Browser Firefox - Browser Version 78.0.2 - Floccus version: 4.2.5 - Floccus sync method: nextcloud folders **Server (please complete the following information):** - OS: debian10 - Nextcloud version: 18.0.6 - Bookmarks app version: 3.2.4 **Debug log** It is often useful to provide a debug log file along with the issue. You can obtain a debug log of the most recent sync runs by clicking 'Debug log' in the bottom right corner of the floccus panel in your browser. Note: As your debug log usually contains large parts of your bookmark data, instead of attaching it publicly to the issue here, I recommend uploading it privately at the following URL https://klehranlage.net/index.php/s/7nn82NSBsfQKdsJ - [x ] Debug log provided floccus-4.2.5-2020-07-10-maurerle **Additional context** Add any other context about the problem here.

kerem

2026-02-25 22:37:04 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 22:37:05 +03:00

Author

Owner

@maurerle commented on GitHub (Jul 13, 2020):

I seems to me, that after throwing the error "trying to remove a non-existing item" the item which should be removed must not be removed again (as it is not there on the server). This would fix issuing the same exception on every sync.
But I didn't look into code.

@maurerle commented on GitHub (Jul 13, 2020): I seems to me, that after throwing the error "trying to remove a non-existing item" the item which should be removed must not be removed again (as it is not there on the server). This would fix issuing the same exception on every sync. But I didn't look into code.

kerem commented

2026-02-25 22:37:05 +03:00

Author

Owner

@marcelklehr commented on GitHub (Jul 19, 2020):

I'm sorry for the delay on my part. I've been tracking this bug for a while and added this assertion in the last release in order to pin it down. Luckily, you found the error now and I can start reproducing and fixing it 🎉

@marcelklehr commented on GitHub (Jul 19, 2020): I'm sorry for the delay on my part. I've been tracking this bug for a while and added this assertion in the last release in order to pin it down. Luckily, you found the error now and I can start reproducing and fixing it :tada:

kerem commented

2026-02-25 22:37:05 +03:00

Author

Owner

@marcelklehr commented on GitHub (Jul 20, 2020):

@Tank-Missile Please be aware that the floccus logs contain a large portion of your bookmarks data, and publishing them on github is likely not a good idea.

@marcelklehr commented on GitHub (Jul 20, 2020): @Tank-Missile Please be aware that the floccus logs contain a large portion of your bookmarks data, and publishing them on github is likely not a good idea.

kerem commented

2026-02-25 22:37:05 +03:00

Author

Owner

@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.

@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.

kerem referenced this issue

2026-02-25 22:40:36 +03:00

[PR #416] [CLOSED] Bump all-contributors-cli from 5.11.0 to 6.11.2 #1560

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/floccus#416

No description provided.

Rows
Columns