-
Notifications
You must be signed in to change notification settings - Fork 346
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
[bug/portal_loop] runtime error: index out of range [2] with length 0
while deploying certain realm on poral-loop
#2283
Comments
Okay, leaving an update on my current investigation. Replication set-upI'm running a gno.land node with this genesis.json. This is a trimmed-down version of the portal loop genesis.json. With this genesis.json, publishing succeeds. To run using this genesis file, you'll need to change the validators key so that your local instance is a validator. You can get the fields you need from Then, I'm running the node with this command:
This allows me to reset the node and start from this genesis. I get the logs redirected to FindingsRunning the replication step pointed above by @r3v4s:
As I said in the previous section, publishing succeeds with the provided genesis.json. However, it won't if you first broadcast this transaction: feeds-add.json. (This should work by simply doing After that, you get the panic pointed above. (This error happens also if the transaction is in the genesis). The surprising, and most revealing, fact about this is that if you re-start the node (without clearing the database/state); then publishing works as normal. SuspicionsLooking through some logs, my suspicions are:
That's it for this week, I may continue this another time. |
Note: I'm trying to get a txtar working before doing an actual fix. If my suspicion is correct, then we'll probably need to discuss either a) removing the caches from the Store (and just using the tm2 store cache), which does support transaction rollback properly, or b) creating a cache system in the Store that can properly handle rollbacks/commits. |
#2319 I found a way to replicate the issue; don't know if I'll have time to fix it though I'm thinking that attempting to fix it would mean trying to make |
I'm prioritizing a fix for this one in the next week, to be ready by Gophercon |
Description
We're trying to deploy our realms against portal-loop, but pool realm is failing while
gnokey maketx addpkg
with below error.Steps to reproduce on LOCAL [couldn't really reproduce on local. it doesn't panic, but succeeds]
unable to reproduce this issue on local chain, seems to be happening only in portal-loop.
Tried below ways on portal-loop, but none of them succeeded
gas-wanted
to maxExpected behaviour
pool should be deployed
Actual behaviour
panic
FYI
There is realm that imports pool realm, such as position
Since deploying pool has been failed on portal-loop, deploying position needs to be fail with message like
unknown import found gno.land/r/demo/pool
. However deploying position also panic with same error(index ouf of range)The text was updated successfully, but these errors were encountered: