Track exceptions first in api helpers in case we raise again
What does this MR do and why?
Track exceptions first in api helpers in case we raise again
As discussed
in Slack (internal)
this code is problematic because we often re-raise when calling current_user
and this means we lose our original exception.
Related to https://gitlab.com/gitlab-org/gitlab/-/issues/429740
So we may be missing the real exception in the logs.
References
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.