-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
You have requested a non-existent parameter "container.build_id". #25695
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
Fixed by #25696 |
Note that this exception can also be triggered when using |
… after-removing passes (nicolas-grekas) This PR was merged into the 3.3 branch. Discussion ---------- [FrameworkBundle] Fix using "annotations.cached_reader" in after-removing passes | Q | A | ------------- | --- | Branch? | 3.3 | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #25695 | License | MIT | Doc PR | - When `annotation_reader` is instantiated in an after-removing pass, it gets the real cache provider, instead of the dummy one that should be provided during compilation of the container. This situation is found in e.g. `JMS\AopBundle\DependencyInjection\Compiler\PointcutMatchingPass`. A workaround before next release could be to "get" the `annotation_reader` service somewhere before (like in a regular compiler pass of your own.) Commits ------- f66f9a7 [FrameworkBundle] Fix using "annotations.cached_reader" in after-removing passes
@fabpot can You please merge it into symfony:3.4 |
@ajtis that's done now |
Thank You @xabbuh |
I still have the error. |
@ajtis I still have the error too, this fix change nothing to me :/ |
From my point, the problem come from the declaration of this service : cache.adapter.system |
to anyone still having this issue, please provide a stack trace of the error (similar as above) |
In ParameterBag.php line 102: [Symfony\Component\DependencyInjection\Exception\ParameterNotFoundException] Exception trace: |
@nicolas-grekas but this fix is not released yet, so it requires running the dev version of Symfony to test it (which most people don't do). |
@stof @nicolas-grekas So this last symfony/symfony change has broke symfony/symfony 3.4 LTS. Problem did not exist in sysmfony/symfony 3.3 (minor release). I did no other changes to my composer file other than symfony/symfony 3.3 to symfony/symfony 3.4. That is a [BC] break for a minor version. You suggest to run dev version for a LTS release seems very odd!! I had to role back to Symfony 3.3. When is the LTS symfony/symfony 3.4 going to have this change rolled back or available as stable? This should be a priority since it is [BC] break of minor version. If not, tell me what I'm missing. Thanks, Dave |
@nicolas-grekas Still getting this same issue today on a fresh install of both symfony v3.4.3. Has this fix been realised to production or just dev version? |
The fix will be part of the next release, by the end of the month. |
Shouldn't this fix be provided as a hotfix, as this issue essentially breaks down current LTS version? As in addition to what @dspiegel said, it breaks [BC] within PATCH release, not even MINOR. Or am I missing something as well with versioning? |
all bugs fit this description @bds-viktoras , this one is no specific |
mine seems to come from doctrine ORM in ParameterBag.php (line 102)at ParameterBag->get('container.build_id')in EnvPlaceholderParameterBag.php (line 57) |
yop ! for me i have removed "jms security" in AppKernel.php, i don't use it yet : And i've no more errors |
Version 3.4.4 => https://symfony.com/blog/symfony-3-4-4-released |
It still exists in Symfony 3.4.4. What's the fix? |
@matteomoretti Maybe a conflict with another library. Take a look my post on top |
I also have this issue today, please check non-existent parameter "container.build_id" , at first, I thought |
since #25671 JMSSecurityExtraBundle is broken because a service is used at compile time. Other libraries could be broken too.
The text was updated successfully, but these errors were encountered: