plugin: handle chunks of output correctly #77
Merged
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.
Motivation
containertoolproduces its normal output in single writes of less than PIPE_BUF bytes, which should be delivered atomically through the pipe to the plugin:https://www.gnu.org/software/libc/manual/html_node/Pipe-Atomicity.html
Progress messages written in this way are displayed correctly. Unfortunately error output from
swift-argument-parseris delivered in smaller chunks which are often broken across several lines by the plugin:At one point the plugin reassembled output from the pipe and re-split it on newlines, but the code triggered strict concurrency warnings with the Swift 6 language mode so it was removed in favour of
PIPE_BUFwrite atomicity. This commit restores the pipe output reassembly.Modifications
containertooland splits it on newlinesDiagnostics.error. Otherwise error and progress output would be interleaved.Result
Error output from
containertoolwill be presented correctly by the plugin.Test Plan
Existing tests continue to pass.
A new integration test checks that error output is not broken into multiple lines.