You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue only present in the argocd cli 2.13.0, tested on argocd-darwin-arm64 and argocd-linux-amd64
All argocd cli commands I tried send to STDERR this kind of message:
2024/11/07 10:21:35 maxprocs: Leaving GOMAXPROCS=12: CPU quota undefined
If you check that the STDERR of your argocd cli command is empty in your CI/CD, this new version produces always an issue because it always sends this message to STDERR, you can only rely on the status code from now on. I don't think that this a relevant message to send to STDERR.
I think that it is not an expected change, checking this code and this PR.
Setting the GOMAXPROCS env variable doesn't fix the issue, it just makes the argo cli send this other message to STDERR:
GOMAXPROCS=12 argocd version
2024/11/07 10:57:35 maxprocs: Honoring GOMAXPROCS="12" as setin environment
To Reproduce
Just invoking an argocd version, argocd app list or an argocd app diff is enough to reproduce the issue.
argocd app list
2024/11/07 10:52:34 maxprocs: Leaving GOMAXPROCS=12: CPU quota undefined
Expected behavior
STDERR of the argocd cli is empty then there is no relevant error. (I don't consider the GOMAXPROCS logs a relevant error).
Checklist:
argocd version
.Describe the bug
Issue only present in the argocd cli 2.13.0, tested on
argocd-darwin-arm64
andargocd-linux-amd64
All argocd cli commands I tried send to STDERR this kind of message:
If you check that the STDERR of your argocd cli command is empty in your CI/CD, this new version produces always an issue because it always sends this message to STDERR, you can only rely on the status code from now on. I don't think that this a relevant message to send to STDERR.
I think that it is not an expected change, checking this code and this PR.
Setting the GOMAXPROCS env variable doesn't fix the issue, it just makes the argo cli send this other message to STDERR:
To Reproduce
Just invoking an
argocd version
,argocd app list
or anargocd app diff
is enough to reproduce the issue.Expected behavior
STDERR of the argocd cli is empty then there is no relevant error. (I don't consider the
GOMAXPROCS
logs a relevant error).Screenshots
Version
(The issue is also in the argocd version )
Logs
The text was updated successfully, but these errors were encountered: