Avoid possible hang in util.RunCmdOut by using byte buffers instead of pipes #5220
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our
util.RunCmdOut()
function runs commands with creating pipes for stdout and stderr, and then reads each of them to completion:skaffold/pkg/skaffold/util/cmd.go
Lines 78 to 95 in 95092ad
But this code may hang if the stderr pipe fills and cause the process to block.
Since this code does not actually monitor the output streams, this PR changes the implementation to use byte buffers instead and let the Go runtime manage reading and writing.