-
Notifications
You must be signed in to change notification settings - Fork 155
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
[SimWF] Protect the -e argument #1551
Conversation
Without this, passing -embedding would work and produce a workflow.json. However, the resulting WF has nothing to with embedding, since the real flag for that has 2 dashed: --embedding What really happened was that the engine would now be "mbedding" So far there are no clashes for -j or -o which are also valid arguments.
REQUEST FOR PRODUCTION RELEASES:
This will add The following labels are available |
Without this, passing -embedding would work and produce a workflow.json. However, the resulting WF has nothing to with embedding, since the real flag for that has 2 dashed: --embedding What really happened was that the engine would now be "mbedding" So far there are no clashes for -j or -o which are also valid arguments. Co-authored-by: Benedikt Volkel <[email protected]>
Without this, passing -embedding would work and produce a workflow.json. However, the resulting WF has nothing to with embedding, since the real flag for that has 2 dashed: --embedding What really happened was that the engine would now be "mbedding" So far there are no clashes for -j or -o which are also valid arguments. Co-authored-by: Benedikt Volkel <[email protected]>
Without this, passing -embedding would work and produce a workflow.json. However, the resulting WF has nothing to with embedding, since the real flag for that has 2 dashed: --embedding What really happened was that the engine would now be "mbedding" So far there are no clashes for -j or -o which are also valid arguments. Co-authored-by: Benedikt Volkel <[email protected]>
Without this, passing -embedding would work and produce a workflow.json. However, the resulting WF has nothing to with embedding, since the real flag for that has 2 dashed: --embedding What really happened was that the engine would now be "mbedding" So far there are no clashes for -j or -o which are also valid arguments. Co-authored-by: Benedikt Volkel <[email protected]> (cherry picked from commit d8bf2aa)
Without this, passing -embedding would work and produce a workflow.json. However, the resulting WF has nothing to with embedding, since the real flag for that has 2 dashed: --embedding What really happened was that the engine would now be "mbedding" So far there are no clashes for -j or -o which are also valid arguments. Co-authored-by: Benedikt Volkel <[email protected]> (cherry picked from commit d8bf2aa)
Without this, passing -embedding would work and produce a workflow.json. However, the resulting WF has nothing to with embedding, since the real flag for that has 2 dashed: --embedding
What really happened was that the engine would now be "mbedding"
So far there are no clashes for -j or -o which are also valid arguments.