Hi All, I was wondering if there is an issue usin...
# ask-metaflow
m
Hi All, I was wondering if there is an issue using parameters that contain spaces (e.g. "A B") with using Argo Workflows in Metaflow? Currently I am getting the following error:
Copy code
Error: Got unexpected extra argument (B)
Error: exit status 2
We are using Metaflow extensions, so have some differences in our Argo Workflow set up. Not touched parameters though, so would expect the same behaviour. Anyway, just wanted to confirm whether it is an issue with vanilla Metaflow first, before I investigate further. Thanks! 🙂
✅ 1
b
Is the space in the CLI command, or the python code?
m
The test I have checked so far, it would be in the CLI command
I am guess it would end up the same in the CLI command if the parameter were specified in python too?
b
Can you share your CLI command?
m
Sorry, I meant the CLI that Argo Workflows uses under the hood to call metaflow within a step. The CLI we use to submit a Metaflow job to Argo is somewhat different to yours, so not sure it makes much sense to share it. I can share the Argo manifest, if it helps?
Can you confirm whether this is an issue in native Metaflow btw?
b
Metaflow flows do not allow spaces in parameter names. I can confirm that flow kind like
Copy code
class ParamFlow(FlowSpec):
    p = Parameter('A B',
                type=str)
gives an error when creating an argo workflow
m
ok, thanks for confirming!
Out of interest, do you think it would be possible to add support for parameters with spaces in them?
b
I personally can’t answer that but I hope someone else can speak to it
You could open an issue on GitHub
m
ok, no worries. If no one answers soon I;ll make a github issue