prisma-risk / tsoracle / 26350400767

95%

push

github

fix(server): carry the fencing epoch into the NOT_LEADER hint on stepdown (#275)

When persist_high_water returns ConsensusError::Fenced { current, .. }
mid window-extension, the stepdown discarded current and published a
NotServing hint with leader_epoch: None, so a fenced client got no epoch
to validate its next leader against.

step_down_due_to_consensus_rejection now takes leader_epoch and the
Fenced arm passes Some(current). NotLeader keeps omitting one: the paxos
persist path fences via Fenced, not NotLeader.

Closes #244

13 of 13 new or added lines in 2 files covered. (100.0%)

10513 of 11096 relevant lines covered (94.75%)

474395.02 hits per line