Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
ChanUpgradeTimeout
handler for 04-channel #3829ChanUpgradeTimeout
handler for 04-channel #3829Changes from all commits
50b1163
ba1fde4
8cd8c0b
392a5b5
0a363de
a227949
8b18b02
7b8b67b
760940b
106ac13
7f12c0b
29f84ce
16f196a
17748af
7341c5a
e9a2c20
900dcb6
8cf4a62
661f006
ba5e566
e3315ea
e1e7da7
de2607d
634b53e
6070c07
8fc3ee6
2df489c
065b003
5b9fa3e
470ee69
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I think this needs to be
<=
. We should not timeout an upgrade where our sequence matches the counterparty upgrade sequence and there exists an error receipt for that upgrade attempt. That should indicate a cancellationnote, I think using
<=
would match the spec as the spec asserts:Thus if the
sequence == error receipt sequence
, the spec fails but this implementation does not@AdityaSripal
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.
i can make a followup PR for this issue! but i think also, now looking at the two functions, im really wondering if there is a way to combine these two such that there is first a check on
proofHeight
to see if it has passed theTimeout
. if so, then we follow theTimeout
flow. Otherwise, we follow theCancel
flow. and then we just expose one API/msg_server function. wdyt?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.
ref #3905