Windows KBDB "permission denied" after other person modified shared file
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Running on windows 10. Drive letter is L: (in case that makes any difference).
I created a shard private folder with 1 other person, created a test file in it. The other person modified the file. Now I see "permission denied" to both public and private folders.
"keybase status" looks normal (I think). I haven't tried rebooting.
my log id: a0e5efaa7eedf8c28cf1911c
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 reviewing the Windows 10 reproduction details, the L: drive context, and the provided log id a0e5efaa7eedf8c28cf1911c; check the reported permission-denied behavior after another person modifies a shared file. Done means the cause is identified and access to both public and private folders is restored or the issue is clearly diagnosed.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100