Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.6k
[FrameworkBundle] [CacheWarmer] RunConfigBuilderCacheWarmer
during execution ofbin/console cache:warmup
#53512
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
carsonbot commentedJan 11, 2024
Hey! Thanks for your PR. You are targeting branch "6.4" but it seems your PR description refers to branch "7.1 for features / 5.4, 6.3, 6.4, or 7.0 for bug fixes". Cheers! Carsonbot |
ConfigBuilderCacheWarmer
during execution ofbin/console cache:warmup
ConfigBuilderCacheWarmer
during execution ofbin/console cache:warmup
I'm proposing#53672 instead, can you please give it a try? |
Thanks for submitting. Please let me know if you're still having the issue. |
…-optional (nicolas-grekas)This PR was merged into the 6.4 branch.Discussion----------[FrameworkBundle] `ConfigBuilderCacheWarmer` should be non-optional| Q | A| ------------- | ---| Branch? | 6.4| Bug fix? | yes| New feature? | no| Deprecations? | no| Issues |Fix#53496| License | MITReplaces#53512This became apparent after#50391, where the warmer is run only when compiling the container. Before, it didn't really matter.Commits-------8bd2ff8 [FrameworkBundle] ConfigBuilderCacheWarmer should be non-optional
Yes, now it works. Thanks! |
Uh oh!
There was an error while loading.Please reload this page.
ConfigBuilderCacheWarmer
is not called when executingbin/console cache:warmup
This is an attempt to fix linked issue.