You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a chain in the v0.46.X version implemented the module parameters in the kv store and therefore added custom messages to change the parameters, the migration of the Cosmos SDK in the gov module to the v4 version does not occur. This is probably related to the fact that the package names have changed according to this information: cosmos-sdk migration protobuf and the proposal voting period migration does not work due to the lack of registered types:
func migrateProposalVotingPeriod(ctx sdk.Context, storeKey storetypes.StoreKey, cdc codec.BinaryCodec) error {
store := ctx.KVStore(storeKey)
propStore := prefix.NewStore(store, v1.ProposalsKeyPrefix)
iter := propStore.Iterator(nil, nil)
defer iter.Close()
for ; iter.Valid(); iter.Next() {
var prop govv1.Proposal
err := cdc.Unmarshal(iter.Value(), &prop)
if err != nil {
return err
}
if prop.Status == govv1.StatusVotingPeriod {
store.Set(VotingPeriodProposalKey(prop.Id), []byte{1})
}
}
return nil
}
Error message:
1:21PM INF migrating module gov from version 3 to version 4 module=server
panic: no concrete type registered for type URL /xxxxx.xxx.xxx.MsgUpdateMintersParams against interface *types.Msg
Cosmos SDK Version
v0.46, v0.47
How to reproduce?
In version v0.46.X add parameters that are stored in kv store to a given module.
Add custom message do change this parameters.
Start the chain and execute parameter change on this module
Submit software upgrade to v0.47.X
Perform the upgrade (when upgrading there should be an error after log "INF migrating module gov from version 3 to version 4 "
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
What happened?
When a chain in the v0.46.X version implemented the module parameters in the kv store and therefore added custom messages to change the parameters, the migration of the Cosmos SDK in the gov module to the v4 version does not occur. This is probably related to the fact that the package names have changed according to this information: cosmos-sdk migration protobuf and the proposal voting period migration does not work due to the lack of registered types:
Error message:
Cosmos SDK Version
v0.46, v0.47
How to reproduce?
The text was updated successfully, but these errors were encountered: