[Bug] arbitrum-one not working

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

• 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

Comienza comparando las etiquetas de imagen 55cff04 y fc80657; después, sigue los reintentos de IPFS.Gateway.send_test_request y la ruta de conexión de EthereumFirehoseBlockIngestor para arbitrum-one. Comprueba cómo el proveedor arbitrum-firehose-pinax gestiona los bloques extendidos; se considera terminado cuando graph-node se reinicia sin los reintentos repetidos con 403 y establece una conexión con el ingestor de bloques.