[Bug] Stopped indexing at the block number 6404191, 6404192 in Bittensor EVM network.

オープン
#6,157 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
35/100
issue の種類
バグ
明瞭さ
説明が足りない
活発さ
停滞
技術スタック
rust

調査の方向性

storageKeys が欠落していることに対して報告された decoder エラーと EthereumPollingBlockIngestor のログを再現コンテキストとして使用し、まず 6404191 と 6404192 のブロックをロードする graph-node の BlockStream パスから開始します。失敗しているブロックに対する provider のレスポンスを確認し、decoder エラーを繰り返すことなく同期がそのブロックを越えて進むことを検証します。

索引モデルが issue の本文から書いたものです。

説明

bug Stale
Bug report

I deployed the uniswap v3 subgraph for the Bittensor EVM network (chain id 964) and until now it is working well.
But yesterday, I noticed that it is stopped at the block number 6404191.
I tried too many times re-syncing but every time it was stopped at the block number 6404191.
Only 6404191 and 6404192 has this problem.
From 6404193, Syncing is working well.

This is the logs of graph node.

Relevant log output
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416281, current_block_head: 6416280, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416282, current_block_head: 6416281, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416283, current_block_head: 6416282, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
WARN Trying again after load block 0x716b…6b99 failed (attempt #10) with result Err(Decoder error: Error("missing field `storageKeys`", line: 0, column: 0)), sgd: 7, subgraph_id: Qme6NH6mTFMmTyKvSwHkXejrQzwHnLz637MoA5sSxHRmCE, component: BlockStream
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416284, current_block_head: 6416283, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416285, current_block_head: 6416284, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416286, current_block_head: 6416285, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416287, current_block_head: 6416286, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416288, current_block_head: 6416287, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416289, current_block_head: 6416288, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416290, current_block_head: 6416289, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416291, current_block_head: 6416290, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416292, current_block_head: 6416291, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416293, current_block_head: 6416292, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Scanning blocks [6404191, 6404191], target_range_size: 1, sgd: 7, subgraph_id: Qme6NH6mTFMmTyKvSwHkXejrQzwHnLz637MoA5sSxHRmCE, component: BlockStream
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416294, current_block_head: 6416293, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416295, current_block_head: 6416294, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416296, current_block_head: 6416295, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416297, current_block_head: 6416296, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416298, current_block_head: 6416297, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
WARN Trying again after load block 0x716b…6b99 failed (attempt #10) with result Err(Decoder error: Error("missing field `storageKeys`", line: 0, column: 0)), sgd: 7, subgraph_id: Qme6NH6mTFMmTyKvSwHkXejrQzwHnLz637MoA5sSxHRmCE, component: BlockStream
INFO Syncing 0 blocks from Ethereum, code: BlockIngestionStatus, blocks_needed: 0, blocks_behind: 1, latest_block_head: 6416299, current_block_head: 6416298, provider: subtensor-rpc-0, component: EthereumPollingBlockIngestor
IPFS hash

Qme6NH6mTFMmTyKvSwHkXejrQzwHnLz637MoA5sSxHRmCE

Subgraph name or link to explorer

http://34.10.242.87/subgraphs/id/Qme6NH6mTFMmTyKvSwHkXejrQzwHnLz637MoA5sSxHRmCE

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

None

主要言語
Rust
スター
3.2k
フォーク
1.1k
平均マージ
4日 1時間
マージ済み PR(30日)
1

コントリビューションガイド

コントリビューションガイドを開く

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

graphprotocol/graph-node のほかの issue

graphprotocol/graph-node の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。