[FrameworkBundle] fix creating ContainerBuilder at warmup/CLI time #41456
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aa3c6b4 to
74e297a
Compare
fabpot
approved these changes
May 31, 2021
|
Thank you @nicolas-grekas. |
|
Oh. Thank you for this fix. |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In prod mode, because we hack the kernel to recreate a container builder at runtime for introspection needs, we end up with a broken object graph. Calling
$this->initializeBundles()creates fresh bundle instances and that fixes the issue.This could be merged on 5.2, but we don't need the fix on 5.2 because we never encountered the situation before adding the cache warmer for config builders.