prisma-risk / tsoracle / 26374152608

95%

Build Type

push

github

Committed by web-flow

Commit Message

feat(core): lift a shared TsoPeer type into tsoracle-core (#266) (#325)

The paxos toolkit and the (dead) driver-paxos type config each carried
their own `{ node_id: u64, endpoint: String }` struct for the consensus
node + advertised tsoracle endpoint used to populate
`LeaderState::Follower::leader_endpoint`. Define the concept once as
`tsoracle_core::TsoPeer` (Clone/Debug/Eq/Hash + optional serde, matching
the Epoch/Timestamp convention) and have both backends use it:

- paxos-toolkit: replace the local `Peer` with `TsoPeer`; `from_omnipaxos`
  now takes `&[TsoPeer]`. Re-exported from the `lifecycle` module.
- driver-paxos: delete the unused `PaxosPeer` and its re-export.
- driver-openraft: `with_peers`/`from_arc_with_peers` ingest
  `impl IntoIterator<Item = TsoPeer>` (bounded `NodeId: From<u64>`) via a
  new `endpoint_map_from_peers` helper; `new`/`from_arc` stay bound-free.

`OpenraftPeer { addr }` is intentionally left untouched: it is openraft's
`Node` type persisted in membership entries (the raft transport address),
a distinct concept from the tso advertised endpoint — the openraft driver
already resolves leader endpoints from a separate node-id -> endpoint map.

Lands as `feat:` (not `refactor:`) so the new tsoracle-core symbol
publishes ahead of the dependent driver crates.

Coverage Stats

99 of 107 new or added lines in 6 files covered. (92.52%)

8 existing lines in 1 file now uncovered.

11354 of 11971 relevant lines covered (94.85%)

466767.28 hits per line