KBFS input/output error for folders including Keybase users without keys
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Adding a private folder that includes a Keybase user that hasn't yet associated a key fails without a descriptive error message. The folder opens in the file manager, but it doesn't appear in the directory structure, throws "Error opening directory ... Input/output error", and fails to add the folder to the list of 'favorites' in the Keybase GUI.
ORIGINAL REPORT (before I realized mkdir is not involved):
I tried mkdir /keybase/private/user1,user2,user3 to see what would happen. No folder is created, but attempting to create this folder using the GUI now causes the folder to open in my file manager, but it throws "Error opening directory ... Input/output error" and the folder does not appear in /keybase/private/. Stopping and restarting Keybase doesn't fix.
my log id: 03d97974fe5904263931461c
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
The report names no source file or test. Start by reproducing the private-folder case with a Keybase user who has no associated key, then inspect the behavior and the provided log ID. Done means the unsupported folder state produces a descriptive error rather than a generic I/O error and does not leave the GUI or directory view inconsistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100