-
Notifications
You must be signed in to change notification settings - Fork 218
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
Allow empty outputs #292
Allow empty outputs #292
Conversation
FYI the problem was introduced here. |
@@ -194,6 +194,8 @@ def _spec_to_flux_dict(spec): | |||
shell_object = spec.component_object.shell | |||
flux_dict['constructorArgs'].append([shell_object.execution_command, | |||
shell_object.script]) | |||
if not spec.outputs or len(spec.outputs) == 0: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Super minor nitpick, but could you please get rid of the or len(spec.outputs) == 0
from this line? It's unnecessary, because if spec.outputs
is empty, not spec.outputs
will be true.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Your are right. Done.
Thanks for the pull request! |
Removed unreachable check
Flux expects at least one output if fails on not defined or empty
spec.outputs
. Since empty outputs were supported in all 3.0.0-dev releases this breaks a lot of recent code.