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

111–120 of 297 posts

Re: GitHub Outage

#111

Post by johnhenry »

clessg wrote: post #83
johnhenry wrote: post #70

Earlier quoted context omitted.

Aren't npm installs actually hosted on npm? This shouldn't affect npm installs.

That's right. Except I of course got unlucky. npm i semantic-ui npm ERR! fetch failed https://github.com/derekslife/wrench-js/tarball/156eaceed68ed31ffe2a3ecfbcb2be6ed1417fb2 npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 503

So, in this case, it looks like github isn't acting as a version control server, but rather a static server... It turns out that github isn't just a single point of failure for some application, but rather multiple points of failure for slightly different reasons...

Re: GitHub Outage

#114

Post by kelseydh »

surferbayarea wrote: post #74

scary... "remote: Unexpected system error after push was received. remote: These changes may not be reflected on github.com! remote: Your unique error code: 7527a6e1bbc9fe126d51c97feac7b4e3 remote: Unexpected system error after push was received. remote: These changes may not be reflected on github.com! remote: Your unique error code: 7527a6e1bbc9fe126d51c97feac7b4e3" seems pushes are going into oblivion, but the cli…

Github's security team should clarify what's going on.

Re: GitHub Outage

#115

Post by debacle »

beat wrote: post #59
debacle wrote: post #19

I'm kind of tired of paying for a service that has so many outages.

Go to bitbucket, or self-host, or find some other shiny new competitor. The market speaks with its feet.

We're already planning a bitbucket move. Unfortunately it's not planned for another week or two.

Re: GitHub Outage

#118

Post by spiralganglion »

vampolo wrote: post #101
ikawe wrote: post #27

Sorry, I think I caused this. =[ bower jquery#1.11.3 not-cached git://github.com/jquery/jquery-dist.git#1.11.3 bower jquery#1.11.3 resolve git://github.com/jquery/jquery-dist.git#1.11.3 bower foundation#~5.5.2 cached git://github.com/zurb/bower-foundation.git#5.5.3 bower foundation#~5.5.2 validate 5.5.3 against git://github.com/zurb/bower-foundation.git#~5.5.2 bower ember#^2.3.0 ECMDERR Failed to execute "git ls-remo…

Oh! i see! So you are the guy that DDoSed github by downloading Ember!

I thought the point of heavy client-side frameworks was to take load off the server.

Re: GitHub Outage

#119

Post by snarkyturtle »

ikawe wrote: post #27

Sorry, I think I caused this. =[ bower jquery#1.11.3 not-cached git://github.com/jquery/jquery-dist.git#1.11.3 bower jquery#1.11.3 resolve git://github.com/jquery/jquery-dist.git#1.11.3 bower foundation#~5.5.2 cached git://github.com/zurb/bower-foundation.git#5.5.3 bower foundation#~5.5.2 validate 5.5.3 against git://github.com/zurb/bower-foundation.git#~5.5.2 bower ember#^2.3.0 ECMDERR Failed to execute "git ls-remo…

That's what you get for using bower and jquery. The react/webpack gods are angry.

Re: GitHub Outage

#120

Post by qwyxzy »

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.

Well… you can still work with Git when the server is down. Just not GitHub.
Post reply on HN