chengjoey
chengjoey
hi @longwuyuan , @anvpetrov and I are not on the same team. I don’t even know him. I just saw this issue and tried to reproduce it using minikube. I...
> Hello, @chengjoey have you been able to identify the root cause of this behavior? I compared the logs forwarded to the new svc and the old svc. This seems...
> Hi @chengjoey , thanks for implementing the fix. But it remains a mystery to me why the problem does not reproduce if you perform the same actions but with...
/assign @kbudde
curl 'https://httpstat.us/200' get result: ``` 200 OK ``` string result cause json.Unmarshal faild
https://github.com/argoproj/argo-workflows/blob/48f877cc9e99129105a757741bf17c08add8cee9/cmd/workflow-controller/main.go#L196-L197 try set `--gloglevel`, I guess some unexpected logs are printed by the k8s go-client.
> We're also seeing info-level log output from workflows that are executed with the above arguments being passed in. @Telefragged Apart from this initial section of the log, there should...
you are not running in docker, it's the `--path.procfs` correct? Or is there any error in the log? maybe it's dial cost too many time https://github.com/prometheus/node_exporter/blob/b9d0932179a0c5b3a8863f3d6cdafe8584cedc8e/collector/arp_linux.go#L79-L83
> @chengjoey looks like you have some linting errors in the `Smoke Test / Helm Charts Check` test. Can you address? The correct commands to run to fix this should...