I didn't realize until today that https://www.npmjs.com/package/geckodriver downloads from Github.
GitHub Is Down
51–60 of 93 posts
Re: GitHub Is Down
#52Their status page is quite pretty, does anyone know of an open-source option that looks similar?
Re: GitHub Is Down
#53If only there was some kind of distributed version control system. /s
Re: GitHub Is Down
#54PSA: I just received a github phishing request that was not detected by Gmail. I almost fell for it. Phishing email looks like a "review your suspicious activity" alert, but the alert is the suspicious activity. https://imgur.com/a/zdtWmuN
Just received a repository vulnerability notification as well, in the Pillow dependency but it seems legit.
Re: GitHub Is Down
#55Okay... so, when is Amazon launching their GitHub alternative?
Re: GitHub Is Down
#56Earlier quoted context omitted.
Remove spiderweb dependencies from your deployment pipeline?
This is a good point, but it could be worded better. One of the things a site reliability engineer should think about is how well the site can be operated when dependencies have issue. After an incident like this, even if you were able to recover, it's worth thinking about how things could have gone better. In the past I had a painful experience with one application I was supporting that needed to install NPM package…
To your point on NPM dependencies, CDNs for JS libraries is another thing that I recently learned is common practice, which I don't fully understand. It seems like if the CDN goes down then your application stops working, but I am convinced I'm missing something here because it seems like such poor engineering judgement. This seems to be really common in SPAs, which is precisely where (it seems to me) you shouldn't be using a CDN.
It seems the convenience of cloud based deployment pipelines is not really worth situations like this.
Re: GitHub Is Down
#57We use a self-hosted GitLab ourselves and I can honestly say we have more up time than GitHub. But 9/10 every project we use is on GitHub and our work is stalled. Centralization will be our downfall :(
This is why it's a good idea to have multiple remotes and advertise those remotes in
the project README (my examples: [0]). You'll lose centralized issues during
downtime, but you'll at least be able to interact with some remotes and do basic
collaboration with `git format-patch` and `git send-email`.
If something like sourcehut [1] goes down, nothing will change; users will still be able to push/pull to mirrors and work with mailing lists and git's built-in email-based pull-requests.
[0]: chattiest-channels, dotfiles, term-dmenu, and mpd-scripts at https://git.sr.ht/~seirdy
Re: GitHub Is Down
#58If only there was some kind of distributed version control system. /s
Of course, there is. You just need to host it. Self-hosted GitLab mirrors work great when GitHub is down.
https://docs.gitlab.com/ee/user/project/repository/repositor...
Re: GitHub Is Down
#59It's working again.
Re: GitHub Is Down
#60I don't see the point for major open-source projects or even company projects to depend on a third-party provider for git services in the cloud that is not on-premise. It's fine if the source code is self-hosted or on premise and the mirror is hosted on some cloud VCS like Github, but not the other-way round, which for the latter you risk getting problems like this. The case for self-hosting a VCS server for serious…
Unless you have the (ops) capacity to host it yourself reliably, chances are GitHub will be up more than your self-hosted solution. As I'm typing this, I'm waiting for GitHub to recover so I can deploy an update to a rather important project for a big client. However, I'm happy it's their engineers to be scrambling to fix their git hosting, instead of me context switching from my work and rushing to duct-tape piece o…
and they rolled out a fix in 45 min which is less time then i took for lunch today.