All errors that are not defined is automatically setup to cause the user to be thrown out of the system (panic). This is good since for all errors that we have not thought about a logout will trigger a reset of many states, which hopefully will resolve any hidden bugs.
If a teacher cancels/press done a request that is already been handled, this causes the backend to respond with an error message. This error is not defined in the frontend and will cause it to throw out the user. A patch should add this error to the list of known errors and display a nice message instead of taking the panic.
All errors that are not defined is automatically setup to cause the user to be thrown out of the system (panic). This is good since for all errors that we have not thought about a logout will trigger a reset of many states, which hopefully will resolve any hidden bugs.
If a teacher cancels/press done a request that is already been handled, this causes the backend to respond with an error message. This error is not defined in the frontend and will cause it to throw out the user. A patch should add this error to the list of known errors and display a nice message instead of taking the panic.