Incident with Github.com [resolved]
341–350 of 1001 posts
Re: Incident with Github.com [resolved]
#342The LLM code influx is not the problem. Microsoft mismanagement is: https://damrnelson.github.io/github-historical-uptime/
I still remember that they launched GitHub Actions in 2018 and back then I was thinking: They can't even make the website reliable, surely this will only cause them more problems.
Re: Incident with Github.com [resolved]
#343This 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…
Re: Incident with Github.com [resolved]
#344To 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
> Github’s servers are constantly on fire as their usage increased something like 50x due to LLM sloppers pushing large amounts of trash code Which means they have a pricing problem. Rate limit non-paying users.
Re: Incident with Github.com [resolved]
#345To 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
That's an overly optimistic view of things. For a lot of us GitHub is critical infrastructure, which if it goes down loses us and our customers money.
Re: Incident with Github.com [resolved]
#346Funny enough, I received a marketing email from GitHub during the outage with the following subject: "What if every pull request you started actually shipped"
Huh, they usually do? I'm not a full-time developer though so I'm surely biased towards doing the obvious quick fixes or already-discussed things, but discussing how to solve a problem before throwing something at the wall seems like the normal thing to do for me Or is their point about abandoned projects where the dev never clicks release after merging, or even never merges?
Re: Incident with Github.com [resolved]
#347This 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…
I think that, exactly how 95% of the people that left Twitter eventually returned, we will see a similar outflux of people from Github and the vast majority of them will quietly be back in a few months.
Re: Incident with Github.com [resolved]
#348Anyone else getting "Cannot retrieve latest commit at this time?"
Re: Incident with Github.com [resolved]
#349Re: Incident with Github.com [resolved]
#350Earlier quoted context omitted.
Just in the US. I have ONE European client... ONE of dozens who use GitHub. EVERY other client I've ever worked with used their own gitforge or at least bitbucket...
Selection bias then as the majority of European companies are for sure not hosting their own Forgejo or GitForge.