[GH-ISSUE #347] XBEL not picking up new folders #289

Closed
opened 2026-02-25 22:36:42 +03:00 by kerem · 20 comments
Owner

Originally created by @xelcho on GitHub (Aug 8, 2019).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/347

Software versions

OS: ubuntu 18.04 lts

  • Browser: firefox quantum
  • Nextcloud: 14
  • Nextcloud Bookmarks app: 1.1.1
  • Floccus: 3.3.2
  • Floccus sync method: XBEL/webdav

Steps to reproduce

  1. added new folder to root of bookmarks toolbar with bookmarks in it.

Expected outcome

after multiple syncs, expected it to show up on other synced machines.
...

Actual outcome

after multiple syncs, expected it did not show up on other synced machines.
...

Debug log

  • Debug log provided
Originally created by @xelcho on GitHub (Aug 8, 2019). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/347 <!-- Hello there! Thank you for providing feedback! Please answer the below questions to allow for as smooth a process of tackling the issue as possible :) (Note: Everything surrounded by arrows, like this text for example, will not be visible.) --> ### Software versions OS: ubuntu 18.04 lts - Browser: firefox quantum - Nextcloud: 14 - Nextcloud Bookmarks app: 1.1.1 - Floccus: 3.3.2 - Floccus sync method: XBEL/webdav <!-- Sync methods are either XBEL/webdav (signified as `webdav`), nextcloud Bookmarks legacy (signified as `nextcloud`), or nextcloud Bookmarks v0.14+ with folders (signified as `nextcloud-folders`) --> ### Steps to reproduce <!-- What did you do? Be as specific as possible --> 1. added new folder to root of bookmarks toolbar with bookmarks in it. 2. ### Expected outcome <!-- What did you think was going to happen or what do you think should have happened? --> after multiple syncs, expected it to show up on other synced machines. ... ### Actual outcome <!-- What actually happened after you did the above steps? --> after multiple syncs, expected it did not show up on other synced machines. ... ### Debug log <!-- It is often useful to provide a debug log file along with the issue. You can obtain a debug log of the most recent sync runs by clicking 'Debug log' in the bottom right corner of the floccus panel in your browser. Note: As your debug log usually contains large parts of your bookmark data, instead of attaching it to the issue here, publicly, I recommend uploading it privately at the following URL https://klehranlage.net/index.php/s/7nn82NSBsfQKdsJ --> - [ ] Debug log provided <!-- Thanks! Now, hit Submit and wait for a reply :) -->
kerem closed this issue 2026-02-25 22:36:42 +03:00
Author
Owner

@marcelklehr commented on GitHub (Aug 10, 2019):

Mh. I cannot reproduce this. Does the folder end up in the xbel file?

<!-- gh-comment-id:520182305 --> @marcelklehr commented on GitHub (Aug 10, 2019): Mh. I cannot reproduce this. Does the folder end up in the xbel file?
Author
Owner

@xelcho commented on GitHub (Aug 15, 2019):

Sorry for the delay!

I am not able to find the folder in the xbel file.

<!-- gh-comment-id:521690762 --> @xelcho commented on GitHub (Aug 15, 2019): Sorry for the delay! I am not able to find the folder in the xbel file.
Author
Owner

@marcelklehr commented on GitHub (Aug 19, 2019):

Which folder did you select to be synced?

<!-- gh-comment-id:522548310 --> @marcelklehr commented on GitHub (Aug 19, 2019): Which folder did you select to be synced?
Author
Owner

@xelcho commented on GitHub (Aug 19, 2019):

I added a new folder to Firefox (on client machine) and expected it to be picked up by floccus and replicated to other client machines. This has been the pattern that has worked in the past, and I don't recall changing anything in the mean time.

Does that answer your question?

<!-- gh-comment-id:522592775 --> @xelcho commented on GitHub (Aug 19, 2019): I added a new folder to Firefox (on client machine) and expected it to be picked up by floccus and replicated to other client machines. This has been the pattern that has worked in the past, and I don't recall changing anything in the mean time. Does that answer your question?
Author
Owner

