Fix: non-interactive output incorrectly sent to stderr instead of stdout #3277
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.
Issue #, if available:
Solves an internal TT related to non-interactive output redirection
Description of changes:
This PR fixes an issue introduced in the refactor of the legacy conduit system where
ControlEnd<DestinationStdout>was incorrectly initializingLegacyPassThroughOutput::Stderr,causing non-interactive model output to be written to
stderrinstead ofstdout.https://github.com/aws/amazon-q-developer-cli/pull/3112/files#diff-a668f28dd7d3f5a5cf37bc315f83d6a5b4f05005651a607c6ec0858770358a31R301-R302
Verified output stream behavior via
q chat --no-interactive "how are you?" 2>/dev/null— output now correctly appears on stdout.> I'm doing well, thanks for asking! I'm here and ready to help you with AWS services, development tasks, or any technical questions you might have. What can I assist you with today?By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.