-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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]: Panic when upgrading to v0.50 from v0.47.x #18644
Comments
Can you try with the latest commit from release/v0.50.x? We have a fix supporting for empty consensus params for v0.50.2. |
Oh, based on the change that I see, it will fix our issue but will try and get back to you on that. Thanks! |
Btw, I see this comment in the fix:
The comment says that this could happen when migrating from |
If you didn't migrate your consensus params in v0.47 (https://github.com/cosmos/cosmos-sdk/blob/release/v0.47.x/UPGRADING.md#xconsensus), then yes 😅. |
It worked! Thanks again :) |
Is there an existing issue for this?
What happened?
Hey, we are testing our node that we recently upgraded to sdk version v0.50. When starting from scratch, the node is running without an issue but when we upgrade from 0.47.x to 0.50, our node panics with the following message:
We followed the migration guide. Also we have fixed the problem by setting the
ConsensusParam
inFinalizeBlock
in a very hacky way but this shouldn't be the solution. I'm thinking that we are missing something but couldn't find the cause.Cosmos SDK Version
0.50
How to reproduce?
Run a v0.47 chain, then upgrade to v0.50.
The text was updated successfully, but these errors were encountered: