graphprotocol / graphprotocol/graph-node
[Bug] Graph node doesn't index the forked hardhat network correctly.
Nessuno ha ancora preso questa issue.
- Lingua principale
- Rust
- Stelle
- 3.2k
- Fork
- 1.1k
- Merge medio
- 4g 1h
- PR unite (30g)
- 1
Descrizione
Bug report
I run hardhat node forking Arbitrum.
I deployed subgraph to the local graph node using https://github.com/radiant-capital/radiant-subgraph/tree/fix-local.
But the api returns empty arrays and it doesn't seem to index it correctly.
Relevant log output
`radiant_indexer | Aug 30 15:40:34.021 INFO Downloading latest blocks from Ethereum, this may take a few minutes..., provider: 31337-rpc-0, component: EthereumPollingBlockIngestor
radiant_indexer | Aug 30 15:40:34.236 ERRO Trying again after block polling failed: Receipt for tx 0xeb96942da9c2a907a30a34883132dbc463022c1365475e96ed422c35c01dfae2 unavailable, block was likely uncled (block hash = 0xcedad82558e06d0de0e1687486c27a79ea28a601975d17918c6bbf1c98132cee), provider: 31337-rpc-0, component: EthereumPollingBlockIngestor
radiant_indexer | Aug 30 15:40:35.240 INFO Downloading latest blocks from Ethereum, this may take a few minutes..., provider: 31337-rpc-0, component: EthereumPollingBlockIngestor
radiant_indexer | Aug 30 15:40:35.426 ERRO Trying again after block polling failed: Receipt for tx 0xeb96942da9c2a907a30a34883132dbc463022c1365475e96ed422c35c01dfae2 unavailable, block was likely uncled (block hash = 0xcedad82558e06d0de0e1687486c27a79ea28a601975d17918c6bbf1c98132cee), provider: 31337-rpc-0, component: EthereumPollingBlockIngestor
radiant_indexer | Aug 30 15:40:36.429 INFO Downloading latest blocks from Ethereum, this may take a few minutes..., provider: 31337-rpc-0, component: EthereumPollingBlockIngestor
radiant_indexer | Aug 30 15:40:36.640 ERRO Trying again after block polling failed: Receipt for tx 0xeb96942da9c2a907a30a34883132dbc463022c1365475e96ed422c35c01dfae2 unavailable, block was likely uncled (block hash = 0xcedad82558e06d0de0e1687486c27a79ea28a601975d17918c6bbf1c98132cee), provider: 31337-rpc-0, component: EthereumPollingBlockIngestor`
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
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Inizia riproducendo il report con un Hardhat node che esegue il fork di Arbitrum e analizza i log di EthereumPollingBlockIngestor, in particolare la ricevuta della transazione e l’hash del blocco non disponibili. Il report non indica file sorgente né test; il lavoro sarà considerato completato quando la rete sottoposta a fork verrà indicizzata correttamente e l’API restituirà i dati del subgraph distribuito.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- blockchain, rust
- Ambito
- backend-api-design, blockchain
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 25/100