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 }}
This repository has been archived by the owner on Jun 15, 2024. It is now read-only.
The either step does not return the step results of its children, making it harder to get data about them, e.g. when processing the information from :pipeline-finished events. It's also just not intuitive if some container steps return :outputs and others don't
The text was updated successfully, but these errors were encountered:
Counterpoint: It currently doesn't return outputs because then it would need to wait for all children to finish/be killed to have a final result to return. Depending on the child step, being killed takes a few seconds so implementing this would mean slowing down the pipeline for more correct but rarely used data.
The
either
step does not return the step results of its children, making it harder to get data about them, e.g. when processing the information from:pipeline-finished
events. It's also just not intuitive if some container steps return:outputs
and others don'tThe text was updated successfully, but these errors were encountered: