-
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: always fail dag when shutdown is enabled. Fixes #11452 #11493
fix: always fail dag when shutdown is enabled. Fixes #11452 #11493
Conversation
Signed-off-by: isubasinghe <isitha@pipekit.io>
|
4c2e3ea
to
2c63eb0
Compare
Signed-off-by: isubasinghe <isitha@pipekit.io>
6211bc0
to
825c7bf
Compare
Signed-off-by: isubasinghe <isitha@pipekit.io>
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.
Makes sense to me
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. just adds an early return and error guards
@@ -140,15 +146,24 @@ func (d *dagContext) assessDAGPhase(targetTasks []string, nodes wfv1.Nodes) wfv1 | |||
targetTaskPhases[d.taskNodeID(task)] = "" | |||
} | |||
|
|||
boundaryNode, err := nodes.Get(d.boundaryID) |
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.
for context for other readers, the nodes.Get
modifications here are just error guards a la #11451. no real semantic changes
Signed-off-by: Yuan (Terry) Tang <terrytangyuan@gmail.com>
Fixes #11452
Motivation
Ensure that stopped workflows are always marked as Failed (as expected).
Modifications
When shutdown is enabled, we don't do the DAG exploration.
Verification
Manually tested