Open
Description
Bug description
Running Callisto (using juno 5.3.0) I get this ERR logs:
9:41AM ERR re-enqueueing failed block err="failed to get transactions for block: error while unpacking message: no concrete type registered for type URL /ibc.core.client.v1.MsgUpdateClient against interface *types.Msg" height=94108
9:41AM ERR re-enqueueing failed block err="failed to get transactions for block: error while unpacking message: no concrete type registered for type URL /ibc.applications.transfer.v1.MsgTransfer against interface *types.Msg" height=94925
9:41AM DBG processing block height=94925
9:41AM DBG processing block height=94108
9:41AM ERR re-enqueueing failed block err="failed to get transactions for block: error while unpacking message: no concrete type registered for type URL /ibc.core.client.v1.MsgUpdateClient against interface *types.Msg" height=14532
9:41AM DBG processing block height=14532
9:41AM DBG enqueueing missing block height=95445
9:41AM ERR re-enqueueing failed block err="failed to get transactions for block: error while unpacking message: no concrete type registered for type URL /ibc.applications.transfer.v1.MsgTransfer against interface *types.Msg" height=95173
9:41AM DBG processing block height=95173
9:41AM ERR re-enqueueing failed block err="failed to get transactions for block: error while unpacking message: no concrete type registered for type URL /ibc.core.client.v1.MsgUpdateClient against interface *types.Msg" height=95169
9:41AM DBG processing block height=95169
9:41AM ERR re-enqueueing failed block err="failed to get transactions for block: error while unpacking message: no concrete type registered for type URL /ibc.applications.transfer.v1.MsgTransfer against interface *types.Msg" height=94090
9:41AM DBG processing block height=94090
9:41AM ERR re-enqueueing failed block err="failed to get transactions for block: error while unpacking message: no concrete type registered for type URL /ibc.core.client.v1.MsgUpdateClient against interface *types.Msg" height=94764Steps to reproduce
Syncing the chain bitcanna-1 we get this errors with old blocks (SDK v044 to v046) and new blocks (v047 from height 12288420)
Expected behavior
The expected behavior is to parse the IBC update & ack messages or skip them after a configurable number of retries (or low amount like 2 or 3 times)