Error Reading Keybase/private
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
The app notified me via macOS notification that it was unable to access the /private/ folder and asked that I generate a log and send. Being a good direction-follower, I did just that.
I appear to still be able to access my /private/ folders.
my log id: ca80d76e6ea43d5dafeb351c
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 log ID ca80d76e6ea43d5dafeb351c and investigate the macOS notification about being unable to access /private/. Reproduce the report if possible and compare it with the user's continued ability to access /private/; done means the cause is identified and the notification behavior is corrected or explained.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100