-
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 {WritePerByte})
#2365
Comments
had this before, #1205, seems it's not fixed. |
grepsuzette
added a commit
to grepsuzette/gno
that referenced
this issue
Jun 17, 2024
grepsuzette
added a commit
to grepsuzette/gno
that referenced
this issue
Jun 17, 2024
grepsuzette
added a commit
to grepsuzette/gno
that referenced
this issue
Jun 27, 2024
Can't reproduce anymore, a git bisect pointed out it's not reproducible since commit f2844 (#2504). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The same kind of bug as #1205 but with
{WritePerByte}
has been happening quite a lot, when adding packages with insufficient gas.Call stack
Sometimes adding the same package and with the same gas settings I simply get
Steps to reproduce
gnodev -minimal
Edit: Note from commit f2844 onwards (#2504), the above method can't seem to reproduce this bug.
The text was updated successfully, but these errors were encountered: