fix(server): preserve integer metrics precision#32
Draft
esko wants to merge 1 commit into
Draft
Conversation
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
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.
CACHE-002 completed all 36 requests but exact metric reconciliation failed: direct prompt timings summed to 1,423,152 while /metrics emitted 1,423,150 because integer JSON values were coerced to double and rendered with default stream precision.
This change preserves signed and unsigned integer JSON types and emits exact decimal literals. Finite floating metrics use round-trip-safe precision; nonnumeric and nonfinite values fail safely. HELP/TYPE/sample layout and metric names remain unchanged.
Validation:
Correctness-only change; no performance claim. Do not merge until deployment repin and full CACHE-002 rerun are reviewed.