magento / magento/community-features
Additional repository kills Web Setup Wizard Component Manager performance
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 46
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Steps to reproduce
- Install Magento 2.1.0-rc1
- Add a custom repository to your main composer.json
- Navigate from the admin to the Web Setup Wizard
- Open the Component Manager
Expected result
- Component Manager is functional
Actual result
- Component Manager never finishes loading the grid in a timely manner (tested with 10 minute timeout)
Cause
This code here https://github.com/magento/magento2/blob/2.1.0-rc2/setup/src/Magento/Setup/Model/PackagesData.php#L361 causes an avalanche of individual composer commands for every single package including Magento ones, if more than 1 repository is present
Original Report: https://github.com/magento/magento2/issues/4986 by @fooman
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with setup/src/Magento/Setup/Model/PackagesData.php around line 361 and reproduce the Component Manager loading delay after adding a second Composer repository. Trace the package command behavior described in the issue. Done means the Component Manager grid loads in a timely manner with an additional repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100