-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Symfony 5.2-RC-1 "It's a requirement to specify a Metadata Driver" #39120
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
Hello @eerison , Could you please share a reproducer or a the project? |
Hi @jderusse I'll check today and post here the results. shield-wall/myprofile#306 |
Thank you for the reproducer. There is a bug in Symfony when generating the container introduced by #38980 The issue in your case is the following:
It wasn't an issue for YOU before #38980 because at that time, Symfony trusted the lazy service. I'll try to find a way to fix it. Otherwise we should considere reverting #38980 /cc @nicolas-grekas |
FYI: I'm testing with dev and happen the same issue|
|
I installed |
The fix has not been merged yet. (but you can try my patch and provide a feedback on the PR, Whether or not it fux your issue). Yeah installing a proxy is a workaround for this issue. |
…truct loop (jderusse) This PR was squashed before being merged into the 4.4 branch. Discussion ---------- [DependencyInjection] Fix circular in DI with lazy + byContruct loop | Q | A | ------------- | --- | Branch? | 4.4 | Bug fix? | yes | New feature? | no | Deprecations? | no | Tickets | Fix #39120 | License | MIT | Doc PR | - This fix another issue lazy service. It partially revert #38980 and #39021 Initially, we trusted lazy services to be lazy and not beeing called while building the services graph => bug #38970 when lazy deps is injected in a factory, it may be consumed directly to build the object before the graph is fully built Fixed by #38980 => lazy service are considered as "normal service" => bug #39015 some loop are not resolvable with "normal service", but it shouldn't be an issue when servie proxifyied Fixed by #39021 => lazy service are considered as "normal service" except when proxyfied => bug #39120 some loop are not resolvable with "normal service", but it shouldn't be an issue because the lazy service is injected in the constructor and user Fixed by this PR => that revert to the initial state. lazy service are trusted. But now, The IterratorArgument injected in a factory (single exception) is not more considered as lazy Commits ------- 54af139 [DependencyInjection] Fix circular in DI with lazy + byContruct loop
Symfony version(s) affected: v5.2.0-RC-1
Description
After migrate symfony 5.1 to 5.2.0-RC-1 I got this error
Additional context
.env
config/packages/doctrine.yaml
The text was updated successfully, but these errors were encountered: