[Bug] gnosis chain run on last nethermind client returned wrong data for indexer with extra ENUM values (trace_filter)

Bug report

Details

graph-node: 0.34 that runs on my host
client for gnosis chain: nethermind v1.25.2 (archive node)

Solution

Seems we have to add this enum to the lib as TheGraph team did before for a couple of networks like Fantom and Celo, ref https://github.com/graphprotocol/graph-node/blob/7fd43cd123ba563489c345f88137823221db2eba/graph/Cargo.toml#L70C1-L74C1

Relevant log output

DEBG Trying again after trace_filter RPC call for block range: [32183842..32183842] failed (attempt #5) with result Err(Decoder error: Error("data did not match any variant of untagged enum Action", line: 0, column: 0)), sgd: 2, subgraph_id: QmV9TkSDSGxj6xfA8inuusq8YtxDbbwKsZzR8tzv3BiSQL, component: BlockStream

IPFS hash

QmV9TkSDSGxj6xfA8inuusq8YtxDbbwKsZzR8tzv3BiSQL

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

Start with graph/Cargo.toml around the referenced network-specific enum entries, then inspect the BlockStream trace_filter decoding path implicated by the log. Verify that the Gnosis response with extra ENUM values no longer produces the Decoder error for the reported block range.