mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 06:35:59 +03:00
[GH-ISSUE #228] Can't find bookmark for id #218
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#218
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 @Tank-Missile on GitHub (Feb 6, 2019).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/228
Software versions
Steps to reproduce
Expected outcome
Changes are reflected from the server to the browser.
Actual outcome
Can't find bookmark for id. This is the first time I've gotten this error, but every other time the bookmarks don't sync into the correct positions. It will instead sync the old bookmark layout from the second computer to the server, overwriting new changes I made on the first computer. How exactly does floccus determine how it should modify the bookmarks from what end?
@marcelklehr commented on GitHub (Feb 12, 2019):
Hey @Tank-Missile
Sorry for the delay. I think I might have found the underlying issue. Could you in any case disable parallel sync and retry to get a cleaner log file?
@marcelklehr commented on GitHub (Feb 24, 2019):
It seems that this fixed it :) 🎉
As always thanks for the feedback! :)
@github-actions[bot] commented on GitHub (Feb 8, 2021):
Hi @Tank-Missile! This issue is being automatically closed because it does not follow the issue template.
@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.