keybase / keybase/keybase-issues
command line id/track need a --refresh
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
I id‐ed a user before they had commit any proofs, which meant further `keybase id` after then did not update as they added twitter, github. Time frame for this was over 20 minutes…
After removing some cache files in ~/.keybase/keybase.idb/ (yes, I know that was very daft), `keybase id` then correctly showed the new proofs.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the stale proof display with `keybase id` and `keybase track` after adding proofs, then inspect how their cached data under `~/.keybase/keybase.idb/` is refreshed. Done means both commands support a `--refresh` option that updates displayed proofs without manually removing cache files.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100