-
Notifications
You must be signed in to change notification settings - Fork 9.4k
[Issue] Avoid lots of uncessary exceptions during layout XML merge loading #39877
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
As mentioned in the comment #37570 (comment) we have tried to reproduced the issue and this issue has been reproducible to us. Please refer to the below screenshot: ![]() Hence confirming the issue. Thanks. |
Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Once all required labels are present, please add |
❌ Something went wrong. Cannot create Jira issue. |
❌ Something went wrong. Cannot create Jira issue. |
✅ Jira issue https://jira.corp.adobe.com/browse/AC-14580 is successfully created for this GitHub issue. |
✅ Confirmed by @engcom-Dash. Thank you for verifying the issue. |
This issue is automatically created based on existing pull request: #37570: Avoid lots of uncessary exceptions during layout XML merge loading
Description
Related Pull Requests
See also: justbetter/magento2-sentry#113
Fixed Issues (if relevant)
No magento issue created.
Manual testing scenarios (*)
Reason
When using tools like Sentry, because of there inner workings, such exceptions still might be reported. While this is not exactly the root cause, it's always cleaner to not throw an exception and immediately catch it, if invalid cases can happen often.
This might even improve performance a bit and improves developer's experience.
Remarks
There seems some invalid XML at that place in the code happen quite often - it might be also interesting to check if that can be avoided.
This is a simple, trivial change to the code and should not break anything, so hopefully this can get triaged quickly and without to much back-and-forth about the testing procedure :-)
Contribution checklist (*)
The text was updated successfully, but these errors were encountered: