Skip to content
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.

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

Scraper should not miss events #5027

Open
ameten opened this issue Dec 17, 2024 · 0 comments
Open

Scraper should not miss events #5027

ameten opened this issue Dec 17, 2024 · 0 comments
Assignees

Comments

@ameten
Copy link
Contributor

ameten commented Dec 17, 2024

Problem

Is your feature request related to a problem? Please describe.
Currently Scraper can miss a delivery message event when it cannot ensure that a block or a transaction are stored into database. It happens in the cases, for example, when RPC is not functional and Scraper cannot request a block or a transaction.

Additional context
It happens only in Scraper since Validator is only indexing MerkleTreeInsertion (always sequance-aware) and Relayer is indexing HyperlaneMessages (sequence-aware), MerkleTreeInsertions (sequence-aware) and InterchainGasPayments (watermark-aware but with back channel from HyperlaneMessages).

Solution

Describe the solution you'd like
Scraper should not advance its cursors if some of the logs are not indexed for any reason.

@ameten ameten self-assigned this Dec 17, 2024
@ameten ameten moved this to Backlog in Hyperlane Tasks Dec 17, 2024
@ameten ameten moved this from Backlog to Sprint in Hyperlane Tasks Dec 17, 2024
@ameten ameten moved this from Sprint to In Progress in Hyperlane Tasks Dec 17, 2024
@ameten ameten moved this from In Progress to In Review in Hyperlane Tasks Dec 18, 2024
@cmcewen cmcewen moved this from In Review to In Progress in Hyperlane Tasks Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

1 participant