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
{{ message }}
Repository navigation
debug_trace* ignores the limit tracing option #1902
The Ethereum execution-apis spec defines the limit field of TraceConfig as the "maximum number of opcode steps to capture. Zero means no limit. When the limit is reached, execution continues but no further StructLog entries are recorded." EDR accepts the field and ignores it.
Request, for a transaction that executes seven opcodes:
Hardhat 2 forwards tracing options unchanged (NomicFoundation/hardhat#7985), so its users get the full trace too.
Cause
alloy_rpc_types_trace::geth::GethDefaultTracingOptions has a limit: Option<u64> field, but revm-inspectors never reads it. TracingInspectorConfig::from_geth_config only maps enable_memory, disable_stack, disable_storage and enable_return_data, and CallTraceArena::geth_traces emits every recorded step.
Possible fixes
Upstream in revm-inspectors, stop recording steps once limit steps have been emitted, or truncate in geth_traces.
Or in edr_provider, truncate structLogs to limit entries after DebugInspector::get_result when limit is non-zero.
Found while writing the debug_trace* contract tests in crates/edr_provider/src/requests/debug/tests.rs on the test/debug-trace-contract branch. A test for this requirement can be added once the behaviour is fixed.
Activity
Wodann commentedon Oct 29, 2026
Fixed on
mainby the revm-inspectors 0.44 upgrade in #1847, and pinned by a test in #1907.