Christophe Coevoet

@Seldaek yes. In that case, guessing the root version fails, while we are inside a git repository (there is a `.git` folder).

All repositories are loaded to initialize the package resolution (to know which package they provide). This does not mean that the local package won't be the one being installed.

this will be solved by https://github.com/symfony/symfony/issues/59925 which allows configuring compound limiters in the rate_limiter configuration of FrameworkBundle.

this is something to be thought about for Doctrine 3

The manager registry is about 2 purposes: - making it possible to support multiple entity managers in the same project easily, by having an easy way to get the needed...

@loiclavoie until now, my workaround was to always inject he registry in my objects. Now that I'm using Symfony 3.3, I can rely on the fact that Symfony itself wraps...

See https://github.com/symfony/symfony/blob/v3.3.9/src/Symfony/Bridge/Doctrine/ManagerRegistry.php, and then the implementation of lazy services based on ProxyManager

restoring the identityMap of the UoW is precisely something which should not be done, as it would bring the broken objects into the new UoW, making it as unreliable than...

@yaroslavbr DoctrineBundle relies on a "hack" to make the Doctrine ORM 2.x EntityManager resettable, by wrapping it in a proxy and resetting the proxy inner element. But that will indeed...

There's no way to keep existing managed entities. When Doctrine closes the entity manager, it is because it cannot trust anymore the state of the unit of work. This feature...