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

Improve the auto disable profiles after 10 failures #1660

Closed
bigdiff opened this issue Jun 25, 2024 · 2 comments
Closed

Improve the auto disable profiles after 10 failures #1660

bigdiff opened this issue Jun 25, 2024 · 2 comments

Comments

@bigdiff
Copy link
Contributor

bigdiff commented Jun 25, 2024

Describe the feature you'd like to request

Now after disconnecting for a little bit all my profiles across multiple browsers are disabled and I have to manually go through all of them and enable (turn on auto-sync) again.

I get this error messages:

Failed to fetch Last synchronized: 7 hours ago
Retried 10 times before disabling this profile

Describe the solution you'd like

I think it is best to increase the interval which it auto-syncs retries after a failure. For example if I've set the sync interval to 20 minutes when it first fails in should increase the interval to 1 hour then to 2 hours after the next failure then 4, 8, 16, 32 ...etc (these numbers are just exmaples)

This to avoid the problem mentioned before. Or an option can be added to disable the "disable auto syncing after 10 failures"

Describe alternatives you've considered

The alternative now is to go through the 20 or so profiles I have in each browser and enable them again 😅 or export all the profiles change the option in the json and import them again lol

Copy link

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 💙

@marcelklehr
Copy link
Member

@bigdiff You're right. Exponential backoff is a better way to handle this. Thanks for the feedback! :)

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

No branches or pull requests

2 participants