GitHub was down • Hacker News Board

Re: GitHub was down

#101

Post by worble » Mon, Jul 13, 2020, 8:59 AM UTC

Evidlo wrote: post #37

rvz wrote: post #27

I said this before many times and I'll say it again, consider self-hosting your projects on a solution like GitLab or Gitea to avoid this sort of situation. [0] GNOME, Xfce, Redox, Wireguard, KDE and Haiku all have self-hosted on either cgit, Gitlab, Phabricator or Gitea. [0] https://news.ycombinator.com/item?id=23676072

The downside is that a lot of these self hosted archives will have disappeared 10 years from now. Meanwhile, I expect many forgotten repos to remain online with Github one way or another for a very long time. If you do go the self-hosting route, add a mainstream host as an additional remote and push your commits to both.

The easy solution to this is that git supports pushing to multiple remotes: https://news.ycombinator.com/item?id=23818609

In fact, with all these free services, I'd probably say it's well worth automatically making remotes (at least) for GitLab, GitHub and having a local Gitea for everything you do. This should be resilient against specific outages, or GitHub simply deciding they don't like your project name, or some other disaster.

Re: GitHub was down

#102

Post by Symbiote » Mon, Jul 13, 2020, 9:12 AM UTC

m0xte wrote: post #42

navanchauhan wrote: post #32

Earlier quoted context omitted.

Oh no! What will you recommend as a long term solution? I have ordered a Pi 4, should I use an USB Flash Drive / HDD / SATA SSD?

Honestly throw the thing in a bin and use an old mini pc instead. Lenovo thinkcentre tiny. You can pick them up on eBay for about the same as a fully equipped pi. Pi is 100% not suitable for 100% duty work. It’s just a toy.

That's 27W (idle), compared to the Pi 4's 3.4W (idle).

That's an additional 145kg of CO₂ per year (2018 US average).

Re: GitHub was down

#103

Post by FBISurveillance » Mon, Jul 13, 2020, 9:14 AM UTC

From what I understood, they are having capacity issues with one of their MySQL masters or something. I've read that they are in process of sharding/resolving that but it takes time.

To GitHub SRE/oncall people: hang in there, you're awesome.

Re: GitHub was down

#104

Post by capableweb » Mon, Jul 13, 2020, 9:15 AM UTC

wg0 wrote: post #97

breakingcups wrote: post #78

Earlier quoted context omitted.

See, I like the idea of K8S quite a lot. Enough that I decided to set up a cluster from scratch to figure out how everything ties together. I've since grown to strongly dislike how much of the entire ecosystem seems to depend on random unversioned Github gists or direct links into a raw file in a repo somewhere.

This actually is testament to the fact that the github used to be that damn reliable at one point.

Eh, I'd love to see numbers on this but I don't think this is true. I remember stuff like homebrew breaking even in the beginning of the project because of the dependency on github to pull down formulas and stuff.

Re: GitHub was down

#105

Post by Symbiote » Mon, Jul 13, 2020, 9:16 AM UTC

chvid wrote: post #59

Cool thing about git is that it is distributed and there is no single point of failure ...

It is. We all have our own copy of the repository, and can still distribute changes using any of the other methods:

- A different central server

- Email

- A shared on-filesystem copy, e.g. local network drive

- HTTP or SSH between developer computers (put your repository somewhere where your NginX or Apache serves it, the other developer can "git remote add chvid http://chvid.example.com/repository").

Re: GitHub was down

#106

Post by m0xte » Mon, Jul 13, 2020, 9:29 AM UTC

Symbiote wrote: post #102

m0xte wrote: post #42

Earlier quoted context omitted.

Honestly throw the thing in a bin and use an old mini pc instead. Lenovo thinkcentre tiny. You can pick them up on eBay for about the same as a fully equipped pi. Pi is 100% not suitable for 100% duty work. It’s just a toy.

That's 27W (idle), compared to the Pi 4's 3.4W (idle). That's an additional 145kg of CO₂ per year (2018 US average).

M600 fanless is around 15W full whack and 5.5W idle (measured). The CPU in it has a 4W TDP.

For that you gain:

Decent thermal design., A decent quality enclosure, A power supply (thinkpad brick), Two displayport holes, An SATA interface (M.2 form) for an SSD, Built in Wifi, A RAM slot you can chuck 16Gb in, 2 more USB ports.

There's no competition. I paid 79 GBP each for mine (I own 3). Pi is 57 GBP bare board.

Pictures. Mac mini for scale: https://imgur.com/a/jXjLusb

And on CO2, perhaps you should just do without it if it's a problem.

Re: GitHub was down

#107

Post by tester34 » Mon, Jul 13, 2020, 9:31 AM UTC

lopis wrote: post #41

quyleanh wrote: post #30

I still don't understand people who always mentions to Microsoft's acquisition. Until the official statement, it isn't Microsoft failure. Don't blame them.

It's not MS fault, of course, but since MS acquired GH, GH has been much more relaxed. New features are added all the time, clearly not ready for the spotlight. It gives you a different comfort knowing your daddy is there as a safety net.

But also they have a lot of new customers/users, so maybe the scale's the problem? I don't know.

Re: GitHub was down

#108

Post by IshKebab » Mon, Jul 13, 2020, 9:44 AM UTC

breakingcups wrote: post #78

a012 wrote: post #17

I know Github is down because I'm trying to update a kops cluster, but Github breaks it > kops update cluster error reading channel "https://raw.githubusercontent.com/kubernetes/kops/master/channels/stable": unexpected response code "500 Internal Server Error" for "https://raw.githubusercontent.com/kubernetes/kops/master/channels/stable": 500: Internal Server Error

See, I like the idea of K8S quite a lot. Enough that I decided to set up a cluster from scratch to figure out how everything ties together. I've since grown to strongly dislike how much of the entire ecosystem seems to depend on random unversioned Github gists or direct links into a raw file in a repo somewhere.

NPM is the same. You might think that all of the packages are stored on NPM servers. Mostly true, but still when you install some of them they'll download precompiled binaries or whatever directly from Github.

Re: GitHub was down

#109

Post by ashishb » Mon, Jul 13, 2020, 9:47 AM UTC

What if we had a smart failover. Use GitHub and GitLab simultaneously. All issues, all comments, all PRs duplicated. If one goes down you use the other one in the time being with no interference at all. One can probably then build a frontend which magically does this failover for ci/CD etc. Isn't that's how much redundant this should be?

Re: GitHub was down

#110

Post by Kiro » Mon, Jul 13, 2020, 9:52 AM UTC

rvz wrote: post #27

I said this before many times and I'll say it again, consider self-hosting your projects on a solution like GitLab or Gitea to avoid this sort of situation. [0] GNOME, Xfce, Redox, Wireguard, KDE and Haiku all have self-hosted on either cgit, Gitlab, Phabricator or Gitea. [0] https://news.ycombinator.com/item?id=23676072

No, the main point of programming for me is to fill up the activity graph on GitHub. Without that I may just as well quit.