Bug #3486
closed
[DRAFT] [Crunch] Cannot have script parameter value of "false" because arv-run-pipeline-instance (and also workbench) don't distinguish between "false" and "nil"
Added by Peter Amstutz over 10 years ago.
Updated over 8 years ago.
Description
Perhaps give warning or error when someone uses the ambiguous parameter form.
Bad:
Good:
- Target version set to Arvados Future Sprints
- Subject changed from Cannot have script parameter value of "false" because arv-run-pipeline-instance (and also workbench) don't distinguish between "false" and "nil" to [Crunch] Cannot have script parameter value of "false" because arv-run-pipeline-instance (and also workbench) don't distinguish between "false" and "nil"
- Subject changed from [Crunch] Cannot have script parameter value of "false" because arv-run-pipeline-instance (and also workbench) don't distinguish between "false" and "nil" to [Crunch] [obsolete?] Cannot have script parameter value of "false" because arv-run-pipeline-instance (and also workbench) don't distinguish between "false" and "nil"
- Subject changed from [Crunch] [obsolete?] Cannot have script parameter value of "false" because arv-run-pipeline-instance (and also workbench) don't distinguish between "false" and "nil" to [DRAFT] [Crunch] Cannot have script parameter value of "false" because arv-run-pipeline-instance (and also workbench) don't distinguish between "false" and "nil"
- Description updated (diff)
- Story points changed from 0.5 to 1.0
Check whether this can be resolved like so:
script_parameters:
foo:
value: false
- Status changed from New to Resolved
- Target version changed from Arvados Future Sprints to 2016-10-26 sprint
This seems to be working as intended, and is merged, so I'm marking resolved.
- Assigned To set to Tom Clegg
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by