-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Exception in kernel.terminal are not easy to debug #27544
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
Not sure what we can do here. Is the error logged? If you use FPM, you'd even not be able to see the error, because of fastcgi_finish_request. What is displayed in stderr in |
Maybe we can catch the error, and display an alternative message instead with a link to the profiler? |
Let's close. Using |
For #28646, I'm the one who suggested it, so I'm fine with it as a poor man solution :) |
@ogizanagi |
Description
If an exception occurs in the "kernel.terminate" listerner:
screenshot
I created a small reproducer on SF4.1: lyrixx/test@29ddcf5
(yeah, the code is YOLO :) )
Example
I don't know how we could fix that. May be we can add a special workflow for error happening on kernel.terminate because they do are specials.
WDYT?
The text was updated successfully, but these errors were encountered: