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: RegisterLegacyAminoCodec should error if Msg name is >39 chars #496

Closed
wants to merge 2 commits into from

Conversation

mattverse
Copy link
Member

Description

Closes: osmosis-labs/osmosis#1106, backport cosmos#11349

What is the purpose of the change

Fixes so that RegisterLegacyAminoCodec errors if Msg name is >39 chars, this has been a long bug that has not been addressed for a long time.


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)

Copy link

github-actions bot commented Jan 6, 2024

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale label Jan 6, 2024
@czarcas7ic
Copy link
Member

czarcas7ic commented Jan 7, 2024

@mattverse can this be revived against the osmo/v0.47.5 branch?

Also, wouldn't it make more sense to just add this directly to osmosis? Since we aren't going to be registering any custom messages generally direct to sdk, and keeps us further from the fork (unless you are going to upstream)

@github-actions github-actions bot removed the Stale label Jan 8, 2024
@ValarDragon
Copy link
Member

Based on ledger updates per matt, seems like we can actually close!

@mattverse mattverse closed this Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Switch RegisterLegacyAminoCodec -> RegisterAminoMsg
3 participants