mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 06:35:59 +03:00
[GH-ISSUE #1203] Cancel sync button doesn't work #799
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#799
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 @InfamousUser on GitHub (Jun 18, 2022).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1203
Which version of floccus are you using?
4.15.0
Sync method
Nextcloud Bookmarks
Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.
Chrome 102.0.5005.115
Which version of Nextcloud Bookmarks are you using? (if relevant)
10.4.0
Which version of Nextcloud? (if relevant)
24.0.1
What kind of WebDAV server are you using? (if relevant)
No response
Describe the Bug
Pressing the "Cancel sync" button does nothing to cancel the sync.
Expected Behavior
Pressing the "Cancel sync" button cancels the sync.
To Reproduce
Debug log provided
@marcelklehr commented on GitHub (Jul 4, 2022):
This may have happened due to a recent bug. Can you try again with v4.16?
@InfamousUser commented on GitHub (Jul 5, 2022):
Still doesn't work or mostly doesn't work. It worked at least once after a long delay.
@marcelklehr commented on GitHub (Mar 22, 2023):
It is somewhat delayed due to the way it works. If the sync run is very fast it may trigger too late, but from my tests, if the sync runs for a longer time, it works fine.
@github-actions[bot] commented on GitHub (Mar 22, 2024):
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.