[GH-ISSUE #1497] This profile will be synced soon. We're either waiting for other devices of yours, or other profiles on this device, to finish syncing. #985

Closed
opened 2026-02-25 22:38:38 +03:00 by kerem · 4 comments
Owner

Originally created by @WantChane on GitHub (Dec 26, 2023).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1497

Which version of floccus are you using?

5.0.4

Sync method

WebDAV

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

edge

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)

https://dav.jianguoyun.com/dav/

Describe the Bug

can not sync

Expected Behavior

In the latest version of floccus (in 5.0.5), the prompt "This profile will be synced soon. We're either waiting for other devices of yours, or other profiles on this device, to finish syncing.",however in other versions, e.g. 5.0.4, 4.19.1, he just repeatedly tries to synchronize and eventually fails

To Reproduce

image

Debug log provided

  • I have provided a debug log file
Originally created by @WantChane on GitHub (Dec 26, 2023). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1497 ### Which version of floccus are you using? 5.0.4 ### Sync method WebDAV ### Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please. edge ### 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) https://dav.jianguoyun.com/dav/ ### Describe the Bug can not sync ### Expected Behavior In the latest version of floccus (in 5.0.5), the prompt "This profile will be synced soon. We're either waiting for other devices of yours, or other profiles on this device, to finish syncing.",however in other versions, e.g. 5.0.4, 4.19.1, he just repeatedly tries to synchronize and eventually fails ### To Reproduce ![image](https://github.com/floccusaddon/floccus/assets/143467549/e443568d-c4c4-4006-ae51-0a0ade6029d9) ### Debug log provided - [ ] I have provided a debug log file
kerem 2026-02-25 22:38:38 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@github-actions[bot] commented on GitHub (Dec 26, 2023):

Hello 👋

Thank you for taking the time to open this issue with floccus. I know it's frustrating when software
causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at
and if possible solved.
I'm Marcel and I created floccus and have been maintaining it ever since.
I currently work for Nextcloud which leaves me with less time for side projects like this one
than I used to have.
I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it.
Until then, please be patient.
Note also that GitHub is a place where people meet to make software better together. Nobody here is under any obligation
to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can
collaborate to make this software better. For everyone.
Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge
and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and
try to fix the odd bug yourself. Everyone will be thankful for extra helping hands!
One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the forum,
to twitter or somewhere else. But this is a technical issue tracker, so please make sure to
focus on the tech and keep your opinions to yourself.

I look forward to working with you on this issue
Cheers 💙

<!-- gh-comment-id:1869500351 --> @github-actions[bot] commented on GitHub (Dec 26, 2023): Hello :wave: Thank you for taking the time to open this issue with floccus. I know it's frustrating when software causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at and if possible solved. I'm Marcel and I created floccus and have been maintaining it ever since. I currently work for Nextcloud which leaves me with less time for side projects like this one than I used to have. I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it. Until then, please be patient. Note also that GitHub is a place where people meet to make software better *together*. Nobody here is under any obligation to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can collaborate to make this software better. For everyone. Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and try to fix the odd bug yourself. Everyone will be thankful for extra helping hands! One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the forum, to twitter or somewhere else. But this is a technical issue tracker, so please make sure to focus on the tech and keep your opinions to yourself. I look forward to working with you on this issue Cheers :blue_heart:
Author
Owner

@jdelker commented on GitHub (Dec 27, 2023):

I can confirm this problem with 5.0.5 (currently on Firefox 115.6.0esr) and Nextcloud-Backend via WebDAV.

The sync seems permanently blocked, due to an existing lock.
Bad: Although no sync is performed, the plugin icon shows the "all-ok" checkmark symbol. Thus, this situation remained unnoticed for some time already.

Looking at the access logs on the Nexcloud server, I see continuous tries of the client to receive a lock, each responded with a code 423 error:

"POST /index.php/apps/bookmarks/public/rest/v2/lock HTTP/1.1" 423

I tried to manually remove the lock with

curl -X DELETE -u <user> https://my.nextcloud.server/index.php/apps/bookmarks/public/rest/v2/lock

