-
Notifications
You must be signed in to change notification settings - Fork 140
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
Provide more user friendly error when SQ is down or not running #1149
Closed
Labels
Projects
Milestone
Comments
andrei-epure-sonarsource
changed the title
Provide more user friendly when SQ is down or not running
Provide more user friendly error when SQ is down or not running
May 25, 2022
github-actions
bot
assigned sebastien-marichal and unassigned costin-zaharia-sonarsource
Mar 27, 2023
github-actions
bot
assigned costin-zaharia-sonarsource and unassigned sebastien-marichal
Mar 27, 2023
github-actions
bot
assigned sebastien-marichal and unassigned costin-zaharia-sonarsource
Mar 28, 2023
github-actions
bot
assigned costin-zaharia-sonarsource and unassigned sebastien-marichal
Mar 28, 2023
github-actions
bot
moved this from Review in progress
to Reviewer approved
in S4NET Kanban
Mar 28, 2023
github-actions
bot
assigned costin-zaharia-sonarsource and unassigned sebastien-marichal
Mar 30, 2023
github-actions
bot
assigned sebastien-marichal and unassigned costin-zaharia-sonarsource
Mar 30, 2023
github-actions
bot
assigned costin-zaharia-sonarsource and unassigned sebastien-marichal
Mar 31, 2023
github-actions
bot
moved this from Review in progress
to Reviewer approved
in S4NET Kanban
Mar 31, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When SQ is not running or cannot be contacted a message with a long call stack is displayed.
We should display user-friendly message about not being able to contact the server and suggesting to check that server is running and address is correct.
Followed by the original message. Without the full stack trace.
Similar message appears when there's a typo in
/d:sonar.host.url="https://localhost:9000"
- wrong protocolThe text was updated successfully, but these errors were encountered: