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.

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

Show the actual error in login error toast #1357

Closed
Efefefef opened this issue Oct 15, 2018 · 3 comments
Closed

Show the actual error in login error toast #1357

Efefefef opened this issue Oct 15, 2018 · 3 comments
Assignees

Comments

@Efefefef
Copy link
Contributor

Efefefef commented Oct 15, 2018

Description of the problem

Sometimes tests are failing because of some connection error
It is scary and uncertain what was the actual error

image

Suggested solution

Would be helpful to show the error to know if it is a typo or too many requests or server is down
And its not bad to show more verbous message to the user

@4fryn
Copy link

4fryn commented Oct 16, 2018

+1 yes please :)

@michaeltomasik
Copy link
Contributor

I have an issue related to this #1274

@slaweet
Copy link
Contributor

slaweet commented Oct 18, 2018

Specification

  • If the response contains an error message, then it should say Unable to connect to the node, Error: {message}, Status code: {code}
  • If the response doesn't contain an error message, then it should say Unable to connect to the node, Status code: {code}
  • If no response, then it should say Unable to connect to the node, no response from the server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants