-
Notifications
You must be signed in to change notification settings - Fork 610
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
update app, middleware and 05-port modules with ChanUpgradeTimeout
function
#3859
update app, middleware and 05-port modules with ChanUpgradeTimeout
function
#3859
Conversation
proofErrorReceipt []byte, | ||
proofHeight ibcexported.Height, | ||
) error { | ||
return im.app.OnChanUpgradeTimeout(ctx, portID, channelID, counterpartyChannel, prevErrorReceipt, proofCounterpartyChannel, proofErrorReceipt, proofHeight) |
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.
any reason why you forward here instead of nil? Just curious.
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.
ah, because we are calling it from the controller middleware here which should pass the call through to the app for the app callback.
basically, this would be called in the usecase where you have an underlying module that you want to use to authenticate ICA actions (the kinda v0 auth module design we had for ICA), and then you wrap that application with the ICA controller middleware. in the v1 design you can pass a nil
app to the ICA controller middleware, and use the controller msg_server
directly.
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.
LGTM!
…m:cosmos/ibc-go into charly/chanupgradetimeout-app-module-impl
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.
Looks good to me 🚀
Can you link me to the discussion for adding |
Where do you see I see:
|
ahhhh i think youre absolutely right 🙈 |
will correct in a followup pr! |
Sounds good, no worries. Just made sense to me to only have 1 app callback for channel upgrade failure scenarios |
Description
part of the work needed for #3855
note that this PR does not actually implement the functionality of the app callbacks, it only sets up the blocker
Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.
docs/
) or specification (x/<module>/spec/
).godoc
comments.Files changed
in the Github PR explorer.Codecov Report
in the comment section below once CI passes.