Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub incident: 2022/03/24

githubstatus.com

Post reply on HN
Print view View original

51–60 of 103 posts

Re: GitHub incident: 2022/03/24

#51

Post by hwbehrens »

danogentili wrote: post #44
AndrewOMartin wrote: post #37

What we need is some kind of distributed version control system, then this would never happen. Ideally it'd be a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency, but I think that's just unrealistic.

My irony meter is currently down for maintenance, but that's precisely what git is, a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency :)

My meter was working perfectly until I read the parent comment, at which point it measured off the scale and promptly broke.

Re: GitHub incident: 2022/03/24

#52

Post by oneepic »

nimbius wrote: post #10

https://www.githubstatus.com/ at the time of posting, webhooks and actions are still struggling :( there have now been 23 incident outages in 90 days. if anyone from Microsoft is reading this, you need to start considering this degradation as the companies highest priority. At this point, Gitea, Gitlab and others (self hosted or otherwise) are beginning to gain traction as a more reliable and performant alternative.…

Did you see the following post? I can't prove the underlying issue caused this issue but I'd wager it's likely. And I'd wager they ARE prioritizing this. https://github.blog/2022-03-23-an-update-on-recent-service-d...

Re: GitHub incident: 2022/03/24

#54

Post by groby_b »

danogentili wrote: post #44
AndrewOMartin wrote: post #37

What we need is some kind of distributed version control system, then this would never happen. Ideally it'd be a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency, but I think that's just unrealistic.

My irony meter is currently down for maintenance, but that's precisely what git is, a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency :)

Can't be git they're talking about, they mentioned speed and efficiency for very large projects.

Re: GitHub incident: 2022/03/24

#55

Post by pzduniak »

iratewizard wrote: post #19
awill wrote: post #12

Earlier quoted context omitted.

Isn't that basically what happened to Skype? Microsoft paid $8.5B for Skype when it was on top of the world, and now I don't know a single person who uses it.

They got patent trolled and flinched. They removed the things that made Skype best in class and turned it into just another low quality corporate messenger.

Was it really due to that lawsuit? IIRC the main issue with P2P was that you could discover anyone's IP address by knowing their Skype username. I recall that people used this to DoS people in multiplayer video games - they looked up accounts with roughly the same name as the in-game one and proceeded to drop their connection. It was especially common in League of Legends.

Re: GitHub incident: 2022/03/24

#56

Post by danogentili »

phphphphp wrote: post #15
raybb wrote: post #5

How does GitLab compare in terms of it's CI/CD reliability?

I’m a big fan of GitHub Actions so take this with that in mind. GitLab (self-hosted) is very reliable however GitLab CI/CD is very different in design to GitHub Actions: it’s much more a bunch of shell scripts stuck together with YAML. Personally, I’d never go back (unless they redesign it).

Personally, I hate Github Actions from the bottom of my heart.

Ever since Travis CI sold its soul and I've been forced to use Github Actions, and I've come to hate every single moment I have to work with some broken or buggy action, with the inability to restart only failed jobs (they added this vital feature only a few weeks ago, 2+ years after launching actions), with slow job spin-up times, which are only slightly reduced when using the self-hosted, RAM-hogging action runners which are only capable of running one job per instance, forcing me to waste RAM setting up multiple instances of the runners, each bundling its own copy of node and the .NET runtime.

I've been using gitlab CI @ work, and I absolutely love its reliability and ease of use and configuration.

Re: GitHub incident: 2022/03/24

#57

Post by dharmab »

groby_b wrote: post #54
danogentili wrote: post #44

Earlier quoted context omitted.

My irony meter is currently down for maintenance, but that's precisely what git is, a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency :)

Can't be git they're talking about, they mentioned speed and efficiency for very large projects.

Ironically, Microsoft has been a major contributor to improvements in git for handling large repos after Windows was migrated to git.

https://github.com/microsoft/git

Re: GitHub incident: 2022/03/24

#58

Post by meibo »

floodle wrote: post #53
Cthulhu_ wrote: post #29

Earlier quoted context omitted.

Name one service with as many users, traffic, and features that doesn't have any issues.

GitHub before Microsoft?

GitHub before Microsoft notoriously shied away from innovating/iterating on their core business for years. We had half as many features before then.

IMO feature wise, GitHub really has improved tenfold. I remember having to fight third party CIs and project trackers, now we're running them all on GitHub and it's a well-integrated pleasure. If it does work, which it usually does and hopefully goes back to doing.

I also really enjoy their live vscode IDE, which lets you e.g. make small changes to PRs in a web vscode by pressing . on the PR page. This is different from their hosted VM offering and free, confusingly.

Re: GitHub incident: 2022/03/24

#59

Post by [deleted] »

AndrewOMartin wrote: post #37

What we need is some kind of distributed version control system, then this would never happen. Ideally it'd be a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency, but I think that's just unrealistic.

[deleted]

Re: GitHub incident: 2022/03/24

#60

Post by [deleted] »

nimbius wrote: post #10

https://www.githubstatus.com/ at the time of posting, webhooks and actions are still struggling :( there have now been 23 incident outages in 90 days. if anyone from Microsoft is reading this, you need to start considering this degradation as the companies highest priority. At this point, Gitea, Gitlab and others (self hosted or otherwise) are beginning to gain traction as a more reliable and performant alternative.…

[deleted]
Post reply on HN