@marcelklehr commented on GitHub (Aug 19, 2019):

Did you try syncing manually? You may also want to try the new beta, to see if this has been fixed by any chance: #338

<!-- gh-comment-id:522593381 --> @marcelklehr commented on GitHub (Aug 19, 2019): Did you try syncing manually? You may also want to try the new beta, to see if this has been fixed by any chance: #338
Author
Owner

@xelcho commented on GitHub (Aug 19, 2019):

For my understanding: Manually Sync is clicking on "Sync now" button in the extension?

I will give the beta a try.

<!-- gh-comment-id:522596895 --> @xelcho commented on GitHub (Aug 19, 2019): For my understanding: Manually Sync is clicking on "Sync now" button in the extension? I will give the beta a try.
Author
Owner

@marcelklehr commented on GitHub (Aug 19, 2019):

For my understanding: Manually Sync is clicking on "Sync now" button in the extension?

Yes. But I assume you tried that already.

<!-- gh-comment-id:522604513 --> @marcelklehr commented on GitHub (Aug 19, 2019): > For my understanding: Manually Sync is clicking on "Sync now" button in the extension? Yes. But I assume you tried that already.
Author
Owner

@xelcho commented on GitHub (Aug 19, 2019):

Yes. But I assume you tried that already.
You know, I think so. Let's table this until I am home and can do so for certain!

Thanks!

<!-- gh-comment-id:522605818 --> @xelcho commented on GitHub (Aug 19, 2019): > Yes. But I assume you tried that already. You know, I think so. Let's table this until I am home and can do so for certain! Thanks!
Author
Owner

@xelcho commented on GitHub (Aug 21, 2019):

It seems that the client is hanging on sync, regardless if it is automatic or manually initiated. It gets hung at...
Screenshot_20190821_163640
If I "mess" with it, I get issues with file locking.
If I delete the lock file, it hangs at the same spot.
I am not sure what I should be looking for in the debug log on client, the following are the last 2 lines:

Syncing failed with E023: Unable to clear lock file, consider deleting bm/bookmarks.xbel.lock manually.
onSyncFail

