fix: raise ValueError for unsorted ExplicitBucketHistogramAggregation boundaries#5340
Open
RudraDudhat2509 wants to merge 11 commits into
Open
Conversation
RudraDudhat2509
added a commit
to RudraDudhat2509/opentelemetry-python
that referenced
this pull request
Jun 22, 2026
Contributor
Author
tests pass on local |
xrmx
reviewed
Jun 22, 2026
Contributor
Author
|
good call added finite checks for NaN, +inf, and -inf, matching Java's full validation. tests added for all three cases |
xrmx
reviewed
Jun 23, 2026
Contributor
Author
|
good catch, updated to match that pattern, also improved the error messages to show the actual violating values, and the validation check is shifted to the top so there is no half object intialization |
herin049
reviewed
Jun 24, 2026
Contributor
Author
|
Pushed the update for simplification, lmk if anything else comes up |
herin049
approved these changes
Jun 24, 2026
Contributor
You might need to fix up the imports, otherwise LGTM! |
xrmx
reviewed
Jun 25, 2026
xrmx
reviewed
Jun 25, 2026
RudraDudhat2509
added a commit
to RudraDudhat2509/opentelemetry-python
that referenced
this pull request
Jun 25, 2026
RudraDudhat2509
force-pushed
the
fix/explicit-bucket-histogram-unsorted-boundaries
branch
from
9c4ab66 to
4f119c9
Compare
herin049
reviewed
Jun 26, 2026
Co-authored-by: Riccardo Magliocchetti <riccardo.magliocchetti@gmail.com>
Co-authored-by: Lukas Hering <40302054+herin049@users.noreply.github.com>
…egation.py accidentally changed this because i used inf without importing math previously so i replaced all instances of 'inf' with math.inf Co-authored-by: Lukas Hering <40302054+herin049@users.noreply.github.com>
RudraDudhat2509
force-pushed
the
fix/explicit-bucket-histogram-unsorted-boundaries
branch
from
7df0782 to
295a35c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fixes #5338
What's wrong
ExplicitBucketHistogramAggregationaccepts unsorted boundary lists without any validation.bisect_left(used inaggregate()) requires sorted input with unsorted boundaries, measurements are silently placed in the wrong buckets with no error or warning.What this does
Adds a validation loop in
_ExplicitBucketHistogramAggregation.__init__that raisesValueErrorif boundaries are not strictly increasing. This matches the behavior of the Java SDK (IllegalArgumentException) and the Go SDK (non-monotonic boundarieserror).Tests
Added
test_unsorted_boundaries_raiseandtest_duplicate_boundaries_raisetoTestExplicitBucketHistogramAggregation.