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

GitHub Outage

github.com

Post reply on HN
Print view View original

171–180 of 297 posts

Re: GitHub Outage

#171

Post by jmcqk6 »

mailanik wrote: post #82
developit wrote: post #14

Earlier quoted context omitted.

If you listen closely you can hear the sound of all bower-dependent builds on earth failing in synchrony

why only bower-dependent?

I'm guessing the parent doesn't mean only bower, but bower uses github as the source of packages/code (I don't use bower, so I'm only going from memory). On a build that downloads everything 'fresh' it's not going to be able to get sources that are only on github.

Bower certainly isn't the only thing that does it. It's a trend that's becoming more and more common.

Re: GitHub Outage

#172

Post by beat »

debacle wrote: post #136
beat wrote: post #124

Earlier quoted context omitted.

Having used both, I find github's tools (mostly) better. And bitbucket isn't 100% reliable either.

Self-hosted is.

Self-hosted isn't 100% reliable either. Nobody is that good. I've done serious high availability (financial system that would land on the front page of the New York Times the way Github lands on HN), and it wasn't 100%. And the overhead of high availability is incredible.

No way would I do self-hosted version control. I have better things to do than babysit servers for commodity services.

Re: GitHub Outage

#173

Post by joeevans1000 »

Too bad I'm not teaching someone to use git and/or github right now. Perfect opportunity for a practical joke. "Oh, great, look... you broke GitHub with that last command."

Re: GitHub Outage

#174

Post by sergiotapia »

Analemma_ wrote: post #92

sigh Many moons ago when I was a starry-eyed lad just learning to use Git, I remember all the cheerful sentences in the Git book like "Unlike SVN, with Git you can work even when the server is down!" The more things change, the more they stay the same.

Git is not Github. If hotmail.com goes down, it doesn't take down email worldwide with it.

Re: GitHub Outage

#175

Post by outworlder »

Perceptes wrote: post #170

Every time this happens people make clever remarks about how Git is distributed but we're all depending on GitHub for so much that we defeat the purpose. But once GitHub comes back up, everyone just gets back to work, trusting and relying on it as much as ever. Eventually it goes down again, and we come back to complain. Convenience is the only thing that we seem to value. (I'm no different, which makes my comment co…

Yes, but at least you can continue to work while it is down. You'll be missing on the collaboration part (and bug trackers, and stuff).

If you are desperate, you can also call another developer and add another remote pointing somewhere else. So Git is a win anyway.

Try that with a "SubversionHub"...

Re: GitHub Outage

#176

Post by brbsix »

Perceptes wrote: post #170

Every time this happens people make clever remarks about how Git is distributed but we're all depending on GitHub for so much that we defeat the purpose. But once GitHub comes back up, everyone just gets back to work, trusting and relying on it as much as ever. Eventually it goes down again, and we come back to complain. Convenience is the only thing that we seem to value. (I'm no different, which makes my comment co…

Even if convenience is not a priority for you, it almost certainly will be for people you want/need to interact with.

Re: GitHub Outage

#177

Post by ianopolous »

brudgers wrote: post #62
firloop wrote: post #50

Earlier quoted context omitted.

Regardless, most dependencies are on GitHub which breaks bower install for most people. It's crazy how much infrastructure relies on this single point of failure.

Someone should make a distributed version control system.

You mean like IPFS? [1] People are working on it.

[1] https://ipfs.io

Re: GitHub Outage

#180

Post by gonzo »

mrdrozdov wrote: post #52

This is new. Looks like github is still "working" when it's down. $ git push origin master Counting objects: 5, done. Delta compression using up to 8 threads. Compressing objects: 100% (5/5), done. Writing objects: 100% (5/5), 433 bytes | 0 bytes/s, done. Total 5 (delta 4), reused 0 (delta 0) remote: Unexpected system error after push was received. remote: These changes may not be reflected on github.com! remote: You…

It's down now.

  jim% git clone git@github.com:pfsense/pfsense.git
  Cloning into 'pfsense'...
  fatal: remote error: 
    GitHub is offline for maintenance. See     
  http://status.github.com for more info.
Post reply on HN