Provide full backtrace in exception log

[onlinebizsoft]

Summary (*)

Since Magento 2.2.x and newer, Magento do not provide a full backtrace for exception. Refer to this ticket https://github.com/magento/magento2/issues/13128

Examples (*)

The issue can be seen whenever an exception happen. I know with xdebug and a test case then developer can get a backtrace on their local environment but in fact, bugs are hard to replicate sometime and when it happens randomly on a production environment, a full backtrace is helpful

Currently all information we get for an exception as below [2018-01-11 09:29:22] main.CRITICAL: Item (Magento\Catalog\Model\Product\Interceptor) with the same ID "1986" already exists. {"exception":"[object] (Exception(code: 0): Item (Magento\Catalog\Model\Product\Interceptor) with the same ID "1986" already exists. at /home/led/domain.com/vendor/magento/framework/Data/Collection.php:404)"} [] [2018-01-11 09:30:27] main.CRITICAL: Item (Magento\Catalog\Model\Product\Interceptor) with the same ID "1986" already exists. {"exception":"[object] (Exception(code: 0): Item (Magento\Catalog\Model\Product\Interceptor) with the same ID "1986" already exists. at /home/led/domain.com/vendor/magento/framework/Data/Collection.php:404)"} [] [2018-01-11 09:42:29] main.CRITICAL: Item (Magento\Catalog\Model\Product\Interceptor) with the same ID "1986" already exists. {"exception":"[object] (Exception(code: 0): Item (Magento\Catalog\Model\Product\Interceptor) with the same ID "1986" already exists. at /home/led/domain.com/vendor/magento/framework/Data/Collection.php:404)"} []

We expected something as below Exception #0 (Exception): Item (Magento/CatalogInventory/Model/Stock/Status/Interceptor) with the same ID "98" already exists.

0 lib/internal/Magento/Framework/Data/AbstractSearchResult.php(233): Magento/Framework/Data/AbstractSearchResult->addItem(Object(Magento/CatalogInventory/Model/Stock/Status/Interceptor))

1 lib/internal/Magento/Framework/Data/AbstractSearchResult.php(102): Magento/Framework/Data/AbstractSearchResult->load()

2 app/code/Magento/CatalogInventoryConfigurableProduct/Plugin/GetInStockAttributeOptionsPlugin.php(62): Magento/Framework/Data/AbstractSearchResult->getItems()

3 lib/internal/Magento/Framework/Interception/Interceptor.php(146): Magento/CatalogInventoryConfigurableProduct/Plugin/GetInStockAttributeOptionsPlugin->afterGetAttributeOptions(Object(Magento/ConfigurableProduct/Model/AttributeOptionProvider/Interceptor), Array, Object(Magento/Catalog/Model/ResourceModel/Eav/Attribute/Interceptor), '128')

.......... ..............)

Proposed solution

The issue were explained and proposed a solution here https://github.com/magento/magento2/issues/13128#issuecomment-816591671

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• [ ] Severity: S0 - Affects critical data or functionality and leaves users with no workaround.
• [ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [x] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @onlinebizsoft. Thank you for your report. To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

  :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[onlinebizsoft]

@MJTheOne @daiduongvo18 @hostep @lbajsarowicz

[lbajsarowicz]

I'm not sure what feedback you expect?

developer can get a backtrace on their local environment

Actually, it's not true, something you've noticed in the logs but you have no idea why this class was called. To investigate the issue, you need information about who called it and how.

[onlinebizsoft]

I'm not sure what feedback you expect?

developer can get a backtrace on their local environment

Actually, it's not true, something you've noticed in the logs but you have no idea why this class was called. To investigate the issue, you need information about who called it and how.

I'm just tagging you here to follow up the new issue :) You know with xdebug and if you can replicate the issue locally then you can have backtrace information.

[m2-assistant[bot]]

Hi @engcom-Echo. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• [ ] 5. Add label Issue: Confirmed once verification is complete.

• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[onlinebizsoft]

@engcom-Echo will this be available for 2.4.3 please? :)

[onlinebizsoft]

Can you take a look at @mrtuvn @ihor-sviziev ?

[ihor-sviziev]

Hi @onlinebizsoft, Could you provide more information on how to reproduce the issue, what is expected, and actual results? Some screenshots or logs would be beneficial.

[onlinebizsoft]

@ihor-sviziev I have edit the description to add more information

[ihor-sviziev]

@sidolov @gabrieldagama @sivaschenko, I think this should be a high priority, as missing the exception stack trace is a terrible thing for debugging issues on production.

PS: we have a custom logger that includes the exception stack trace. That's why I didn't notice it earlier.