We clearly need someone with the word 'Manager' in their title to ask GitHub.

@dr0ptp4kt this would be a great use of twitter :)

In T106452#1469572, @yuvipanda wrote:

We clearly need someone with the word 'Manager' in their title to ask GitHub.

What are the CIDRs for our outbound IPv4 traffic? I can certainly send an email or two.

Here's an example of the rate limit being exhausted:

$ date; curl -sD - https://api.github.com/rate_limit | grep '^X-RateLimit'
Wed Jul 22 15:52:55 UTC 2015
X-RateLimit-Limit: 60
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 1437580844

$ date -d '@1437580844'
Wed Jul 22 16:00:44 UTC 2015

$ curl https://api.ipify.org
208.80.155.255

In T106452#1469573, @Jdlrobson wrote:

@dr0ptp4kt this would be a great use of twitter :)

@Jdlrobson, got some proposed text?

@bd808 208.80.155.128/25 is the labs CIDR

I sent this to GitHub:

Before I get to whining and asking for favors, thanks for making such a great platform for the FLOSS community.

The Wikimedia Foundation [0] runs a hosting platform for volunteer created projects related to Wikipedia and the rest of the Wikimedia movement projects [1] called Wikimedia Labs [2]. Many of the projects within this hosting environment are PHP applications that make use of Composer. As use of Composer has increased we have had more and more reports of people hitting the GitHub anonymous API rate limit of 60 requests per IP per hour [3].

The outbound addresses of these virtual machines map the the 208.80.155.128/25 CIDR block. Before we try to do something more heroic in the way of end-user education and work arounds, I thought it would be worthwhile to see if it is possible for GitHub to raise the anon API rate limit [4] for requests originating in this particular IP range.

Here's an example of the rate limit being exhausted:

$ date; curl -sD - https://api.github.com/rate_limit | grep '^X-RateLimit'
Wed Jul 22 15:52:55 UTC 2015
X-RateLimit-Limit: 60
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 1437580844
$ date -d '@1437580844'
Wed Jul 22 16:00:44 UTC 2015
$ curl https://api.ipify.org
208.80.155.255

[0]: https://wikimediafoundation.org/wiki/Home
[1]: https://wikimediafoundation.org/wiki/Our_projects
[2]: https://wikitech.wikimedia.org/wiki/Help:FAQ
[3]: https://phabricator.wikimedia.org/T106339
[4]: https://developer.github.com/v3/#rate-limiting

Thanks,
Bryan

I'll report back when I hear from them.

Changing the project tags on this. This is really for mediawiki-vagrant.
Anything else should use github auth to avoid ratelimiting

Might be causing problems for CI now T248387: Could not authenticate against github.com :(

Change 583483 had a related patch set uploaded (by BryanDavis; owner: Bryan Davis):
[integration/config@master] Inject GitHub OAuth token into composer runtime

https://gerrit.wikimedia.org/r/583483

Change 585609 had a related patch set uploaded (by Jforrester; owner: Jforrester):
[integration/config@master] jjb: Update composer docker images and inject GitHub OAuth token

https://gerrit.wikimedia.org/r/585609

Change 583483 merged by jenkins-bot:
[integration/config@master] dockerfiles: [composer-php70] Inject GitHub OAuth token into composer runtime

https://gerrit.wikimedia.org/r/583483

Mentioned in SAL (#wikimedia-releng) [2020-04-02T21:59:59Z] <James_F> Docker: [composer-php70] Inject GitHub OAuth token into composer runtime T106452 T248387

CI (running on the integration WMCS project) is now configured to use a custom GitHub token, but this isn't fixed at large for other WMCS-hosted users.

Change 585609 merged by jenkins-bot:
[integration/config@master] jjb: Inject GitHub OAuth token as a default for all jobs

https://gerrit.wikimedia.org/r/585609