search

Codeception / module-doctrine

Next gen Doctrine module for Codeception
MIT License
2 stars 1 forks source link

After Symfony Kernel reboot - Doctrine EventManager keep old Container #24

Open ewgRa opened 7 years ago

ewgRa commented 7 years ago

What are you trying to achieve?

I have case, when my service have some state, like MemoryStorage collect some data and I want to test what it collects. This MemoryStorage filled by some listeners, subscribed to Doctrine events.

What do you get instead?

My MemoryStorage empty.

Here is reproduce test https://github.com/ewgRa/symfony-standard/blob/codeception-bug-with-container/tests/functional/ContainerCest.php .

tryToTest failed, and tryToTestProof show the reason why it fail. Problem that doctrine.orm.entity_manager is persistent service and it have EventManager, that actually ContainerAwareEventManager, that store container. When Symfony module reboot kernel, it create new Container, but since doctrine is persistent, EventManager continue keep old container. As a result Doctrine events work with its own container, while $I->grabService(...) work with another container.

Reproduce: git clone git@github.com:ewgRa/symfony-standard.git cd symfony-standard/ git checkout codeception-bug-with-container composer install vendor/bin/codecept run

So, is it feature? Or bug? Looks like 100% bug. Possible solution is update EventManager container also on kernel reboot. Or another solution - unpersist doctrine.

At least this must be mentioned somehow in documentation. Also some "I make service persistent, and it not works" issues can be related to this.

toby-griffiths commented 5 years ago

We've experienced this issue as well, with event doctrine event listeners being persisted within the entity manager, whilst other services access the newly created container services (rather than the some ones in the EntityManager::$uow::$listenersInvoker::$eventManager::$listeners).