Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Create better error when core is not running #269

Closed
NicolasMahe opened this issue Jun 29, 2018 · 1 comment
Closed

Create better error when core is not running #269

NicolasMahe opened this issue Jun 29, 2018 · 1 comment
Labels
enhancement New feature or request
Milestone
v1.1.0

Comments

@NicolasMahe
Copy link
Member

NicolasMahe commented Jun 29, 2018 •
edited
Loading

Now, when we execute a command that requires the core, and the core is not running, we get really not user friendly error. Eg:

rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial tcp :50052: connect: connection refused"

We should detect if the core is running and return a nice message like:

The Core is not running.
Please start the Core with the command: "mesg-core start"
@NicolasMahe NicolasMahe added enhancement New feature or request application labels Jun 29, 2018
@NicolasMahe NicolasMahe added this to the v1.1.0 milestone Jul 17, 2018
@antho1404
Copy link
Member

fixed with #299

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
v1.1.0
Development

No branches or pull requests
2 participants
@antho1404 @NicolasMahe