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
It happens that sometimes, a request errors out and we send the response without having an ERROR log. To catch all possible errors, we could check in the handle_request function in the front end handler if the response we are about to send is an error or not.
if response.header.status != Success{error!("Sending back an error: {}", response.header.status);}
or something similar.
The text was updated successfully, but these errors were encountered:
Are you suggesting replacing the other error messages we raise in the providers with this one? Or just adding this on top of the others we already have?
I think it's good to keep the ones we have mostly because it's more easily apparent where they happened. We should maybe review all the paths and try to add logs where we miss them, but a catch-all would also be good.
That log message is also not that comprehensive - we don't copy across the old error when we convert to ResponseStatus, so we just end up not knowing why we got it in the first place.
handle_request function.
An ERROR will now be logged before the error response is sent to the
client. Issue parallaxsecond#417.
Signed-off-by: Matt Davis <[email protected]>
It happens that sometimes, a request errors out and we send the response without having an
ERROR
log. To catch all possible errors, we could check in thehandle_request
function in the front end handler if the response we are about to send is an error or not.or something similar.
The text was updated successfully, but these errors were encountered: