Unexpected email identity doesn't present failure message
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Keybase GUI Version: 1.0.16-20160726182352+0c2a52a
Attempting to create an encrypted share based on unknown keybase username generates a failure message. I guess I expect that.
Attempting to create an encrypted share based on unknown keybase email identity does not generate a failure message. I would expect that if the previous case presented a failure message.
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 by reproducing the encrypted-share flow in the Keybase GUI with an unknown username and then an unknown email identity. Trace where each failure is surfaced and consider the work complete when both cases present consistent failure messages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100