Skip to content
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(agent): no more requeue when the node succeeded #10681

Merged

Conversation

sxllwx
Copy link
Contributor

@sxllwx sxllwx commented Mar 14, 2023

Fixes: As the title

Copy link
Contributor

@alexec alexec left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for this fix. How would you go about testing it? Unit tests?

@sxllwx
Copy link
Contributor Author

sxllwx commented Mar 20, 2023

Thank you for this fix. How would you go about testing it? Unit tests?

ok~

@sxllwx sxllwx force-pushed the fix/never-requeue-when-node-succeeded branch from 0489744 to b7325a3 Compare March 24, 2023 09:08
@sxllwx
Copy link
Contributor Author

sxllwx commented Mar 24, 2023

done~ PTAL, thx @alexec

@sxllwx sxllwx requested a review from alexec March 24, 2023 09:10
Signed-off-by: scott <scottwangsxll@gmail.com>
@sxllwx sxllwx force-pushed the fix/never-requeue-when-node-succeeded branch from b7325a3 to 380d370 Compare March 27, 2023 11:49
@@ -368,6 +368,9 @@ func (ae *AgentExecutor) executePluginTemplate(ctx context.Context, tmpl wfv1.Te
return 0, err
} else if reply.Node != nil {
*result = *reply.Node
if reply.Node.Phase == wfv1.NodeSucceeded {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this include failed and errored nodes?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think so. Because in failure, the user needs to explicitly give the delay of the requeue.

@alexec alexec merged commit 1011172 into argoproj:master Apr 3, 2023
elifarley pushed a commit to elifarley/argo-workflows that referenced this pull request Apr 6, 2023
Signed-off-by: scott <scottwangsxll@gmail.com>
Signed-off-by: Elifarley <elifarley@gmail.com>
JPZ13 pushed a commit to pipekit/argo-workflows that referenced this pull request Jul 4, 2023
Signed-off-by: scott <scottwangsxll@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants