[Bug] Celo blocks before Gingerbread fail to parse since v0.42.0 (missing `sha3Uncles`)
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 52/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- rust
- 領域
- backend, blockchain
研究方向
Read the Alloy migration in #6063 and the earlier Celo fix in commit bfba0af or #2284 to see how the missing sha3Uncles field was handled. Reproduce the deserialization failure for a pre-Gingerbread block such as 18946750, then trace the block parsing path. Done means those blocks parse successfully while post-Gingerbread behavior remains correct.
由索引模型根據 Issue 內容生成。
描述
Bug report
Since v0.42.0, graph-node can't parse Celo blocks from before the Gingerbread hard fork (mainnet block 21616000). Every eth_getBlockByNumber / eth_getBlockByHash call for such a block fails, and the call is retried without a limit:
Trying again after eth_getBlockByNumber RPC call for block number 18946750 failed (attempt #6) with result Err(deserialization error: missing field `sha3Uncles` at line 1 column 2161 ...
Subgraphs that need these blocks from RPC stall on re-deployments, re-syncs, and grafts with a start block before 21616000.
Root cause
Celo blocks before Gingerbread have no uncles hash in their header, so RPC nodes omit sha3Uncles. Gingerbread added the field back.
- Up to v0.41.x, graph-node used rust-web3 fork. Commit
bfba0af(2021-03-16, pulled in by #2284) made the lack ofsha3Unclesfor Celo not an issue by establishing a default value. - #6063 (merged 2026-01-22, released in v0.42.0) replaced rust-web3 with alloy. The Celo patch wasn't ported for the alloy library.
Relevant log output
Trying again after eth_getBlockByNumber RPC call for block number 18946750 failed (attempt #6) with result Err(deserialization error: missing field `sha3Uncles` at line 1 column 2161 ...
IPFS hash
No response
Subgraph name or link to explorer
No response
Some information to help us out
- Tick this box if this bug is caused by a regression found in the latest release.
- Tick this box if this bug is specific to the hosted service.
- I have searched the issue tracker to make sure this issue is not a duplicate.
OS information
Linux
- 主要語言
- Rust
- 星號
- 3.2k
- 分支
- 1.1k
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
graphprotocol/graph-node 的其他 Issue
-
current: include emits an all-null bucket for dimensionless aggregations, nulling the whole response未關閉
難度 2/5 1-3 小時 新手友好度 78/100
graphprotocol/graph-node#6719 ·
-
RUSTSEC-2026-0194: Quadratic run time when checking a start tag for duplicate attribute names可能已有人在做 @szupzj18 於 62 天前認領。 未關閉
難度 2/5 1-3 小時 新手友好度 68/100
graphprotocol/graph-node#6673 ·
-
RUSTSEC-2026-0185: Remote memory exhaustion in quinn-proto from unbounded out-of-order stream reassembly可能已有人在做 @abisheik687 於 104 天前認領。 未關閉
難度 2/5 1-3 小時 新手友好度 70/100
graphprotocol/graph-node#6650 · 1 則留言 ·
-
[Bug] Subgraph startup rehashes the WASM module once per data source (minutes for subgraphs with millions of dynamic data sources)可能已有人在做 @madumas 於 4 天前認領。 未關閉
難度 3/5 半天 新手友好度 22/100
graphprotocol/graph-node#6731 · 1 則留言 ·
-
`loadRelated` can return stale children while blocks are queued for writing (`!= any` in `FindDerivedQuery`; unrelated queued writes not excluded)可能已有人在做 @madumas 於 10 天前認領。 未關閉
難度 4/5 3-5 天 新手友好度 50/100
graphprotocol/graph-node#6726 ·
查看 graphprotocol/graph-node 的全部 Issue
相似的 Issue
-
agent:iq3-xxs area: cli duplication enhancement priority: P3 ready-for-agent
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 85/100
維護者通常 2 天內回覆
-
難度 2/5 1-3 小時 新手友好度 68/100
bytecodealliance/rustix#1703 ·
維護者通常 3 天內回覆
-
bug discussion
難度 2/5 1-3 小時 新手友好度 70/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 74/100
farion1231/cc-switch#8298 ·
維護者通常 1 天內回覆