Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Folder #xxx[xxx] contains an nonexistent bookmark xxx #267

Closed
linux0uid opened this issue Apr 17, 2019 · 3 comments
Closed

Folder #xxx[xxx] contains an nonexistent bookmark xxx #267

linux0uid opened this issue Apr 17, 2019 · 3 comments

Comments

@linux0uid
Copy link

Software versions

  • Browser:
    • Chromium Version 73.0.3683.75 (Developer Build) built on Debian buster/sid, running on Debian buster/sid (64-bit);
    • Firefox Quantum 60.6.1esr (64-bit);
  • Nextcloud: v15.0.7
  • Nextcloud Bookmarks app: v0.17.0
  • Floccus: for chomium - v3.2.16, for firefox - v3.2.15
  • Floccus sync method: nextcloud Bookmarks v0.14+ with folders

Expected outcome

I have try make sync from firefox and chromium. And even if first sync finished successfully after some time I had this error. On server side I did find the logging errors related to this issue. I have do sync from screech (removed flocuss from all browsers, remove all bookmarks on server) several times without success. I have run sync with both browsers together and with each of them alone. All the time sooner or later I have the same error.

Debug log

https://cloud.steli-horizon.com.ua/s/34jeHoQWMGidAXJ

@tkurbad
Copy link

tkurbad commented Apr 25, 2019

I'm seeing the same. Also, when trying to sync FF and Chromium concurrently.

@marcelklehr
Copy link
Member

This is an artifact of two sync runs happening at the same time from two different browsers. This leads to one client observing an inconsistent server state and stopping with the above message. This should no longer happen with sparse tree syncing as introduced by the upcoming v3.3.0 (see #269 )

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 21, 2023
@marcelklehr marcelklehr moved this to Done in Floccus May 19, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

3 participants