mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #1319] Failed to map parentId: 1097 Last synchronized: 1 day ago #874
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#874
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 @ghost on GitHub (Jan 10, 2023).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1319
Which version of floccus are you using?
4.18
Sync method
Google Drive
Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.
EDGE Version 108.0.1462.76 (Official build) (64-bit)
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
I just clicked "push up" and it failed.

Yesterday it synced correctly, but after last sync I had changed many bookmarks (like moved and deleted).
After these changes floccus is not working.
Expected Behavior
complete the sync without errors.
To Reproduce
Attached is redacted log.
redacted-floccus-4.18.0-2023-01-10.log
Debug log provided
@marcelklehr commented on GitHub (Jan 14, 2023):
Thank you for providing a debug log! This will hopefully be gone with the next release today
@ghost commented on GitHub (Jan 16, 2023):
thanks!
@github-actions[bot] commented on GitHub (Jan 17, 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.