You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
running Hera code without submitting to Argo (e.g. when exporting to YAML)
running Hera code and submitting to Argo
Bug report
Describe the bug
When using script annotations, an alternative name can be specified. When using with_param, it checks through the python names only, here. When using the alternative name in an arguments={"param-name": "a value"} alongside a with_param, the with_param will populate the other arguments as param_name.
This will then fail on submission to Argo with
inputs.parameters.param-name was not supplied
I'll add a reproducible example here soon!
Expected behavior
Annotated names are also checked/linked with the python names (then probably always use the alternative name if specified)
Environment
Hera Version: 5.9.0
Python Version: 3.11.6
Version of Argo: 3.X.X
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Pre-bug-report checklist
1. This bug can be reproduced using YAML
2. This bug occurs when...
Bug report
Describe the bug
When using script annotations, an alternative name can be specified. When using
with_param
, it checks through the python names only, here. When using the alternative name in anarguments={"param-name": "a value"}
alongside awith_param
, thewith_param
will populate the other arguments asparam_name
.This will then fail on submission to Argo with
I'll add a reproducible example here soon!
Expected behavior
Annotated names are also checked/linked with the python names (then probably always use the alternative name if specified)
Environment
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: