prisma-risk / tsoracle / 26350123394 / 1
95%
main: 95%

DEFAULT BRANCH: main
Ran
Files 74
Run time 2s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 94.724% (-0.01%) from 94.736%
26350123394.1

push

github

web-flow 
fix(client): seat leader hints atomically under the monotone-forward check (#240) (#274)

The decision to honor a NOT_LEADER hint and the cache write were two
separate lock acquisitions: `classify_not_leader_hint` checked the
monotone-forward rule via `accept_hint`, released the lock, and the
dispatch loop later wrote via `set_leader_with`. A concurrent
`record_success(higher_epoch)` landing between them could be overwritten
by the lower-epoch hint, briefly moving the cache backward during a
leadership transition. The monotone-forward guarantee held per-operation
but not across the gate-then-write pair.

Replace the pair with a single `compare_and_set_leader(endpoint, epoch)`
that re-checks the rule and writes under one lock acquisition, returning
whether the write happened. The rule itself is unchanged: reject only
when the cache is fresh, both epochs are known, and the hint's epoch is
strictly below the cached one; absent/expired entries and unknown epochs
still accept. `classify_not_leader_hint` calls it directly (its return
value still selects LeaderHint vs StaleLeaderHint), and the redundant
write in the dispatch loop is removed.

`accept_hint` and `set_leader_with` had no remaining production callers
and would have tripped the dead-code lint, so both are removed and their
tests migrated onto `compare_and_set_leader`.

10503 of 11088 relevant lines covered (94.72%)

462722.06 hits per line

Source Files on job 26350123394.1