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

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

githubstatus.com

Post reply on HN
Print view View original

101–110 of 130 posts

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

#101

Post by sofixa »

goodoldneon wrote: post #99
hospitalJail wrote: post #93

I'm the lone person at my team that still believes in keeping most of our stuff local, with online versions as primarily backup. Every time some global service goes down, or internal internet/intranet goes down, there is a security breach, or a WFH person has a power outage I'm reminded I'm right. I'm no luddite, these services make you dependent on them. The worst thing I'm dependent on here is a bad computer. We ha…

I don't know about you, but the stuff I self-manage usually has worse uptime than SaaS products

Really depends on the "stuff". GitLab pretty much manages itself through their Helm and Omnibus installs.

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

#102

Post by meling »

__alexs wrote: post #88
wun0ne wrote: post #3

Does GitHub provide uptime stats? Seems very unreliable recently.

Performance of the GitHub website in general feels increasingly bad.

Yes, my experience too. I feel it the most when reviewing code. It felt much snappier before.

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

#103

Post by ht85 »

idk1 wrote: post #47

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…

Next time try coffee, it's another worthy experience.

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

#104

Post by electroly »

Kelteseth wrote: post #5

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

GitHub outages aren't nearly long or often enough to consider this. Git is distributed, just keep working locally until GitHub is back up. GitHub outages are nowhere near the threshold of pain I'd require to introduce a second Git hosting provider to the mix.

Really, GitHub outages barely hurt at all. It's not like an AWS or Cloudflare outage which is more likely to be a production disaster. Every outage a bunch of people on HN start screaming about owning their own on-prem destiny or wondering why we're still on GitHub. Nothing changes because it's not nearly as bad as those people are making it out to be. Life is all about tradeoffs.

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

#105

Post by solotronics »

hospitalJail wrote: post #93

I'm the lone person at my team that still believes in keeping most of our stuff local, with online versions as primarily backup. Every time some global service goes down, or internal internet/intranet goes down, there is a security breach, or a WFH person has a power outage I'm reminded I'm right. I'm no luddite, these services make you dependent on them. The worst thing I'm dependent on here is a bad computer. We ha…

GIT is actually a great protocol for keeping distributed copies of code. You can pretty easily with bash cycle through a list of backup urls for a git repo, looking for updates.

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

#108

Post by voynich »

KomoD wrote: post #106

This happens constantly, what is the Github team doing?

I've started working on a Forgejo instance for myself (Gitea fork). It's honestly disappointing how bad GitHub has gotten, just in terms of uptime anymore. I hope they get their stuff together.

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

#110

Post by joshmanders »

darkwater wrote: post #96
that_guy_iain wrote: post #39

Earlier quoted context omitted.

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 mont…

> while we have 3-4 days of downtime on our self hosted jenkins during the same time Wow. This sounds like a broken organization?

It sounds like literally every organization.
Post reply on HN