[Windows 10] KBFS on Windows assumes it owns K:, whether it does or not.
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
If another drive already owns K:, KBFS won't create the storage area, it will just silently fail.
For example, I somehow had my optical drive as K: and when I selected "Open Folders" from the Keybase popup tray thing, it opened a DVD I had in my drive.
Keybase GUI Version: 1.0.17-20160822153555+692af12
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 tracing the Windows KBFS handling reached from the “Open Folders” action and determine where the assumed K: drive is used. Done means a conflicting drive assignment is handled safely instead of silently failing or opening unrelated media; the issue names no files or tests to begin with.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100