-
Notifications
You must be signed in to change notification settings - Fork 54
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
build: upgrade ibc-go from v2 to v3 #131
Conversation
- bump ibc-go from v2.2.0 to v3.3.1 - bump cosmos-sdk to v0.45.10 - add v3 upgrade handler script - resolve golang ci linter issues - resolve failing test cases
We can discuss if we need to upgrade (UPDATE) We decided to bump ibc-go to v3.4.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for your work. In task, there is Add v4 upgrade handler script (Allow MsgLimitOrder and MsgMarketOrder custom messages)
. Shouldn't this be out?
I'm not sure if I follow. If you look inside the |
99a5f89
to
b7c94f5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Description
This PR migrates from ibc-go from v2.2.0 to either v3.3.1.This PR migrates from ibc-go from v2.2.0 to either v3.4.0.
closes: #124
Tasks
MsgLimitOrder
andMsgMarketOrder
custom messages)farming
module due to reverted customization in cosmos-sdk (dynamic block address)References
Notes
Transferring tokens with slashes from Chain A (ibc-go v3.4.0) to Chain B (ibc-go v2.2.0) fails due to the following error message
ABCI code: 1: error handling packet on destination chain: see events for details
. See this transaction hash that is executed to try transferring tokens with slashes from Chain A (ibc-go v3.4.0) to Cosmos Hub (ibc-go v3.0.0 at the time of writing).After doing some research, ABCI code 1 is an internal error and it is coming from
trace info must come in pairs of port and channel identifiers
error in this line of code because the IBCtransfer
module expects trace path information to always have an even number of identifiers. It's unfortunate that the events don't tell much about the actual error. Error message handling is improved in v3.4.0 and that is why we need to upgrade Core asap.Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.
docs/
) or specification (x/<module>/spec/
)godoc
comments.Files changed
in the Github PR explorerCodecov Report
in the comment section below once CI passes