[Bug] arbitrum-one not working

[rotarur]

Bug report

Every time the graph-node restarts I see these logs bellow.

This makes the pod to take more time restarting.

I found these logs bellow to help defining the fix

Affected Image tag: 55cff04 Working Image tag: fc80657

Relevant log output

After every graph-node restart:

graph-node Nov 22 11:08:46.708 DEBG Trying again after IPFS.Gateway.send_test_request failed (attempt #3) with result Err(RequestFailed(RequestError(reqwest::Error { kind: Status(403
) })))
graph-node Nov 22 11:08:47.170 DEBG Trying again after IPFS.Gateway.send_test_request failed (attempt #4) with result Err(RequestFailed(RequestError(reqwest::Error { kind: Status(403
) })))
graph-node Nov 22 11:08:53.800 DEBG Trying again after IPFS.Gateway.send_test_request failed (attempt #5) with result Err(RequestFailed(RequestError(reqwest::Error { kind: Status(403
) }))

Nov 22 11:18:33.794 ERRO Provider 'arbitrum-firehose-pinax' does not support extended blocks on chain 'arbitrum-one'
Nov 22 11:18:33.794 ERRO Unable to get a connection for block ingestor, err: all providers failed for chain 'arbitrum-one', component: EthereumFirehoseBlockIngestor
Nov 22 11:18:34.046 ERRO Unable to get a connection for block ingestor, err: all providers failed for chain 'arbitrum-one', component: EthereumFirehoseBlockIngestor

IPFS hash

No response

Subgraph name or link to explorer

No response

Some information to help us out

• [X] 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.
• [X] I have searched the issue tracker to make sure this issue is not a duplicate.

OS information

Linux

[matthewdarwin]

Pinax supports extended blocks for arbitrum-one only for nitro blocks. For classic blocks, they are base blocks. Pinax returns the type of block supported as "hybrid".

[matthewdarwin]

Apparently there is some sort of flag you can set in graph-node to bypass this check.

[matthewdarwin]

GRAPH_NODE_FIREHOSE_DISABLE_EXTENDED_BLOCKS_FOR_CHAINS="arbitrum-one" see https://github.com/graphprotocol/graph-node/pull/5672/files for the changes that implement this check

[rotarur]

thanks @matthewdarwin . this worked fine and now I see arbitrum-one blocks ingested

[rotarur]

is there any update on this issue? I had to disable the extended blocks support for all these chains bellow

              value: "arbitrum-one,optimism,mainnet,starknet-mainnet,matic,sepolia,bsc,solana-devnet"

[abarmat]

I came across this issue looking for something else. Shouldn't it be closed? since the default way the graph-node works is to validate for extended blocks unless disabled.

[github-actions[bot]]

Looks like this issue has been open for 6 months with no activity. Is it still relevant? If not, please remember to close it.