Skip to content
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

Merged
merged 14 commits into from
Dec 21, 2022

Conversation

queencre
Copy link
Contributor

@queencre queencre commented Dec 14, 2022

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

  • Bump ibc-go and cosmos-sdk
  • Add v4 upgrade handler script (Allow MsgLimitOrder and MsgMarketOrder custom messages)
  • Commend out some lines of code in the farming module due to reverted customization in cosmos-sdk (dynamic block address)
  • Resolve golangci linter issues
  • Resolve failing test cases
  • Update docs

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 IBC transfer 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.

  • Appropriate labels applied
  • Targeted PR against correct branch
  • Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
  • Code follows the module structure standards.
  • Wrote unit and integration
  • Updated relevant documentation (docs/) or specification (x/<module>/spec/)
  • Added relevant godoc comments.
  • Re-reviewed Files changed in the Github PR explorer
  • Review Codecov Report in the comment section below once CI passes

- 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
@github-actions github-actions bot added the build label Dec 14, 2022
@queencre
Copy link
Contributor Author

queencre commented Dec 15, 2022

We can discuss if we need to upgrade ibc-go to v3.4.0 or even above (v0.4.x or v0.5.x).

(UPDATE) We decided to bump ibc-go to v3.4.0

@github-actions github-actions bot removed the build label Dec 19, 2022
@queencre queencre marked this pull request as ready for review December 19, 2022 05:08
Copy link
Member

@richard-bachman richard-bachman left a 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?

@queencre
Copy link
Contributor Author

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 upgrades/mainnet/v4/upgrades.go, we should define what messages to be allowed as a host chain.

go.mod Show resolved Hide resolved
Copy link
Contributor

@kingcre kingcre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@queencre queencre merged commit 388bf88 into crescent-network:main Dec 21, 2022
@queencre queencre mentioned this pull request Dec 21, 2022
12 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bump ibc-go from v2.2.0 to v3.3.1
4 participants