eth_getBlockByHash RPC call failed

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:

Apr 09 23:32:01.095 WARN Trying again after load block 0x7a35…fb8a failed (attempt #10) with result Err(Decoder error: Error("invalid length 64, expected a (both 0x-prefixed or not) hex string with length of 40", line: 0, column: 0)), sgd: 1, subgraph_id: QmXiZ4ZeVSCCdo3jHpj1oeGXtPPirfRSXjNXGjAJAnrCpr, component: BlockStream

Apr 09 23:32:01.100 ERRO Subgraph instance failed to run: Decoder error: Error("invalid length 64, expected a (both 0x-prefixed or not) hex string with length of 40", line: 0, column: 0), sgd: 1, subgraph_id: QmXiZ4ZeVSCCdo3jHpj1oeGXtPPirfRSXjNXGjAJAnrCpr, component: SubgraphInstanceManager

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

Start by reproducing the failure from the v0.26.0 Docker image with an Alchemy archive node and inspect the eth_getBlockByHash call reported by the BlockStream component. The work is done when the same block loads without the decoder error and the subgraph continues running.