Call go-kit/log instead of go-kit/kit/log to fix spurious debug logs #1094
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.
Because some upstream code is now using
go-kit/log
instead ofgo-kit/kit/log
, some debug logging from that code will pass through the level filter.go-kit/kit
v0.12.0 addresses this by makinggo-kit/kit/log
just a pass-through togo-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:
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
CHANGELOG.md
updated