From 3cbb667655468f77f1343be213f4ef27505f22e8 Mon Sep 17 00:00:00 2001 From: Johnathan Corgan Date: Sun, 3 May 2026 23:51:32 +0000 Subject: [PATCH] Regenerate show_bloom snapshot for next-branch bloom v2 stats The control-query show_bloom snapshot, baselined on master, mismatches the next-branch output because the bloom filter v2 work on next added six new stats fields (deltas_sent, full_sends, nacks_received, nacks_sent, size_changes, total_compressed_bytes, total_raw_bytes) and dropped non_v1. The snapshot test correctly flagged this as schema drift. The drift is intentional (next's bloom v2 is a deliberate schema expansion, not a regression), so the right action per the test's own guidance is to delete the fixture and let the test regenerate it against next's actual output. No production-code change. --- src/control/snapshots/show_bloom.json | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/src/control/snapshots/show_bloom.json b/src/control/snapshots/show_bloom.json index 1fdb6c8..8c5f5ff 100644 --- a/src/control/snapshots/show_bloom.json +++ b/src/control/snapshots/show_bloom.json @@ -10,13 +10,19 @@ "accepted": 0, "debounce_suppressed": 0, "decode_error": 0, + "deltas_sent": 0, "fill_exceeded": 0, + "full_sends": 0, "invalid": 0, - "non_v1": 0, + "nacks_received": 0, + "nacks_sent": 0, "received": 0, "send_failed": 0, "sent": 0, + "size_changes": 0, "stale": 0, + "total_compressed_bytes": 0, + "total_raw_bytes": 0, "unknown_peer": 0 } },