-
Notifications
You must be signed in to change notification settings - Fork 160
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
error: panic: invalid height: 2; expected: 3
#816
Comments
Weird, not happening now. Will reopen if it happens again |
Still occuring, this time at block 5: https://app.warp.dev/block/lxqGnI1puzDtEnEiPUpEIX |
Run 1Replicated with v0.8.0-rc2 of celestia-node in https://github.com/jcstein/local-celestia-devnet Rollup logs: https://app.warp.dev/block/fbwEXCK1f4eswx3ZbLkEkD Run 2Crash at block 4: https://app.warp.dev/block/jpXpuEy2GNLOkvP0Q81Xd7 |
Run on Blockspace Race using a light nodei’m not sure what’s up with this. it doesn’t work on upgraded container for local-celestia-devnet, but works on the BSR network (logs). i’m positive i’ve cleared chain history and re-initing the chain when on local network |
Odd, still occuring on v0.8.0 of node on |
However, it works when posting to Blockspace Race testnet on v0.8.0 Balance change on DA node: Before: curl -X GET http://localhost:26659/balance
{"denom":"utia","amount":"4434000"} After: curl -X GET http://localhost:26659/balance
{"denom":"utia","amount":"4416000"} |
This is not fixed as there is no version with the fix. cc @nashqueue |
I thought last night that this error was specific to lazy aggregation, but it is happening with lazy aggregation off too. it produces 2 blocks, then errors:
panic: invalid height: 2; expected: 3
repro details: #802 (comment)
https://app.warp.dev/block/UfQ2rKEZRsgOd4XAwNisbQ full logs
The text was updated successfully, but these errors were encountered: