New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Handle `head` events where blocks can't get retrieved #80

Open

PJColombo opened this issue Jan 29, 2025 · 0 comments

Member

PJColombo commented Jan 29, 2025 •

edited

Loading

There could be the case where a head event is received and immediately after the slot gets orphaned

indexer-1  | 2025-01-29T16:41:56.021497Z ERROR blob_indexer::indexer: An error occurred while running a syncing task error=LiveIndexingError(BeaconEventHandlingError(HeadEventHandlerError(BlockHeaderNotFound(Slot(3522208)))))
indexer-1  | Error: failed to handle beacon event
indexer-1  |
indexer-1  | Caused by:
indexer-1  |     header for block "3522208" not found

(holesky example)

We should skip the event handling if it happens instead of throwing error

The text was updated successfully, but these errors were encountered:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment