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
{{ message }}
Repository navigation
The stopped flag is never reset: later flows through a stopped task are dropped silently #481
A stop without error (StopTask, ProcessState::stop()) sets stopped on each task of its flow, and nothing resets it. The documentation says that "other root tasks are executed, blocking tasks that already received inputs are proceeded", but their outputs going through a task of the stopped flow are dropped silently:
a second root task stops after its first item;
the output of an aggregate proceeded after the stop never reaches the next tasks;
an iterable task interrupted by the stop restarts with its former items when another root reaches it.
Proposed fix
Reset the flag at the beginning of each execution of a task, except for an iterable task interrupted by the stop and for a task whose initialization has failed (deprecated behaviour).
Requirements
Documentation updates
Reference
Cookbooks
Changelog
Unit tests
Breaking changes
Outputs that were dropped silently after a stop now go on through the tasks of the stopped flow, as documented (see UPGRADE).
Activity
#481 - A stop only stops the flow it happened in
#481 - A stop only stops the flow it happened in
Merge pull request #482 from cleverage/481