Create auto Restart Mechanism for KBFS Dokan
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Sometimes, when kbfsdokan.exe starts with the System, it fails to mount the virtual Drive. Trying to open that Drive returns the Error "N:\ is not available"(or whatever Drive Letter is assigned).
Restarting kbfsdokan.exe fixes this Issue, but it can happen again after the next restart.
My Idea would be to integrate an Check for this, if the Drive is not accessable, restart it up to 3 Times, then spit out an Error.
Win 10 64
Keybase GUI Version: 5.1.1-20191211174240+15bbb94c23
Havent found any Errors/Warnings related to Keybase or Dokan.
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 how kbfsdokan.exe starts with the system and how the virtual drive's accessibility can be checked. Define the restart behavior around the reported mount failure, including the three-attempt limit. Done means an inaccessible drive triggers automatic retries and a clear error after the limit is reached.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- desktop, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100