3 ms·
The language in this post is very curious. It seems like they're going out of their way to avoid acknowledging that this was all their fault. > issues that our
by dantiberian 10y ago
The language in this post is very curious. It seems like they're going out of their way to avoid acknowledging that this was all their fault.
> issues that our users had.
> GitHub infrastructure team were quick to explain that this was because of us hitting CPU rate limits on their end
and finally at the end of the paragraph
> which turned out to be caused, besides the high volume of clones, by the default options we chose to clone this repo.
If it was me writing this, I'd apologise to Github for the (unintentional) bad design of CocoaPods, and the effect it had on their servers.