Enforce rate limits on simulator#505
Open
tarcisiozf wants to merge 3 commits into
Open
Conversation
timothyF95
previously approved these changes
Jun 25, 2026
45a76bf to
fea951a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request introduces rate limiting for both HTTP and EVM log triggers in the simulation workflow, ensuring that trigger events cannot exceed configurable limits. The changes add support for specifying and enforcing these rate limits, update the relevant services and listeners to respect them, and include comprehensive tests to verify correct behavior.
Rate limiting for triggers:
ManualHTTPTriggerService, including storing a limiter per trigger and rejecting manual triggers that exceed the limit.EVMLogTriggerListener, enforcing the limit per event, and returning a specific error when exceeded.