Open Folder triggers 'openWithCurrentMountDir requires K prefix' error on Windows 10
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Fixed error referenced in #11209 (thanks @zanderz!) but now have a separate error. When clicking "open folder" in the app, I get a warning pane with the message openWithCurrentMountDir requires K prefix: /keybase/public/brush701. The folder does not open, though KBFS is mounted and works perfectly through explorer.
my log id: 18b9b2221029da25677e521c
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 reproducing the Open Folder action on Windows 10 with KBFS mounted, using the reported path and log ID 18b9b2221029da25677e521c. Trace why openWithCurrentMountDir rejects the /keybase/public/brush701 path; done means the folder opens without the warning pane.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100