-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
kernel.exception is not triggered when (e.g.) new relic registers an error handler #25827
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
fabpot
added a commit
that referenced
this issue
Jan 18, 2018
…l with fatal errors (nicolas-grekas) This PR was merged into the 2.7 branch. Discussion ---------- [Debug] Always decorate existing exception handlers to deal with fatal errors | Q | A | ------------- | --- | Branch? | 2.7 | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #25827 | License | MIT | Doc PR | - Decorating the exception is seamless, let's always do it and fix handling of fatal errors. Related to #25408 also. Commits ------- 205d7ae [Debug] Always decorate existing exception handlers to deal with fatal errors
@fabpot can you reopen this issue please? It's not fixed yet 😢 |
nicolas-grekas
added a commit
that referenced
this issue
Jan 18, 2018
…he existing exception handler (nicolas-grekas) This PR was merged into the 2.7 branch. Discussion ---------- [HttpKernel] DebugHandlersListener should always replace the existing exception handler | Q | A | ------------- | --- | Branch? | 2.7 | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #25827 | License | MIT | Doc PR | - The current logic is inconsistent because replacing or not depends whether an ExceptionHandler is registered or not. Embeds tests for the previous PR on the same topic, Debug component's side. Commits ------- a4ddcc2 [HttpKernel] DebugHandlersListener should always replace the existing exception handler
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After @nicolas-grekas dug in this for me on slack, it turns out that the Symfony error handler is not registered because new relic already registers on.
Related issue seems to be an old one: https://discuss.newrelic.com/t/how-to-disable-newrelic-set-exception-handler/35544/16
Snippet of our discussion on Slack:
It seems that exceptions are still caught, as long as they are custom exceptions. Fatal errors (and possibly core exceptions) are not caught.
The class logging this (similar to the class that's redirecting it), are registered on the
kernel.exception
event (which is no longer triggered):In result with new relic:
kernel.exception
is not triggeredThe text was updated successfully, but these errors were encountered: