[GH-ISSUE #1978] E029: Failsafe #1322

Closed
opened 2026-02-25 22:39:41 +03:00 by kerem · 5 comments
Owner

Originally created by @liweishu on GitHub (Jun 18, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1978

Which version of floccus are you using?

5.4.5

How many bookmarks do you have, roughly?

3231

Are you using other means to sync bookmarks in parallel to floccus?

是,我也通过 Edge 账户同步

Sync method

Git

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

Edge 137.0.3296.83

Which version of Nextcloud Bookmarks are you using? (if relevant)

No response

Which version of Nextcloud? (if relevant)

No response

What kind of WebDAV server are you using? (if relevant)

No response

Describe the Bug

3k 的书签量,将 550 左右书签(不到 1/5)移出同步的文件夹,另有不到 100 书签在当前同步文件夹内调整目录结构,以及不到 30 的新书签添加。提示:
E029: Failsafe: The current sync run would delete 87% of your bookmarks. Refusing to execute. Disable this failsafe in the account settings if you want to proceed anyway.

Expected Behavior

Failsafe 的标签删除量应该正确统计。
仅显示 delete 87% of your bookmarks,应具区分远程备份与本地标签,否则无法辨别问题。
本地书签删除不达50%应正常同步。

To Reproduce

3k 的书签量,将 550 左右书签(不到 1/5)移出同步的文件夹,另有不到 100 书签在当前同步文件夹内调整目录结构,以及不到 30 的新书签添加。

Debug log provided

  • I have provided a debug log file
Originally created by @liweishu on GitHub (Jun 18, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1978 ### Which version of floccus are you using? 5.4.5 ### How many bookmarks do you have, roughly? 3231 ### Are you using other means to sync bookmarks in parallel to floccus? 是,我也通过 Edge 账户同步 ### Sync method Git ### Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please. Edge 137.0.3296.83 ### Which version of Nextcloud Bookmarks are you using? (if relevant) _No response_ ### Which version of Nextcloud? (if relevant) _No response_ ### What kind of WebDAV server are you using? (if relevant) _No response_ ### Describe the Bug 3k 的书签量,将 550 左右书签(不到 1/5)移出同步的文件夹,另有不到 100 书签在当前同步文件夹内调整目录结构,以及不到 30 的新书签添加。提示: `E029: Failsafe: The current sync run would delete 87% of your bookmarks. Refusing to execute. Disable this failsafe in the account settings if you want to proceed anyway.` ### Expected Behavior Failsafe 的标签删除量应该正确统计。 仅显示 `delete 87% of your bookmarks`,应具区分远程备份与本地标签,否则无法辨别问题。 本地书签删除不达50%应正常同步。 ### To Reproduce 3k 的书签量,将 550 左右书签(不到 1/5)移出同步的文件夹,另有不到 100 书签在当前同步文件夹内调整目录结构,以及不到 30 的新书签添加。 ### Debug log provided - [ ] I have provided a debug log file
Author
Owner

@github-actions[bot] commented on GitHub (Jun 18, 2025):

Hello 👋

Thank you for taking the time to open this issue with floccus. I know it's frustrating when software
causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at
and if possible solved. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings.
I'm Marcel. I created floccus a few years ago, and have been maintaining it since. I currently work for Nextcloud
which leaves me with less time for side projects like this one than I used to have.
I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it.
Until then, please be patient. It helps when you stick around to answer follow up questions I may have,
as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report
and the issue cannot be solved without it, I will have to close the issue after a while.
Note also that GitHub in general is a place where people meet to make software better together. Nobody here is under any obligation
to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can
collaborate to make this software better. For everyone.
Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge
and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and
try to fix the odd bug yourself. Everyone will be thankful for extra helping hands!
If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way,
I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already.
You can find donation options at https://floccus.org/donate/. Thank you!

One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the Nextcloud forum,
to twitter or somewhere else. But this is a technical issue tracker, so please make sure to
focus on the tech and keep your opinions to yourself.

Thank you for reading through this primer. I look forward to working with you on this issue!
Cheers 💙

<!-- gh-comment-id:2984517893 --> @github-actions[bot] commented on GitHub (Jun 18, 2025): Hello :wave: Thank you for taking the time to open this issue with floccus. I know it's frustrating when software causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at and if possible solved. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings. I'm Marcel. I created floccus a few years ago, and have been maintaining it since. I currently work for Nextcloud which leaves me with less time for side projects like this one than I used to have. I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it. Until then, please be patient. It helps when you stick around to answer follow up questions I may have, as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report and the issue cannot be solved without it, I will have to close the issue after a while. Note also that GitHub in general is a place where people meet to make software better *together*. Nobody here is under any obligation to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can collaborate to make this software better. For everyone. Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and try to fix the odd bug yourself. Everyone will be thankful for extra helping hands! If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way, I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already. You can find donation options at <https://floccus.org/donate/>. Thank you! One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the Nextcloud forum, to twitter or somewhere else. But this is a technical issue tracker, so please make sure to focus on the tech and keep your opinions to yourself. Thank you for reading through this primer. I look forward to working with you on this issue! Cheers :blue_heart:
Author
Owner

@liweishu commented on GitHub (Jun 18, 2025):

无论如何,标签改动量都远不到 50%,更不用说提示的 87%。

<!-- gh-comment-id:2984521871 --> @liweishu commented on GitHub (Jun 18, 2025): 无论如何,标签改动量都远不到 50%,更不用说提示的 87%。
Author
Owner

@marcelklehr commented on GitHub (Jul 16, 2025):

是,我也通过 Edge 账户同步

I think this may have something to do with your problem. I have often found that the native syncing mechanism of browsers interferes with floccus' ability to detect changes. Could you try disabling the sync with Edge and try to provoke this issue again?

<!-- gh-comment-id:3078556254 --> @marcelklehr commented on GitHub (Jul 16, 2025): > 是,我也通过 Edge 账户同步 I think this may have something to do with your problem. I have often found that the native syncing mechanism of browsers interferes with floccus' ability to detect changes. Could you try disabling the sync with Edge and try to provoke this issue again?
Author
Owner

@github-actions[bot] commented on GitHub (Oct 15, 2025):

Hello 👋
This issue appears to have had no activity for 3 months. We cannot keep track of whether individual issues
have resolved themselves or still require attention without user interaction. We're thus adding the stale label to this issue to schedule
it for getting closed in 5 days time. If you believe this issue is still valid and should be fixed, you can add a comment
or remove the label to avoid it getting closed.

Cheers 💙

<!-- gh-comment-id:3404254238 --> @github-actions[bot] commented on GitHub (Oct 15, 2025): Hello :wave: This issue appears to have had no activity for 3 months. We cannot keep track of whether individual issues have resolved themselves or still require attention without user interaction. We're thus adding the stale label to this issue to schedule it for getting closed in 5 days time. If you believe this issue is still valid and should be fixed, you can add a comment or remove the label to avoid it getting closed. Cheers :blue_heart:
Author
Owner

@github-actions[bot] commented on GitHub (Oct 20, 2025):

This issue was closed because it has been stalled for 5 days with no activity.

<!-- gh-comment-id:3420279065 --> @github-actions[bot] commented on GitHub (Oct 20, 2025): This issue was closed because it has been stalled for 5 days with no activity.
Sign in to join this conversation.
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#1322
No description provided.