fix #5022: adds a small amount of additional buffering to exec streams #5054
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.
Description
Fix #5022 - for most scenarios coming from older releases with multiple exec streams, this will remove the need to proactively read them. The additional buffering is being done as part of the consume call so sometimes this will mean that once the buffers are full, they must be drained to fill it back up again.
Ideally the user would supply a minimally blocking output stream directly to write into instead.
Type of change
test, version modification, documentation, etc.)
Checklist