Better exception handling during cli commands

[PascalBrouwers]

Preconditions (*)

1. Magento 2.3.x

Steps to reproduce (*)

1. Have a module with a wrong path in registration.php. For example set the path in vendor/magento/module-catalog/registration.php to __DIR__ . '/wrong_folder'
2. Run bin/magento setup:upgrade

Expected result (*)

1. A clear exception what actually goes wrong. Instead the general error There are no commands defined in the "setup" namespace. is displayed.

Actual result (*)

1. The general error There are no commands defined in the "setup" namespace. is displayed.

Also see: #4832

[m2-assistant]

Hi @PascalBrouwers. 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.3-develop instance - upcoming 2.3.x release

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

@PascalBrouwers 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.

[PascalBrouwers]

Made a pull request to fix this issue

[m2-assistant]

Hi @shikhamis11. 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.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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.

[magento-engcom-team]

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

• 9ffe7eb2d3e6fcbf18eb39b6b847e99b0550a028
• 2861ca40b7f550c9e8498603c9f3763b12350f90
• cd9ff1e34d8b19094b056f9c5b35909a7633d739

The fix will be available with the upcoming 2.3.4 release.

[magento-engcom-team]

Hi @PascalBrouwers. Thank you for your report.
The issue has been fixed in #24734 by @p-bystritsky in 2.3-develop branch
Related commit(s):

• dfd481d22616708a7e55d7b8757581e90ba4f41c

The fix will be available with the upcoming 2.3.4 release.