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

GitHub was down

status.github.com

Post reply on HN
Print view View original

81–90 of 253 posts

Re: GitHub was down

#81

Post by cjbprime »

0xbear wrote: post #64
cjbprime wrote: post #20

Earlier quoted context omitted.

Newly introduced errors in site code are only one of many sources of failure for a site like GitHub, and probably a fairly rare one.

It's a nearly weekly occurrence. Avoidable one, I might add. When was the last time a major Google service had a major outage?

You're still missing the point, by assuming that the outages are code related when you call them avoidable. Distributed systems at scale are terrifyingly hard to control.

When I said "probably a fairly rare one", I didn't mean that the outages are rare. I meant that new code is probably a rare cause of the outages that happen. They have other causes unrelated to new code.

(I'm also skeptical that GitHub major outages happen "nearly weekly", but I don't have data.)

Re: GitHub was down

#84

Post by nicodjimenez »

Pretty shocking how accustomed we've all become to Github outages. Mission critical developer tools should have gratuitously high uptime. Github is a 100M company whose most important operational objective is just keeping the site running. I call shenanigans.

Re: GitHub was down

#85

Post by tedmiston »

weberc2 wrote: post #63
tinalumfoil wrote: post #54

Earlier quoted context omitted.

> bored developers Bored? Git's a distributed version control system, so no excuses. Get back to work! But in all seriousness I kind of wish GitHub provided a way to mirror things like issues and PRs so you never have to be fully reliant on one service. Not being able to read these really does make it impossible to get work done offline.

I'm of the impression that issues and PRs are all accessible via an API. What more should they do?

From the perspective of someone mid code review during the outage, it's worked as well as it could too. They preserve comment drafts client side that haven't posted to the server yet across page reloads. While it's a little frustrating to have to submit something 3-5x, they're definitely doing something for this use case already.

Also as others pointed out, just because the GitHub app is down doesn't always mean the GitHub git server itself is down.

Re: GitHub was down

#88

Post by pavement »

syshum wrote: post #62
tinalumfoil wrote: post #54

Earlier quoted context omitted.

> bored developers Bored? Git's a distributed version control system, so no excuses. Get back to work! But in all seriousness I kind of wish GitHub provided a way to mirror things like issues and PRs so you never have to be fully reliant on one service. Not being able to read these really does make it impossible to get work done offline.

But they want you to Rely on Github... if they could find away to make Git only work with Github they would in a heart bet. Github is not a open source company, it is not really even a supporter of free software IMO they are a danger to free software for this very reason. They are following the old school Microsoft model of Embrace and Extend... I am waiting to see if they can extinguish,

Just because it's A common motivation and strategy, doesn't mean it's THEIR motivation and strategy.

A more likely strategy/motivation is that the product is you. AKA: farming the users.

Create a desirable pasture, and the animals farm themselves.

Re: GitHub was down

#90

Post by twblalock »

tambourine_man wrote: post #82

Insert remark on why we use a centralized service for a distributed source control system, etc. No one seems to care, unfortunately

Lots of people care, but we also recognize that the advantages of using a centralized system outweigh the disadvantages for many use cases.
Post reply on HN