keybase / keybase/keybase-issues
Unclear error message during provisioning
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
I provisioned a new device using an existing device and received an error message (Error in transport: Operation timed out) followed by a success message. Here's an output screenshot:

It is unclear to me:
1. What the error actually is/means vis-a-vis the operation it intends to flag and
2. Whether it was relevant since the operation _seems_ to have been successful
Did some part of the operation actually time out and thus some part of provisioning fail? If the timeout is relevant, that error message would benefit from being specific and/or having information re:next steps/troubleshooting.
Error messages: the gift that keeps on giving :)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing provisioning a new device from an existing device and examine the sequence around the transport timeout and subsequent success message. Trace the provisioning flow to determine whether the timeout indicates a failed sub-operation, then make the resulting error status and troubleshooting guidance unambiguous.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100