Poll missing blocks in gap handler

[iuwqyir]

TL;DR

Changed block gap handling to poll missing blocks instead of marking them as failures.

What changed?

• Replaced the block failure recording mechanism in handleGap with a new polling approach
• Created a new BoundlessPoller that can poll arbitrary block ranges
• Refactored the Poller to extract common functionality into BoundlessPoller
• Updated tests to reflect the new polling behavior

How to test?

1. Run the indexer with a gap in block sequence
2. Verify that missing blocks are now polled and processed
3. Confirm that blocks are properly indexed instead of being marked as failures
4. Run unit tests to verify the new gap handling behavior

Why make this change?

The previous implementation would mark missing blocks as failures without attempting to retrieve them. This new approach actively tries to fetch and process missing blocks, improving indexing speed

[iuwqyir]

• Add missing block polling in committer #114
• Poll missing blocks in gap handler #113 👈
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @iuwqyir and the rest of your teammates on Graphite

[catalyst17]

with this new approach, under which conditions blocks can still be marked as failed?

[iuwqyir]

Merge activity

• Oct 25, 9:17 AM EDT: A user started a stack merge that includes this pull request via Graphite.
• Oct 25, 9:17 AM EDT: A user merged this pull request with Graphite.