Re: Anubis check stuck?
Project / Subsystem
gcc / gcc
Date
2026-08-14
Proposer
Jonathan Wakely <jwakely.gcc@gmail.com>
Source type
public_inbox
Consensus
Proposed
Sentiment
—/10
Technical tradeoffs
- • Increased security/stability via rate limiting vs. user accessibility.
- • Potential need for more authentication mechanisms to bypass rate limits.
All attributes
- project
- gcc
- subsystem
- gcc
- patch_id
- —
- discussion_id
- CAH6eHdRUOyoKTONSJs7XDD8AS9MSM5p7ksZ50roNy_szQNso4w@mail.gmail.com
- source_type
- public_inbox
- title
- Re: Anubis check stuck?
- headline
- Anubis check stuck?
- tldr
- Users report persistent 429 Too Many Requests errors on sourceware.org, potentially due to a new nginx rate limiter.
- proposer
- Jonathan Wakely <jwakely.gcc@gmail.com>
- consensus
- Proposed
- outcome
- proposed
- sentiment_score
- —
- technical_tradeoffs
-
- • Increased security/stability via rate limiting vs. user accessibility.
- • Potential need for more authentication mechanisms to bypass rate limits.
- series_id
- —
- series_role
- standalone
- series_parts
- []
- tags
-
- • nginx
- • rate limiting
- • gitweb
- • cgit
- • sourceware.org
- url
- https://inbox.sourceware.org/gcc/CAH6eHdRUOyoKTONSJs7XDD8AS9MSM5p7ksZ50roNy_szQNso4w@mail.gmail.com
- bugzilla_url
- —
- date
- 2026-08-14T00:00:00.000Z
Re: Anubis check stuck?
Users are experiencing repeated “429 Too Many Requests” errors when accessing various sourceware.org services, including gitweb and cgit. Initially thought to be an Anubis authentication issue, it’s now believed to be caused by a new nginx rate limiter. While authenticated users might bypass this, the current implementation is hindering general access.