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

151–160 of 297 posts

Re: GitHub Outage

#151

Post by i336_ »

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…

So... you were doing a production redeploy, and it crashed?

The URL "git://github.com/components/ember.git" [1] suggests this is an internal GitHub Bower build log, but your post history doesn't mention anything about GitHub (let alone whether you work there), so I'm not 100.00% sure.

[1] https://webcache.googleusercontent.com/search?q=cache:3e00jl...

Assuming this is, in fact, a GH Bower log, the first thing that came to mind was that this architecture isn't (and possibly should be) using a dual-silo approach: when you upgrade, the upgrade gets loaded into a new blank namespace/environment, tested, and if it worked (passes CI test coverage or something like that), the main entry point is switched to the new environment (maybe with a web server restart or config rehash) and the old environment gets purged (possibly after a trial period). The current stack looks quite akin to "click this button to flash the new firmware and DO NOT UNPLUG your device or you'll brick it."

But then I realized... wait. You guys have like... isn't it like, a few dozen RoR worker boxes? Was this crash on the inbound router or something? xD

It's all good though; consider this "curious criticism" - like constructive criticism, but with extra sympathy. And hey, GH's never broken on my watch before (not that I need it atm... hopefully); this is interesting =P

Re: GitHub Outage

#152

Post by traviswebb »

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.

That was never the main design consideration of Git, but you nonetheless can make commits and branches when the server is down. Go try it.

Re: GitHub Outage

#153

Post by sondring »

ljw1001 wrote: post #53

Reminds of the talk where a Github guy says, basically, we just push, push, push, and if something breaks we hear about it on twitter.

That was Zach Holman. He called it TDD - twitter driven development.

Re: GitHub Outage

#155

Post by cmg »

krapp wrote: post #143
cmg wrote: post #126

Earlier quoted context omitted.

I was trying to copy a library down that's not available via composer, and found that this worked: git clone git://github.com/MunGell/Codeigniter-TwitterOAuth.git . where git clone https://.. . failed. YMMV, of course.

If you're talking about PHP's composer, You can include arbitrary repos with it, you don't have to depend on packagist at all.

Good point, I always forget about that. Thanks.

Re: GitHub Outage

#157

Post by Sir_Cmpwn »

halayli wrote: post #104

I wish they say more than > We're investigating a significant network disruption affecting all github.com services.

I would prefer that they focus on getting back up and publish a post-mortem after the fact.

Re: GitHub Outage

#160

Post by [deleted] »

AndyKelley wrote: post #144
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.

I'm still working over here. I mean I took a quick break to read HN. But no productivity problems. Why can't you keep working?

[deleted]
Post reply on HN