keybase / keybase/client

No UID given... on follow

Open
#5,607 3 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

I attempted to follow a user while my network was shoddy. Since then, I cannot 'id' or 'follow' that user, getting:

▶ ERROR No UID given but one was expected

I was able to get a partial response when I did a follow using USER@twitter.

Redacted version below:

$ keybase id REDACTED
▶ ERROR No UID given but one was expected
 $ keybase follow USER@twitter
▶ INFO Identifying REDACTED
✔ public key fingerprint: xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx
฿  bitcoin REDACTED
✔ "REDACTED" on twitter: https://twitter.com/REDACTED/status/REDACTED
✔ "REDACTED" on github: https://gist.github.com/REDACTED
✔ "REDACTED" on hackernews: https://news.ycombinator.com/user?id=REDACTED
✔ "REDACTED" on coinbase: https://coinbase.com/REDACTED/public-key
Is this the REDACTED you wanted? [Y/n] 
Publicly follow? [Y/n] 
▶ ERROR No resolution for name=REDACTED

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

Start by reproducing the failure with the reported keybase id REDACTED and keybase follow USER@twitter commands, then trace the CLI entry points for id and follow. Done means the previously followed user can be resolved and identified without the “No UID given” or “No resolution” errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.