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
"""Emit event to all registered observers.
The current storage state is committed before and after each observer is notified.
+ Note that emission of custom events is handled immediately. This means that a call to+ `emit` is followed by immediately calling the observers. In other words, emission of+ custom events is not queued but rather nested. For example:+ 1. Core hook (emits custom_event_1)+ 2. Custom event 1 handler (emits custom_event_2)+ 3. Custom event 2 handler+ 4. Resume custom event 1 handler+ 5. Resume core hook handler
"""
Iiuc, emission of custom events does not get queued: when they are emitted, their handler is called immediately, before the previous hook finished.
operator/ops/framework.py
Lines 331 to 335 in 26c6e95
I.e. emission is nested, not sequential.
Could be handy to have it outlined in the docs.
The text was updated successfully, but these errors were encountered: