Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Firefox: Trying to calculate hash of a folder that isn't loaded (2024 edition) #1786

Closed
1 task
johanneskastl opened this issue Dec 1, 2024 · 8 comments
Closed
1 task
Labels

Comments

@johanneskastl
Copy link

Which version of floccus are you using?

V5.3.4

How many bookmarks do you have, roughly?

5000

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

No

Sync method

Nextcloud Bookmarks

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

Firefox 133.0

Which version of Nextcloud Bookmarks are you using? (if relevant)

14.2.6

Which version of Nextcloud? (if relevant)

v29.0.X

What kind of WebDAV server are you using? (if relevant)

No response

Describe the Bug

After putting more and more bookmarks into the folder, that is being synced from Firefox to Nextcloud Bookmarks, I am now stuck with Trying to calculate hash of a folder that isn't loaded.

Apparently this was solved in 2021 in #873

Expected Behavior

Sync should succeed.

To Reproduce

No idea.

I have put more and more bookmarks into the synced folder and removed them again, if the sync failed. Then put some of them back in, until I find the culprit.

See #1760 (reply in thread)

Debug log provided

  • I have provided a debug log file
Copy link

github-actions bot commented Dec 1, 2024

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 a few years ago, 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!
To continue the development and maintenance of this project in a sustainable way it is expected that you donate to the project when opening a ticket,
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.

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

@johanneskastl
Copy link
Author

BTW: The URL to upload the debug.log was not reachable, is it in maintenance or is the URL outdated?

@johanneskastl
Copy link
Author

OK, and after many many retries suddenly the sync is successful? Huh?

@marcelklehr
Copy link
Member

BTW: The URL to upload the debug.log was not reachable, is it in maintenance or is the URL outdated?

The URL is no longer in operation, I will remove it

@marcelklehr
Copy link
Member

Mmmh, for some reason you seem to be plagued by many problems

@marcelklehr
Copy link
Member

Can you post a redacted log here?

@johanneskastl
Copy link
Author

Can you post a redacted log here?

Sorry, while I was preparing the bug report the sync healed itself and I can no longer reproduce the problem.

As you mentioned the possibly outdated db schema, could this be related?

Otherwise, as I cannot reproduce, I propose to close this issue.

@marcelklehr
Copy link
Member

huh. Alright, then let's close. We can always reopen if it comes back again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants