For every package manager operation, it first calls composer multiple times to ensure that:
- composer exists
- that the executable is actually composer
- that the composer version is correct
This can add seconds before anything actually gets called.
I think we could consider moving these checks to the automatic updates and project browser modules, and they could run them before undertaking series of operations and potentially cache the check for an hour or so. If composer is valid, it's not going to become invalid again a few seconds later.
Noticed this when profiling package_manager tests, but it's a runtime performance issue in package manager.
| Comment | File | Size | Author |
|---|---|---|---|
| Screenshot from 2026-07-25 22-23-15.png | 575.54 KB | catch |
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #3
catchComment #4
catchTest failures show that we don't explicitly validate before creating a sandbox, so added explicit validation there.
Comment #5
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #6
catchRebased.