-
Notifications
You must be signed in to change notification settings - Fork 592
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
Ensure rate limits are not applied to packets that aren't ics20s #7357
Conversation
// This will error out, but not because of rate limiting | ||
suite.Require().NotContains(err.Error(), "rate limit") |
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.
Instead of notContains, could we just match the error that we get from this? Just in case we update the rate limit error in the future.
Is a nit though.
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 was thinking the same but from a different direction: if the underlying error changes in ibc, this will continue to pass. But I can add the other check when I untangle the uncommitted changes on my current branch
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.
Just a small nit, if you don't want to address feel free to merge.
What is the purpose of the change
Non-ics20 packets were being caught by rate limits. We check the packets now and skip rate limits if they don't have an amount or denom.
Testing and Verifying
added a unit test
Documentation and Release Note
Unreleased
section ofCHANGELOG.md
?Where is the change documented?
x/{module}/README.md
)