fix(backend): iterate placeholder substitution to fixpoint in launcher_v2 - #13984
fix(backend): iterate placeholder substitution to fixpoint in launcher_v2#13984vizansh wants to merge 1 commit into
Conversation
|
Hi @vizansh. Thanks for your PR. I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
Nice catch adding the The loop needs a cap though: for {
prev := s
for placeholder, replacement := range placeholders {
s = strings.ReplaceAll(s, placeholder, replacement)
}
if s == prev {
break
}
}It stops at a fixpoint, but a value containing its own placeholder never reaches one. Set parameter The SDK files look accidental. Removing the On the test, it runs once over two placeholders, so map order gives it roughly a 50% pass rate against the unfixed code. Looping it makes the regression reproducible. Worth a look at #12811 too, which resolves placeholders inside list and struct constants in the driver. If that lands, some of these nested cases would be resolved before the launcher sees them. Not a blocker, just worth settling which layer owns it. |
1042540 to
0072ca0
Compare
0072ca0 to
6fa2aa1
Compare
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Thanks @dobbydobap for the thorough review! These were excellent points:
Updated and force-pushed! |
|
/assign @chensun |
|
Cap logic is right, and dropping the SDK files cleaned it up nicely. One thing that will bite CI though: the new |
Fixes #13977
Thanks to @ahn132 for the issue report and root cause breakdown.