-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Config] Fixed issue between ComposerResource and symfony/phpunit-bridge #40092
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
What effect does this have in practice? |
the cache is not fresh, so the container keep rebuilding. With this patch:
Without this patch:
I forgot to mention something: The client had BIG performance issue because in functional tests they are using this kind of code |
b2fd8b0
to
3295b10
Compare
I feel like the current patch fixes a symptom rather than a cause. Why doesn't ComposerResource work here? |
I'll try to represent what's going on:
Is it more clear? |
@lyrixx this could happen with any tool which is installed as a separate installation than your project vendor folder while also relying on a composer autoloader. this is not specific to the phpunit-bridge. |
What about using |
I propose #40098 instead. |
…irs (nicolas-grekas) This PR was merged into the 4.4 branch. Discussion ---------- [DependencyInjection] fix tracking of changes to vendor/ dirs | Q | A | ------------- | --- | Branch? | 4.4 | Bug fix? | yes | New feature? | no | Deprecations? | no | Tickets | Fix #40092 | License | MIT | Doc PR | - Commits ------- 6867475 [DI] fix tracking of changes to vendor/ dirs
We using
symfony/phpunit-bridge
package, it installs a newpackage in
vendor/bin/.phpunit
. This package comes with itsown autoloader. When booting symfony with
simple-phpunit
, theautoloader is used and discovered here. But we do not want to
affect the container freshness for this package.