Closed NyanHelsing closed 6 years ago
A better example
{!r}
mfr.extensions.tabular.exceptions.UnexpectedFormattingError: 500, Unexpected formatting error. <EmptyTableError(400, Table empty or corrupt.)>
mfr.extensions.tabular.exceptions.UnexpectedFormattingError: 500, Unexpected formatting error. 400, Table empty or corrupt.
As discussed with @birdbrained , we don't want the detailed error message goes to the user. So (1) the general error message remains the same (2) send a log to sentry (sentry.log()
???) with detailed error message and stack trace.
Ticket
https://openscience.atlassian.net/browse/SVCS-612
Purpose
This changes the logging message to include the name of the error that actually triggered it to assist in debugging tasks
Changes
Adds the nae of the error to the log message
Side effects
Better debugging
QA Notes
Deployment Notes