51–60 of 130 posts
I debugged for one min at 11:59 trying to push, and then my eat-lunch notification came in at 12:00 and I opened hackernews with a tuna sandwich and this is super helpful because it means I wont need to debug it locally for 10 mins before figuring out Github is down. Edit - Just want to clarify when I say "opened hackernews with a tuna sandwich" I want to clear up that I did indeed full on mash the keyboard letters w…
* Where I am
Does GitHub provide uptime stats? Seems very unreliable recently.
CivitAI.com is down and Hugging Face is having 502s for some operations. Perhaps there is a larger issue?
Was unable to merge PRs. Earlier, I also got GitHub PR comment emails about 6 hours late. Whatever it is, it’s been happening for more than 6 hours.
Thankfully git is a distributed version control system, so such outages are not of major concern.
Earlier quoted context omitted.
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.
You can self-host GitLab and have few, if any, incidents that get resolved very quickly. Worked for a company that had no incidents that I observed in ~3 years, now work at a company that had ~2 incidents in 1.5 years.
Perhaps this is a continuing argument for self-hosting, especially if you don't have to expose the instance publicly. But then, if that's an option, you can also self-host GitHub (though I have heard less anecdotes about the stability of that).