error in stdout not stderr

[andreineculau]

I have discovered that a failing "aws s3 cp" for instance that ends up in error "Transfer failed: An error occurred (404).." outputs that line in stdout, not stderr. The same might apply to other aws-cli commands.

Context: aws s3 cp s3://... - i.e. outputting the object to stdout

[andreineculau]

By change, I have now found that this is a regression, since it was supposedly fixed in #820.

An implicit bug is also back: --quiet can silences errors!

[JordonPhillips]

What version of the CLI are you using? Running the following results in nothing being displayed:

aws s3 cp . s3://bucket-that-does-not-exist/ 2> /dev/null

This is on the most recent version of the CLI. --quiet suppressing error output is intentional, use --only-show-errors to continue showing them while suppressing other output.

[andreineculau]

aws-cli/1.10.64 Python/2.7.10 Darwin/15.6.0 botocore/1.4.54

running

$ aws s3 cp s3://bucket-that-exists/object-that-does-not-exist - 2>/dev/null
Transfer failed: An error occurred (404) when calling the HeadObject
operation: Not Found

$ aws s3 cp s3://bucket-that-exists/object-that-does-not-exist
filename 2>/dev/null
Completed 1 part(s) with ... file(s) remaining

this one would have printed to stderr

An error occurred (404) when calling the HeadObject operation: Key

"object-that-does-not-exist" does not exist

So I guess a problem with the "-" (use stdout) case.

On Fri, Sep 23, 2016 at 7:05 PM, Jordon Phillips notifications@github.com
wrote:

What version of the CLI are you using? Running the following results in
nothing being displayed:

aws s3 cp . s3://bucket-that-does-not-exist/ 2> /dev/null

This is on the most recent version of the CLI. --quiet suppressing error
output is intentional, use --only-show-errors to continue showing them
while suppressing other output.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#2187 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AArOQSLhfQSEFMjNNocblKtro2haIPXqks5qtAbNgaJpZM4KCnTp
.

andreineculau.com http://www.andreineculau.com

[JordonPhillips]

I've confirmed the issue, thanks for reporting!

[jamesls]

Confirmed fixed on the latest version of the CLI:

$ aws s3 cp s3://jamesls-test-sync/object-that-does-not-exist - 2>/dev/null
$ echo $?
1