Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[DI] Fix initialization of legacy containers by delaying include_once#25858
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
Merged
Uh oh!
There was an error while loading.Please reload this page.
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
5a8b3a7 tofc9a6f4Comparefabpot approved these changesJan 23, 2018
Member
fabpot commentedJan 23, 2018
Thank you@nicolas-grekas. |
fabpot added a commit that referenced this pull requestJan 23, 2018
…nclude_once (nicolas-grekas)This PR was merged into the 3.4 branch.Discussion----------[DI] Fix initialization of legacy containers by delaying include_once| Q | A| ------------- | ---| Branch? | 3.4| Bug fix? | yes| New feature? | no| BC breaks? | no| Deprecations? | no| Tests pass? | yes| Fixed tickets | -| License | MIT| Doc PR | -Best reviewed ignoring whitespaces:https://github.com/symfony/symfony/pull/25858/files?w=1Noticed while removing a package: silencing the failing `include_once` as introduced in#25255 is not working for the `$oldContainer` in `Kernel`, and fails with a fatal error when an include succeeds but the class inside misses a parent.Delaying the calls to `include_once` to the moment where the fresh container is actually used first, when setting the "kernel" service, works around the situation.Commits-------5e750ec [DI] Fix initialization of legacy containers by delaying include_once
Sign up for freeto 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.
Uh oh!
There was an error while loading.Please reload this page.
Best reviewed ignoring whitespaces:
https://github.com/symfony/symfony/pull/25858/files?w=1
Noticed while removing a package: silencing the failing
include_onceas introduced in#25255 is not working for the$oldContainerinKernel, and fails with a fatal error when an include succeeds but the class inside misses a parent.Delaying the calls to
include_onceto the moment where the fresh container is actually used first, when setting the "kernel" service, works around the situation.