nextcloud / nextcloud/files_lock
The "lock_timeout" (set by OCC command) timer should start ONLY if there are no more users in the file
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 39
- Forks
- 10
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 48
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Steps to reproduce
Bug description here : https://github.com/nextcloud/files_lock/issues/292
Bug is still present with nextcloud 30.0.6 and files_lock app 30.0.1
Expected behaviour
The lock_timeout countdown should ONLY start when there's no one left in the file
Actual behaviour
The lock_timeout countdown start when the file is opened.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked reproduction issue and trace the OCC command's lock_timeout handling in this repository. Determine when the file is considered to have no remaining users, then verify that the countdown begins only at that point. Done means the reported behavior is corrected and the existing reproduction no longer shows the timeout starting while the file is open.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100