<!-- gh-comment-id:523643006 --> @xelcho commented on GitHub (Aug 21, 2019): It seems that the client is hanging on sync, regardless if it is automatic or manually initiated. It gets hung at... ![Screenshot_20190821_163640](https://user-images.githubusercontent.com/30007489/63466992-71502f00-c432-11e9-9a85-4b90020362e3.png) If I "mess" with it, I get issues with file locking. If I delete the lock file, it hangs at the same spot. I am not sure what I should be looking for in the debug log on client, the following are the last 2 lines: Syncing failed with E023: Unable to clear lock file, consider deleting bm/bookmarks.xbel.lock manually. onSyncFail
Author
Owner

@marcelklehr commented on GitHub (Aug 21, 2019):

Can you check the debug log, when it hangs?

<!-- gh-comment-id:523667384 --> @marcelklehr commented on GitHub (Aug 21, 2019): Can you check the debug log, when it hangs?
Author
Owner

@xelcho commented on GitHub (Aug 22, 2019):

Client debug log:

I am not sure what I should be looking for in the debug log on client, the following are the last 2 lines:

Syncing failed with E023: Unable to clear lock file, consider deleting bm/bookmarks.xbel.lock manually.
onSyncFail

It is working, for now, by renaming the xbel file and creating a new one. Let's see if the other clients behave. :)

<!-- gh-comment-id:523847435 --> @xelcho commented on GitHub (Aug 22, 2019): Client debug log: > I am not sure what I should be looking for in the debug log on client, the following are the last 2 lines: >Syncing failed with E023: Unable to clear lock file, consider deleting bm/bookmarks.xbel.lock manually. >onSyncFail It is working, for now, by renaming the xbel file and creating a new one. Let's see if the other clients behave. :)
Author
Owner

@bhlevca commented on GitHub (Aug 22, 2019):

I am experiencing periodically the same behaviour and I need quite often to
delete the lock file and sometimes the xbel file. There is something
corrupting the process and I think that the locking mechanism need to be
reviewed. In particular, if a sync process is stopped for various reasons
including closing the browser, the lock file is not removed. Also,it
happens one in a while that I get duplicates, sometimes folders sometimes
duplicates inside the folder. It is so random that it is hard if not
impossible to catch.

I don't know how can I help to fix these issues.

Bogdan

On Thu, 22 Aug 2019 at 06:32, xelcho notifications@github.com wrote:

Client debug log:

I am not sure what I should be looking for in the debug log on client, the
following are the last 2 lines:

Syncing failed with E023: Unable to clear lock file, consider deleting
bm/bookmarks.xbel.lock manually.
onSyncFail

It is working, for now, by renaming the xbel file and creating a new one.
Let's see if the other clients behave. :)


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/marcelklehr/floccus/issues/347?email_source=notifications&email_token=AABMRXTUPBZYJSZ4B7R24Z3QFZTMFA5CNFSM4IKJRT5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD44UOCY#issuecomment-523847435,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABMRXQINM6E537EGKMHNDDQFZTMFANCNFSM4IKJRT5A
.

<!-- gh-comment-id:523906322 --> @bhlevca commented on GitHub (Aug 22, 2019): I am experiencing periodically the same behaviour and I need quite often to delete the lock file and sometimes the xbel file. There is something corrupting the process and I think that the locking mechanism need to be reviewed. In particular, if a sync process is stopped for various reasons including closing the browser, the lock file is not removed. Also,it happens one in a while that I get duplicates, sometimes folders sometimes duplicates inside the folder. It is so random that it is hard if not impossible to catch. I don't know how can I help to fix these issues. Bogdan ᐧ On Thu, 22 Aug 2019 at 06:32, xelcho <notifications@github.com> wrote: > Client debug log: > > I am not sure what I should be looking for in the debug log on client, the > following are the last 2 lines: > > Syncing failed with E023: Unable to clear lock file, consider deleting > bm/bookmarks.xbel.lock manually. > onSyncFail > > It is working, for now, by renaming the xbel file and creating a new one. > Let's see if the other clients behave. :) > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/marcelklehr/floccus/issues/347?email_source=notifications&email_token=AABMRXTUPBZYJSZ4B7R24Z3QFZTMFA5CNFSM4IKJRT5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD44UOCY#issuecomment-523847435>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AABMRXQINM6E537EGKMHNDDQFZTMFANCNFSM4IKJRT5A> > . >
Author
Owner

@xelcho commented on GitHub (Aug 22, 2019):

So on my windows 10 firefox quantum client, the sync can not complete the debug log:

Bookmark unchanged
Syncing failed with E011: Item in folder ordering is not an actual child: {"id":813,"type":"bookmark"}
E011: Item in folder ordering is not an actual child: {"id":1353,"type":"bookmark"}
E012: Folder ordering is missing some of the folder's children
E012: Folder ordering is missing some of the folder's children
E011: Item in folder ordering is not an actual child: {"id":1333,"type":"bookmark"}
onSyncFail

Please advise, thx.

<!-- gh-comment-id:523911280 --> @xelcho commented on GitHub (Aug 22, 2019): So on my windows 10 firefox quantum client, the sync can not complete the debug log: Bookmark unchanged Syncing failed with E011: Item in folder ordering is not an actual child: {"id":813,"type":"bookmark"} E011: Item in folder ordering is not an actual child: {"id":1353,"type":"bookmark"} E012: Folder ordering is missing some of the folder's children E012: Folder ordering is missing some of the folder's children E011: Item in folder ordering is not an actual child: {"id":1333,"type":"bookmark"} onSyncFail Please advise, thx.
Author
Owner

@marcelklehr commented on GitHub (Aug 23, 2019):

@xelcho uh,oh. These errors suggest an inconsistency occurring somewhere in the sync algorithm. Are you using the new beta for this? Did you enable a different syncing strategy?

