-
Notifications
You must be signed in to change notification settings - Fork 716
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
Prepare gaia alpha release for cosmoshub-4.6 upgrade #834
Conversation
Codecov Report
@@ Coverage Diff @@
## main #834 +/- ##
========================================
- Coverage 0.41% 0.39% -0.02%
========================================
Files 7 7
Lines 483 504 +21
========================================
Hits 2 2
- Misses 480 501 +21
Partials 1 1 |
I have two places in the code commented with Note that these breaking changes don't look like they were included in the SDK changelog. |
* Updates installation, join-mainnet and first start for service provider docs * Modifies service providers doc * Updates Service Providers remote access gaia * Remove validator step from full-node setup * Updates service provider guide rest api documentation * Updates to go v1.16 on gaia v4.2.1 * Changes format on the join-mainnet guide * Updates to go v1.16 and wording in the join-mainnet documentation * Updates CLI commands * Adds more descriptive CLI command output * Adds more account cli details * Adds index with links * Remove transaction signing for now * Adds sentence that default pruning is recommended for most setups * Apply suggestions from code review Co-authored-by: Barrie Byron <barrie.byron@tendermint.com> * Use go1.15 * Remove relayer as word for http calls Co-authored-by: Barrie Byron <barrie.byron@tendermint.com>
* Changes version in reproducible-builds * Updates reproducible build example
* Update gaia to go1.16
not intended for use
@@ -68,7 +68,9 @@ func loadKeydataFromFile(clientCtx client.Context, replacementrJSON string, genD | |||
|
|||
toReplaceValConsAddress, _ := val.GetConsAddr() | |||
|
|||
consPubKey, err := sdk.GetPubKeyFromBech32(sdk.Bech32PubKeyTypeConsPub, replacement.ConsensusPubkey) | |||
// TODO: cosmoshub-4.6 |
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.
Disable linter for use of deprecated api
Wouldn't this be gaia 5.0? |
There's a regression in this branch when compared against v4.2.1. The Verified by installing this and v4.2.1 and running Haven't looked into where the bug is exactly Quickly looking at the diffs, looks like the issue should be in the SDK, but I was unable to reproduce using simd from v0.43.0-alpha1 |
@colin-axner I have a lead on the root cause for this bug. I ran into it too. It's missing changes in |
Thanks, good point. I'll apply this to the codebase. This branch name is 4.6 for now to note the tentative upgrade month, and that the Cosmos Hub chain id won't be changing. |
Here is a fix for the home flag issue. |
* Removed unnecessary slash in the link
* Adds the necessary setup to the gaia viper root to handle the home flag and config.toml file correctly * Add an environment variable prefix.
* Completing feegrant module integration * Completing authz module integration and added vesting cli
* Adds the necessary setup to the gaia viper root to handle the home flag and config.toml file correctly * Add an environment variable prefix.
Seems like non-deterministic sim is failing with
I will look into this. |
Maybe try bumping to beta1? I'd expect this to be an error in the SDK, but a lot has changed since their alpha1 release |
Thanks @colin-axner I suspect it's because feegrant module wasn't included in sim setup within the gaia app. I added it so hopefully that'll do the trick. |
Apart from adding the code that was missing, I updated to sdk beta1 and ibc-go alpha2, and the sims seem to be running. Thanks @colin-axner for the suggestion! |
The migrate command should be removed or updated. I'm in favor of updating it I view the plan for this upgrade as the following:
My main concern is validators not doing a back up before upgrade migrations and upgrade migrations failing for some unforeseen reason . Does cosmovisor do backups before restarting? I think Plan C is super rare, but if Plan A and Plan B fail, it'd be a real mess to get the network back up |
Closing this as the liquidity module has been merged into master through another branch #858 |
this branch was unrelated to the liquidity module and was preparation for SDK v0.43. Is there a new branch that will be opened? |
Closes #829
This branch is for the DEX and the upcoming Hub upgrade
Updates deps to Cosmos SDK v0.43-alpha1 and ibc-go v1.0.0-alpha1