Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Excessive Unwanted Warning Logs #2999

Open
3 tasks done
andrewwatson opened this issue Feb 3, 2025 · 2 comments
Open
3 tasks done

Excessive Unwanted Warning Logs #2999

andrewwatson opened this issue Feb 3, 2025 · 2 comments
Labels
bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. potential-regression Marking this issue as a potential regression to be checked by team member

Comments

@andrewwatson
Copy link
Contributor

Acknowledgements

Describe the bug

I'm running these versions of the various libraries and every time i make a call to S3 i get tons of these unstructured log messages that most emphatically do not want in my stdout / stderr

	github.com/aws/aws-sdk-go-v2 v1.36.0
	github.com/aws/aws-sdk-go-v2/config v1.29.4
	github.com/aws/aws-sdk-go-v2/feature/dynamodb/attributevalue v1.18.0
	github.com/aws/aws-sdk-go-v2/feature/dynamodb/expression v1.7.66
	github.com/aws/aws-sdk-go-v2/feature/s3/manager v1.17.57
	github.com/aws/aws-sdk-go-v2/service/dynamodb v1.39.8
	github.com/aws/aws-sdk-go-v2/service/s3 v1.75.2
SDK 2025/02/03 14:38:10 WARN Response has no supported checksum. Not validating response payload.

The documentation explicitly says By default, service clients do not produce log messages. but this seems to not be true.
How can I turn this off?

Regression Issue

  • Select this option if this issue appears to be a regression.

Expected Behavior

I expect the library not to log anything by default

Current Behavior

this keeps getting piped out to my stdout/stderr

SDK 2025/02/03 14:38:10 WARN Response has no supported checksum. Not validating response payload.

Reproduction Steps

any calls to S3 to ListObjects, ListObjectVersions, PutObject etc

Possible Solution

No response

Additional Information/Context

No response

AWS Go SDK V2 Module Versions Used

	github.com/aws/aws-sdk-go-v2 v1.36.0
	github.com/aws/aws-sdk-go-v2/config v1.29.4
	github.com/aws/aws-sdk-go-v2/feature/dynamodb/attributevalue v1.18.0
	github.com/aws/aws-sdk-go-v2/feature/dynamodb/expression v1.7.66
	github.com/aws/aws-sdk-go-v2/feature/s3/manager v1.17.57
	github.com/aws/aws-sdk-go-v2/service/dynamodb v1.39.8
	github.com/aws/aws-sdk-go-v2/service/s3 v1.75.2

Compiler and Version used

% go version go version go1.23.4 darwin/arm64

Operating System and version

MacOS 15.2

@andrewwatson andrewwatson added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Feb 3, 2025
@github-actions github-actions bot added the potential-regression Marking this issue as a potential regression to be checked by team member label Feb 3, 2025
@andrewwatson
Copy link
Contributor Author

when i downgrade to 1.27.0 the issue goes away. I also tried this to override logging options and that didn't work either.

	cfg, err := config.LoadDefaultConfig(context.TODO(), config.WithRegion("us-east-1"), config.WithClientLogMode(aws.ClientLogMode(0)))
	if err != nil {
		panic(err)
	}

Maybe something like a aws.LogNone option to disable logging completely?

@andrewwatson
Copy link
Contributor Author

ok i found this that seems relevant #2976 so I guess I just need to go into my code where i fetch things from S3 and add

func(o *s3.Options) {
		o.DisableLogOutputChecksumValidationSkipped = true
	}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. potential-regression Marking this issue as a potential regression to be checked by team member
Projects
None yet
Development

No branches or pull requests

1 participant