<!-- gh-comment-id:524487270 --> @marcelklehr commented on GitHub (Aug 23, 2019): @xelcho uh,oh. These errors suggest an inconsistency occurring somewhere in the sync algorithm. Are you using the new beta for this? Did you enable a different syncing strategy?
Author
Owner

@bhlevca commented on GitHub (Aug 24, 2019):

Hi,

I don't use the beta version and I get occasionally the same errors.

Bogdan

On Fri, Aug 23, 2019, 19:00 Marcel Klehr, notifications@github.com wrote:

@xelcho https://github.com/xelcho uh,oh. These errors suggest an
inconsistency occurring somewhere in the sync algorithm. Are you using the
new beta for this? Did you enable a different syncing strategy?


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/marcelklehr/floccus/issues/347?email_source=notifications&email_token=AABMRXT6EWEYYSAFOW64SMLQGBTZ7A5CNFSM4IKJRT5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5BQUZQ#issuecomment-524487270,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABMRXWDGLWGCZPWER7UL2DQGBTZ7ANCNFSM4IKJRT5A
.

<!-- gh-comment-id:524504455 --> @bhlevca commented on GitHub (Aug 24, 2019): Hi, I don't use the beta version and I get occasionally the same errors. Bogdan On Fri, Aug 23, 2019, 19:00 Marcel Klehr, <notifications@github.com> wrote: > @xelcho <https://github.com/xelcho> uh,oh. These errors suggest an > inconsistency occurring somewhere in the sync algorithm. Are you using the > new beta for this? Did you enable a different syncing strategy? > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/marcelklehr/floccus/issues/347?email_source=notifications&email_token=AABMRXT6EWEYYSAFOW64SMLQGBTZ7A5CNFSM4IKJRT5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5BQUZQ#issuecomment-524487270>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AABMRXWDGLWGCZPWER7UL2DQGBTZ7ANCNFSM4IKJRT5A> > . >
Author
Owner

@xelcho commented on GitHub (Aug 25, 2019):

@marcelklehr So I am not using the beta, same version from start of this post (3.3.2)

Current situation:
Home Client (Ubuntu) works fine, I can add bookmarks and folders and it syncs as it should.
My work Client (Windoz 10) with firefox is the machine having fits.

Please advise.

I'm considering download the bookmarks from my work machine, wipe them and rebuild from sync.

<!-- gh-comment-id:524632834 --> @xelcho commented on GitHub (Aug 25, 2019): @marcelklehr So I am not using the beta, same version from start of this post (3.3.2) Current situation: Home Client (Ubuntu) works fine, I can add bookmarks and folders and it syncs as it should. My work Client (Windoz 10) with firefox is the machine having fits. Please advise. I'm considering download the bookmarks from my work machine, wipe them and rebuild from sync.
Author
Owner

@marcelklehr commented on GitHub (Aug 26, 2019):

I've just released v3.4.0. You can now easily run the latest code.

<!-- gh-comment-id:524679921 --> @marcelklehr commented on GitHub (Aug 26, 2019): I've just released v3.4.0. You can now easily run the latest code.
Author
Owner

@xelcho commented on GitHub (Aug 26, 2019):

Thanks!

I ran it with the new release on the windows client and it hung, same issue (E011...) . So I carried through with my plan to backup, then delete all book marks and then sync.

Seems good for now.
The result is a clean sync, now I have to do a diff on the backup and current book marks. :)

<!-- gh-comment-id:524917794 --> @xelcho commented on GitHub (Aug 26, 2019): Thanks! I ran it with the new release on the windows client and it hung, same issue (E011...) . So I carried through with my plan to backup, then delete all book marks and then sync. Seems good for now. The result is a clean sync, now I have to do a diff on the backup and current book marks. :)
Author
Owner

@marcelklehr commented on GitHub (Sep 2, 2019):

@bhlevca Feel free to open a separate issue with your errors

<!-- gh-comment-id:527075209 --> @marcelklehr commented on GitHub (Sep 2, 2019): @bhlevca Feel free to open a separate issue with your errors
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:1477332279 --> @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#289
No description provided.