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
#1903 introduced a bug that caused messages sent to an agent outside a component's lifecycle to be delayed until a component lifecycle event is triggered.
Yewdux uses an agent bridge for generating flexible callbacks. If a message is sent immediately inside a component's lifecycle, it is executed as expected:
Fixes an issue where a runnable added from outside the component
lifecyle (i.e. agent bridge message from inside a callback) would not be
executed until the next component lifecycle event.
* Fix scheduler main queue delay (#1953)
Fixes an issue where a runnable added from outside the component
lifecyle (i.e. agent bridge message from inside a callback) would not be
executed until the next component lifecycle event.
* Add test for `scheduler::run`
Ensures `scheduler::run` executes runnables immediately.
Problem
#1903 introduced a bug that caused messages sent to an agent outside a component's lifecycle to be delayed until a component lifecycle event is triggered.
Yewdux uses an agent bridge for generating flexible callbacks. If a message is sent immediately inside a component's lifecycle, it is executed as expected:
However when a message is sent from a inside a callback it will not be executed.
Only when a component lifecycle event is triggered will the bridge message then be executed.
Expected behavior
Bridge messages should be executed normally when sent from a callback.
Environment:
master
nightly
Questionnaire
The text was updated successfully, but these errors were encountered: