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 #297, the __call__ dunder is moved to call method and used directly in add_task_subscriber. The function is an async function, and the reason is the proc.step_until_terminal() need to be scheduled into the event loop. It can actually make the call a sync function to consistent with both message_receiver and broadcast_reveiver. In the call, the proc.execute() method is called by step the process forward.
The problem can be checked and fixed together with unkcpz#39 to have a sophisticate control on event loop. Because when initialize a process will create an event loop if it is not created in the event loop, the event loop then need to reset to the runner one to launch.
The text was updated successfully, but these errors were encountered:
In #297, the
__call__
dunder is moved tocall
method and used directly inadd_task_subscriber
. The function is an async function, and the reason is theproc.step_until_terminal()
need to be scheduled into the event loop. It can actually make thecall
a sync function to consistent with bothmessage_receiver
andbroadcast_reveiver
. In the call, theproc.execute()
method is called by step the process forward.The problem can be checked and fixed together with unkcpz#39 to have a sophisticate control on event loop. Because when initialize a process will create an event loop if it is not created in the event loop, the event loop then need to reset to the runner one to launch.
The text was updated successfully, but these errors were encountered: