You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In App_KernelDevDebugContainer.php line 153:
Circular reference detected for service "getCategoryRepositoryService", path: "getCategoryRepositoryService -> getDoctrineService -> getDoctrine_Orm_DefaultEntityManagerService -> getDoctrine_Dbal_DefaultConnectionService -> getDoctrine_Dbal_DefaultConnection_EventManagerService -> getDoctrine_Orm_DefaultListeners_AttachEntityListenersService -> getStofDoctrineExtensions_Listener_TreeService -> getSomeListenerService -> getProductRepositoryService -> getCategoryRepositoryService".
Additional Context
The reason it's not an infinite loop is that \Symfony\Bridge\Doctrine\ContainerAwareEventManager::initializeListeners sets $this->initialized[$eventName] = true immediately after being called, even though the event is not initialized, which seems incorrect.
The container does not retain any state of whether the current service is being initialized, therefore it does not throw any exceptions, though it arguably should.
The text was updated successfully, but these errors were encountered:
Symfony version(s) affected
6.4.2
Description
Screenshot will answer all the questions:
How to reproduce
To address the complex bug, follow these steps:
https://github.com/oleg-andreyev/bug_app
Possible Solution
Update PhpDumper and alter load method to track loading status of a service.
as result container will throw:
Additional Context
The reason it's not an infinite loop is that
\Symfony\Bridge\Doctrine\ContainerAwareEventManager::initializeListeners
sets$this->initialized[$eventName] = true
immediately after being called, even though the event is not initialized, which seems incorrect.The container does not retain any state of whether the current service is being initialized, therefore it does not throw any exceptions, though it arguably should.
The text was updated successfully, but these errors were encountered: