Unable to fetch block using Hardhat node

[zeGzD]

Unable to fetch block using Hardhat node

[marty-nilli]

I'm seeing this same error on Ubuntu. When I run the same setup on Mac, it does work properly (and the frontend returns transactions made against Hardhat). It may have to do with host.docker.internal reference that seemingly doesn't exist on Linux the same way it does on Mac/Win??

[zeGzD]

This issue is still there with the last version.

[zeGzD]

@vbaranov Still not working with the last release.
The backend log keeps getting spammed with things like:
{"time":"2024-04-15T15:16:25.828Z","severity":"error","message":"failed to fetch block: [%{code: 404, data: %{number: 6}, message: \"Not Found\"}]. Block will be retried by catchup indexer.","metadata":{"block_number":6,"fetcher":"block_realtime"}}

[vbaranov]

Please provide all steps to reproduce the issue.

[zeGzD]

1. Grab blockscout for docker-compose : https://github.com/blockscout/blockscout/tree/master/docker-compose
2. Add one container running hadhat with, by example, this config:

require("hardhat-tracer");

module.exports = {
    defaultNetwork: "hardhat",  
    networks: {
      hardhat: {
        chainId: 31337,
        gas: 30000000,
        blockGasLimit: 0x1fffffffffffff,
        gasPrice: 20000000000,
        mining: {
          auto: true
        },
      },
    },
    solidity: "0.8.21"
};

3. Up the container stack and wait for every single container to be running
4. Setup metamask on the hardhat container and verify the default wallet addresses actually own 1000 ETH
5. Start making basic transferts from those addresses and verify in the hardhat node log the transactions are passed (and in metamask the balances have changed)
6. Check the blockscout frontend to see no data are populated, then check the blockscout backend container log to see the errors I told about previously

[zeGzD]

@vbaranov feel free to let me know if you need more details