Having the application symfony/* components upgraded to 4.4.x causes application cache unusable.
Sonata:
"sonata-project/admin-bundle": "~3.54.1",
"sonata-project/classification-bundle": "~3.9.2",
"sonata-project/exporter": "~2.0.1",
"sonata-project/intl-bundle": "~2.7",
"sonata-project/media-bundle": "~3.21.0",
"sonata-project/doctrine-orm-admin-bundle": "~3.11.0",
"sonata-project/user-bundle": "~4.5.1",
Steps:
4.4,composer update[php] Fatal Compile Error: Declaration of Sonata\Form\Validator\Constraints\InlineConstraint::__sleep() must be compatible with Symfony\Component\Validator\Constraint::__sleep(): arrayI looked at form-extension and the signature is ok. But how should I replace CoreBundle with that library if there's a conflict within composer.json? What is an official upgrade path not to break Symfony?
Do I need to fix CoreBundle until the new major is being released?
I think it's already fixed in 3.x branch of sonata-project/core-bundle (https://github.com/sonata-project/SonataCoreBundle/blob/4b4c65f7117cdeb54d19cc35b8bd0ef0aff5e37b/src/Form/Validator/Constraints/InlineConstraint.php#L52). Then this issue should then be opened on sonata-project/core-bundle to release a version compatible with SF4.4. WDYT @sonata-project/release-managers ?
Not in stable release, unfortunately.
@core23 can we create a release?
We can, but I'm not sure if this will work, because we have conflict entries for the extracted libs :/
Yup, but IMO you should fix this because of the constraints in composer.json.
The current release versions of various Sonata bundles require SonataCoreBundle, so a release of that including the fix that's already in master seems sensible to me, unless there's a blocker to doing that? As things stand, we're stuck with Symfony <4.4 if we want to use SonataAdminBundle.
@core23 — any news? It's quite urgent because blocks applications from upgrade do Sf LTS.
@core23 — any news? It's quite urgent because blocks applications from upgrade do Sf LTS.
I'm not activity working on this at the moment.
Btw. this is a symfony bug: https://github.com/symfony/symfony/issues/34478
You're right, we're waiting for merge and release.
Maybe we should add version contraints in our composer.json to blacklist buggy versions once https://github.com/symfony/symfony/pull/34513 is released? Or maybe even before?
It's hard to decide because the fix has been merged into the master yesterday and introducing blacklisting will create some kind of lag between two releases of Sonata…
I don't get it, sorry… what fix are you talking about? Can you share a link? If it's only available on sf master, I fail to see how this is going to help. Also, what do you mean by "some kind of lag". If 4.4.0 is buggy, we should blacklist it, period. I was wondering if this was going to be fixed in 4.4.1 or not, hence my question.
Ah, sorry, misunderstood.
BTW: https://github.com/symfony/symfony/pull/34513#issuecomment-558174683
Ok, that means we can and should blacklist 4.4.0. Can you please make a PR for this @er1z?
Also, is this really the right repo to report that issue? Your error message seems to say the bug occurs with a class from the core bundle or another, please check.
This issue should be fixed in Symfony 4.4.1.
I try to install on symfony 4.4.7 and having problem:
```
As explained in the error message ; don't install Twig 3, install Twig 2.
Most helpful comment
@core23 — any news? It's quite urgent because blocks applications from upgrade do Sf LTS.