Handle fractional rate limits in thread history projection - #36083
Merged
copyberry[bot] merged 1 commit intoJul 30, 2026
Conversation
## Why Paginated thread history could reject valid rollout records when rate-limit percentages were encoded as floating-point JSON values, preventing later final answers from being projected. ## What changed Deserialize each rollout line through `serde_json::Value` before converting it to `RolloutLine`, preserving floating-point rate-limit values during history materialization. ## Testing Added coverage for projecting fractional, integral, very small, and large floating-point rate-limit percentages across both catch-up materialization and subsequent history appends. GitOrigin-RevId: 68da907987ffe59f4a3033ef90f3b88c39734cb1
copyberry
Bot
force-pushed
the
copyberry/codex-internal-to-codex-oss/68da907987ffe59f4a3033ef90f3b88c39734cb1
branch
from
July 30, 2026 04:55
18e90dc to
88ec932
Compare
copyberry
Bot
deleted the
copyberry/codex-internal-to-codex-oss/68da907987ffe59f4a3033ef90f3b88c39734cb1
branch
July 30, 2026 04:56
AndyAlvarezDev
temporarily deployed
to
issue-triage
July 30, 2026 05:26 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
AndyAlvarezDev
temporarily deployed
to
issue-triage
July 30, 2026 05:26 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
AndyAlvarezDev
temporarily deployed
to
issue-triage
July 30, 2026 05:26 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
SlavaVasilakiy
temporarily deployed
to
issue-triage
July 30, 2026 05:46 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
SlavaVasilakiy
temporarily deployed
to
issue-triage
July 30, 2026 05:46 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
SlavaVasilakiy
temporarily deployed
to
issue-triage
July 30, 2026 05:46 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
8 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.
Handle fractional rate limits in thread history projection
Why
Paginated thread history could reject valid rollout records when rate-limit
percentages were encoded as floating-point JSON values, preventing later final
answers from being projected.
What changed
Deserialize each rollout line through
serde_json::Valuebefore converting itto
RolloutLine, preserving floating-point rate-limit values during historymaterialization.
Testing
Added coverage for projecting fractional, integral, very small, and large
floating-point rate-limit percentages across both catch-up materialization and
subsequent history appends.