Live data from Hacker News

Incident with Issues and Pull Requests

githubstatus.com

111–120 of 143 posts

Re: Incident with Issues and Pull Requests

#111
Three days in a row of outages, in less than a week of unreliability after yesterday's downtime of GitHub Actions [0].

Really at this point, you just might as well consider self hosting and it is looking very chronic with GitHub falling apart and self-hosting was indeed the sensible idea just like how the other open source projects have done for years.

GitHub is going just great, and centralizing everything to GitHub really was a good idea wasn't it? [1] /s

[0] https://news.ycombinator.com/item?id=35887029

[1] https://news.ycombinator.com/item?id=22867803

Re: Incident with Issues and Pull Requests

#112
post #111

Three days in a row of outages, in less than a week of unreliability after yesterday's downtime of GitHub Actions [0]. Really at this point, you just might as well consider self hosting and it is looking very chronic with GitHub falling apart and self-hosting was indeed the sensible idea just like how the other open source projects have done for years. GitHub is going just great, and centralizing everything to GitHub…

There's no way a company could run its own source management system and have an uptime approaching 23 hours a day -- that's like one nine of uptime!

(/s of course)

Re: Incident with Issues and Pull Requests

#113

Anecdotal - I've been using Gitlab for a few years on some projects, and haven't experienced any downtime issues with them of this magnitude.

Same. Overall, I like GitLab a lot more than GitHub. I wonder how much of GitHub's popularity is buoyed by its status as the defacto home for OSS

It has good parity with GitHub on core functionality and a generous free tier.

Re: Incident with Issues and Pull Requests

#115
post #107

Earlier quoted context omitted.

Ah, unbalanced shards via wrong sharding keys was an issue at one point, IIRC. I remember talking with an SRE there when something bad happened at GitHub last year, and I know that this time the current DB cluster failed. To be clear, I _was_ mapping previous incidents with this year's incident — no competitor or hard feelings involved. I really like Vitess, fwiw. And the only thing I really love is FoundationDB :)

That wasn't clear. Side note: "Autosharding" is largely a myth that unproven databases are touting. Sharding is complex and requires planning and control. Databases that start shuffling data round without oversight produce nasty surprises. Trying to be too magic is normally always a mistake with databases.

Yeah, fair, totally get it. Wasn't aiming to spread FUD, and I know that FDB is a little hard to compare against... it is pretty magic with how it routes and shards :D (https://forums.foundationdb.org/t/keyspace-partitions-perfor...)

Re: Incident with Issues and Pull Requests

#116
post #105

Earlier quoted context omitted.

Gitea is pretty light on resources so even though it has a extra functionality you don't need it's not really a resource pig. Unlike say, GitLab.

Gitea requires a database which is unwanted feature for "git server" in my little world. I'm just looking for "website" (read: interface) that list files over HTTPS, with the ability to show nice looking diffs. Some sort of ssh keys(?) to prevent unauthorized access etc.

Maybe something like gitolite then?

https://github.com/sitaramc/gitolite

I've not used it personally though, so no idea how well it works in practise.

Re: Incident with Issues and Pull Requests

#117
post #34

Earlier quoted context omitted.

My money is on some significant backend architecture migration gone wrong without a viable way to roll back the time machine :)

Feels like an organization as big as Microsoft must surely have some sort contingency plan in place before doing such a large migration. Right?

I worked on the volume licensing part of Microsoft years ago and deployments were stressful. They'd start at friday late like 8pm or so and go until 8am in the morning. Everyone was on a long call the entire time. I hated it.

Re: Incident with Issues and Pull Requests

#118
post #17

Just lost a merge commit to dev/null. This is getting tiresome

How??? You do the merge, which either creates a new commit for the change, or appends the commits to your existing tree. Then you push that to the remote. If the push fails, you can just push again, it's not lost. And if the merge failed, you didn't have any merge commit to begin with.

You can do a lot of operations on the github web UI nowadays. Could have been that

Re: Incident with Issues and Pull Requests

#120
post #35

Earlier quoted context omitted.

Everyone thinking they've been laid off and notified via git push. Just GitHub being GitHub.

Exactly what I thought! Maybe I'm too paranoid

The first time it did that to me as well. Now I'm used to it.
Post reply on HN