Live data from Hacker News

GitHub incident: ongoing issues with Actions, Issues and other Git operations

githubstatus.com

31–40 of 130 posts

Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations

#31

Thankfully git is a distributed version control system, so such outages are not of major concern.

I mean, you joke but that's actually fairly true. P4 users always notice when the central server goes down because you can't reliably look at changelist history, draft CLs, and do a host of other operations that are possible on git locally. (using a central VCS confers other advantages of course).

Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations

#33

Thankfully git is a distributed version control system, so such outages are not of major concern.

Ignoring the fact that what people actually do with GitHub, git is such a small part. Issues, PRs, CI/CD and basically everything that isn't git, doesn't happen over git (besides the wiki, which somehow miraculously actually is via git).

Some people have their entire roadmap in GitHub, and every single bug report / feature request, without any offline backup. Don't ask me why, I don't get it. Especially since they have proven for the last few years that they cannot keep the platform up in a stable manner.

Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations

#34
post #14

The GitHub Status shows 14 incidents affecting Git Operations this year alone [1]. That's quite a lot, considering it's only May. I wonder if the outages were always this frequent and just get more publicity on here now, or whether there was a significant increase in outages fairly recently. [1] https://www.githubstatus.com/history

Many outages happen because something changed, and someone/something missed one of the effects of said change, bringing the platform down immediately, or after a while.

There was a period of time when GitHub basically didn't change, for years. And the platform was relatively stable (although "unicorns" (downtime)) still happened from time to time.

But nowhere near as often as now, but then again, there is a lot of more moving pieces now compared to before.

Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations

#35

Why don't we all collectively mirror our repos to gitlab and switch development to there during the monthly outage?

GitLab is quite a bit more expensive. If you have GitHub Enterprise with the security features, it's $70/month/user whereas you'll need to get GitLab Ultimate for the security features, which is $99/month/user.

Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations

#36
post #24

Earlier quoted context omitted.

https://status.gitlab.com/ lists 27 incidents this year, so far.

https://www.githubstatus.com/history lists 72 incidents since January

The point isn't that GitLab has more, the point is that running these things at global scale is pretty complicated, and everyone has problems. "Just switch to GitLab" is pithy but isn't in itself an actual solution.

Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations

#37
post #3

Does GitHub provide uptime stats? Seems very unreliable recently.

They used to, some screenshots of it existing here: https://interface.lt/github-uptime-and-microsoft

> Let’s hope it’s temporary and GitHub error 500 won’t become their own version of Blue Screen of Death. In this case it would be Green Screen of Death (GSoD or GhSoD).

Heh, if anything it has gotten worse.

Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations

#39
post #3

Does GitHub provide uptime stats? Seems very unreliable recently.

About 10 years ago someone said we should move to self hosting because bitbucket who we used were unreliable. I looked at the status page and say 2 hours of downtime over 3-months, while we have 3-4 days of downtime on our self hosted jenkins during the same time. I always think of that when I see people complain about services being unreliable. Often we see one or two problems in short span and forget about the months were we didn't see any issues.

GitHub is probably as reliable now as it has been for the past 10 years. It's always had downtime.

Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations

#40

Why don't we all collectively mirror our repos to gitlab and switch development to there during the monthly outage?

Feature mismatch of anything outside Git. And no one wrote the tooling needed to synchronize issues, pull/merge requests, ... back and forth.
Post reply on HN