You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When making debug_traceBlockByNumber RPC request for transactions that failed with out-of-gas error response would not include anything in the error field.
🐛 Bug Report
📝 Description
When making
debug_traceBlockByNumber
RPC request for transactions that failed with out-of-gas error response would not include anything in theerror
field.🔄 Reproduction Steps
Example transactions:
Block 2558830 -> Tx: 0x1d55f591f2dec2db4ede9dfdf1e921c38f315daeddfc5f4f690ab13c1fa0cc72 (example listed above)
Block 2637427 -> Tx: 0xacb4bb951661950a9cb0df04f3e5ce8dce37c98a684924a07e1bab5f118202c8
Block 2610752 -> Tx: 0x38822e3ef0298e9131790333356986d5051784861e43e602da5a9b97b8c66118
Block 2579103 -> Tx: 0x45634aa7756181707f1b8e6ef6404069c4f2c4506f20466ed637850a113237ab
Block 2642447 -> Tx: 0x94fc982c4c2fb8146912f15a362bb5292e8094a77ec68c6be243e5861cec2321
🤔 Expected Behavior
error
field includes error message😯 Current Behavior
In the response
error
field would benull
.🖥️ Environment
Mainnet
📋 Additional Context
Github Discussion report - zkSync-Community-Hub/zksync-developers#836
📎 Log Output
The text was updated successfully, but these errors were encountered: