-
Notifications
You must be signed in to change notification settings - Fork 915
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
Error message "could not connect to server" is misleading in case of server error #990
Comments
The error message is rather misleading as it isn't a connection failure but a server side error. Generating the project results in a 500 response from the server:
|
Perhaps we could split this in two, keeping this issue for improving the error message? |
Yeah, I think that sounds good. It really is two separate problems. |
This comment was marked as off-topic.
This comment was marked as off-topic.
@snicoll, I would like to work on this, could you assigned me this? |
Hey @vnayakg, i've assigned it to you. Have fun! |
Hey @vnayakg, how's it going? Are you still working on it? |
Hey @mhalbritter, @oodamien had already raised pr for this, unassigned myself |
Superseded by #1624. |
When configuring a project I encountered a weird error. I don't know the suggested way of naming project but since it isn't the artifact name I though of naming it more 'commercially' using proper diacritics of my language. Pressing 'Generate' resulted in an 'Could not connect to server. Please check your network.' error.
Edit: Tested with Firefox and Chrome.
Expected result: Correct project generation or an "Invalid name " error within the form.
Actual result: "Could not connect to server. Please check your network." popup error (see screenshot)
Sample input:
Error preview:
The text was updated successfully, but these errors were encountered: