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

251–260 of 297 posts

Re: GitHub Outage

#251

Post by cflat »

chuhnk wrote: post #94
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…

I once ran rm -rf in the production mysql data directory. Shit happens.

You are the human manifestation of "the chaos monkey"

Re: GitHub Outage

#252

Post by matthuggins »

Help! The site is back, but I just pushed a new branch that isn't showing on the site, meaning I can't create a pull request.

    circuitry git:(feature/middleware) git push origin feature/middleware
    Counting objects: 18, done.
    Delta compression using up to 8 threads.
    Compressing objects: 100% (18/18), done.
    Writing objects: 100% (18/18), 5.01 KiB | 0 bytes/s, done.
    Total 18 (delta 9), reused 0 (delta 0)
    To git@github.com:kapost/circuitry
     * [new branch]      feature/middleware -> feature/middleware
This branch is not appearing in the repo: https://github.com/kapost/circuitry/branches

Re: GitHub Outage

#253

Post by davidcelis »

rcthompson wrote: post #219
bobwaycott wrote: post #166

Earlier quoted context omitted.

Yeah, I am confused by the existence of a status report for a time 3.5hrs in the future. Guess they're just trying to get ahead of the game and set some realistic expectations.

Maybe it's GMT mistakenly labeled as PST?

It is.

Re: GitHub Outage

#254

Post by davidcelis »

matthuggins wrote: post #252

Help! The site is back, but I just pushed a new branch that isn't showing on the site, meaning I can't create a pull request. circuitry git:(feature/middleware) git push origin feature/middleware Counting objects: 18, done. Delta compression using up to 8 threads. Compressing objects: 100% (18/18), done. Writing objects: 100% (18/18), 5.01 KiB | 0 bytes/s, done. Total 18 (delta 9), reused 0 (delta 0) To git@github.co…

We're still recovering; please give the site a bit of time to come back! Not everything can be expected to work until we've gone green on status.github.com. Thanks

Re: GitHub Outage

#255

Post by kelseydh »

ianopolous wrote: post #234
kelseydh wrote: post #203

Earlier quoted context omitted.

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.

That sounds very cool. I was just pointing out how divorced these ideas still are from the way we actually program and implement things on the web.

In an ideal world, a link to a source code repository (or a link to anything for that matter...) would never fail because there would be automatic mirrors to at least provide read-only access to it.

It sort of forces one to ask whether this is the result of fundamental mistakes within HTTP / DNS itself. It's not realistic for a web designer to put time into making external links fault tolerant by running some query to switch the routing link to an available node.

Re: GitHub Outage

#256

Post by Shizza »

chuhnk wrote: post #94
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…

I once ran rm -rf in the production mysql data directory. Shit happens.

I'm going to put that on a T-shirt

Re: GitHub Outage

#257

Post by matthuggins »

davidcelis wrote: post #254
matthuggins wrote: post #252

Help! The site is back, but I just pushed a new branch that isn't showing on the site, meaning I can't create a pull request. circuitry git:(feature/middleware) git push origin feature/middleware Counting objects: 18, done. Delta compression using up to 8 threads. Compressing objects: 100% (18/18), done. Writing objects: 100% (18/18), 5.01 KiB | 0 bytes/s, done. Total 18 (delta 9), reused 0 (delta 0) To git@github.co…

We're still recovering; please give the site a bit of time to come back! Not everything can be expected to work until we've gone green on status.github.com. Thanks

Got it, thanks!

Re: GitHub Outage

#258

Post by GrAfiXoNeR »

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…

Yeah I got this as well and no changes on github.com so much for creating this release tonight. :/ I hope they will fix this otherwise this push went into oblivion and the client thinks all is well.

Re: GitHub Outage

#259

Post by halayli »

Sir_Cmpwn wrote: post #157
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.

It's not like Github has 2 engineers only.

Re: GitHub Outage

#260

Post by vinceyuan »

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.

BitBucket
Post reply on HN