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 }}
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.
Since we know how much gas is left, we should be able to deduce that we're out of gas, instead of the current message:
There was no revert message. This may be due to an in intentional halting expression, such as assert(), revert(), or require(), or could be due to an unintentional exception such as out-of-gas exceptions.
Please inspect your transaction parameters and contract code to determine the meaning of this error.
If we use trace.step's gasCost and gas, we might be able to provide a higher degree of certainty for out-of-gas errors.
The text was updated successfully, but these errors were encountered:
Hm, do we know that gasCost is reliable? I'd want to check that out before implementing this. If it is then I guess this should be fine.
There's also the question of whether this is only checked at end of transaction or on any revert. I suppose we'd have to do the latter if we want to to work it with the stacktraces, but that's not too bad; we cam just store that info.
Notionally we could expand this system to other low-level reasons, but that probably isn't worth it because people care about the high-level reasons, not the low-level reasons, and that would be a lot harder (and low-level reasons other than out of gas, invalid instruction, and REVERT aren't that likely to come up in a contract compiled from a higher-level language like Solidity).
Since we know how much gas is left, we should be able to deduce that we're out of gas, instead of the current message:
If we use
trace.step
'sgasCost
andgas
, we might be able to provide a higher degree of certainty for out-of-gas errors.The text was updated successfully, but these errors were encountered: