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

141–150 of 298 posts

Re: Another GitHub outage in the same day

#141

Post by danudey »

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…

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 heard more than anything is that when faced with the choice of improving the core product that everyone wants and needs or adding functionality to the core product that no one wants or needs and which is actively making the product worse (e.g. PR slop), management is too focused on the latter.

What GitHub needs is a leader who is willing and able to say no to the forces enshittifying the product with crap like Copilot, but GitHub has become a subsidiary of Copilot instead and that doesn't bode well.

Re: Another GitHub outage in the same day

#142

Post by amarant »

Andrex wrote: post #102
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…

Things don't always ramp up after 2-4 years. Sometimes MS just kills the project or company after that period of time. See also their moves in the gaming industry.

Heh, I was working at 2 of those gaming companies when they were acquired by m$. I almost fear taking another job in the gaming industry, there seems to be some kind of bastardised version of Murphy's law that any gaming company that hires me will be acquired by ms 6 months later.

I mean, that's obviously not the case, but it's weird that it happened twice!

Re: Another GitHub outage in the same day

#143

Post by h4kunamata »

GitLab is the solution, if you aren't on it already.

I worked for one of Australia largest airline company, monthly meeting with Github team resumed in one word: AI

There is zero focus into the actual platform as we knew it, it is all AI, Copilot, more AI and more Copilot.

If you are expecting things to get better, I have bad news for you. Copilot is not being adopted by companies as they hoped, they are using Claude themselves. If Microsoft ever rollback, boy oh boy, things will get ugly.

Re: Another GitHub outage in the same day

#144

Post by monkaiju »

dec0dedab0de wrote: post #111

I still say that mixing CI/CD with code/version control hosting is a mistake. At it's absolute best, everything just works silently, and you now have vendor lock-in with whichever proprietary system you chose. Switching git hosting providers should be as easy as changing your remotes and pushing. Though now a days that requires finding solutions for the MR/PR process, and the wiki, and all the extra things your team…

I mean, not necessarily proprietary right? There are OSS solutions like forgejo that make it pretty simple, at least as simple as running a git system and a standalone CI system

Re: Another GitHub outage in the same day

#145

Post by matthewisabel »

Etheryte wrote: post #139
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…

Literally everyone who has used Github to look at a pull request in say the last year has experienced the ridiculous performance issues. It's a constant laughing point on HN at this point. There is no way you don't know this. Inviting to take this to a private channel, along with the rest of your comment really, is simply standard corporate PR.

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.

Re: Another GitHub outage in the same day

#146

Post by Wojtkie »

noodlesUK wrote: post #3

Can someone in GitHub senior leadership please start paying attention and reprioritise towards actually delivering a product that's at least relatively reliable? I moved my company over to GH enterprise last year (from AzDO) and I'm considering moving us away to another vendor altogether as a result of the constant partial outages. Things that used to "just work" now are slow in the UI, and GH actions fail to schedul…

My org just moved to Gitlab because of the GH actions problems.

Re: Another GitHub outage in the same day

#147

Post by [deleted] »

h4kunamata wrote: post #143

GitLab is the solution, if you aren't on it already. I worked for one of Australia largest airline company, monthly meeting with Github team resumed in one word: AI There is zero focus into the actual platform as we knew it, it is all AI, Copilot, more AI and more Copilot. If you are expecting things to get better, I have bad news for you. Copilot is not being adopted by companies as they hoped, they are using Claude…

[deleted]

Re: Another GitHub outage in the same day

#148

Post by monkaiju »

sisve wrote: post #129

I moved everything on github to a self hosted foregjo instanse some days ago. I really did not do anything. Created some tokens so that CC could access github and forgejo and my dns API. Self hosting is so much simpler and easier with AI. Expect more people to self host small to medium stuff.

Ironic that that same AI you're mentioning is probably a large part of why this class of outages are increasing. Id highly recommend folks understand their infrastructure enough to setup/run it without AI before they put anything critical on it.

Re: Another GitHub outage in the same day

#149

Post by macintux »

nfg wrote: post #121
kasey_junk wrote: post #5

Earlier quoted context omitted.

“ I enjoy GH copilot as much as the next person” So not at all?

Really? I’d be interested to hear more. Disclaimer: I work in Microsoft (albeit in a quite disconnected part of it, nothing to do with GitHub or Copilot).

I’ve only started using it, so maybe I’m holding it wrong, but the other day I asked the IntelliJ plugin to explained two lines of code by referencing the line numbers. It printed & explained two entirely different lines in a different part of the file. I asked again. It picked two lines somewhere else.

After using ChatGPT for the last 6 months or so, Copilot feels like a significant downgrade. On the other hand, it did easily diagnose a build failure I was having, so it’s not useless, just not as helpful.

Post reply on HN