-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
improve exception handling in Layout render #27478
Conversation
Hi @fsw. Thank you for your contribution
For more details, please, review the Magento Contributor Guide documentation. |
Hi @engcom-Charlie. The fix is good to go. But we still need the to cover it at least with a unit test. |
@magento run all tests |
Hi @rogyar, thank you for the review. |
@magento create issue |
Hi @fsw, thank you for your contribution! |
Description (*)
When layout is being rendered in production mode, all exception messages are logged to system log as critical issues. However exception stack is lost. If we pass exception to
LoggerInterface::critical
instead this data will be saved tovar/report
.Manual testing scenarios (*)
throw \Exception('test');
in a template.var/report
in addition to its message being logged.Questions or comments
Exception
toLoggerInterface::critical
a preferred way of logging issues? (I see it being used this way in other places)LocalizedException
adding any value?Contribution checklist (*)
Resolved issues: