Open imbenwolf opened 2 years ago
Thanks for reporting, could you please provide reproduction instructions? Either a subgraph we can build, or a subgraph id that can be found on a public IPFS gateway (such as the hosted service).
Thanks for reporting, could you please provide reproduction instructions? Either a subgraph we can build, or a subgraph id that can be found on a public IPFS gateway (such as the hosted service).
hi, thanks for the reply! sure thing, here is a fork of this repo with the code changed to reproduce the issue: https://github.com/imbenwolf/graph-node-issue-3450
the steps are:
cd docker
export ARCHIVE_NODE=[alchemy archive node url]
docker-compose up -d
& wait for the block ingestor to start polling for eth_getBlockByHash to see the issue logged in graph-node docker service.
again, thanks for looking at this!
Using the following versions:
@leoyvens can you reproduce?
@imbenwolf this looks like this is related to using a ganache mainnet fork rather than an Alchemy URL directly. Have you experienced this with Alchemy directly? And have you had success running regular ganache (i.e. not forking mainnet)?
happening with anvil as well WARN Trying again after eth_getBlockByNumber(0, false) RPC call failed (attempt #15) with result Err(Decoder error: Error("invalid length 1, expected a (both 0x-prefixed or not) hex string with length of 16", line: 0, column: 0)), provider: mainnet-rpc-0
fails with/without fork enabled. just fails in general using ganache/anvil. how do you guys run a local graph node connected to a local testnet?
Same error for arbitrum goerli testnet
Do you want to request a feature or report a bug? bug
What is the current behavior? using v0.26.0 docker image, graph-node fails with:
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. using alchemy archive node as the mainnet url in docker compose
What is the expected behavior? not failing