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
Currently, when contract runs out of gas, you can see the 'panic' message, but you don't know the reason. It would be great if we passed the clear information that this was caused by out of gas.
🤔 Rationale
This will make debugging a lot easier.
🖼️ Mockups/Examples
This should say 'out of gas' instead of 'only' Panic.
📋 Additional Context
You can fetch the panic reason from the error_flags.
Here's the (very dirty) example, how this could work: 8338df6
We should probably move it either into CallTracer - or create a separate tracer just for era test node to catch and print this information.
The text was updated successfully, but these errors were encountered:
🌟 Feature Request
📝 Description
Currently, when contract runs out of gas, you can see the 'panic' message, but you don't know the reason. It would be great if we passed the clear information that this was caused by out of gas.
🤔 Rationale
This will make debugging a lot easier.
🖼️ Mockups/Examples
This should say 'out of gas' instead of 'only' Panic.📋 Additional Context
You can fetch the panic reason from the error_flags.
Here's the (very dirty) example, how this could work:
8338df6
We should probably move it either into CallTracer - or create a separate tracer just for era test node to catch and print this information.
The text was updated successfully, but these errors were encountered: