-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[DI] Error on dumped container for inlined services #28658
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
Comments
Thanks for reporting. This is the same as #28657, right? |
It seems that yes. Every call for |
Thanks for confirming and for creating the reproducer. 👍 |
Same for our codebase, got the problem today morning (meh, Monday mood). Temporary locked Symfony version to 3.4.15, but I hope that this will be solved asap, this is critical issue for us. |
@nicolas-grekas the fact that we have |
This PR was merged into the 3.4 branch. Discussion ---------- [DI] fix error in dumped container | Q | A | ------------- | --- | Branch? | 3.4 | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #28658 | License | MIT | Doc PR | - (test case on its way) Commits ------- 2d0aba6 [DI] fix error in dumped container
Uh oh!
There was an error while loading. Please reload this page.
Symfony version(s) affected: 3.4.16
Description
After update to 3.4.16 version inlined dependencies (in my case with circular dependencies) dumped with use
$this->privates
value from the container for return as service.But every value from
$this->privates
is a boolean.How to reproduce
Additional context
Repository with reproduce script: https://github.com/andrew-demb/sf-di-3.4.16-circular-reference-dump
This PR #28388 represents a change for PhpDumper to use
privates
in dumped container.Some pieces from cached container:
YAML config
The text was updated successfully, but these errors were encountered: