handle string nan results in pool_health_check_stats #14
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.
If a node is defined but in status=unused, the
average_retry_count
and
average_duration
columns appear to return a literal stringresult of
-nan
. The result parsing switch correctly returnsmath.NaN()
in this case, but will returnfalse
as the second returnvalue, leading to errors being logged:
(45, 110, 97, 110 are the sequential ordinal values for
-nan
)Check for a literal value of
-nan
in the string/byte parsing portionof
dbToFloat64()
and returnmath.NaN(), true
, since in this casewe are correctly forwarding a NaN value.