-
Notifications
You must be signed in to change notification settings - Fork 61
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
Command invalid when db is down #800
Labels
Comments
nowdays without the database the devserver crashes. |
You'd probably have to start the devserver while the database is up and then take the database down to reproduce this. |
@Askaholic Could you review my PR when you get the chance? All actions are passing including the unit test that I added. |
Askaholic
pushed a commit
that referenced
this issue
Apr 20, 2024
* Add graceful error handling for database outages * Add abort to OperationalError handling * Add unit tests for OperationalError handling in lobbyconnection * Replace apostrophe string with double quotes string * Fix unit test to pass * Fix Flake8 warnings * Rerun actions * Add logging when OperationalError is raised * Fix linting issues * Fix linting issues pt2
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When the database is down and someone tries to login the error message from the server for why it fails claims that the command is invalid rather than saying the server can't reach the db.
It would probably be good to change this just for debugging purposes
The text was updated successfully, but these errors were encountered: