#26206 Add information about currently reindexed index.

[lbajsarowicz]

Description (*)

Answers the need for more information about failed reindex.

Change additionally improves performance by replacing foreach() { array_merge() } with array_merge(...$args). Additionally with -v debug information included about exception trace.

Fixed Issues (if relevant)

1. Missing information about currently reindexed index on failure #26206 Missing information about the currently reindexed index on failure

Manual testing scenarios (*)

1. Run desired reindex. Expect the reindex name to be immediately visible

Questions or comments

N/A

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @lbajsarowicz. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

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

[lbajsarowicz]

Clean 2.4-develop also fails the same test for me. Rolling back my changes to see if it's issue related with 2.4-develop itself, or can I fix that.

The integration test is - in general - useless, written wrong way, so I'm not sure about it's corectness.

[lbajsarowicz]

#26225 Has to be merged first (!).
↑ is already merged to this feature branch, to pass the Integration and Functional Tests.

[magento-engcom-team]

Hi @pmclain, thank you for the review.
ENGCOM-6533 has been created to process this Pull Request
✳️ @pmclain, could you please add one of the following labels to the Pull Request?

Label	Description
Auto-Tests: Covered	All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered	Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required	Changes in Pull Request does not require coverage by auto-tests

[engcom-Alfa]

✔️ QA Passed

[m2-assistant]

Hi @lbajsarowicz, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.