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

Backport #9081: bump tendermint core #9082

Merged
merged 2 commits into from
Apr 8, 2021

Conversation

alessio
Copy link
Contributor

@alessio alessio commented Apr 8, 2021

From: #9081


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.

  • Targeted PR against correct branch (see CONTRIBUTING.md)
  • 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 tests
  • Updated relevant documentation (docs/) or specification (x/<module>/spec/)
  • Added relevant godoc comments.
  • Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
  • Re-reviewed Files changed in the Github PR explorer
  • Review Codecov Report in the comment section below once CI passes

Depends on 0.34.9.
@@ -410,7 +409,7 @@ func (s *IntegrationTestSuite) TestQueryDelegationsResponseCode() {
val := s.network.Validators[0]

// Create new account in the keyring.
info, _, err := val.ClientCtx.Keyring.NewMnemonic("test", keyring.English, sdk.FullFundraiserPath, keyring.DefaultBIP39Passphrase, hd.Secp256k1)
info, _, err := val.ClientCtx.Keyring.NewMnemonic("test", keyring.English, sdk.FullFundraiserPath, hd.Secp256k1)
Copy link
Contributor

Choose a reason for hiding this comment

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

@alessio can you clarify what this is doing, and why this is necessary here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

API change introduced in the keyring. The build was broken since 5aec5e6 was merged in

Copy link
Contributor

Choose a reason for hiding this comment

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

@alessio the commit you link here is the one from this PR. Is there another commit with the actual prior change? I'd like to understand if we need to have this fixed on master, or if not, why this has diverged?

Copy link
Contributor

Choose a reason for hiding this comment

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

Answering my own question here. The new keyring api on master has not actually been backported to v0.42.x yet, so this needs to diverge from master until we backport the keyring API to v0.42.x

@clevinson clevinson merged commit 13418f1 into release/v0.42.x Apr 8, 2021
@clevinson clevinson deleted the alessio/042x-tm-core-0349 branch April 8, 2021 19:26
@aaronc aaronc removed the backlog label Apr 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants