GUI-CLI conflict when tracking
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
When using the keybase track <user> command on the CLI with the GUI client installed, the terminal brings up the GUI to nicely show the selected user's verified social accounts.
The issue is that, since the CLI doesn't know that I've pushed the "track" button in the GUI, it still waits for me to answer to Is this the <user> you wanted? [Y/n] and Publicly write tracking statement to server? [Y/n], but, as I've already written the statement on the server through the GUI, I get the ▶ ERROR Tracking statement was stale error.
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 the keybase track <user> CLI flow and the GUI client's track action described in the issue. Trace how the GUI records the tracking statement and how the CLI waits for confirmation; done means choosing Track in the GUI does not leave the CLI prompts active or produce a stale tracking statement error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100