-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
fix: make WF global parameters available in retries #12698
Conversation
…ables in a retry Signed-off-by: eduardodbr <eduardodbr@hotmail.com>
Signed-off-by: eduardodbr <eduardodbr@hotmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks for root causing this, fixing it, and adding tests!
I was looking at some other substitution code for #12693 just yesterday; you might be interested in taking a look at that one too, although it seems potentially more complex since it regressed twice already |
yeah sure, I'll assign it to me :) |
Signed-off-by: eduardodbr <eduardodbr@hotmail.com> (cherry picked from commit 9bec114)
Signed-off-by: eduardodbr <eduardodbr@hotmail.com>
Signed-off-by: eduardodbr <eduardodbr@hotmail.com>
Fixes #10362
This bug was found on this issue although its title complains about another bug that doesn't exist.
Motivation
It is not possible to use the
retries
variable in anexpression
that also uses global variables likeworkflow.parameters.<param>
. When the global variables are substituted the retry number isn't available and when the retry number is injected, the global params are not being used for substitution.Modifications
Add the global params to SubstituteParams when retrying a node
Verification
The memory limit should be defined by the value of the parameter
memreqnum
multiplied by the retry number.