kbfsdokan crash
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
This is with latest master of dokany and commit b070619c589090a43dc7019f65d2c344a127e6f2 of taruti/wip-dokan-1-test.
Tested by logging in, browsing private files, rebooting, trying to access private files again, logging out and logging in at CLI.
my log id: 9e749c464a2508f57067c41c
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 kbfsdokan crash report and the supplied log ID 9e749c464a2508f57067c41c. Reproduce the sequence described—logging in, browsing private files, rebooting, then accessing them again—and compare it with the stated Dokany and taruti/wip-dokan-1-test revisions. Done means identifying the crash cause and confirming the sequence no longer crashes.
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
- 20/100