Parse receipts reason in a better way

[luizstacio]

Motivation

Today when a transaction fails, we do not parse the reason in a proper way, making it very difficult to debug errors.

Receipt output example

[
  {
    "type": "Panic",
    "id": "0x0000000000000000000000000000000000000000000000000000000000000000",
    "reason": "733327132687597568",
    "pc": "12336",
    "is": "10352"
  },
  {
    "type": "ScriptResult",
    "result": "2",
    "gasUsed": "14773"
  }
]

edit: Hex string for the panic here is 0x000000000000000300000000000000000000000000000000000000000000000000000000000000000a2d4d245000000000000000000030300000000000002870
We should parse "reason": "733327132687597568", to the proper enum issue name https://docs.rs/fuel-asm/latest/fuel_asm/enum.PanicReason.html.

[QuinnLee]

Can i take this issue?

[luizstacio]

Can I take this issue?

I just assigned it to you!

[QuinnLee]

I parsed Panic Receipts from tests where fuel core returns an error and the decoded values do not make sense.

0x0000000000000003
00000000000000000000000000000000000000000000000000000000000000000a2d4d245000000000000000000030300000000000002870

a2d4d2450000000 is the encoded reason, but decoding it doesn't make sense because the values should be between 0-255; decoded value is 733327132687597568

Is there a different way to decode the value or parse the resulting number?

Docs
https://github.com/FuelLabs/fuel-specs/blob/8bb43ae61aab69e72275c004792aef34efed1d9b/specs/protocol/abi.md#panic-receipt

https://docs.rs/fuel-asm/latest/fuel_asm/enum.PanicReason.html

[QuinnLee]

I think we are handling the graphql response incorrectly. I looked at the requests via wireshark and I can see the correct reason. I'll dig into this more