Cache clear, cannot declare class

[KDederichs]

Q	A
Bug report?	yes
Feature request?	no
BC Break report?	no
RFC?	no
Symfony version	3.3.14

Hey,
I've been seeing a strange thing where the clear cache command cannot declare classes on it's first execution if there is no previous cache.

On the first execution it will always fail with something like
PHP Fatal error: Cannot declare class EnhancedProxy_84f26540d03882f66a8da2bedf47ccf4f27752f4\__CG__\TaskBundle\Controller\SupervisionController, because the name is already in use in /home/kai/public_html/washeroo/var/cache/tes_/jms_diextra/lookup_method_classes/TaskBundle-Controller-SupervisionController.php on line 11 14:33:41 CRITICAL [php] Fatal Compile Error: Cannot declare class EnhancedProxy_84f26540d03882f66a8da2bedf47ccf4f27752f4\__CG__\TaskBundle\Controller\SupervisionController, because the name is already in use ["exception" => Symfony\Component\Debug\Exception\FatalErrorException { …}] []
On any subsequent run of the clean cache command it will be successful though.
I'm not exactly sure if it is a bug in the clear cache command or if the jms_diextra bundle is causing it.

Another thing is that the class it seems to have an issue with doesn't have a method that's annotates the lookup_method from jms_diextra but its parent class does.

[xabbuh]

Can you provide steps that allow to reproduce your issue?

[nicolas-grekas]

@KDederichs the fact this in on branch 3.3 means this bug is unseen to me.
I'd be happy to try a reproducer you could provide. Thanks.

[Simperfit]

@KDederichs Could you please help us reproducing the bug by providing a little project.

• Fork the Symfony Standard Edition
• Do the minimum modification to reproduce the bug
• Post the link in here

In case you need some help you can read this blog post : https://symfony.com/doc/current/contributing/code/reproducer.html

[KDederichs]

Hey sorry for the lack of replies, Christmas and such.
Here is a link with the minimum modification I needed to reproduce the bug:

https://github.com/KDederichs/symfony-standard/tree/issue_25576

It will occur when you do a bin/console cache:clear on a fresh cache or if you previously deleted the cache.

[KDederichs]

So it's their bug and not cache:clear related?

[nicolas-grekas]

I managed to reproduce. As far as I tried correctly, the issue is not new to 3.3.14 specifically. On which version of Symfony did this work last? I would suggest to open an issue on JMS Di-extra instead, as I'm not sure the issue is on symfony/symfony's side.

[mvrhov]

Oh, he's using JMS di-extra. IMO he should get rid of it.

[nicolas-grekas]

Closing as this is an issue with JMS di-extra.