Skip to content

bug(forge): custom errors are not decoded in invariant test traces #4178

@PaulRBerg

Description

@PaulRBerg

Component

Forge

Describe the feature you would like

Custom errors are not decoded in invariant test traces:

  [87114] LockupLinear_Handler::createStream((48843050768258118766642263247164992475545483473374652544843776, (0x00000000000000000000000000000000000045Fe, 1051), false, 287754237733202155210052262418297055004, (7300, 19493552128, 2031), 0x000000000000000000000000000000000000075F, 0x00000000000000000000000000000000000002AE))
    ├─ [0] console::log(Bound Result, 86) [staticcall]
    │   └─ ← ()
    ├─ [0] VM::startPrank(Actor 86: [0x0871433Ba612011908963BB42a64F42d65AD2f72])
    │   └─ ← ()
    ├─ [0] VM::assume(true) [staticcall]
    │   └─ ← ()
    ├─ [0] VM::assume(false) [staticcall]
    │   └─ ← 0x464f554e4452593a3a415353554d45
    └─ ← 0x464f554e4452593a3a415353554d45

The 0x464f554e4452593a3a415353554d45 at the end is the custom error the transaction reverted with, and it is part of my code base.

Update: here's another trace:

[FAIL. Reason: Custom Error 216caf0d:(0x0000000000000000000000000000000000000009, 201181830302072226773591759703971470263002656411)]

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions