Commit 0ad1c4b
committed
Remove incorrect duplicate batch skipping in ReorgAwareStream
The _is_duplicate_batch check was incorrectly skipping batches based only
on comparing ranges to the previous batch. This is wrong because:
1. Proper duplicate detection is handled by state_store.is_processed() in
load_stream_continuous, which checks against ALL processed batches
2. The range-only comparison does not check hashes, so batches with same
ranges but different data (after reorg) would be incorrectly skipped
3. After crash/restart, prev_ranges_by_network is empty anyway1 parent 8ce25f1 commit 0ad1c4b
1 file changed
+0
-7
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
49 | 49 | | |
50 | 50 | | |
51 | 51 | | |
52 | | - | |
53 | | - | |
54 | | - | |
55 | | - | |
56 | | - | |
57 | | - | |
58 | | - | |
59 | 52 | | |
60 | 53 | | |
61 | 54 | | |
| |||
0 commit comments