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

Github experiencing major service outages across all services.

status.github.com

Post reply on HN
Print view View original

101–110 of 147 posts

Re: Github experiencing major service outages across all services.

#101

Post by csense »

zalew wrote: post #99
csense wrote: post #66

Earlier quoted context omitted.

Here I took it as evidence of Github's generous-to-the-point-of-being-ridiculously-foolish attitude toward their customers: They'll even give free public Git hosting to products that directly compete with their core business at a lower price point (free)! Even if you Do No Evil (R), some people will still complain about you. That being said, Git hosting would be better for everyone if Github had a bigger competitor i…

> They'll even give free public Git hosting to products that directly compete with their core business at a lower price point (free)! unless you are providing paid accounts and expensive enterprise solutions with support, you are not competing with them in any way.

> unless you are providing paid accounts and expensive enterprise solutions with support, you are not competing with them in any way.

Yes, you are. If you would have bought their product (paid Git hosting), but you used somebody else's product instead (Gitolite), then that other product (Gitolite) is competing with Github for your business.

I agree that there is a subset of the market that (a) won't or can't figure out Git hosting on their own, or (b) decides that paying for a Github account will actually be less expensive. But I never said that Gitolite will ever replace Github.

Re: Github experiencing major service outages across all services.

#102

Post by chuhnk »

csense wrote: post #100

It should be pretty far down their list of priorities at this point, but I just noticed the "Exception Percentage" value at https://status.github.com/graphs/past_day is saying 483.704%. The fact that they're measuring this in percentages implies the maximum is 100%, but this isn't so.

I imagine it was a percent measured against successful responses. The exceptions now far exceed those successful responses. You are correct in saying it should be 100% but people have a habit of scaling beyond it.

Re: Github experiencing major service outages across all services.

#104

Post by buttscicles »

fomojola wrote: post #92

Interesting: Github Pages is still up (got a blog on there and it doesn't appear to have experienced any outages). Static site generators for the win.

Pages was out briefly a couple of hours ago (certainly some repos, anyway)

Seems to be fine now though.

Re: Github experiencing major service outages across all services.

#106

Post by zemanel »

kh_hk wrote: post #96
zemanel wrote: post #83

Earlier quoted context omitted.

i understood that and was aware. What i mean was for a web service that would monitor changes on public repos (commits, tags, branches) and would sync them automatically (mapping accounts, pruning branches, etc).

What would happen if that service goes down?

:-) the original and mirror repos would still be available, even if the mirrors would be outdated since the mirror service failure ?

Re: Github experiencing major service outages across all services.

#107

Post by csense »

chuhnk wrote: post #102
csense wrote: post #100

It should be pretty far down their list of priorities at this point, but I just noticed the "Exception Percentage" value at https://status.github.com/graphs/past_day is saying 483.704%. The fact that they're measuring this in percentages implies the maximum is 100%, but this isn't so.

I imagine it was a percent measured against successful responses. The exceptions now far exceed those successful responses. You are correct in saying it should be 100% but people have a habit of scaling beyond it.

If this is in fact how they're measuring...I was going to make this post a long rant about how ridiculous it is to measure it in that way, but then I realized that people do sometimes measure probabilities by quoting the win-to-loss or loss-to-win ratio.

This is called "odds" and frequently used in gambling. Usually, though, someone says "4.7 to 1" or "47 to 10" (abbreviated 4.7:1 or 47:10) instead of 470%. Usually the larger number is stated first, and the direction is usually indicated by a word like "favorite" or "longshot." So one would say "Errors seem to be a 4.7:1 favorite today."

It's slightly complicated by the fact that odds can measure one of several things:

A. A probability ratio ("Red" is a slight underdog in the game of roulette [1]; the odds against hitting it are 20:18 since there are 20 non-red spaces and 18 red spaces)

B. A payout ratio ("Red" pays 1:1, meaning the prize if you win this bet is equal to the amount of the bet)

C. The current payout of a paramutuel pool [2]

Odds are seldom used outside of a gambling context.

[1] http://en.wikipedia.org/wiki/Roulette

[2] http://en.wikipedia.org/wiki/Parimutuel_betting

Re: Github experiencing major service outages across all services.

#108

Post by kh_hk »

zemanel wrote: post #106
kh_hk wrote: post #96

Earlier quoted context omitted.

What would happen if that service goes down?

:-) the original and mirror repos would still be available, even if the mirrors would be outdated since the mirror service failure ?

I know this is just speculative, and in fact I was joking, but to achieve that you either have to:

1) Configure a push hook on the master server, which you need access to.

2) Remove decentralized from DVCS, as your service becomes a new master which then mirrors.

3) Continuously poll (pull) the master server from your mirror service.

I can't seem to find any of these three options more desirable than simply adding a new remote, other than being automatic.

Re: Github experiencing major service outages across all services.

#109

Post by zemanel »

kh_hk wrote: post #108
zemanel wrote: post #106

Earlier quoted context omitted.

:-) the original and mirror repos would still be available, even if the mirrors would be outdated since the mirror service failure ?

I know this is just speculative, and in fact I was joking, but to achieve that you either have to: 1) Configure a push hook on the master server, which you need access to. 2) Remove decentralized from DVCS, as your service becomes a new master which then mirrors. 3) Continuously poll (pull) the master server from your mirror service. I can't seem to find any of these three options more desirable than simply adding a…

Yes :-) plus the bandwidth and storage would be overkill overtime

Re: Github experiencing major service outages across all services.

#110

Post by syncsynchalt »

kh_hk wrote: post #94
syncsynchalt wrote: post #82

Earlier quoted context omitted.

I created a new org on GitHub today (through all the unicorns) and was about to push an existing repo to them so we could all start pulling it. Talk about unlucky.

The good part is you can do it yourself without GitHub (which, after the downtime, could come into the equation quite easily): -- Remote machine, or SSH port forwarded machine -- > adduser git (you either add pusher/puller's ssh pubkeys to its authorized_hosts, or use a shared password) > su git > cd ~ > git init --bare myproject.git -- Your local repo -- > git remote add git@aforementionedmachine:myproject.git > git…

Already had the repo up and running elsewhere, thanks. Just needed to do some non-git stuff on github (create a new repo on GH to push it to, add team members, and so on).

I've been doing private DVCS for years (mercurial) but this is my first project that's on git and I've been looking forward to the opportunity to host it on github and see what I've been missing.

Post reply on HN