Fix how Process output in sz cli is captured to (hopefully) fix timout issue. #55
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 CI Pipeline for #51 had timeouts.
While investigating the issue I found out that it seems like
dart pub get
doesn't close it'sstderr
Stream when having an error thus causing waiting for inifinity if one depends on a closed stream (e.g. to capture the error output fully).Additionally
await process.exitCode
doesn't seem to finish when I'm not listening toprocess.stdout
orprocess.stderr
.I think this is also only for
dart pub get
but I'm not sure really :/