Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Add fallback for ancestor_block to handle cache truncation #6262

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

Open
incrypto32 wants to merge 3 commits into krishna/alloy-abi-fixes
base: krishna/alloy-abi-fixes
Choose a base branch
Loading
from krishna/ancestor-block-rpc-fallback

Conversation

@incrypto32
Copy link
Member

@incrypto32 incrypto32 commented Jan 8, 2026

Subgraphs would stall when block cache is truncated because ancestor_block returned None when the requested ancestor wasn't in cache.

This PR adds RPC/Firehose fallback for ancestor_block logic

When ancestor_block falls back to RPC due to cache deserialization failures,
fetch full blocks with receipts instead of light blocks. Empty receipts caused
missing block handler call triggers and log triggers.
Copy link
Member Author

@lutter Integration cluster caught an issue i have updated the PR with the fix, i was using a Light Block for the rpc fall back for ancestor_block and was keeping an empty array for transaction_receipts, this was not right. So i've added a commit that uses the full block instead.

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

Reviewers

@lutter lutter Awaiting requested review from lutter

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

AltStyle によって変換されたページ (->オリジナル) /