From 8f15aa311f9022df4084fc8ec2a04cde81cf5414 Mon Sep 17 00:00:00 2001 From: sprites0 <199826320+sprites0@users.noreply.github.com> Date: Sun, 12 Oct 2025 02:22:55 +0000 Subject: [PATCH] fix: Fix --debug-cutoff-height semantics NOTE: This is a debug feature not on by default. The original intention of it was limiting the highest block number. But it was instead enforcing the starting block number for fetching, leading to block progression. --- src/pseudo_peer/service.rs | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/src/pseudo_peer/service.rs b/src/pseudo_peer/service.rs index d0324b6e7..ddca88f1b 100644 --- a/src/pseudo_peer/service.rs +++ b/src/pseudo_peer/service.rs @@ -81,13 +81,13 @@ impl BlockPoller { .await .ok_or(eyre::eyre!("Failed to find latest block number"))?; - if let Some(debug_cutoff_height) = debug_cutoff_height && - next_block_number > debug_cutoff_height - { - next_block_number = debug_cutoff_height; - } - loop { + if let Some(debug_cutoff_height) = debug_cutoff_height + && next_block_number > debug_cutoff_height + { + next_block_number = debug_cutoff_height; + } + match block_source.collect_block(next_block_number).await { Ok(block) => { block_tx.send((next_block_number, block)).await?;