-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
result
output parameter of script templates occasionally become empty
#11330
Comments
I found that this can be reproduced by directly running When I run the following command for a long time,
|
i was also affected by this issue! |
Thanks for providing detailed repo instructions. @tooptoop4 - can you please upvote the issue to help prioritize it if you're also affected? |
Any workaround here before new version is released? |
actually, we don't need this line: cmd.WaitDelay = 100 * time.Millisecond according this link: golang/go#50436 , if we did't set the _ = cmd.Wait() so, i think it is better to remove the WaitDelay, as if we set it, golang will do wait, and when it is timeout, golang will close the pipes, which may leading a partial content, because it is hard to decide how long to wait. although i have merged the commit, but this issue can still happen, outputs only has a partial part, not the whole content. |
The PR #11368 specifies that It may make sense to make that delay configurable if that becomes a problem though. If you are having partial content issues, please file a new issue about that. |
…proj#11330 (argoproj#11368) Signed-off-by: boiledfroginthewell <boiledfroginthewell@users.noreply.github.com> Signed-off-by: Dillen Padhiar <dillen_padhiar@intuit.com>
Pre-requisites
:latest
What happened/what you expected to happen?
The attached workflow runs successfully most of the time but it randomly fails once in 40 to 100 runs. When it failed, the value of
{{steps.echo.outputs.result}}
was empty even if theecho
step successufully finished.The outputs and archived logs in the UI are also empty.
But kubernetes logs show that the script correctly displayed messages.
Version
v3.4.8
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
Logs from the workflow controller
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: