Live data from Hacker News

Another GitHub outage in the same day

githubstatus.com

111–120 of 298 posts

Re: Another GitHub outage in the same day

#111
I still say that mixing CI/CD with code/version control hosting is a mistake.

At it's absolute best, everything just works silently, and you now have vendor lock-in with whichever proprietary system you chose.

Switching git hosting providers should be as easy as changing your remotes and pushing. Though now a days that requires finding solutions for the MR/PR process, and the wiki, and all the extra things your team might have grown to rely on. As always, the bundle is a trap.

Re: Another GitHub outage in the same day

#114
I'm starting to wonder if people doing what were previously unconventional workflows (which may not be performance optimized) are affecting things.

For example, today, I had claude basically prune all merged branches from a repo that's had 8 years of commits in it. It found and deleted 420 branches that were merged but not deleted.

Deleting 420 branches at once is probably the kind of long tail workflow that was not worth optimizing in the past, right? But I'm sure devs are doing this sort of housekeeping often now, whereas in the past, we just never would've made the time to do so.

Re: Another GitHub outage in the same day

#115

Can someone in GitHub senior leadership please start paying attention and reprioritise towards actually delivering a product that's at least relatively reliable? I moved my company over to GH enterprise last year (from AzDO) and I'm considering moving us away to another vendor altogether as a result of the constant partial outages. Things that used to "just work" now are slow in the UI, and GH actions fail to schedul…

I second this. GitHub used to be a fantastic product. Now it barely even works. Even basic functionality like the timeline updating when I push commits is unreliable. The other day I opened a PR diff (not even a particularly large one) and it took fully 15 seconds after the page visually finished loading -- on a $2,000 dev machine -- before any UI elements became clickable. This happened repeatedly. It is fairly stun…

> GitHub used to be a fantastic product. Now it barely even works.

it's almost as if Microsoft bought it, isn't it?

Re: Another GitHub outage in the same day

#116

Earlier quoted context omitted.

I second this. GitHub used to be a fantastic product. Now it barely even works. Even basic functionality like the timeline updating when I push commits is unreliable. The other day I opened a PR diff (not even a particularly large one) and it took fully 15 seconds after the page visually finished loading -- on a $2,000 dev machine -- before any UI elements became clickable. This happened repeatedly. It is fairly stun…

So React rewrite did not help after all? Imagine, one of the largest software tool companies on Earth cannot reliably REbuild something in React. I lost count of the inconsistency issues React introduced. https://news.ycombinator.com/item?id=33576722

React isn't causing these issues.

Re: Another GitHub outage in the same day

#117

I still say that mixing CI/CD with code/version control hosting is a mistake. At it's absolute best, everything just works silently, and you now have vendor lock-in with whichever proprietary system you chose. Switching git hosting providers should be as easy as changing your remotes and pushing. Though now a days that requires finding solutions for the MR/PR process, and the wiki, and all the extra things your team…

I don't think any of this was a mistake ;) Lock-in was by design.

Re: Another GitHub outage in the same day

#118

Earlier quoted context omitted.

> We are in a future that nobody wanted. Nor deserved.

Then why is it the future we have?

Let’s just say there are a couple of guys, who are up to no good. And they started making trouble in our neighborhood.

jokes aside it’s all because of hyper financial engineering. Every dollar every little cent must be maximized. Every process must be exploited and monetized, and there are a small group of people who are essentially driving all this all across the world in every industry.

Re: Another GitHub outage in the same day

#119

Earlier quoted context omitted.

I second this. GitHub used to be a fantastic product. Now it barely even works. Even basic functionality like the timeline updating when I push commits is unreliable. The other day I opened a PR diff (not even a particularly large one) and it took fully 15 seconds after the page visually finished loading -- on a $2,000 dev machine -- before any UI elements became clickable. This happened repeatedly. It is fairly stun…

I've been a GitHub user since the very early days. I had a beta invite to the service. I really wish they didn't swap out the FE for a React FE. They need to start rolling back some of their most recent changes. I mean, if they want people to start moving to self hosted GitLab, this is gonna get that ball rolling.

GitLab is slower for me than that React GH app. Why would I move to GitLab?

Re: Another GitHub outage in the same day

#120

Earlier quoted context omitted.

The trend of "non-functional software" is happening everywhere. See the recent articles about Copilot in Notepad, failing to start because you aren't signed in with your Microsoft Account. We are in a future that nobody wanted.

> We are in a future that nobody wanted. some people wanted this future and put in untold amount of money to make it happen. Hint: one of them is a rabid Tolkien fan.

the irony of Tolkien being associated with a techno-dystopia makes me nauseous
Post reply on HN