You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When we start the server and there is no database attached, or even when the latter goes down afterwards, the moment the back-end needs to provide a result using a query to ask to the database, the error throw by the fact that mongodb is down is not catch and make all the program crash.
Would be nice to catch it and redirect to a front-end dedicated page stating that the service is currently unavailable.
And redirect the user to the previous page (in M2, the login is the only one supported due to authorization) whenever the db connection becomes available again.
To Reproduce
Steps to reproduce the behavior:
Don't initialize the db service
Start the handshake server
See error
Expected behavior
Server crash. Error level: HIGH
Screenshots
none
Desktop:
OS: Ubuntu 22.04 LTS
Browser: Chromium
Version: 108.0.5359.94 snap
The text was updated successfully, but these errors were encountered:
Describe the bug
When we start the server and there is no database attached, or even when the latter goes down afterwards, the moment the back-end needs to provide a result using a query to ask to the database, the error throw by the fact that mongodb is down is not catch and make all the program crash.
Would be nice to catch it and redirect to a front-end dedicated page stating that the service is currently unavailable.
And redirect the user to the previous page (in M2, the login is the only one supported due to authorization) whenever the db connection becomes available again.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Server crash. Error level: HIGH
Screenshots
none
Desktop:
The text was updated successfully, but these errors were encountered: