"read operation took too long"
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Read timeout in /keybase/private..., asked by app to send a log so here it is, but also during 'keybase log send':
Continue sending logs to keybase.io? (type 'YES' to confirm): YES
▶ WARNING error opening log "/Users/[username]/Library/Logs/keybase.updater.log": open /Users/[username]/Library/Logs/keybase.updater.log: no such file or directory
my log id: 615bf1180e4369dfda13e51c
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 reproducing the read timeout under /keybase/private and the keybase log send command on macOS. Inspect how the command handles the missing /Users/[username]/Library/Logs/keybase.updater.log; done should include a confirmed diagnosis and a clear expected outcome for both reported errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, macos
- Domain
- backend, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100