Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[DoctrineBridge] Fix eventListener initialization when eventSubscriber constructor dispatch an event#40425
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
reypm commentedMar 9, 2021 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
@jderusse steps followed:
Results with the fix: no more issues |
michanismus commentedMar 9, 2021
@jderusse Works! |
fliespl commentedMar 10, 2021
@jderusse I can confirm that it works in our case as well. |
fabpot commentedMar 10, 2021
Thank you@jderusse. |
PierrickMartos commentedMar 11, 2021
Any idea when this will be released to 4.4? Thanks |

Uh oh!
There was an error while loading.Please reload this page.
The issue occurred, when an EventSubscriber (lazyLoaded) dispatch an event when constructed. In that case, the state of the
ContainerAwareEventManagerbecome inconsistent for the triggered event:listenerproperty contains both listener instance andserviceIdmeaning it's not fully initializedinitializedproperty containstruemeaning the listeners are initializedSorry for this PR without test, But it's really to hard to reproduce the issue :(
@parijke@michanismus@fliespl@reypm could you please check if this patch fixes the issue for you?