[core]Change file lock behavior for custom directory
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Can you change dokan/fuse behavior FileLock/FileUnlock functions from local scope to global using Lock/Unlock(libfs/file.go), like in git-remote module only for a custom directory (.kbfs_git?). So it would be possible to safely use other DVCS on KBFS.
@strib
Contributor guide
No contributing guide indexed for this repository
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 comparing the dokan/fuse FileLock and FileUnlock functions with Lock/Unlock in libfs/file.go and the corresponding behavior in the git-remote module. Trace how the custom .kbfs_git directory is handled, then verify that locking is global only for that directory and allows other DVCS operations to run safely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100