[GH-ISSUE #723] 4.4.6 on firefox cannot sync - claims that a lock file exists #463

Closed
opened 2026-02-25 22:37:14 +03:00 by kerem · 7 comments
Owner

Originally created by @bhlevca on GitHub (Nov 5, 2020).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/723

Describe the bug
cannot sync fils with cannot remove lock file

To Reproduce
Steps to reproduce the behavior:
1 delete any lock file in nextcloud
2 press sync

Expected behavior
expect sync to happen

Desktop (please complete the following information):

  • OS: opensuse linux thumbleweed
  • Browser : firefox
  • Browser Version 84
  • Floccus version: 4.4.6
  • Floccus sync method: webdav

Server (please complete the following information):

  • OS: debian
  • Nextcloud version: 19.4
  • Bookmarks app version: [if applicable]

Debug log
020-11-05T03:42:36.609Z onSyncStart: begin
a long list of
2020-11-05T03:52:24.282Z https://nextcloud.hlevca.com/remot.php/webdav/bookmarks.xbel.lock

Originally created by @bhlevca on GitHub (Nov 5, 2020). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/723 **Describe the bug** cannot sync fils with cannot remove lock file **To Reproduce** Steps to reproduce the behavior: 1 delete any lock file in nextcloud 2 press sync **Expected behavior** expect sync to happen **Desktop (please complete the following information):** - OS: opensuse linux thumbleweed - Browser : firefox - Browser Version 84 - Floccus version: 4.4.6 - Floccus sync method: webdav **Server (please complete the following information):** - OS: debian - Nextcloud version: 19.4 - Bookmarks app version: [if applicable] **Debug log** 020-11-05T03:42:36.609Z onSyncStart: begin a long list of 2020-11-05T03:52:24.282Z https://nextcloud.hlevca.com/remot.php/webdav/bookmarks.xbel.lock
Author
Owner

@bhlevca commented on GitHub (Nov 5, 2020):

forgot to mention that 4.4.5 was working just fine, but the automatic update screwed it up

<!-- gh-comment-id:722127780 --> @bhlevca commented on GitHub (Nov 5, 2020): forgot to mention that 4.4.5 was working just fine, but the automatic update screwed it up
Author
Owner

@marcelklehr commented on GitHub (Nov 5, 2020):

remot.php/webdav/bookmarks.xbel.lock

there's a typo in this URL

<!-- gh-comment-id:722348464 --> @marcelklehr commented on GitHub (Nov 5, 2020): > remot.php/webdav/bookmarks.xbel.lock there's a typo in this URL
Author
Owner

@bhlevca commented on GitHub (Nov 5, 2020):

You are right. It was late last night and I did not see the missing e. It is working now, sync is in progress ...

Is there a way for the client to figure out when an URL is bad, some type of response from the server and print an error message?

<!-- gh-comment-id:722396787 --> @bhlevca commented on GitHub (Nov 5, 2020): You are right. It was late last night and I did not see the missing `e`. It is working now, sync is in progress ... Is there a way for the client to figure out when an URL is bad, some type of response from the server and print an error message?
Author
Owner

@bhlevca commented on GitHub (Nov 5, 2020):

It seemed to work up to a point, but unlike 4.4.5 the "Cycle(s) detected; toposort only works on acyclic graphs" has resurfaced
I deleted all teh bookmarks in the browsers and synchronized again. This part works. Subsequent sync may be not working similarly to 4.4.4.

<!-- gh-comment-id:722444541 --> @bhlevca commented on GitHub (Nov 5, 2020): It seemed to work up to a point, but unlike 4.4.5 the `"Cycle(s) detected; toposort only works on acyclic graphs"` has resurfaced I deleted all teh bookmarks in the browsers and synchronized again. This part works. Subsequent sync may be not working similarly to 4.4.4.
Author
Owner

@bhlevca commented on GitHub (Dec 24, 2020):

It appears that lock management is too simple to handle multiple browsers competing for the resources.
I switched to the Nextcloud App and even if it is slower the locking problems do not exist. I think that a much more robust locking mechanism needs to be implemented on the WebDAV solution in order to work properly, Also the problem with duplicating children seems to be solved.

<!-- gh-comment-id:750764060 --> @bhlevca commented on GitHub (Dec 24, 2020): It appears that lock management is too simple to handle multiple browsers competing for the resources. I switched to the Nextcloud App and even if it is slower the locking problems do not exist. I think that a much more robust locking mechanism needs to be implemented on the WebDAV solution in order to work properly, Also the problem with duplicating children seems to be solved.
Author
Owner

@marcelklehr commented on GitHub (Jan 5, 2021):

Thank you for the feedback! I*m closing this for now.

<!-- gh-comment-id:754730821 --> @marcelklehr commented on GitHub (Jan 5, 2021): Thank you for the feedback! I*m closing this for now.
Author
Owner

@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.

<!-- gh-comment-id:1477177576 --> @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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/floccus#463
No description provided.