mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 22:26:06 +03:00
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#696
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 @0cwa on GitHub (Feb 26, 2022).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1051
I've been getting this same error referenced in #992 since installing floccus weeks ago:
Syncing failed with E020: Could not parse server response.I get this same error despite reinstalling bookmarks and floccus, and running the troubleshooting guide, here are the logs:
Originally posted by @0cwa in https://github.com/floccusaddon/floccus/issues/992#issuecomment-1035866892
@github-actions[bot] commented on GitHub (Feb 26, 2022):
Hi @0cwa! This issue is being automatically closed because it does not follow the issue template.
@github-actions[bot] commented on GitHub (Feb 26, 2022):
Hi @0cwa! This issue is being automatically closed because it does not follow the issue template.
@github-actions[bot] commented on GitHub (Feb 26, 2022):
Hi @0cwa! This issue is being automatically closed because it does not follow the issue template.
@github-actions[bot] commented on GitHub (Feb 26, 2022):
Hi @0cwa! This issue is being automatically closed because it does not follow the issue template.
@github-actions[bot] commented on GitHub (Feb 26, 2022):
Hi @0cwa! This issue is being automatically closed because it does not follow the issue template.
@github-actions[bot] commented on GitHub (Mar 20, 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.