bogdang989
bogdang989
I am not sure why tbh. It is quite strange, running the same tool on Mac works fine but on Linux it fails (both on the Jenkins run and local...
Hi @martina-g it's not required but is highly recommended if portability is important. If docker image field is left unspecified, tools will just run in the local environment
I only encountered this in CWLv1.0 workflow
Hi @jeremiahsavage , you can also set valueFrom : "", i.e. add an empty string to the command line. This should work everywhere.
[test_array.zip](https://github.com/rabix/bunny/files/1155607/test_array.zip) If only the prefix: -in for array elements is deleted, the command line is built properly.
I was in process of writing nearly the same thing as Vladimir :) Agree
I think the most important user requirement we should solve here is: - I as a user have a script I run and test locally. - Now I want to...
To chime in with our previous thinking (from a few years ago I think) if it is useful, Seven Bridges considered this as an internal hint for start as well,...
This should probably fit in the specification here: https://www.commonwl.org/v1.1.0-dev1/CommandLineTool.html#Input_binding @mr-c @tetron can you please help with the technical explanation why baseCommand item with space is quoted in the command line?...
What confuses me is why do the strings need to be quoted when there is space in some of them? I.e., why does `baseCommand: ["a b", "c"]` return `'a b'...