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

Another GitHub outage in the same day

githubstatus.com

Post reply on HN
Print view View original

191–200 of 298 posts

Re: Another GitHub outage in the same day

#191

Post by hunterpayne »

danudey wrote: post #151
dev_l1x_be wrote: post #136

Earlier quoted context omitted.

Good to know. So it only causes the UI inconsistency bugs.

The new design/architecture allows them to do great stuff in the name of efficiency; for example, when browsing through some parts of the UI, it's now much more capable of just updating the part of the page that's changed, rather than having to reload the entire thing. This is a significantly better approach for a lot of things. I understand that the 'updating the part of the page that's changed' functionality is now…

> for example, when browsing through some parts of the UI

React allows this? I didn't realize that I needed React to do this when we used Java and Js to do this 20 years ago. I also didn't realize I needed React to do this when we used Scala and generated Js to do this 10 years ago. JFC, the world didn't start when you turned 18.

Re: Another GitHub outage in the same day

#192

Post by multisport »

kevmo314 wrote: post #12

I wonder if GitHub is feeling the crush of fully automated development workflows? Must be a crazy number of commits now to personal repos that will never convert to paid orgs.

No, its because they are in the middle of a AWS->Azure migration, and because they cannot/will not be held accountable for downtime.

Re: Another GitHub outage in the same day

#193

Post by dizhn »

adamcharnock wrote: post #82
Kovah wrote: post #20

I consider moving away from Github, but I need a solid CI solution, and ideally a container registry as well. Would totally pay for a solution that just works . Any good recommendations?

We can run a Forgejo instance for you with Firecracker VM runners on bare metal. We can also support it and provide an SLA. We're running it internally and it is very solid. We're running the runners on bare metal, with a whole lot of large CI/CD jobs (mostly Rust compilation). The down side is that the starting price is kinda high, so the math probably only works out if you also have a number of other workloads to r…

You've got any docs for firecracker as forgejo runners?

Re: Another GitHub outage in the same day

#194

Post by endgame »

its_magic wrote: post #105
amarant wrote: post #73

Earlier quoted context omitted.

Not quite everywhere. There's a common denominator for all of those: Microsoft. Their business is buying good products and turning them into shit, while wringing every cent they can out of the business. Always has been. They have a grace period of about 2-4 years after acquisition where interference is minimal. Then it ramps up. How long a product can survive once the interference begins largely depends on how good s…

I for one am shocked--SHOCKED, I say!--to learn that anything bad could happen as a result of a) putting everything in "the cloud" and b) handing control over the entire world's source code to the likes of Microsoft. Who could have POSSIBLY foreseen any kind of dire consequences?

Nobody. Nobody at all could have seen it. Microsoft is cool now, haven't you seen VSCode? They do Open Source, they run Linux, they've joined the fold, the tiger shed its stripes.

Re: Another GitHub outage in the same day

#196

Post by dham »

catigula wrote: post #116
dev_l1x_be wrote: post #110

Earlier quoted context omitted.

So React rewrite did not help after all? Imagine, one of the largest software tool companies on Earth cannot reliably REbuild something in React. I lost count of the inconsistency issues React introduced. https://news.ycombinator.com/item?id=33576722

React isn't causing these issues.

Then why is the site slower than it was in 2012 on a 2009 Macbook?

Re: Another GitHub outage in the same day

#197

Post by tjwebbnorfolk »

tayo42 wrote: post #190
danudey wrote: post #141

Earlier quoted context omitted.

For what it's worth, I doubt that people think it's the engineering teams that are the problem; it feels as though leadership just doesn't give a crap about it, because, after all, if you have a captive audience you can do whatever you want. (See also: Windows, Internet Explorer, ActiveX, etc. for how that turned out) It's great that you're working on improving the product, but the (maybe cynical) view that I've hear…

> people think it's the engineering teams that are the problem; It could be, some people are just terrible at their job. Lots of teams have low quality standards for their work. Maybe that still comes down to leaders but for different reasons. You can ship useless features without downtime.

Permitting terrible engineers to continue to work for you is a management problem.

Re: Another GitHub outage in the same day

#198

Post by bigstrat2003 »

ChrisArchitect wrote: post #123
esafak wrote: post #96

Earlier quoted context omitted.

No, it's a new outage -- that's the point! Check the URLs.

That's not the point. The point is it's a duplicate discussion of one of a number of incident links being discussed, all over there.

The point is that when a second, independent event occurs, a new thread is not a duplicate.

Re: Another GitHub outage in the same day

#199

Post by whstl »

matthewisabel wrote: post #135
sobjornstad wrote: post #8

Earlier quoted context omitted.

I second this. GitHub used to be a fantastic product. Now it barely even works. Even basic functionality like the timeline updating when I push commits is unreliable. The other day I opened a PR diff (not even a particularly large one) and it took fully 15 seconds after the page visually finished loading -- on a $2,000 dev machine -- before any UI elements became clickable. This happened repeatedly. It is fairly stun…

Hey from the GitHub team. Outages like this are incredibly painful and we'll share a post-mortem once our investigation is complete. It stings to have this happen as we're putting a lot of effort specifically into the core product, growing teams like Actions and increasing performance-focused initiatives on key areas like pull requests where we're already making solid progress[1]. Would love if you would reach out to…

It's insulting to see the word "progress" being used when the PR experience is orders of magnitude slower than it was years ago, when everyone had way worse computers. I have a maxed M5 MacBook and sometimes I can barely review some PRs.

Re: Another GitHub outage in the same day

#200

Post by natas »

This is exactly why my employer is unlikely to adopt Azure. When CoreAI assets like GitHub appear poorly managed, it undermines confidence in the rest of the ecosystem. It’s unfortunate, because Microsoft seems to overlook how strongly consumer experience shapes business perception. Once trust is damaged, no amount of advertising spend can fully restore it.
Post reply on HN