keybase / keybase/keybase-issues
Confusing error messages related to automatic upgrade
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
I'm not sure what just happened.
```
rcsheets@fireball:~$ keybase follow pubal
▶ WARNING Restarting after upgrade; service is running v1.0.18-20161104184826+1bf9718, while v1.0.18-20161108170622+007a7ce is available
▶ ERROR dial unix /run/user/1000/keybase/keybased.sock: connect: no such file or directory
```
When I tried again, it worked fine, so I suspect something went wrong with what seems to be some kind of automatic upgrade process.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the reported `keybase follow pubal` command and its automatic-upgrade warning. Investigate why the service reports one version while another is available and why `/run/user/1000/keybase/keybased.sock` is temporarily missing; done means explaining or preventing the transient error during automatic upgrades.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100