[GH-ISSUE #1966] Sync error: Expected "Two strings separated by '\x00'" but received ... #1317

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

Originally created by @johanvanmol on GitHub (May 27, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1966

Which version of floccus are you using?

v.5.4.5

How many bookmarks do you have, roughly?

500

Are you using other means to sync bookmarks in parallel to floccus?

No

Sync method

Git

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

Chrome Versie 137.0.7151.41 (Officiële build) (64-bits)

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 get a sync error:

Expected "Two strings separated by '\x00'" but received "50a7e708aa4423ce9c06e77cb00ca0fcd83bf939 refs/heads/mainreport-status report-status-v2 delete-refs side-band-64k ofs-delta atomic object-format=sha1 quiet agent=github/spokes-receive-pack-acac8763c60f636c44baaf5c3887895cf5f55c30 session-id=8EBC:3C2FA3:87BAC85:8B29A94:683583CE push-optio ". | Last synchronized: 1 uur ago

Expected Behavior

Normal syncing: periodically and when I manually press the sync button.

To Reproduce

I didn't do anything special.
My Floccus is set to auto sync every 15 minutes.
Trying to sync manually gives the same error.

floccus-5.4.5-2025-05-27-redacted.log

Debug log provided

  • I have provided a debug log file
Originally created by @johanvanmol on GitHub (May 27, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1966 ### Which version of floccus are you using? v.5.4.5 ### How many bookmarks do you have, roughly? 500 ### Are you using other means to sync bookmarks in parallel to floccus? No ### Sync method Git ### Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please. Chrome Versie 137.0.7151.41 (Officiële build) (64-bits) ### 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 get a sync error: Expected "Two strings separated by '\x00'" but received "50a7e708aa4423ce9c06e77cb00ca0fcd83bf939 refs/heads/mainreport-status report-status-v2 delete-refs side-band-64k ofs-delta atomic object-format=sha1 quiet agent=github/spokes-receive-pack-acac8763c60f636c44baaf5c3887895cf5f55c30 session-id=8EBC:3C2FA3:87BAC85:8B29A94:683583CE push-optio ". | Last synchronized: 1 uur ago ### Expected Behavior Normal syncing: periodically and when I manually press the sync button. ### To Reproduce I didn't do anything special. My Floccus is set to auto sync every 15 minutes. Trying to sync manually gives the same error. [floccus-5.4.5-2025-05-27-redacted.log](https://github.com/user-attachments/files/20454453/floccus-5.4.5-2025-05-27-redacted.log) ### Debug log provided - [x] I have provided a debug log file
kerem 2026-02-25 22:39:40 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@github-actions[bot] commented on GitHub (May 27, 2025):

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. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings.
I'm Marcel. I created floccus a few years ago, and have been maintaining it 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. It helps when you stick around to answer follow up questions I may have,
as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report
and the issue cannot be solved without it, I will have to close the issue after a while.
Note also that GitHub in general 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!
If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way,
I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already.
You can find donation options at https://floccus.org/donate/. Thank you!

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

Thank you for reading through this primer. I look forward to working with you on this issue!
Cheers 💙

<!-- gh-comment-id:2911885154 --> @github-actions[bot] commented on GitHub (May 27, 2025): 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. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings. I'm Marcel. I created floccus a few years ago, and have been maintaining it 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. It helps when you stick around to answer follow up questions I may have, as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report and the issue cannot be solved without it, I will have to close the issue after a while. Note also that GitHub in general 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! If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way, I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already. You can find donation options at <https://floccus.org/donate/>. Thank you! 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 Nextcloud 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. Thank you for reading through this primer. I look forward to working with you on this issue! Cheers :blue_heart:
Author
Owner

@LaurentOngaro commented on GitHub (May 27, 2025):

I've got the same issue.
All my syncs were working well yesterday, but they are broken with the same error today.
I've done nothing special.
No update of floccus or of my browser
I use Brave

<!-- gh-comment-id:2911925358 --> @LaurentOngaro commented on GitHub (May 27, 2025): I've got the same issue. All my syncs were working well yesterday, but they are broken with the same error today. I've done nothing special. No update of floccus or of my browser I use Brave
Author
Owner

@1995parham commented on GitHub (May 27, 2025):

Yes, same here. I think maybe something in the GitHub API may changed.

<!-- gh-comment-id:2911997989 --> @1995parham commented on GitHub (May 27, 2025): Yes, same here. I think maybe something in the GitHub API may changed.
Author
Owner

@lixpng commented on GitHub (May 27, 2025):

I've got the same issue. All my syncs were working well yesterday, but they are broken with the same error today. I've done nothing special. No update of floccus or of my browser I use Brave

Same as you.

<!-- gh-comment-id:2912248071 --> @lixpng commented on GitHub (May 27, 2025): > I've got the same issue. All my syncs were working well yesterday, but they are broken with the same error today. I've done nothing special. No update of floccus or of my browser I use Brave Same as you.
Author
Owner

@exoticatom commented on GitHub (May 27, 2025):

same issue started today when syncing with github. Firefox, or Chrome, or Brave.
I tried recreating profile, it didn't help.

<!-- gh-comment-id:2912271574 --> @exoticatom commented on GitHub (May 27, 2025): same issue started today when syncing with github. Firefox, or Chrome, or Brave. I tried recreating profile, it didn't help.
Author
Owner

@adcin commented on GitHub (May 27, 2025):

I have the same Issue in Brave "Version 1.78.102 Chromium: 136.0.7103.113 (Official Build) (64-bit)" with Floccus version 5.5.3.1. The last successfull sync with my GitHub repo was yesterday 2025-05-26 at about 22:00 UTC. But this was also the time I shut down the pc.

For redundancy reasons I have a 2nd sync profile to Google-Drive and this one works fine.

<!-- gh-comment-id:2912483747 --> @adcin commented on GitHub (May 27, 2025): I have the same Issue in Brave "`Version 1.78.102 Chromium: 136.0.7103.113 (Official Build) (64-bit)`" with Floccus version 5.5.3.1. The last successfull sync with my GitHub repo was yesterday 2025-05-26 at about 22:00 UTC. But this was also the time I shut down the pc. For redundancy reasons I have a 2nd sync profile to Google-Drive and this one works fine.
Author
Owner

@marcelklehr commented on GitHub (May 27, 2025):

Thank you for reporting this! It seems this is an issue specific to the combination of isomorphic-git and github, it seems: https://github.com/isomorphic-git/isomorphic-git/issues/2102

<!-- gh-comment-id:2912498384 --> @marcelklehr commented on GitHub (May 27, 2025): Thank you for reporting this! It seems this is an issue specific to the combination of isomorphic-git and github, it seems: https://github.com/isomorphic-git/isomorphic-git/issues/2102
Author
Owner

@O5ten commented on GitHub (May 27, 2025):

The maintainer has now raised the question to github. Join the discussion! 👍
https://github.com/orgs/community/discussions/160400

<!-- gh-comment-id:2912518654 --> @O5ten commented on GitHub (May 27, 2025): The maintainer has now raised the question to github. Join the discussion! :+1: https://github.com/orgs/community/discussions/160400
Author
Owner

@rgdevment commented on GitHub (May 27, 2025):

same issue :(

<!-- gh-comment-id:2913180364 --> @rgdevment commented on GitHub (May 27, 2025): same issue :(
Author
Owner

@prono69 commented on GitHub (May 27, 2025):

Same here . I was trying everything 😭 but still no luck and then I came here and found out that GitHub did something sussy 🥲👍

<!-- gh-comment-id:2913378961 --> @prono69 commented on GitHub (May 27, 2025): Same here . I was trying everything 😭 but still no luck and then I came here and found out that GitHub did something sussy 🥲👍
Author
Owner

@O5ten commented on GitHub (May 27, 2025):

Seems to work now again.

<!-- gh-comment-id:2914017797 --> @O5ten commented on GitHub (May 27, 2025): Seems to work now again.
Author
Owner

@prono69 commented on GitHub (May 28, 2025):

Yes, it's working again.

<!-- gh-comment-id:2914864072 --> @prono69 commented on GitHub (May 28, 2025): Yes, it's working again.
Author
Owner

@johanvanmol commented on GitHub (May 28, 2025):

Confirmed. Sync is working again across all my browsers.
Floccus version is still 5.4.5. It must have been an external issue. I'll close this issue.

<!-- gh-comment-id:2915153188 --> @johanvanmol commented on GitHub (May 28, 2025): Confirmed. Sync is working again across all my browsers. Floccus version is still 5.4.5. It must have been an external issue. I'll close this issue.
Author
Owner

@marcelklehr commented on GitHub (May 28, 2025):

Thanks everyone for your cooperation. Indeed, GitHub rolled back an update of their Git proxy which broke access with isomorphic-git and some other clients.

<!-- gh-comment-id:2915432256 --> @marcelklehr commented on GitHub (May 28, 2025): Thanks everyone for your cooperation. Indeed, GitHub rolled back an update of their Git proxy which broke access with isomorphic-git and some other clients.
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#1317
No description provided.