From 70b969c3c4932e882e3ed3e7249c18722e6bb16f Mon Sep 17 00:00:00 2001 From: tv Date: Tue, 17 Nov 2026 02:02:53 +0000 Subject: simtest: show what screening holds back in a failed simulation's dump A failed simulation prints, for each node, the writer it writes as, the changes its screening keeps waiting (the latest few: whose writer and seq, how many of their dependencies it holds, whether a signature vouches for them) and the latest changes it refused, and, holding a store, the store's checkpoint, current version and what it took and refused. --- src/access/screen.rs | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'src/access/screen.rs') diff --git a/src/access/screen.rs b/src/access/screen.rs index f9c67bf..b6fb8fd 100644 --- a/src/access/screen.rs +++ b/src/access/screen.rs @@ -283,6 +283,12 @@ impl Waiting { self.0.len() } + /// The changes waiting, oldest first. + #[cfg(test)] + pub(crate) fn changes(&self) -> &[Change] { + &self.0 + } + /// The newest `MAX_WAITING`: the oldest go, so changes a peer sent that will never /// be taken (whose dependencies or signatures never come) make way for others. fn keep_newest(&mut self) { -- cgit v1.3.1