When I worked at one of the early paging and cellular companies, every company had phones and pagers on at least one or two competitors for the oncall folks - you can't get a call to fix your cellular network when you are down.

Likewise while at Google, they didn't let us put Google Voice numbers down as our oncall phone number. Some folks even had multiple phones on different networks as backups.

I'm sure they have either other SOTA models or open source models around to help if things to completely pear shaped.

Please give GitHub some slack, just check out the massive number of copilot changes they've had to release over the last 3 weeks (https://github.blog/changelog/). There's clearly little time left for security, maintenance, or reliability work.

Unfortunately this is very true. It often takes someone pretty high up on the food chain to see it on HN, X, or get an email/LinkedIn message asking about something for it to become a priority.

I don't see that changing for any of the large companies unfortunately, anytime soon.

``` This git endpoint is seeing a high influx of requests for this repository, to preserve the availability of Codeberg your search request will not be processed. Sorry for the inconvenience and please try again later. ```

Any mirror?

The PR is still accessible https://codeberg.org/forgejo/forgejo/pulls/14300

    Critical: fix: prevent template expansion from interfering with git repo initialization. When generating a new repository from a template repository, Forgejo clones the template repository, removes the .git folder, performs variable template expansion on files listed in .forgejo/template, and initializes a new git repository. During this process, variable template expansion could be misused in order to create a new .git folder, which git would adopt and incorporate during its initialization of a new git repository. A malicious template repository could be used to read arbitrary data from the Forgejo host, and to execute arbitrary processes on the Forgejo host, as a remote code execution attack. To address this issue, after variable expansion is completed, any existing .git folder is removed from the directory before the git repository is initialized.

I'd bet they are all using capacity at X.ai's colossus datacenter and that had a hiccup.

Totally, and as long as they don't turn on the AWS NAT Gateway, they'll be just fine.

Sounds a lot like K8s. It's not a framework you use, it's a framework to build a framework on top of.

I wish the observability vendors would move to using it under the covers so it's easier to mix and match.

I wish the otel support wasn't super buggy in most of the frameworks and backends.

But then you wouldn’t be locked in!

Gitlab has the benefit of having very little traffic, both free and paid. Their limits are still way above the current usage so less likely to be an issue

Worth mentioning GitLab's paid enterprise offering are more expensive than GitHub's, on a per-seat basis.

Lots of companies moved because it was cheap, but it's not anymore. Ironic that companies might choose to migrate to them now for stability, rather than price.

GitLab has its own problems. It might be somewhat more available than GitHub lately, but it too is not immune to incidents, particularly involving workflow dispatch and managed runner availability.

Plus the UX isn’t nearly as good. Sometimes it feels downright clunky in comparison.

There's always a cliff, this part is fine. You sometimes know the cliff but often do not.

Great read - I'm glad they realize there's work ahead but what I'm missing is: * Paid customers: we know you pay us often a ton of money, and we burn your month on actions during these outages - we'll refund you for the days we spent your money and gave you no value. * Paid customer: We know you put your trust in us, so we'll ensure we have a separate pool of capacity to ensure we can keep that trust. * Paid customer: we'll proactively refund you when we miss our SLA.

What I read from this is: * Scaling is hard, we don't have enough capacity * We give away a shitton of compute for free * I have to talk about Azure not being a steaming pile of poop, otherwise my bonus will get tweaked downward in the next comp cycle.

Notice there's nothing about paid customers, I'll add in what they are missing:

Paid customers: Go F*ck yourself, you don't pays us enough to be an interesting line item compared to windows server.

This. I own a small company with 5 people. I pay Github $250/m. I'm sorry but the narrative of, "look at this burden we have, it's hard to take care of all of this code!" is pretty insulting when I'm paying $50 per person per month to host code and run CI pipelines. If they do not want my money, I'll find a company who does.