Live data from Hacker News

Another GitHub outage in the same day

githubstatus.com

81–90 of 298 posts

Re: Another GitHub outage in the same day

#81

Earlier quoted context omitted.

Ya, it really was one of the most enjoyable web apps to use pre-MS. I'm sure there are lots of things that have contributed to this downfall. We certainly didn't need bullshit features like achievements.

Even just a year or two ago its web interface was way snappier. Now an issue with a non-trivial number of comments, or a PR with a diff of even just a few hundred or thousand lines of changes causes my browser to lock up.

But even clicking around tabs and whatnot is noticeably slower. It used to be incredibly snappy.

Re: Another GitHub outage in the same day

#82
post #20

I consider moving away from Github, but I need a solid CI solution, and ideally a container registry as well. Would totally pay for a solution that just works . Any good recommendations?

We can run a Forgejo instance for you with Firecracker VM runners on bare metal. We can also support it and provide an SLA. We're running it internally and it is very solid. We're running the runners on bare metal, with a whole lot of large CI/CD jobs (mostly Rust compilation).

The down side is that the starting price is kinda high, so the math probably only works out if you also have a number of other workloads to run on the same cluster. Or if you need to run a really huge Forgejo server!

I suspect my comment history will provide the best details and overview of what we do. We'll be offering the Firecracker runner back to the Forgejo community very soon in any case.

https://lithus.eu

Re: Another GitHub outage in the same day

#83
post #20

I consider moving away from Github, but I need a solid CI solution, and ideally a container registry as well. Would totally pay for a solution that just works . Any good recommendations?

GitLab can be selfhosted with container based CI and fairly easy to setup CE

CE is pretty good. The things that you will miss that made us eventually pay:

* Mandatory code reviews

* Merge queue (merge train)

If you don't need those it's good.

Also it's written in Ruby so if you think you'll ever want to understand or modify the code then look elsewhere (probably Forgejo).

Re: Another GitHub outage in the same day

#85
post #18

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…

We loved Github as a product when it needed to return or profit beyond "getting more users". I feel this is just the natural trajectory for any VC-funded "service" that isn't actually profitable at the time you adopt it. Of course it's going to change for the worse to become profitable.

I don’t get it. Why making the UI shittier would possibly lead to more profit?

Re: Another GitHub outage in the same day

#86

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…

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.

This thread has complaints about software coming from the same supplier both degrading.

The person(s) who wanted this want Azure to get bigger and have prioritized Azure over Windows and Office, and their share price has been growing handsomely.

‘Microslop’, perhaps, but their other nickname has a $ in it for a reason.

Re: Another GitHub outage in the same day

#87

Earlier quoted context omitted.

How much has the volume increased, from what you know?

Over 100x is what I’m hearing. Though that could just be panic and they don’t know the real number because they can’t handle the traffic.

One hundred? Did I read that right?

Re: Another GitHub outage in the same day

#88

At this point, GitHub outages feel closer to cloud provider outages than a SaaS blip. Curious how many people here still run self-hosted Git (GitLab / Gitea) vs fully outsourcing version control.

Self-hosted Gitea is a good time if you're comfortable taking care of backups and other self-hosting stuff.

Re: Another GitHub outage in the same day

#89

Earlier quoted context omitted.

Amazon's deprecated CodeCommit is limited to 150 chars like it's an old SMS or Tweet.

Ha! Nice. I never worked with CodeStar / CodeCommit. Was it pretty bad?

That's going to depend on each user's demands. The PR message limit is the biggest pain for me. I don't depend on the UI very often. I'm not trying to do any CI/CD nonsense. I just use it as a bog standard git repo. When used as that, it works just fine for me

Re: Another GitHub outage in the same day

#90
post #58

Earlier quoted context omitted.

I was just looking into this today but it seems pricey. $29/user/month for basic features like codeowners and defining pr approval requirements. Going with Forgejo.

Wait, what? So you're on the hook for backups, upgrades, etc. and you have to pay them for the privilege? I thought GitLab was free as in speech and beer.

It's an Open Core model. You can deploy the free version, but it lacks some pretty important features like SSO.

But that $30 per month per user is also the cost for their cloud-hosted version. It also includes quite a bit of CI/CD runtime.

Post reply on HN