-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
either does not return :outputs #156
Labels
Projects
Comments
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: