-
Notifications
You must be signed in to change notification settings - Fork 379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
out of gas error is unclear (VM call panic: {ReadPerByte}
)
#1205
Comments
It's actually an 'out of gas' error. Solution: increase gas wanted. The hint is in the stacktrace: the line after panic.go is gas.go. I'd still say to keep this issue open until we make the error clear. |
Damn! It worked at |
VM call panic: {ReadPerByte}
)
have a base solution to make the error clear, more digging needed to beautify the entangled logs:
|
I think you can already make a PR with this. The logs should be improved in general, and it's part of the greater effort in #999 and probably needs to be discussed further :) |
This issue should be fixed, the errors should now be saner:
|
VM call panic: {ReadPerByte}
Description
VM halts with a panic on calling this code. I'm not sure which part of it generates it, but I suspect it may be related to how we read marshalled JSONs.
call:
Stack trace:
realm function call (flippando.gno):
package related functions (flippandoserver.gno):
client calls (gno-js-client):
flip.js
actions.ts
Your environment
Steps to reproduce
The repo containing all the above code is here: https://github.com/irreverentsimplicity/gno, feel free to pull and try generating a call using some of the approaches above.
Expected behaviour
The call should returned a formatted JSON.
Actual behaviour
The call generates a VM panic
Proposed solution
No proposed solution.
The text was updated successfully, but these errors were encountered: