Timing out
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I've gotten a few popups saying that keybase was taking too long to something edit: read and has timed out. It also says I should keybase log send so you can take a look at it.
It's complaining about my two public folders, although my /keybase/public/donaldedgar folder seems to be working fine despite the complaint. The other one, which is shared with another user isn't currently being displayed in my filesystem.
edit: Happened again. I think the problem is in Win10 because I can't access any of the folders there, but have no problem on Linux with any of the folders.
The log id may have been from my linux box, but I can run it again on Windows if need be.
my log id: 005dc0b61fca4c69f451ba1c
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 timeout on Windows 10, comparing access to the affected public folders with the reported Linux behavior. Run keybase log send to collect a current log and use the existing log id as context; done means the folders can be accessed without timing out and the platform-specific failure is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100