Skip to content

Handle rate limit from GitLab API gracefully

Context: more rate limiting is being added on APIs:

These rate limits are implemented through GitLab::ApplicationRateLimiter, which is different from RackAttack and do not set the headers RateLimit-*.

This class implements a simple rate limiter that can be used to throttle certain actions. Unlike Rack Attack and Rack::Throttle, which operate at the middleware level, this can be used at the controller or API level.

gitlab-org/gitlab!53637 (merged) has been merged and ApplicationRateLimiter does not implement any allowlist. This means that gitlab-bot will start being throttled.

Edited by Albert Salim