magento2 icon indicating copy to clipboard operation
magento2 copied to clipboard

#39415 - Fixed an issue where the ExceptionHandler did not display the correct file and line number of the thrown exception.

Open GrassH opened this issue 1 year ago • 12 comments

Description (*)

Fix #39415

Fixed Issues (if relevant)

  1. Fixes magento/magento2#39415

Manual testing scenarios (*)

  1. Add the following line of code to any .phtml file: <?php throw new \Exception('Test'); ?>
  2. In developer mode, navigate to the page corresponding to the modified .phtml file.
  3. An error will be thrown, displaying the following exception message: Exception #0 (Exception): "Test" thrown at [app/code/Magento/Catalog/view/frontend/templates/product/list.phtml:7]

Contribution checklist (*)

  • [x] Pull request has a meaningful description of its purpose
  • [x] All commits are accompanied by meaningful commit messages
  • [ ] All new or changed code is covered with unit/integration tests (if applicable)
  • [ ] README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
  • [ ] All automated tests passed successfully (all builds are green)

GrassH avatar Dec 10 '24 02:12 GrassH

Hi @GrassH. Thank you for your contribution! Here are some useful tips on how you can test your changes using Magento test environment. :exclamation: Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s) For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:
  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests
  13. Semantic Version Checker

You can find more information about the builds here :information_source: Run only required test builds during development. Run all test builds before sending your pull request for review.


For more details, review the Code Contributions documentation. Join Magento Community Engineering Slack and ask your questions in #github channel.

m2-assistant[bot] avatar Dec 10 '24 02:12 m2-assistant[bot]

@magento run all tests

GrassH avatar Dec 10 '24 02:12 GrassH

@magento run all tests

GrassH avatar Dec 10 '24 06:12 GrassH

@magento run all tests

GrassH avatar Dec 11 '24 01:12 GrassH

@magento run all tests

GrassH avatar Dec 13 '24 08:12 GrassH

@magento run all tests

GrassH avatar Dec 16 '24 01:12 GrassH

@magento run all tests

GrassH avatar Dec 19 '24 00:12 GrassH

@magento run all tests

GrassH avatar Dec 23 '24 01:12 GrassH

@magento run all tests

GrassH avatar Dec 31 '24 00:12 GrassH

@magento run all tests

GrassH avatar Jan 02 '25 01:01 GrassH

@magento run all tests

GrassH avatar Jan 08 '25 02:01 GrassH

@magento run all tests

GrassH avatar Dec 11 '25 05:12 GrassH