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

231–240 of 297 posts

Re: GitHub Outage

#232

Post by mitchtbaum »

mrdrozdov wrote: post #36
mikesickler wrote: post #16

I think I'm setting some kind of Ctrl-R land speed record.

Heh, talk about a negative feedback loop. DDOS propagating more DDOS....

That would mean a positive feedback loop. https://en.wikipedia.org/wiki/Positive_feedback_loop

(Positive in this sense has a similar meaning in behavioral psychology's terminology for operant conditioning, adding punishment.. which both come off as odd with our common use of positive as good and beneficial :/ https://en.wikipedia.org/wiki/Operant_conditioning)

...Carrying on with your analysis, since uninterrupted positive feedback loops result in explosion, I guess that would mean either (for this outage) github's fallback status page would go down or the parts of the network carrying that traffic, which could not handle their increased load, would go down.

Probably better we would rework these control mechanisms and reroute \ rewire \ entirely change these processes.

Re: GitHub Outage

#233

Post by gnuvince »

beat wrote: post #131
melvinmt wrote: post #125

Earlier quoted context omitted.

Why would your commit fail?

First noticed it when making a wiki commit, actually. Edited the story slightly for artistic license. :)

I think he meant that the commit should work fine, but the push would fail.

Re: GitHub Outage

#234

Post by ianopolous »

kelseydh wrote: post #203
ianopolous wrote: post #177

Earlier quoted context omitted.

You mean like IPFS? [1] People are working on it. [1] https://ipfs.io

Their source code pointing to Github is symbolic of exactly how this problem hasn't been solved yet.

I didn't say it was solved, but they are very close. IPFS is essentially a global p2p git repo, with a cryptographically controlled branch namespace.

Re: GitHub Outage

#236

Post by smurpy »

madmod wrote: post #80

For the impatient. I would make a gist but... while true; do curl -s https://status.github.com/api/status.json | grep good && tput bel || echo -n .; sleep 1; done

Here is a version which uses OSX's say command for a spoken announcement of "github is up again". It also checks once every minute instead of once a second.

    while true; do curl -s https://status.github.com/api/status.json | egrep 'good|minor' && say -r 160 "github is up again" || echo -n .; sleep 60; done
Edit: accept a status of minor as an indication of up-ness.

Re: GitHub Outage

#237

Post by aylmao »

fpgaminer wrote: post #186

Relavant: GitTorrent: A Decentralized GitHub ( http://blog.printf.net/articles/2015/05/29/announcing-gittor... ) The repo is at ... https://github.com/cjb/GitTorrent , so just clone that and ... oh ...

From the site:

  First we connect to GitHub to find out what the latest 
  revision for this repository is, so that we know what we
  want to get. GitHub tells us it’s 5fbfea8de... Then we 
  go out to the GitTorrent network.
So yeah, wouldn't have saved you.

Re: GitHub Outage

#239

Post by AdamJacobMuller »

gjtorikian wrote: post #207
i336_ wrote: post #151

Earlier quoted context omitted.

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

Hate to be the bearer of bad news, but ikawe was joking about the bower thing. Source: I work at GitHub.

> Source: I work at GitHub.

So, you're saying you broke it.

Everybody, over here, gang up on this guy.

Re: GitHub Outage

#240

Post by andytuba »

niutech wrote: post #221
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…

Companies/people don't learn on their mistakes. Almost everything is on GitHub nowadays. This makes it a SPOF even if Git itself is distributed. More companies should host their projects on premises. There are good open source alternatives to GitHub: Apache Allura, Fossil, GitBucket, GitLab, Phabricator, and Redmine.

... GitHub Enterprise ...
Post reply on HN