Un-substituted ${username_service} in Twitter assertion failure message
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I changed the name on my Twitter account from resiak to wjjjjt this morning. The error from keybase id about my previous proof in the name of resiak contains a literal ${username_service}:
% keybase id resiak@twitter
▶ INFO Identifying wjt
✔ public key fingerprint: 1E68 E58C F255 8883 0164 5B56 3422 DC0D 7AD4 82A7
[ irrelevant, passing assertions removed ]
✔ "resiak" on twitter failed: Bad post authored: wanted ${username_service} but got wjjjjt (code=203) [cached 2017-02-22 08:58:41 GMT]
▶ ERROR Unmet remote assertions for user "wjt"
I also notice that it has a check mark, rather than (say) a cross.
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 id resiak@twitter entry point and use the reported assertion failure as the reproduction case. Trace the Twitter proof failure output; done means the username placeholder is substituted correctly and the failure indicator accurately reflects the failed assertion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100