Socket error for ls'ing /keybase/public/<tracked user>/ for the first time.
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
This was a simple ls of a /keybase/public/ whom I track. Though it should be noted that the second ls succeeded.
my log id: 741501d8913b0769c52ec31c
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 log id 741501d8913b0769c52ec31c and compare the first and second ls of /keybase/public/. Trace the socket error associated with the initial access; done means the first ls succeeds without the reported error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100