-
-
Notifications
You must be signed in to change notification settings - Fork 500
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
feat: exec multiplexed to return stderr #1933
feat: exec multiplexed to return stderr #1933
Conversation
✅ Deploy Preview for testcontainers-go ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
# Conflicts: # docker_exec_test.go
@@ -129,7 +129,7 @@ require ( | |||
github.com/secure-systems-lab/go-securesystemslib v0.4.0 // indirect | |||
github.com/serialx/hashring v0.0.0-20190422032157-8b2912629002 // indirect | |||
github.com/shibumi/go-pathspec v1.3.0 // indirect | |||
github.com/shirou/gopsutil/v3 v3.23.9 // indirect | |||
github.com/shirou/gopsutil/v3 v3.23.10 // indirect |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change is probably unrelated, but let's include it as it's harmless
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks for contributing this fix! It's important to return the stdError in that case
I'm changing the |
What does this PR do?
This PR allows container command execution to return stderr, when the command execution produces an error.
Why is it important?
It's important to get the output of a error when executing a command in a container, to facilitate the error debug.
Related issues