mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 22:26:06 +03:00
[GH-ISSUE #775] Interrupting sync causes duplicates? #494
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#494
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 @marcelklehr on GitHub (Jan 5, 2021).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/775
From chrome webstore review
@daniu-de commented on GitHub (Feb 1, 2021):
Hi,
unfortunately I also seem to have that issue with Firefox.
Please solve it soon ... it sounds really cool to be ably to sync my bookmarks with nextcloud
regards
@marcelklehr commented on GitHub (Feb 7, 2021):
@daniu-de Thanks for your feedback! I'll try to investigate. By interrupting you mean closing the browser or clicking "cancel sync" in the ui? Or both?
@mikeperalta1 commented on GitHub (Feb 9, 2021):
I'm unaware of how I received my own duplicates. I just know last time I deleted a duplicate, it left zero copies in NextCloud.
I might have time to run tests somewhat soon if you have anything in mind.
@stale[bot] commented on GitHub (Feb 24, 2021):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
@stale[bot] commented on GitHub (Mar 10, 2021):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
@github-actions[bot] commented on GitHub (May 24, 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.