-
Notifications
You must be signed in to change notification settings - Fork 6
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: rate limiting #231
feat: rate limiting #231
Conversation
@@ -539,6 +525,24 @@ pub async fn verify_identity( | |||
}) | |||
} | |||
|
|||
fn parse_cacao_statement(statement: &str, domain: &str) -> Result<AuthorizedApp> { |
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 be in a different PR as it seems is not related to the rate limiting
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 related because the rate limit prevents more than 5 /notify
calls in a single second, and the tests all use the same project ID. So had to refactor the type of tests to allow them to pass. This was also tech-debt already.
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 and I trust your tests in integration.rs
.
…into feat/rate-limiting
Description
Adds rate limiting.
Attempt refactoring of notify endpoint to reduce complexityRate limit data export for each endpoint call, containing the project and remaining tokensResolves #14
How Has This Been Tested?
Automated tests
Due Diligence