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
feat: ics 29 packet callbacks #357
feat: ics 29 packet callbacks #357
Changes from 31 commits
7b51ebd
150211d
412f3b6
734ead7
1e894fe
f735e57
435a2fa
8d0c194
bfa8795
09985ce
ff7db8a
8c6d8ec
9d9bcae
d8e4429
e514f1a
f561cc0
97cc863
0a0022d
8e83ba2
40951eb
e8b2ddc
04763b6
e574499
e7297a8
db93ac9
2870993
64f77b9
721a6c7
9f00d29
0844485
e374cb2
232e906
a8c69db
6c85913
9d84834
141d281
76b7de9
7ced819
dc33d66
903b9d5
8fc3aac
2a061e4
aae78ce
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.
should we keep the same naming for both rather than source/forward?
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.
This isn't actually testing the
OnAcknowledgementPacket
call, it's just testing your setup functions.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.
Ahhh, I think see what you're doing here. The setup in
suite.run
fails when you don't explicitly escrow the packet etc in each test case. I think it would be easier to read (and also reduce code) if you calledEscrowPacketFee
after calling malleate and used each case to malleate/change the data to force the test to fail :)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.
it's not really that the setup fails but that the OnAck callback checks if an identified fee exists, so if it hasn't been escrowed then that error should surface
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.
Yeah, I see. I feel like it's a bit hard to read using the malleate functions like this (I think the general approach is you change (malleate) data here to force an error rather than have the default case fail) but I think it's ok for now :)
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 don't understand the purpose of
suite.Require().Error(types.ErrFeeNotFound)
. It is just asserting thattypes.ErrFeeNotFound
is of type error, it isn't checking any logic related to ibc_module.go