I have also seen pretty same errors here (but w/o the txHash field in the response body) and here (the txHash has 0x0...0 value like in the current issue, although there's no any TypeError and even "error" field).
Actually it looks like there's a bug in built-in tracers' code
I'm not sure whether these issues are related to each other, its' behaviours looks pretty same, but I can't find an issue which combines both of them :/
Next days I'll also update op-geth & op-node and then will check if response changes in a better way; the report will be here
System information
op-geth image: us-docker.pkg.dev/oplabs-tools-artifacts/images/op-geth:v1.101308.2 op-node image: us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.7.2 historicalrpc geth image: ethereum/client-go:v1.12.0 OS & Version: Debian GNU/Linux 11 (bullseye)
op-geth params
op-node params
historicalrpc geth params:
Expected behaviour
'Usual' response with no error
Actual behaviour
Steps to reproduce the behaviour
Backtrace
No backtrace
Comment
I have also seen pretty same errors here (but w/o the txHash field in the response body) and here (the txHash has 0x0...0 value like in the current issue, although there's no any TypeError and even "error" field). Actually it looks like there's a bug in built-in tracers' code
I'm not sure whether these issues are related to each other, its' behaviours looks pretty same, but I can't find an issue which combines both of them :/
Next days I'll also update op-geth & op-node and then will check if response changes in a better way; the report will be here