3 ms·
From the description, it sounds like someone(s) is automatically downloading GMP as a part of a CI process. GHA being the source would explain why it's coming f
by notamy 3y ago
From the description, it sounds like someone(s) is automatically downloading GMP as a part of a CI process. GHA being the source would explain why it's coming from "several hundred IP addresses owned by Microsoft cooperation (sic)," as well as (maybe) why GH puts the blame on the GMP project for not being able to handle the load.
Edit: This seems to be the responsible project/issue: https://github.com/BtbN/FFmpeg-Builds/issues/278 https://github.com/BtbN/FFmpeg-Builds/issues/278
- Aardwolf 3y agoGithub could cache it then to improve this?
- rwmj 3y agoThe title is a bit confusing. It seems the GMP project has a self-hosted Mercurial repo (https://gmplib.org/devel/repo-usage https://gmplib.org/devel/repo-usage) which is being hit by a user at Microsoft that they've somehow tied back to a single github account. I'm sure it's going to be CI or mirroring or some other automated process.
- cxr 3y agoWhy is this a response to the person you sent this reply to?
- rwmj 3y agoGithub can't easily cache a remotely hosted repo that some random CI test (essentially a script) accesses, at least not without some very hairy proxying.
- cxr 3y agoIs GitHub's CI infrastructure (and cloud compute, generally) not hairy? (A basic attempt at straightforward proxying seems like it would be the _least_ hairy aspect of the stack, besides.)