keybase / keybase/client

Keybase Chat apparently stopped

Open
#6,092 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

After the MacBook went to sleep mode and got woken up the Keybase client complained about a read timeout and asked for sending log messages.

my log id: 8f51468d930a27f7a95e511c

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report concerns the Keybase client on macOS after a sleep/wake transition and mentions a read timeout plus log ID 8f51468d930a27f7a95e511c. Start by reviewing the submitted logs and the chat client’s sleep/wake handling; done means identifying the cause and confirming that chat reconnects without the timeout.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.