-
Notifications
You must be signed in to change notification settings - Fork 326
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
Allow ChainEndpoint
implementations to fetch any types of clients and consensus states
#1625
Conversation
This method was previously returning `Self::ConsensusState` instead of `AnyConsensusState` which made it impossible to implement it for non-Cosmos chains since it would force the implementation to return a `Self::ConsensusState` even when the given client id corresponds to another type of client with a different consensus state.
ChainEndpoint
implementations to fetch any types of clients and consensus states
@lightyear15 and @hu55a1n1, can you help with reviewing this, once it's marked ready for review? I think the PR is almost there. We don't have any automated tests to cover the upgrade CLIs & functionality, so we may need to test that manually. |
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.
Thanks, @romac! Nicely done! 👌 Just a couple of comments related to the separation of Tendermint specific code. I am trying to test the upgrade procedure manually and will follow up with the results soon.
Tested the upgrade functionality manually with gaiad v6.0.0 and it seems to work as expected. 👍 |
…count for any client types
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.
❤️
…nd consensus states (informalsystems#1625)
Closes: #1481
TODO
For contributor use:
unclog
.docs/
) and code comments.Files changed
in the Github PR explorer.