nextcloud / nextcloud/files_lock
Windows clients retain stale file locks after server-side lock timeout when connection is lost
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 39
- Forks
- 10
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 48
Description
Steps to reproduce
"Temporary file lock" and "Group folder" apps are installed. User1 and User2 have write permissions to a group folder.
Both users have desktop synchronization with virtual file systems enabled. The lock_timeout setting is set on server (5 or 10 min for test - 12h in prod environment).
User1 upload a Microsoft file via web (docx, xlsx, etc..) and open it
The file is locked on server and on User2's computer
User1 looses connection with the server,
File is unlocked on server after timeout
File stay locked on other clients.
Operating system
Windows 10
Nextcloud Server version
27.1.4
Nextcloud Desktop Client version
3.10.1
Workaround
Lock and unlock the file on the web App.
Is this a bug of Temporary file lock App or Nextcloud client?
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 by reproducing the disconnect and timeout sequence with the Temporary file lock app, a group folder, and Windows desktop synchronization with virtual file systems enabled. Compare the server lock state with the state reported by other clients after lock_timeout expires; done means clients release the stale lock without requiring a web-app lock/unlock cycle.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100