keybase / keybase/keybase-issues
If and how to report strange replies from the server?
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I'm using the command line client as it is shipped with homebrew on MacOS. From time to time strange things happen like the following:
```
keybase track wyllys
```
Yields a fat red error which ends in `error: (1701 v 1702)`.
Another thing is that a track command can emit a warning:
```
warn: When checking spaetz: BadSeqnoError: bad sequence in root: 2 != 3
warn: Likely this is a bug or transient error; but the server could be compromised
```
From a users perspective:
1) Should I report these somewhere?
2) How worried should I be? (Assume I'm paranoid. How to calm me down?)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the `keybase track wyllys` and `keybase track spaetz` cases from the issue, focusing on the reported error and BadSeqnoError output. Trace the `track` command's handling of these server replies and use the issue thread for context; done means establishing whether this is a client bug or transient response and documenting where users should report it and how concerned they should be.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- cli, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100