trace_get returns error -- differs to Nethermind

[tjayrush]

System information

Erigon version: ./erigon --version

The error appears differently on two different versions. See below.

erigon version 2022.99.99-dev-c0de0488 erigon version 2022.99.99-dev-bcb3cac2

OS & Version: Windows/Linux/OSX

OSX

Commit hash :

Expected behaviour

Returns the same data as Nethermind and also the same data it used to return a few weeks/months ago.

Actual behaviour

Returns null value in version at commit c0de0488 and error message at commit bcb3cac2.

Steps to reproduce the behaviour

Use this curl command against Nethermind, then commit bcb3cac2, then commit c0de0488. See three different results.

curl --data '{"method":"trace_get","params":["0x6df0b4a0d15ae3b925b9819646a0cff4d1bc0a53b294c0d84d884865302d13a5",["0x17"]],"id":"3","jsonrpc":"2.0"}' -H "Content-Type: application/json" -X POST <RPC_ENDPOINT>

Against Nethermind:

{
  "jsonrpc": "2.0",
  "result": [
    {
      "action": {
        "callType": "call",
        "from": "0x109c4f2ccc82c4d77bde15f306707320294aea3f",
        "gas": "0x8fc",
        "input": "0x",
        "to": "0xeab290b146d9fc82589a817012aa157d5963aa61",
        "value": "0x5d423c655a9ffff"
      },
      "blockHash": "0x186551139aa3ac5918543ccab0319281fc9e8fae9977b76182be7156d6b79d86",
      "blockNumber": 50871,
      "result": {
        "gasUsed": "0x0",
        "output": "0x"
      },
      "subtraces": 0,
      "traceAddress": [
        23
      ],
      "transactionHash": "0x6df0b4a0d15ae3b925b9819646a0cff4d1bc0a53b294c0d84d884865302d13a5",
      "transactionPosition": 0,
      "type": "call"
    }
  ],
  "id": "3"
}

Against commit c0de0488

{
  "jsonrpc": "2.0",
  "id": "3",
  "result": null
}

EDIT: Note - this machine is fully synced.

Against commit bcb3cac2

{
  "jsonrpc": "2.0",
  "id": "3",
  "error": {
    "code": -32000,
    "message": "first run for txIndex 0 error: nonce too high: address 0xf88a65846C19D8fc76fFf545fEAa7bbc7114F667, tx: 2 state: 0"
  }
}

EDIT: Note - this last result may be related to the sync state of the chain. This machine is still syncing...