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

GitHub having issues [resolved]

githubstatus.com

Post reply on HN
Print view View original

131–140 of 150 posts

Re: GitHub having issues [resolved]

#131

Post by gobalini »

khaledh wrote: post #49
gobalini wrote: post #45

Earlier quoted context omitted.

How frequent? I think the obsession with uptime is annoying. If GitHub is down, if there’s something so critical, then you need some more control of the system. Otherwise take a couple hours and get a coffee or an early lunch.

Frequent enough to interrupt the flow of an entire organization, wasting thousands of hours. Take a look: https://mrshu.github.io/github-statuses

Yeah that is pretty bad I guess. For decades 99% has been achievable for many orgs. 92% phew.

But “waste” is arguable. If folks have literally nothing to do when GitHub is down, I question that a bit. For example, design, administrative work (everyone has that), lunch. You know?

Critical CI/CD can use Jenkins, but in that case folks might end up with 89% uptime!

Re: GitHub having issues [resolved]

#132

Post by OtomotO »

terminalbraid wrote: post #56

I would prefer we have posts when github is not having issues to cut down on noise.

Yeah, right. I mean, I'm so happy that only one of my clients is using GitHub as their GitForge. Every single other one hosts their own GitForge. And I can't state how much better every single other GitForge is.

GitHub was the pinnacle of GitForge a couple of years back, and it seems like they wanted to hit a wall.

Otherwise, you cannot explain how you can enshittify a software that much.

Re: GitHub having issues [resolved]

#133

Post by heliumtera »

OtomotO wrote: post #132
terminalbraid wrote: post #56

I would prefer we have posts when github is not having issues to cut down on noise.

Yeah, right. I mean, I'm so happy that only one of my clients is using GitHub as their GitForge. Every single other one hosts their own GitForge. And I can't state how much better every single other GitForge is. GitHub was the pinnacle of GitForge a couple of years back, and it seems like they wanted to hit a wall. Otherwise, you cannot explain how you can enshittify a software that much.

There was GitHub, and then it was Microsoft.

Re: GitHub having issues [resolved]

#135

Post by [deleted] »

duggan wrote: post #97

A directory over SSH can be your git server. If your CI isn't too complex, a post-receive hook looping into Docker can be enough. I wrote up about self hosting git and builds a few weeks ago[1]. There are heavier solutions, but even setting something like this up as a backstop might be useful. If your blog is being hammered by ChatGPT traffic, spare a thought for Github. I can only imagine their traffic has ballooned…

[deleted]

Re: GitHub having issues [resolved]

#136

Post by OtomotO »

heliumtera wrote: post #133
OtomotO wrote: post #132

Earlier quoted context omitted.

Yeah, right. I mean, I'm so happy that only one of my clients is using GitHub as their GitForge. Every single other one hosts their own GitForge. And I can't state how much better every single other GitForge is. GitHub was the pinnacle of GitForge a couple of years back, and it seems like they wanted to hit a wall. Otherwise, you cannot explain how you can enshittify a software that much.

There was GitHub, and then it was Microsoft.

Exactly. But given all the slop, not even just AI slop, I wonder how Microsoft can still be in business.

Re: GitHub having issues [resolved]

#137

Post by khaledh »

gobalini wrote: post #131
khaledh wrote: post #49

Earlier quoted context omitted.

Frequent enough to interrupt the flow of an entire organization, wasting thousands of hours. Take a look: https://mrshu.github.io/github-statuses

Yeah that is pretty bad I guess. For decades 99% has been achievable for many orgs. 92% phew. But “waste” is arguable. If folks have literally nothing to do when GitHub is down, I question that a bit. For example, design, administrative work (everyone has that), lunch. You know? Critical CI/CD can use Jenkins, but in that case folks might end up with 89% uptime!

> If folks have literally nothing to do when GitHub is down, I question that a bit.

It's not about a single person. I work at a company with over 10k employees, most of them rely on GitHub one way or another. It's not just about PRs and issues; there's a huge amount of automation, workflows, and integrations that depend on GitHub, round the clock. With this kind of uptime it has material impact on productivity of the company as a whole.

Re: GitHub having issues [resolved]

#138

Post by kevwil »

heliumtera wrote: post #133
OtomotO wrote: post #132

Earlier quoted context omitted.

Yeah, right. I mean, I'm so happy that only one of my clients is using GitHub as their GitForge. Every single other one hosts their own GitForge. And I can't state how much better every single other GitForge is. GitHub was the pinnacle of GitForge a couple of years back, and it seems like they wanted to hit a wall. Otherwise, you cannot explain how you can enshittify a software that much.

There was GitHub, and then it was Microsoft.

Microsoft trying to run a Ruby on Rails + SSH + Git system.

Re: GitHub having issues [resolved]

#139

Post by OtomotO »

dzonga wrote: post #127

I remember the days when it was mostly Gitlab having issues. Github was super stable - then it got shitty once they switched to React on the frontend instead of the server rendered pages, then Co-pilot stuff lately I haven't heard them bragging about the Rails Monolith

The question I ask myself to this day is why they began switching to React. It made no sense at all for me. Like it was a working product, so why would you switch?

I get that new developers might be more familiar with React, but then again, as soon as the trade-offs were apparent, I would've pulled the plug.

But they said: Buckle up, everyone, let's ruin our product!

Re: GitHub having issues [resolved]

#140

Post by nadirollo »

noplacelikehome wrote: post #129
nadirollo wrote: post #91

Earlier quoted context omitted.

This is a must when your systems deal with critical workloads. At Fastly, we process a good chunk of the internet's traffic and can't afford to be "down" while waiting for the CI system to recover in the event of a production outage. We built a CI platform using dagger.io on top of GH Actions, and the "break glass" pattern was not an afterthought; it was a requirement (and one of the main reasons we chose dagger as t…

I would really love to hear more about this, but my cursory search didn't find a write up about it. I did a PoC of Dagger for an integration and delivery workload and loved the local development experience. Being able to define complex pipelines as a series of composable actions in a language which can be type checked was a great experience, and assembling these into unix-style pipelines felt very natural. I struggle…

We don't have any public posts around our setup (yet), but I think it's time we do. I'll put some time into it and will revert here to link to it.
Post reply on HN