Live data from Hacker News

GitHub Outage

github.com

81–90 of 297 posts

Re: GitHub Outage

#83
post #50

Earlier quoted context omitted.

Regardless, most dependencies are on GitHub which breaks bower install for most people. It's crazy how much infrastructure relies on this single point of failure.

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

Re: GitHub Outage

#84
post #50

Earlier quoted context omitted.

Regardless, most dependencies are on GitHub which breaks bower install for most people. It's crazy how much infrastructure relies on this single point of failure.

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

It is possible to install npm packages that are hosted on GitHub: http://stackoverflow.com/a/17509764/889864

Re: GitHub Outage

#85

This is new. Looks like github is still "working" when it's down. $ git push origin master Counting objects: 5, done. Delta compression using up to 8 threads. Compressing objects: 100% (5/5), done. Writing objects: 100% (5/5), 433 bytes | 0 bytes/s, done. Total 5 (delta 4), reused 0 (delta 0) remote: Unexpected system error after push was received. remote: These changes may not be reflected on github.com! remote: You…

The Git backend is different from the GitHub frontend, unsurprisingly.

Re: GitHub Outage

#86

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…

I was getting plain-old 500 errors, which is what brought me here

Re: GitHub Outage

#87
post #50

Earlier quoted context omitted.

Regardless, most dependencies are on GitHub which breaks bower install for most people. It's crazy how much infrastructure relies on this single point of failure.

Someone should make a distributed version control system.

Or a local cache of dependencies

Re: GitHub Outage

#90
post #50

Earlier quoted context omitted.

Regardless, most dependencies are on GitHub which breaks bower install for most people. It's crazy how much infrastructure relies on this single point of failure.

Someone should make a distributed version control system.

What would that look like? Can you describe it? It's not very useful to say stuff without providing some sort of useful idea. You can't just say "someone should write some sort of stupid content tracker, and give it some random three-letter combination that is pronounceable," or whatever.
Post reply on HN