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
curl log REST endpoint causing memory error #3411
Labels
Comments
Panic in workflow-logger.go line 69: the request is missing log options - and that should be catered for. @zhxu73 this can be easily fixed by adding a nil check at line 68 - would you be interested in submitting a PR. In the meantime - you maybe able to workaround by adding log options to you request:
|
alexec
added a commit
to alexec/argo-workflows
that referenced
this issue
Jul 8, 2020
alexec
added a commit
to alexec/argo-workflows
that referenced
this issue
Jul 8, 2020
6 tasks
alexec
added a commit
that referenced
this issue
Jul 8, 2020
alexec
added a commit
that referenced
this issue
Jul 8, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist:
What happened:
Argo server hit a
invalid memory address or nil pointer dereference
when query the/api/v1/workflows/{namespace}/{name}/{podName}/log
REST endpointWhat you expected to happen:
returning actual logs of the pod, similar to
argo logs
orkubectl logs
How to reproduce it (as minimally and precisely as possible):
argo
namespaceNodePort
forargo-server
service, so that the service is exposedminikube service argo-server --url -n argo
curl http://172.17.0.3:32746/api/v1/workflows/argo/$workflow_name/$pod_name/log
invalid memory address or nil pointer dereference
Anything else we need to know?:
Environment:
v2.9.1
Logs
Message from the maintainers:
If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: