First batch of rate limiter changes #6872
Merged
Conversation
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
Turbo87
added
C-internal 🔧
pietroalbini
force-pushed
the
pa-rate-limits-part1
branch
from
7529392 to
c4ebc04
Compare
Turbo87
reviewed
Jul 25, 2023
|
Addressed all review comments. |
Turbo87
approved these changes
Jul 26, 2023
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 PR contains the first batch of changes needed to implement proper rate limiting for yanking and unyanking:
actioncolumn to the rate limit tables. Right now it only supports thepublish-newaction, but in a future PR it'll allow for different kinds of rate limits.PublishRateLimittoRateLimiter, in anticipation for it being able to limit more actions.