[CI]: move away from raw github domain to API #4265
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
apostasie
force-pushed
the
2025-05-github-raw-429
branch
from
a46b5e6 to
63d4340
Compare
apostasie
force-pushed
the
2025-05-github-raw-429
branch
from
63d4340 to
5b74fe9
Compare
apostasie
changed the title
|
Failure is random logs failure. |
AkihiroSuda
reviewed
May 19, 2025
apostasie
force-pushed
the
2025-05-github-raw-429
branch
from
5b74fe9 to
9721413
Compare
apostasie
force-pushed
the
2025-05-github-raw-429
branch
2 times, most recently
from
3b7d403 to
8634a87
Compare
Signed-off-by: apostasie <[email protected]>
apostasie
force-pushed
the
2025-05-github-raw-429
branch
from
8634a87 to
3b89195
Compare
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.
Fix (part of?) #4264
See ^ for context.
TL;DR: recent changes in GitHub rate limits (presumably https://github.blog/changelog/2025-05-08-updated-rate-limits-for-unauthenticated-requests/) now break the build for us, apparently for requests to raw.githubusercontent.
This PR does a couple of things:
Note that it is unclear if we are going to get throttled on other GitHub requests as well - but at least we now have the infrastructure in place to perform authenticated requests, so, we can change what needs be later on piece-meal.