Closed jmf-mordis closed 1 day ago
Also able to replicate
If anyone thinks that it is the OhMyZsh Plugin it is just argoCD CLI itself,
➜ ~ argocd version
2024/11/07 20:30:46 maxprocs: Leaving GOMAXPROCS=14: CPU quota undefined
argocd: v2.13.0+347f221
BuildDate: 2024-11-04T15:31:13Z
GitCommit: 347f221adba5599ef4d5f12ee572b2c17d01db4d
GitTreeState: clean
GoVersion: go1.23.2
Compiler: gc
Platform: darwin/arm64
FATA[0000] Argo CD server address unspecified
➜ ~ argocd
2024/11/07 20:30:55 maxprocs: Leaving GOMAXPROCS=14: CPU quota undefined
This issue exists in release-2.13, but not exists in master, probably we just didnt cherry-pick the fix
Fix has been merged.
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