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

Call go-kit/log instead of go-kit/kit/log to fix spurious debug logs #1094

Merged
merged 5 commits into from
Nov 2, 2021

Conversation

bboreham
Copy link
Contributor

@bboreham bboreham commented Nov 2, 2021

Because some upstream code is now using go-kit/log instead of go-kit/kit/log, some debug logging from that code will pass through the level filter. go-kit/kit v0.12.0 addresses this by making go-kit/kit/log just a pass-through to go-kit/log, but we need to update all the calls in Tempo otherwise golangci-lint fails because the passthrough is also marked deprecated.

Updates a number of dependencies, including the following:

  • github.com/aws/aws-sdk-go from v1.38.68 to v1.40.45
  • github.com/go-kit/log from v0.1.0 to v0.2.0
  • github.com/json-iterator/go from v1.1.11 to v1.1.12
  • github.com/hashicorp/go-hclog from v0.14.0 to v0.16.2
  • golang.org/x/net from ad29c8ab022f to 978cfadd31cf

None of these changes looks material to Tempo.

github.com/klauspost/compress updates from v1.13.5 to v1.13.6, advertising some performance improvements.

Checklist

  • NA Tests updated
  • NA Documentation added
  • CHANGELOG.md updated

This version of go-kit/kit/log is just a pass-through to go-kit/log.

Also updates a number of dependencies, including the following:
* github.com/aws/aws-sdk-go from v1.38.68 to v1.40.45
* github.com/go-kit/log from v0.1.0 to v0.2.0
* github.com/json-iterator/go from  v1.1.11 to v1.1.12
* github.com/hashicorp/go-hclog from v0.14.0 to v0.16.2
* github.com/klauspost/compress from v1.13.5 to v1.13.6
* golang.org/x/net from ad29c8ab022f to 978cfadd31cf

None of these changes looks material to Tempo.

After update, ran `go mod tidy -go=1.16 && go mod tidy -go=1.17`.
This makes `make vendor-check` pass; I don't think it actually changes
what gets linked.
They are identical - the first is a pass-through to the latter -
but the linter generates errors due to go-kit/kit/log being marked
deprecated.
@bboreham bboreham changed the title Update go-kit/kit to 0.12.0 to fix spurious debug logs Call go-kit/log instead of go-kit/kit/log to fix spurious debug logs Nov 2, 2021
Copy link
Contributor

@mdisibio mdisibio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the update. Basic testing is looking good (log level filtering, s3 backend)

@joe-elliott joe-elliott merged commit c5d007d into main Nov 2, 2021
@joe-elliott joe-elliott deleted the update-go-kit branch November 2, 2021 18:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants