fix: prevent hitting github.com rate limits when bazel is fetching dependencies#8863
Merged
basvandijk merged 5 commits intomasterfrom Feb 15, 2026
Conversation
…igher rate limits for fetching dependencies
basvandijk
added
the
CI_ALL_BAZEL_TARGETS
basvandijk
deleted the
basvandijk/handle-github-rate-limiting-errors-on-namespace
branch
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
1 participant
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.
We keep frequently hitting HTTP 500 errors when bazel is fetching dependencies from github.com. These seem to happen more frequently on Namespace.so runners.
The hypothesis is that we're hitting github.com rate limits which have a higher probability of triggering on Namespace runners since they share egress IPs across multiple tenants. So all Namespace customers fetching from github.com (releases, archives) contribute to the same rate-limit bucket.
To fix this we:
~/.netrccontaining the GitHub token which bazel will use to authenticate with github.com to raise the rate limit from ~60 req/hr (unauthenticated, per-IP) to ~15000 req/hr (authenticated, per-token).--experimental_repository_downloader_retries=3override and use the default of 5 retries.cat /tmp/bazel-cache.bazelrcto know what cache settings Namespace installs.