KBFS not usable after wifi disconnect
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
My Surface, on Windows 10 WiFi connection dropped when I put it to sleep, now I'm not able to access the K drive. KBFS does not appear to be running (from looking at keybase status) From the logs, it appears KBFS isn't logging in for some reaso. I've done keybase -d login, that appears to look normal. Any ideas what I can do to resolve this?
I've sent over my logs, its ID is e3d35881cabb35205658191c
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 with the supplied logs (ID e3d35881cabb35205658191c) and reproduce the Windows 10 sleep/WiFi-disconnect sequence. Check KBFS and the outputs of keybase status and keybase -d login to determine why KBFS does not log in or expose the K drive. Done means KBFS remains usable after reconnecting from sleep, with a regression test or documented diagnosis.
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
- 25/100