starred/floccus

Fork 0

mirror of https://github.com/floccusaddon/floccus.git synced 2026-04-26 06:35:59 +03:00

[GH-ISSUE #1769] Feature: Allow user to manually clear lock #1182

New issue

Closed

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

kerem commented

2026-02-25 22:39:14 +03:00

Owner

Originally created by @joshqou on GitHub (Nov 18, 2024).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1769

Describe the feature you'd like to request

Floccus currently doesn't have any self-contained way to clear any bugged out locks which can be created from network/server issues or other floccus agents misbehaving.

Describe the solution you'd like

An additional button under dangerous actions, with a confirmation prompt before clearing the lock.

Describe alternatives you've considered

n/a; Floccus isn't able to determine if a lock being held improperly. Having floccus locks held for a set duration could be used to prevent infinite locks however that could cause issues on it's own if two floccus agents have different system times.

Originally created by @joshqou on GitHub (Nov 18, 2024). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1769 ### Describe the feature you'd like to request Floccus currently doesn't have any self-contained way to clear any bugged out locks which can be created from network/server issues or other floccus agents misbehaving. ### Describe the solution you'd like An additional button under dangerous actions, with a confirmation prompt before clearing the lock. ### Describe alternatives you've considered _n/a;_ Floccus isn't able to determine if a lock being held improperly. Having floccus locks held for a set duration _could_ be used to prevent infinite locks however that could cause issues on it's own if two floccus agents have different system times.

kerem

2026-02-25 22:39:14 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-25 22:39:15 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Nov 18, 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 💙

@github-actions[bot] commented on GitHub (Nov 18, 2024): 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. 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 :blue_heart:

kerem commented

2026-02-25 22:39:15 +03:00

Author

Owner

@JGKle commented on GitHub (Nov 28, 2024):

Strongly agree here. I keep having this issue, & keep finding myself searching for how I fixed it :P I'm using git as the backend, most of the (many) issue reports related to this are about WebDAV. A way to force-clear the lock when I'm certain there are no other clients running would make life a lot easier.

@JGKle commented on GitHub (Nov 28, 2024): Strongly agree here. I keep having this issue, & keep finding myself searching for how I fixed it :P I'm using git as the backend, most of the (many) issue reports related to this are about WebDAV. A way to force-clear the lock when I'm certain there are no other clients running would make life a lot easier.

kerem commented

2026-02-25 22:39:15 +03:00

Author

Owner

@JGKle commented on GitHub (Nov 28, 2024):

Oh right, I remember how to release it. Have to go to the git repo & delete the floccus-lock-xxx tag.

@JGKle commented on GitHub (Nov 28, 2024): Oh right, I remember how to release it. Have to go to the git repo & delete the `floccus-lock-xxx` tag.

kerem commented

2026-02-25 22:39:15 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Nov 30, 2025):

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.

@github-actions[bot] commented on GitHub (Nov 30, 2025): 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.

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#1182

No description provided.

Rows
Columns