which resulted in the sync to start again.
The client performs a successful lock

"POST /index.php/apps/bookmarks/public/rest/v2/lock HTTP/1.1" 200

followed by about 50 GETs on various "/index.php/apps/bookmarks/public/..." URLs:

"GET /index.php/apps/bookmarks/public/rest/v2/folder/-1/hash HTTP/1.1" 200
"GET /index.php/apps/bookmarks/public/rest/v2/folder?root=-1&layers=0 HTTP/1.1" 200
"GET /index.php/apps/bookmarks/public/rest/v2/folder/1/hash HTTP/1.1" 200
"GET /index.php/apps/bookmarks/public/rest/v2/folder/1/children?layers=1 HTTP/1.1" 200
"GET /index.php/apps/bookmarks/public/rest/v2/folder/494/hash HTTP/1.1" 200
"GET /index.php/apps/bookmarks/public/rest/v2/folder/198/hash HTTP/1.1" 200
...

(Not sure, if that is an adequate number for >1k bookmarks)

Then suddenly (4sec after the last GET), the client sends another POST on the lock:

"POST /index.php/apps/bookmarks/public/rest/v2/lock HTTP/1.1" 423

which is again blocked with code 423.
Now the client is back in the same situation as before.

NOTE: The above was observed with no interference of other Floccus clients. All requests originated from a single client.

<!-- gh-comment-id:1870228839 --> @jdelker commented on GitHub (Dec 27, 2023): I can confirm this problem with 5.0.5 (currently on Firefox 115.6.0esr) and Nextcloud-Backend via WebDAV. The sync seems permanently blocked, due to an existing lock. Bad: Although no sync is performed, the plugin icon shows the "all-ok" checkmark symbol. Thus, this situation remained unnoticed for some time already. Looking at the access logs on the Nexcloud server, I see continuous tries of the client to receive a lock, each responded with a code 423 error: ``` "POST /index.php/apps/bookmarks/public/rest/v2/lock HTTP/1.1" 423 ``` I tried to manually remove the lock with ``` curl -X DELETE -u <user> https://my.nextcloud.server/index.php/apps/bookmarks/public/rest/v2/lock ``` which resulted in the sync to start again. The client performs a successful lock ``` "POST /index.php/apps/bookmarks/public/rest/v2/lock HTTP/1.1" 200 ``` followed by about 50 GETs on various "/index.php/apps/bookmarks/public/..." URLs: ``` "GET /index.php/apps/bookmarks/public/rest/v2/folder/-1/hash HTTP/1.1" 200 "GET /index.php/apps/bookmarks/public/rest/v2/folder?root=-1&layers=0 HTTP/1.1" 200 "GET /index.php/apps/bookmarks/public/rest/v2/folder/1/hash HTTP/1.1" 200 "GET /index.php/apps/bookmarks/public/rest/v2/folder/1/children?layers=1 HTTP/1.1" 200 "GET /index.php/apps/bookmarks/public/rest/v2/folder/494/hash HTTP/1.1" 200 "GET /index.php/apps/bookmarks/public/rest/v2/folder/198/hash HTTP/1.1" 200 ... ``` (Not sure, if that is an adequate number for >1k bookmarks) Then suddenly (4sec after the last GET), the client sends another POST on the lock: ``` "POST /index.php/apps/bookmarks/public/rest/v2/lock HTTP/1.1" 423 ``` which is again blocked with code 423. Now the client is back in the same situation as before. NOTE: The above was observed with no interference of other Floccus clients. All requests originated from a single client.
Author
Owner

@marcelklehr commented on GitHub (Dec 27, 2023):

This is a duplicate of #1495

<!-- gh-comment-id:1870234755 --> @marcelklehr commented on GitHub (Dec 27, 2023): This is a duplicate of #1495
Author
Owner

@github-actions[bot] commented on GitHub (Dec 27, 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.

<!-- gh-comment-id:2563191894 --> @github-actions[bot] commented on GitHub (Dec 27, 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.
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#985
No description provided.