Could not check compatibility between `Laminas\ClassGenerator` and `Zend\ClassGenerator`

Question

Could not check compatibility between `Laminas\ClassGenerator` and `Zend\ClassGenerator`

joshlopes opened this issue 3 years ago · 4 comments

Hello everyone, having this issue and is confusing me and haven't any luck on fixing it.

Fatal error: Could not check compatibility between Symfony\Bridge\ProxyManager\LazyProxy\PhpDumper\LazyLoadingValueHolderGenerator::generate(ReflectionClass $originalClass, Zend\Code\Generator\ClassGenerator $classGenerator): void and ProxyManager\ProxyGenerator\LazyLoadingValueHolderGenerator::generate(ReflectionClass $originalClass, Laminas\Code\Generator\ClassGenerator $classGenerator), because class Zend\Code\Generator\ClassGenerator is not available in /var/www/vendor/symfony/symfony/src/Symfony/Bridge/ProxyManager/LazyProxy/PhpDumper/LazyLoadingValueHolderGenerator.php on line 33

When trying to upgrade

Bumps ocramius/proxy-manager from 2.12.0 to 2.13.0.

Does anyone faced the same or knows what is wrong?

I've looked in this issue list and most of people say to use composer v2 we are using composer:v2.1.3 so not quite sure what could be causing this issue.

Answer 1 · 2021-08-05T10:24:50.000Z

This could be an inadvertently introduced BC break due to stricter API signatures: will check 👍

Answer 2 · 2021-08-05T10:45:40.000Z

@Ocramius dependabot is also trying to update laminas library, but I think if I manually update this by hand without laminas update it works fine.

This is what dependabot is doing. Guess some sort of incompatibility with laminas 4.4.2 ?

Answer 3 · 2021-08-05T23:51:06.000Z

Wait, is this during PHP preloading operations, or runtime?

…

On Thu, 5 Aug 2021, 12:45 Luis Lopes, ***@***.***> wrote: @Ocramius <https://github.com/Ocramius> dependabot is also trying to update laminas library, but I think if I manually update this by hand without laminas update it works fine. [image: 8adca224-2c1f-4c91-9ff1-b9b7565c55f9] <https://user-images.githubusercontent.com/3440849/128337542-10df22f7-58b6-4750-940f-b4922fbcde08.png> This is what dependabot is doing. Guess some sort of incompatibility with laminas 4.4.2 ? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#715 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABFVEEX2C4L7F3X4MBA7XDT3JTV5ANCNFSM5BTRQGXQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email> .

Answer 4 · 2021-08-06T11:20:05.000Z

Ah, I see the problem:

laminas/laminas-code no longer requires laminas/laminas-zendframework-bridge since 4.4.0
symfony/symfony declares that it ocramius/proxy-manager, but does not declare that it also needs zendframework/zend-code
laminas/laminas-zendframework-bridge made it so that component requiring Zend\ stuff, also worked with Laminas\ stuff

Therefore, the alternatives here are two:

upgrade to a newer symfony/symfony releases: even if they did their own weird thing and started replacing ocramius/proxy-manager with a fork, because of political reasons of their own, they no longer rely on the Zend\ dependency
manually add laminas/laminas-zendframework-bridge to your dependencies if you cannot upgrade

I've already made the problem clear at symfony/symfony#41742 (comment)