promql: Fix issue where summation of +/- infinity returns NaN instead of infinity #14362
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.
This fixes an issue with
kahanSumInc
which would result in NaN being used as the final result when +Inf or -Inf was one of the values added.I've expanded the test coverage of
kahanSumInc
to cover these cases and others involving NaN.This does now mean that
kahanSumInc
does an extra check for Inf at each step. An alternative to this would be to check for +Inf or -Inf when computing the final result (ie. after all the calls tokahanSumInc
), but I opted for this as the simplest, least invasive change given how widelykahanSumInc
is used.This also revealed what I believe was an incorrect test case in
promql/promqltest/testdata/native_histograms.test
, where the stddev and stdvar were incorrectly calculated when a native histogram contained a sample at +Inf.