GitHub Is Down Again | Hacker News Reader

GitHub Is Down Again

githubstatus.com

43 pointsnapsterbr12 comments

Disregarding the business impact, I always find it kind of amusing when github goes down. All the developers around me will start to stand up and walk around as if in a collective haze. I work in an area with a large density of tech companies and sidewalk traffic will increase during these outages.

If only we had a distributed system that would let you work off a local server.

The problem is that things like issues and PR comments aren’t distributed. Perhaps they should be, but they aren’t now.

Sure you can do some work locally but if your CI server can't check out the branch to build it and you can't approve pull requests for merge, then its a bit limiting.

Maybe CI shouldn't be farmed out to the cloud.

Even if you run the CI on your own network, if it can't check out from Github it isn't going to have the latest code unless you're hosting your own repos for CI. Developers will need to push their changes to CI Git in addition to Github. Its certainly possible but far outside the practices of what most companies relying on Github are likely to do for the once or twice a year it goes down briefly.

Are people that reliant on GitHub to cause such a thing?

All of my code lives on GitHub, my employer's repos are there, everything... Yet I've never been like "shit, GitHub is down, I can't work anymore"

This is the first time in a while where I actually saw they were down while it happened.

If you push code often and rely on ci and PRs and issues then you are pretty tied. I think a good portion of it is a bit tongue in cheek, but it’s also a good reminder that you can standup and walk around and be alive.

    $ git push
    All ok, pushing.
    Counting objects: 8, done.
    Delta compression using up to 8 threads.
    Compressing objects: 100% (8/8), done.
    Writing objects: 100% (8/8), 1.23 KiB | 0 bytes/s, done.
    Total 8 (delta 7), reused 0 (delta 0)
    remote: Resolving deltas: 100% (7/7), completed with 7 local objects.
    remote: Internal Server ErrorTo git@...
    ! [remote failure]  ... -> ... (remote failed to report status)
    error: failed to push some refs to 'git@...'

I guess we'll have to wait.

What is the breaking point that forces us to create a more distributed, fault-tolerant internet that doesn't have us reliant on central authorities?

me too

Yes, just 500.

Reply on news.ycombinator.com