cyyangnb
cyyangnb
Hi @isubasinghe, @tooptoop4, @shuangkun - First of all, thank you all for continuously improving Argo Workflows! Back to the issue where the workflow-controller can create duplicate pods due to informer...
Hi @isubasinghe, the change is based on v3.6.2.
Sure! Good to know it's a correct direction. I will open a PR for it.
Hi @isubasinghe , I've already submitted a PR for the fix, but I’m unable to assign reviewers. Please let me know if there’s anything I need to do to formalize...
Hi @isubasinghe @alexec — The fix has been running in our production environment for a month and has proven effective in resolving the uncertainty caused by informer delay. After the...
Thank you, @isubasinghe!
We encounter this issue a few times every day and found that the provided changes successfully helped us eliminate the `unable to resolve outputs from scope: xxx` errors. However, we...
> > Would it make sense to remove the tmpl.HasOutputs() check? (I'm new to the codebase, so I’d appreciate any insights on this.) > > hi @cyyangnb, thanks for the...
Hi @isubasinghe, would you have time to review my changes?
> > We continuous encountered pod duplicate issue because workflow-controller can create duplicate pods due to informer delays. > > You mean multiple pods were created for the same node?...