There was a problem with the connexion to the websocket when the user was not connected to an account. In fact, we did not add a case where the user_id was nil in the connexion to the websocket which caused this error. It is fixed by adding this check, then the application_runner takes care of handling the nil user and logging him as a guest instead of a "user" role.
About this PR
Closes #
There was a problem with the connexion to the websocket when the user was not connected to an account. In fact, we did not add a case where the user_id was nil in the connexion to the websocket which caused this error. It is fixed by adding this check, then the application_runner takes care of handling the nil user and logging him as a guest instead of a "user" role.
Technical highlight/advice
How to test my changes
Checklist
I included unit tests that cover my changes
I added/updated the documentation about my changes