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
We are using drf_standardized_errors and this package is handling unhandled exception without propagating them: ghazi-git/drf-standardized-errors#91
I would like to ask if it is possible to add the support for such scenario?
There can be 2 scenarios:
unhandled exceptions are propagated using standard django way and calling process_exception on middlewares (got_request_exception is emitted in this scenario as well)
unhandled exception is "handled" by some package and wrapped to return 500 and the signal got_request_exception is emitted.
Could we support both these scenarios as relying on signal which is used by Sentry as well is much more reliable than on middleware code which can be not called if exception is handled manually.
Best regards,
Sergei
The text was updated successfully, but these errors were encountered:
Hi dear maintainer
We are using
drf_standardized_errors
and this package is handling unhandled exception without propagating them: ghazi-git/drf-standardized-errors#91I would like to ask if it is possible to add the support for such scenario?
There can be 2 scenarios:
process_exception
on middlewares (got_request_exception
is emitted in this scenario as well)got_request_exception
is emitted.Could we support both these scenarios as relying on
signal
which is used by Sentry as well is much more reliable than on middleware code which can be not called if exception is handled manually.Best regards,
Sergei
The text was updated successfully, but these errors were encountered: