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
Update — the diagnostic endpoint now returns raw oog_info samples and the format is not what the original issue body assumed. There's no struct at all:
(All three random non-null samples have this exact text. The accompanying divergence_location for the same rows is the usual DivergenceLocation { contract: 0x…, function_selectors: [], pc: 0, call_depth: 0, opcode: 0, opcode_name: "" } — itself with placeholder values per #3.)
So the oog_info field as it currently lands in the parquet is just the EVM error's Display string — no contract address, no pc, no call depth, no opcode, no gas_remaining. The consumer's regex pipeline (which expects OutOfGasInfo { contract: 0x…, pc: …, call_depth: …, opcode_name: "…", pattern: "…", gas_remaining: … }) was anticipating richer data that never gets written.
So this isn't the same shape as #3 (struct with placeholders) — it's "the structured OOG context never gets constructed; only the error display reaches the parquet."
What the consumer needs from oog_info to make the OOG analysis useful:
contract: the address whose call ran out of gas (probably the inner-most callee)
pc: program counter at the OOG step
call_depth: how deep the call stack was when OOG fired
opcode / opcode_name: which opcode was executing when gas ran out
pattern: a coarse classifier (e.g. Basic / Memory / Precompile / StateGas) — OutOfGas(Basic) is already a step in this direction, but it would help to also surface things like OutOfGas(Stipend2300) for the 63/64 stipend case
gas_remaining: gas at the point of OOG (in the current frame and probably the parent frame too)
A struct like OutOfGasInfo { contract, pc, call_depth, opcode, opcode_name, pattern, gas_remaining } written via Debug would parse cleanly under the existing regex shape used for DivergenceLocation, so this is largely about plumbing the missing fields through.
Activity
v-jitenderpalsingh commentedon Sep 1, 2026
Closing as spam.
eraandriyanerandriyan-blip commentedon Sep 2, 2026
Originally posted by @CarlBeek in #6
eraandriyanerandriyan-blip commentedon Sep 2, 2026
``