Empty commits in git repo

[plantroon]

Which version of floccus are you using?

5.7.0

How many bookmarks do you have, roughly?

130

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 142.0.7444.60

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

Every sync (triggered manually or on schedule) creates (empty) commits even if there were no changes.

I noticed this was also dealt with in #1944, so I'll mention it here.

Expected Behavior

Do not create commit when there are no changes

To Reproduce

I am unable to reproduce this reliably. It started happening yesterday after I switched web browser, but I have since cleaned up the bookmarks repo and pushed up from the browser to recreate the file.

But when it happens:

1. trigger sync manually (or wait for scheduled sync)
2. look at your git repo and notice the empty commit
3. repeat after ~2 minutes from last sync and you'll have another such commit (with no diff)

I will update if/when I can reliably reproduce this.

Debug log provided

• I have provided a debug log file

[github-actions]

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! 💙

[plantroon]

I found an older Chromium install with the same data and Floccus 5.6.0 where this is not happening if I sync from there and leave it running. After updating to 5.7.0 it started happening there as well.

[marcelklehr]

Hi @plantroon
Thank you for taking the time to give feedback by opening this issue! I was now able to reproduce this and identify the cause. The new release should fix this.

[marcelklehr]

Fixed in 741c14b