-
Notifications
You must be signed in to change notification settings - Fork 96
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
test: disable rate limit #427
Conversation
|
src/test/TestGhoCcipSteward.t.sol
Outdated
@@ -252,6 +252,105 @@ contract TestGhoCcipSteward is TestGhoBase { | |||
); | |||
} | |||
|
|||
function testDisableRateLimitFromNonZeroToZero() public { |
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 we can rename to testChangeEnabledRateLimit
and test both directions: enabled -> disabled -> enabled
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.
as per discussion on slack: it is currently expected behaviour that Steward cannot re-enable disabled rate limits (due to these range checks using the current value as max permittable value) and once disabled, the dao can enable rate limits again by directly interacting with the token pool
test for this behaviour added in - a194c76
No description provided.