Andrey Vasnetsov ec66b87042 fix: notify pending consensus ops on snapshot apply (#8990) ...

When an `AddPeer` / `RemovePeer` / `UpdatePeerMetadata` /
`UpdateClusterMetadata` operation is proposed locally and then committed
remotely, the resulting log entry can be delivered back to us as part of
a raft snapshot rather than as a regular log entry. In that case the
operation never flows through `apply_conf_change_entry` /
`apply_normal_entry`, so the awaiter registered by
`propose_consensus_op_with_await` was never woken and timed out after
10s — manifesting as flaky failures of `test_peer_snapshot_bootstrap`
("Failed to add peer: ... Waiting for consensus operation commit failed").

Resolve awaiters in `apply_snapshot` whenever their effect is directly
observable in the new persistent state.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-11 15:50:56 +02:00

..

src

fix: notify pending consensus ops on snapshot apply (#8990)

2026-05-11 15:50:56 +02:00

tests/integration

Dynamic cpu pool (#8790)

2026-04-27 12:56:29 +02:00

Cargo.toml

Remove unused dependency crates (#8589)

2026-04-01 18:15:18 +02:00