Any reason for not printing Exception Message in ObjectManager\Factory\AbstractFactory::createObject?

[marvinhinz]

Summary (*)

When debugging an error that prevents object creation, the original exception message is not printed, its just logged. I think it would improve the developer experience when working on cli code, to see the message instantly and not having it to look up in the log.

Source of the RuntimeException:
magento/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php::createObject

Examples (*)

CLI Output:

In AbstractFactory.php line 124:
  [Magento\Framework\Exception\RuntimeException]                               
  Type Error occurred when creating object:   
  Leonex\Import\Model\Transformer\ProductData\Categories
  Exception trace: [...]

system.log:

[2020-01-27 11:36:15] main.CRITICAL: Type Error occurred when creating object: Leonex\Import\Model\Transformer\ProductData\Categories, Too few arguments to function Leonex\ETL\Logger\AbstractLog::__construct(), 0 passed in /srv/projects/rb/htdocs/magento/app/code/Leonex/Import/Model/Transformer/ProductData/Categories.php on line 63 and exactly 1 expected [] []

Proposed solution

Printing the exception message too.

[m2-assistant]

Hi @marvinhinz. 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.

@marvinhinz do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

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

[m2-assistant]

Hi @engcom-Hotel. 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: 👇

• 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.

[engcom-Hotel]

Hello @sdzhepa
This issue looks like feature request. Could you transfer this issue to the feature request repository?
Thanks for collaboration!

[slavvka]

Hi @marvinhinz. Thank you for your report.
The issue has been fixed in #26572 by @marvinhinz in 2.4-develop branch
Related commit(s):

• f2b46df5b6a681d63e4254abdb13b49733574db1
• 00971d065a6cc353b83ace91dd65f06efe2640fe
• f7f5696dc1241b886dc5bedefad8f39e691ea2c9
• f619400ac3282291a95885905d1fc44d7868c2fe
• 6448147a2521ad3df0a876f20d6e02206451cbab

The fix will be available with the upcoming 2.4.0 release.

[magento-engcom-team]

Based on the provided information internal tickets MC-34529 were created.

[magento-engcom-team]

✅ Confirmed by @sdzhepa
Thank you for verifying the issue. Based on the provided information internal tickets MC-34529 were created

Issue Available: @sdzhepa, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.