Client can't login : ▶ ERROR No resolution for name
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
$ ~ keybase login
Your keybase username or email address: myemail@foobar.com
▶ WARNING Error running Bug 3964 repairman: lksec load: no device id set, thus can't fetch server half
▶ WARNING In Bug 3964 repair: lksec load: no device id set, thus can't fetch server half
▶ ERROR No resolution for name=agusmakmun
This issue similiar with this one #5378, but here we found ERROR No resolution for name=
my log id: 397ead83494218f5d06a211c
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 login flow and the reported log ID 397ead83494218f5d06a211c; compare the failure with issue #5378. Investigate the reported No resolution for name=agusmakmun error and the Bug 3964 warnings. Done means the cause is identified and login can resolve the supplied username or email without this failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100