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

fix(gov): fail proposal when implementation not found #17873

Merged
merged 8 commits into from
Sep 26, 2023
Merged

Conversation

julienrbrt
Copy link
Member

@julienrbrt julienrbrt commented Sep 25, 2023

Description

This adds logic to fail a proposal when its message isn't registered.
This can typically happen after an upgrade, the chain developer removed a type that were used in a proposal on chain.
Credits to @colin-axner that found the issue on v0.50 rc.


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title
  • added ! to the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • followed the guidelines for building modules
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • included comments for documenting Go code
  • updated the relevant documentation or specification
  • reviewed "Files changed" and left comments if necessary
  • run make lint and make test
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed ! in the type prefix if API or client breaking change
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic
  • reviewed API design and naming
  • reviewed documentation is accurate
  • reviewed tests and test coverage
  • manually tested (if applicable)

@julienrbrt julienrbrt added the backport/v0.50.x PR scheduled for inclusion in the v0.50's next stable release label Sep 25, 2023
@julienrbrt julienrbrt marked this pull request as ready for review September 25, 2023 20:08
@julienrbrt julienrbrt requested a review from a team as a code owner September 25, 2023 20:08
@github-actions

This comment has been minimized.

Copy link
Contributor

@likhita-809 likhita-809 left a comment

Choose a reason for hiding this comment

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

one qq, otherwise lgtm

x/gov/abci.go Outdated Show resolved Hide resolved
x/gov/abci.go Outdated Show resolved Hide resolved
x/gov/abci.go Outdated Show resolved Hide resolved
Copy link
Contributor

@colin-axner colin-axner left a comment

Choose a reason for hiding this comment

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

ACK, tested with our e2e's:

proposal failed to decode; deleted expedited=false module=x/gov proposal=2 results="collections: encoding error: value decode: no concrete type registered for type URL /ibc.core.client.v1.UpgradeProposal against interface *v1beta1.Content" title=title

@julienrbrt julienrbrt added this pull request to the merge queue Sep 26, 2023
Merged via the queue into main with commit 2f7bc22 Sep 26, 2023
49 checks passed
@julienrbrt julienrbrt deleted the julien/fix-gov branch September 26, 2023 11:31
mergify bot pushed a commit that referenced this pull request Sep 26, 2023
(cherry picked from commit 2f7bc22)

# Conflicts:
#	CHANGELOG.md
julienrbrt added a commit that referenced this pull request Sep 26, 2023
… (#17882)

Co-authored-by: Julien Robert <julien@rbrt.fr>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/v0.50.x PR scheduled for inclusion in the v0.50's next stable release C:x/gov
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants