GitHub Outage • Hacker News Board

Re: GitHub Outage

#71

Post by dozzie » Thu, Jan 28, 2016, 12:45 AM UTC

ChickeNES wrote: post #30

fletchowns wrote: post #6

If you listen closely you can hear the sound of continuous integration builds around the world breaking

Yup, a coworker was wondering why a build failed, a minute later I saw this.

Well, it's not like we have invented binary and source packages two decades ago, so people don't need to re-download and re-build their build-time dependencies every time they start compilation.

Oh wait, we have.

Re: GitHub Outage

#72

Post by msie » Thu, Jan 28, 2016, 12:46 AM UTC

dsl wrote: post #57

Fortunately git is distributed and lets you work offline. https://git-scm.com/about/distributed

I'm trying to read some webpages hosted on GitHub.

Re: GitHub Outage

#73

Post by upbeatlinux » Thu, Jan 28, 2016, 12:46 AM UTC

The status page update seems like some ironic machine rant "The status is still red at the beginning of the day" (http://take.ms/50Tox)

Hubot has assumed control...the singularity is upon us!!!

Re: GitHub Outage

#74

Post by surferbayarea » Thu, Jan 28, 2016, 12:47 AM UTC

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 client side gets a return code that the push was successful.

Re: GitHub Outage

#75

Post by foobarbecue » Thu, Jan 28, 2016, 12:47 AM UTC

placeybordeaux wrote: post #48

debacle wrote: post #37

Earlier quoted context omitted.

A bitbucket license is $10. Paying $50 a month is redonk.

Whats your service level agreement?

I liked that question better with the apostrophe.

Re: GitHub Outage

#76

Post by kelseydh » Thu, Jan 28, 2016, 12:47 AM UTC

Well that's the last time I ever write a deployment that assumes Github is working...

Re: GitHub Outage

#77

Post by ChickeNES » Thu, Jan 28, 2016, 12:47 AM UTC

"We're investigating a significant network disruption effecting all http://github.com services." - https://twitter.com/githubstatus/status/692508939792039936

Re: GitHub Outage

#78

Post by rodgerd » Thu, Jan 28, 2016, 12:47 AM UTC

fletchowns wrote: post #6

If you listen closely you can hear the sound of continuous integration builds around the world breaking

Which is, in a sense, a bit disturbing.

Re: GitHub Outage

#79

Post by firloop » Thu, Jan 28, 2016, 12:47 AM UTC

johnhenry wrote: post #70

firloop wrote: 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.

Oh wow, color me surprised. I edited my comment.

Re: GitHub Outage

#80

Post by madmod » Thu, Jan 28, 2016, 12:47 AM UTC

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