Skip to content

[FrameworkBundle] [CacheWarmer] Run ConfigBuilderCacheWarmer during execution of bin/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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

ArtemBrovko
Copy link
Contributor

@ArtemBrovko ArtemBrovko commented Jan 11, 2024

Q A
Branch? 6.4
Bug fix? yes
New feature? no
Deprecations? no
Issues Fix #53496
License MIT

ConfigBuilderCacheWarmer is not called when executing bin/console cache:warmup
This is an attempt to fix linked issue.

@carsonbot
Copy link

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".
Could you update the PR description or change target branch? This helps core maintainers a lot.

Cheers!

Carsonbot

@carsonbot carsonbot changed the title [CacheWarmer] [FrameworkBundle] Run ConfigBuilderCacheWarmer during execution of bin/console cache:warmup [FrameworkBundle] [CacheWarmer] Run ConfigBuilderCacheWarmer during execution of bin/console cache:warmup Jan 11, 2024
@nicolas-grekas
Copy link
Member

I'm proposing #53672 instead, can you please give it a try?

@nicolas-grekas
Copy link
Member

Thanks for submitting. Please let me know if you're still having the issue.

nicolas-grekas added a commit that referenced this pull request Jan 29, 2024
…-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       | MIT

Replaces #53512

This 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
@ArtemBrovko
Copy link
Contributor Author

Yes, now it works. Thanks!

@ArtemBrovko ArtemBrovko deleted the fix_53496 branch April 11, 2024 12:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants