metrics: Fix bug where num_buckets became inconsistent #6957
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.
Motivation
In Tokio 1.41, #6897 refactored histograms and their construction. Unfortunately, this change included a bug where
num_buckets
was not properly preserved when the legacy builder methods were used. This could cause an inconsistency where even if the customer set max buckets, we would still use the default.This can result in a runtime panic because the histogram thinks it has
N
buckets, but in reality, it only has 10.Solution
Fix the bug.