prisma-risk / tsoracle / 26350529015

95%

push

github

fix(driver-openraft): validate snapshot meta.last_log_id against payload.last_applied (#276)

`install_snapshot` applied openraft's `meta` and the decoded payload
independently: `get_current_snapshot` reads back `meta.last_log_id` while
`applied_state` reads back `payload.last_applied`. `build_snapshot` derives
both from the same `last_applied`, so an honest peer never produces a
mismatch — but if they ever disagreed (corruption, a peer bug), the install
would silently desync those two reader methods permanently, with no error.

Guard at the top of `install_snapshot`: reject a `meta.last_log_id` /
`payload.last_applied` disagreement with an `InvalidData` io::Error before
persisting or mutating, so a rejected install leaves both the store and
in-memory state untouched for openraft to retry. Chosen over `debug_assert!`
because the desync is a production-safety hazard and would compile out of
release builds.

Closes #261

40 of 43 new or added lines in 1 file covered. (93.02%)

10553 of 11139 relevant lines covered (94.74%)

476878.97 hits per line