GitHub was down again • Hacker News Board

Re: GitHub was down again

#111

Post by redsky17 » Wed, Jul 15, 2020, 7:26 PM UTC

nine_k wrote: post #91

zelly wrote: post #15

https://gitea.io/en-us/ https://git.zx2c4.com/cgit/ https://about.gitlab.com/install/?version=ce

The first two links miss the idea a bit, I'd say. I don't often need a web interface to a git repo. I can pull and do everything locally. What I do use GitHub for is (1) code review and approval process, (2) CICD / actions, (3) releases to push stuff out. The branch / tag / file browser is a nice addition, but it's not key. Rendering README.md is almost as important, if not more.

Gitea has a lot of those features already: https://docs.gitea.io/en-us/comparison/

Issues with a green 'X' means they link to a feature on their issue tracker.

And, as far as I know, they are working on integrating CI/CD right now. They already have support for other non-integrated CI/CD platforms: https://docs.gitea.io/en-us/ci-cd/

Re: GitHub was down again

#112

Post by emilfihlman » Wed, Jul 15, 2020, 7:30 PM UTC

arilotter wrote: post #13

I was seeing PRs failing to update & webhooks failing to trigger upon pushing code for 30 minutes before GH's status page acknowledged anything. I'm surprised they don't have monitoring in place that would catch webhooks failing within minutes of the failure beginning.

That's the way it is _everywhere_.

For example status.digitalocean.com is _not_ real time, it's manually updated.

And it's irritating as fuck.

Re: GitHub was down again

#113

Post by ThA0x2 » Wed, Jul 15, 2020, 7:32 PM UTC

I hope this is because someone/somethey/someotherkin decided to rename the racist, sexist, homophobic, transphobic, white word "master" to "main" somewhere in the codebase.

Re: GitHub was down again

#114

Post by non-entity » Wed, Jul 15, 2020, 7:35 PM UTC

ThA0x2 wrote: post #113

I hope this is because someone/somethey/someotherkin decided to rename the racist, sexist, homophobic, transphobic, white word "master" to "main" somewhere in the codebase.

> Eschew flamebait. Don't introduce flamewar topics unless you have something genuinely new to say. Avoid unrelated controversies and generic tangents.

https://news.ycombinator.com/newsguidelines.html

Re: GitHub was down again

#115

Post by NoobTW » Wed, Jul 15, 2020, 7:39 PM UTC

mlang23 wrote: post #102

Likely unrelated, but I recently noticed that GitHub stopped updating my activities overview for july. I definitely pushed commits, but they are not noticed. Anyone else having a similar issue?

Are you pushing to master branch?

Re: GitHub was down again

#116

Post by neurostimulant » Wed, Jul 15, 2020, 7:49 PM UTC

So that's why my automated build wasn't triggered ~4 hours ago. I was like "no way github is having issues again, they were down just the other day, it's probably just docker hub's fault". If they decided to publish a blog post about these series of outages later, I bet it would be pretty interesting.

Re: GitHub was down again

#117

Post by neurostimulant » Wed, Jul 15, 2020, 8:09 PM UTC

jkaplowitz wrote: post #22

cameronfraser wrote: post #16

Why is outage history pre-acquisition removed from their history? If you try to go back in time it seems they only retain history up to a couple months after the acquisition. Is this just a 2 year retention policy or something being swept under the rug?

I have never worked at Github or MS and have no inside info on this, but it may be as simple as having switched to a MS-run system for outage history tracking as part of their own M&A integration.

I think they switched to Atlassian StatusPage[1] a while ago.

[1] https://www.atlassian.com/software/statuspage

Re: GitHub was down again

#118

Post by neurostimulant » Wed, Jul 15, 2020, 8:18 PM UTC

marcinzm wrote: post #19

How is GitLab like in terms of downtime? I looked at their status history page and I'm seeing a lot of incidents but it's hard to figure out what it actually means.

Gitlab used to have more outages than github, but these days they're about the same or even better than github. Also, they're really transparent about handling outages. They post link directly to the issue page in their status page so you see all those gitlab employees frantically trying to restore the service. I was pretty mad when they were having the last outage because I can't finish my work, but after checking the issue page and seeing how hard they work, I felt bad and decided to cut them some slack :)

Re: GitHub was down again

#119

Post by may4m » Wed, Jul 15, 2020, 8:36 PM UTC

I had a problem with github a while ago when I tried merging a PR to the master branch, the merge commits reflected on master but the PR was still open.I would repeatedly click the merge button but the PR wouldn't show as merged

Re: GitHub was down again

#120

Post by 0xy » Wed, Jul 15, 2020, 9:19 PM UTC

ShorsHammer wrote: post #95

niftylettuce wrote: post #58

There have been at least three major outages, e.g. git clone of a repo, in the past week alone. All three of which have been unreported (and NOT shown on their incident page), but I have email confirmation from GitHub support of these issues. It's almost time to switch to Gitlab. I have hundreds of repositories, organizations, and packages to transfer, while it will be daunting... I need reliability. I have several p…

To be fair they've been busy fixing the issue of slavery nomenclature in that time too. Respect where respect is due, important issues are being tackled here, you can't do everything at once. https://twitter.com/natfriedman/status/1271253144442253312

Hilarious. GitHub has their fingers on the pulse of what developers and their customers really want. Not stability, but pretending to do things to help POCs through mindless censorship.