-
Notifications
You must be signed in to change notification settings - Fork 359
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 client upgrade #2304
Fix client upgrade #2304
Conversation
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.
Left some improvement suggestions.
Co-authored-by: Adi Seredinschi <adi@informal.systems>
Can we add an integration test for client upgrade? Maybe in a different PR? |
I would vote for a different PR; I never looked into our integration framework, and I currently don't have the capacity to delve into it. But I agree that it is desirable; I'll create one and assign myself as an opportunity to learn it. |
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.
* use appropriate query height in upgrade * changelog * use application height in build_update_client * don't wait for target height * better error message * Update relayer/src/foreign_client.rs Co-authored-by: Adi Seredinschi <adi@informal.systems> * docstrings and var name change * use ibc::Height::decrement * add warning * query_latest_height call once Co-authored-by: Anca Zamfir <zamfiranca@gmail.com> Co-authored-by: Adi Seredinschi <adi@informal.systems>
Closes: #2185
Description
I did not add a
query_chain_height()
vsquery_latest_application_height()
, as thequery_chain_height()
would only be used in the special case of a client upgrade. Also, I now think it would be best if the cli for client upgrade forced the user to specify the chain upgrade height: it would be better UX IMO, and we wouldn't need to ever query the "chain height" (i.e. tendermint height). To be considered when dealing with #2300.PR author checklist:
unclog
.docs/
).Reviewer checklist:
Files changed
in the GitHub PR explorer.