prisma-risk / tsoracle / 26414407657

95%

Build Type

push

github

Committed by web-flow

Commit Message

fix(core): normalize allocator write-back to a packable cursor (#430)

`try_grant` wrote back `next_logical = logical_start + count`. Because
`project_grant` admits a grant that fills a millisecond's logical range
exactly, that sum can reach `LOGICAL_MAX + 1` — a logical value the packed
46/18-bit timestamp layout cannot hold (`Timestamp::pack` asserts
`logical <= LOGICAL_MAX`).

The stored sentinel was safe only by the implicit invariant that the next
`project_grant` call always wraps or resets the cursor before it is ever
packed. Nothing enforced that structurally, leaving a latent panic one new
read path away.

Normalize at write-back instead: when the grant fills the millisecond
exactly, roll the stored cursor to `(physical_ms + 1, 0)` — the same
position the next call would have computed — so stored state is always a
directly packable pair. Observable behavior is unchanged; `next_physical_ms`
may now hold `PHYSICAL_MS_MAX + 1`, which is never packed directly and is
rejected as out-of-range by the next grant's `project_grant`.

Adds a regression test asserting the stored cursor is packable after an
exact-fill grant.

Coverage Stats

22 of 23 new or added lines in 1 file covered. (95.65%)

2 existing lines in 1 file now uncovered.

10338 of 10706 relevant lines covered (96.56%)

474042.15 hits per line