Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Incident with Github.com [resolved]

githubstatus.com

Post reply on HN
Print view View original

211–220 of 1001 posts

Re: Incident with Github.com [resolved]

#211

Post by noahbp »

leishman wrote: post #171

I don't understand why Github hasn't solved this problem with pricing updates. My understanding is they are getting hammered with LLM generated code growing their traffic by over an order of magnitude. So why not rate limit non-paying users and charge for whatever scarce resource is being consumed that is causing them to constantly fall-over? This seems like a basic economics problem.

Because any price at all will immediately cause users to shift to another platform, and GitHub's value is that it is _the_ place to put your code on the internet.

Re: Incident with Github.com [resolved]

#212

Post by phtrivier »

leishman wrote: post #171

I don't understand why Github hasn't solved this problem with pricing updates. My understanding is they are getting hammered with LLM generated code growing their traffic by over an order of magnitude. So why not rate limit non-paying users and charge for whatever scarce resource is being consumed that is causing them to constantly fall-over? This seems like a basic economics problem.

They also sell the machinery to produce the slop (through OpenAI at least).

If they make it harder to push slop on github, people might treat it as an incentive to generate less slop. Less tokens sold. Bad. Very bad.

The github paying customers are not going to move away.

Plus, it's probably genuinely hard to scale. And they can't throw compute at the problem - all compute is already going to the LLMs.

Re: Incident with Github.com [resolved]

#213

Post by anonymousab »

gottagocode wrote: post #49
pavo-etc wrote: post #31

> Update - We are seeing an approximate 20% error rate across numerous experiences including Pull Requests, Issues, and others. Investigations are currently under way and we will be posting updates as they become available brutal

20%, do we just make numbers up?

It seems vastly higher on every region and VPN I've tested, so I think this is a case of the "technicalies".

It is technically 20%, because a bunch of the requests that happen on page load do succeed. Just not the few crucial ones that are required for the page to load correctly - those return a 500 the vast supermajority of the time.

Re: Incident with Github.com [resolved]

#214

Post by madeforhnyo »

ieie3366 wrote: post #100

To everyone who is angry: calm down. Github’s servers are constantly on fire as their usage increased something like 50x due to LLM sloppers pushing large amounts of trash code Unless you have a emergency hotfix (you don’t), go hit the gym or walk outside. If a work tool going down triggers you enough mentally to start angrily ranting online, it’s a sign you need to chill out and focus more on your health

> due to LLM sloppers pushing large amounts of trash code

Which they encouraged by pushing Copilot down everyone's throat

Re: Incident with Github.com [resolved]

#216

Post by robin_reala »

z3ugma wrote: post #181

You know, I think Fossil with its integrated issue management right in the repo is actually a perfect match for the LLM era. Maybe today is the day I migrate to using a Fossil forge with GitHub becoming increasing untenable. Anyone else using Fossil?

Biggest problem with Fossil is immutable history. That’s a design choice, and I respect them for that, but it’s not the right choice for me.

Re: Incident with Github.com [resolved]

#217

Post by slowin »

ieie3366 wrote: post #100

To everyone who is angry: calm down. Github’s servers are constantly on fire as their usage increased something like 50x due to LLM sloppers pushing large amounts of trash code Unless you have a emergency hotfix (you don’t), go hit the gym or walk outside. If a work tool going down triggers you enough mentally to start angrily ranting online, it’s a sign you need to chill out and focus more on your health

Well, they’re a critical piece of infrastructure with terrible stability. I’m in the process of migrating us off GitHub now.

I’m not a Meta fan but it’s interesting that they manage to keep their systems up with an order of magnitude more traffic. GitHub’s uptime is inexcusable.

Re: Incident with Github.com [resolved]

#218

Post by iamcoder18 »

eddieroger wrote: post #132
ieie3366 wrote: post #100

To everyone who is angry: calm down. Github’s servers are constantly on fire as their usage increased something like 50x due to LLM sloppers pushing large amounts of trash code Unless you have a emergency hotfix (you don’t), go hit the gym or walk outside. If a work tool going down triggers you enough mentally to start angrily ranting online, it’s a sign you need to chill out and focus more on your health

For the amount of money enterprises are paying to GitHub, there is a reasonable (and contractual) expectation of uptime. I don't think my boss would find it to fun if I bailed work to hit the gym just because GitHub was down.

Yes, but GitHub enterprise has different uptime (https://us.githubstatus.com/posts/dashboard) and actually does have an SLA.

Edit: it seems GHE is also affected by the outage and isn't much better.

Re: Incident with Github.com [resolved]

#219

Post by AustinDev »

ieie3366 wrote: post #100

To everyone who is angry: calm down. Github’s servers are constantly on fire as their usage increased something like 50x due to LLM sloppers pushing large amounts of trash code Unless you have a emergency hotfix (you don’t), go hit the gym or walk outside. If a work tool going down triggers you enough mentally to start angrily ranting online, it’s a sign you need to chill out and focus more on your health

Alternatively, don't use GH for critical infrastructure they are no longer reliable, simple as.

Re: Incident with Github.com [resolved]

#220

Post by duxup »

Arubis wrote: post #99

This is starting to feel like Twitter. For a variety of reasons, we had a centralized place where everyone of a particular set of persuasions could connect, and this had outsize benefits for the community as a whole. That place is becoming untenable, and with the loss of goodwill and stability, the community’s started to dissipate. But there isn’t one obvious transition candidate, so the diaspora is finding itself sp…

And like Twitter most people will keep using it anyway?
Post reply on HN