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

251–260 of 298 posts

Re: Another GitHub outage in the same day

#251

Post by tosti »

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…

Why does it trigger a usage limit whenever I search anything at all? Sometimes I can get through but when I go back one page, boom error.

Re: Another GitHub outage in the same day

#252

Post by Akronymus »

tosti wrote: post #251
matthewisabel wrote: post #135

Earlier quoted context omitted.

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…

Why does it trigger a usage limit whenever I search anything at all? Sometimes I can get through but when I go back one page, boom error.

Oh I assumed that was just me/because of a linux OS.

Re: Another GitHub outage in the same day

#253

Post by agos »

tazjin wrote: post #131
bigbuppo wrote: post #94

Earlier quoted context omitted.

Not going to happen. This is terminal decline. Next step is to kill off free repos, and then they'll start ratcheting up the price to the point that they have one small dedicated engineering team supporting each customer they have. They will have exactly one customer. At some point they'll end up owned by Broadcom, OpenText, Rocket, or Progress.

Killing off free repos is not going to happen. That would be a suicide move on the level of the Digg redesign, or Tumblr's porn ban. It kind of would be good for everyone if they did do it though. Need to get rid of this monopoly, and maybe people will discover that there are alternatives with actually good workflows out there.

it would indeed be a suicide move, but note that you are comparing that to two moves that have happened, so it's not unprecedented.

Re: Another GitHub outage in the same day

#254

Post by Skwid »

OkayPhysicist wrote: post #125
zero_shift wrote: post #23

Earlier quoted context omitted.

As an aside, God, Azure DevOps, what a total pile of crap that product is My "favourite" restriction that an Azure DevOps PR description is limited to a pathetic 4000 characters.

My favourite restriction is the fact that colored text doesn't work in dark mode. Why? Because whatever intern they had implement dark mode didn't understand how CSS works, and just slapped !important on all the style changes that make dark mode dark, and thus overwrite the color data. I ended up writing a browser extension for my team to fix it, because the boss loved to indicate stuff with red/green text.

When I last had the misfortune of using devops copy and pasting text from a work item would take the background colour with it, though not the text colour. Colleages in dark mode would rearrange some sentences, and I'd be left with black text on almost black background.

Genuinely baffling incompetence

Re: Another GitHub outage in the same day

#255

Post by captn3m0 »

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…

GitHub used jQuery + pjax to do exactly this a decade ago - rendered HTML for smaller components was fetched and replaced in-place with a single DOM update. It even had fancy sliding transitions.

Re: Another GitHub outage in the same day

#256

Post by palata »

tosti wrote: post #241
habitable5 wrote: post #225

Earlier quoted context omitted.

Peter Thiel. Evil incarnate and the next president of the United States you've never heard of. Vance is his sock puppet, he was chosen because he is guaranteed not to have a single independent thought so when Trump croaks Thiel will be the president in all but name. It was also he who willed OpenAI to be in order to help destroying American democracy.

IDK what you're smoking, but he was born in Germany so can't be the next potus.

> IDK what you're smoking

Or maybe it's a problem with your English? (Note: I'm being offensive just because you are :-) ).

> when Trump croaks Thiel will be the president in all but name.

This means that he will have the power, but not the title.

Re: Another GitHub outage in the same day

#259

Post by johnisgood »

its_magic wrote: post #107
heliumtera wrote: post #95

Earlier quoted context omitted.

Then why is it the future we have?

It was a complete accident. Nobody could have foreseen it. We are currently experiencing the sudden discovery that Microsoft is an evil corporation and maybe putting everything in the cloud wasn't the best move after all.

Some people, sure. I never thought that putting everything in the cloud is the best move, but I guess N=1.

In fact I was shocked to see that so many allegedly tech-literate people were so blindly pro-cloud (and they still are).

Re: Another GitHub outage in the same day

#260

Post by Etheryte »

ibrahima wrote: post #238
matthewisabel wrote: post #145

Earlier quoted context omitted.

Yes agreed it's been a huge problem, and we shipped changes last week to address some of the gnarly p99 interactions. It doesn't fix everything and large PRs have a lot of room to be faster. It's still good to know where some worst performance issues are to see if there's anything particularly problematic or if a future change will help.

FWIW, I find the new React-based diff viewer worse than the old server-rendered page. I disabled the preview for this reason. It does have some nice features but overall it feels more finicky. I would think that in theory this should be better at handling large diffs but I'm not sure that that's the case, and at least the UX feels more choppy.

That's financialization at play. When you render and syntax highlight the diff on the server, Github pays the cost, if you do it on the client side, the cost is paid by the client. At Github's scale it's probably a large enough of a difference that they decided the reduced customer experience is worth it.
Post reply on HN