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

Days since last GitHub incident

github-incidents.pages.dev

Post reply on HN
Print view View original

21–30 of 142 posts

Re: Days since last GitHub incident

#21

Post by Croftengea »

behnamoh wrote: post #14
blibble wrote: post #10

Earlier quoted context omitted.

because Microsoft are known for listening to their customers? this trivial bug fix took more than a year to be merged: https://github.com/actions/runner/pull/3157 that bug likely ended up costing customers millions

Why is Microsoft supposed to listen? I'm not happy with them either but I understand their shift in business strategy. So many people here treat github like it's a utility; it's not. If you're not happy with it, move on to alternatives or make your own version.

Genuinely curios, what shift?

Re: Days since last GitHub incident

#22

Post by NewJazz »

behnamoh wrote: post #14
blibble wrote: post #10

Earlier quoted context omitted.

because Microsoft are known for listening to their customers? this trivial bug fix took more than a year to be merged: https://github.com/actions/runner/pull/3157 that bug likely ended up costing customers millions

Why is Microsoft supposed to listen? I'm not happy with them either but I understand their shift in business strategy. So many people here treat github like it's a utility; it's not. If you're not happy with it, move on to alternatives or make your own version.

The decision makers about what software forge to use are often not the same folks using the software forge.

Re: Days since last GitHub incident

#23

Post by hiccuphippo »

blibble wrote: post #10
behnamoh wrote: post #5

[flagged]

because Microsoft are known for listening to their customers? this trivial bug fix took more than a year to be merged: https://github.com/actions/runner/pull/3157 that bug likely ended up costing customers millions

Woah, they actually fixed it? I mean, they are still using a poor man's sleep that uses up a core in the CPU instead of just using sleep, but progress!

Re: Days since last GitHub incident

#25

Post by toastal »

This is why I keep encouraging folks to a) have a mirror & b) make sure their tools automatically pick up the mirrors.

I recently got mirror support upstreamed into Nixpkgs for fetchdarcs & fetchpijul which actually work on my just-alpha-released pinning tool, Nixtamal https://darcs.toastal.in.th/nixtamal/trunk/README.rst>, for just this sort of thing.

Re: Days since last GitHub incident

#26

Post by blahyawnblah »

llbbdd wrote: post #6
behnamoh wrote: post #5

[flagged]

I don't work at Github but I'd read here recently that they've been undergoing a herculean migration from whichever cloud provider they were on to Azure since their Microsoft acquisition, and that it coincides with an increase in outages. I'm guessing that the solution here was probably just to not do that and it's too late.

Yes I would image the issues are due to doing a migration period. Not the fact that it's moving to Azure in and of itself.

Re: Days since last GitHub incident

#27

Post by bastardoperator »

llbbdd wrote: post #16

I've gotten accustomed lately to spending a lot of time in the Github Copilot / agent management page. In particular I've been having a lot of fun using agents to browse some of my decade-old throwaway projects; telling it to "setup playwright, write some tests, record screenshots/videos and commit them to the repo" works every time and it's a great way to browse memory lane without spending my own time getting some…

They do, it's called GHES.

https://docs.github.com/en/enterprise-server@3.19/admin/over...

"GitHub Enterprise Server is a self-hosted version of the GitHub platform"

Re: Days since last GitHub incident

#28

Post by tracker1 »

behnamoh wrote: post #14
blibble wrote: post #10

Earlier quoted context omitted.

because Microsoft are known for listening to their customers? this trivial bug fix took more than a year to be merged: https://github.com/actions/runner/pull/3157 that bug likely ended up costing customers millions

Why is Microsoft supposed to listen? I'm not happy with them either but I understand their shift in business strategy. So many people here treat github like it's a utility; it's not. If you're not happy with it, move on to alternatives or make your own version.

Largely, because they want money from people. If you are in a business selling a product or service and you don't at least pay some attention to what customers are calling for, then you're likely to eventually fall flat no matter how big you are.

Of course IBM and Oracle still exist, so who knows.

Re: Days since last GitHub incident

#29

Post by Tade0 »

ZeroConcerns wrote: post #11

This is a bit... low-effort, isn't it? I'd at least expect a video of an exasperated Github user walking up to the '# days since the last GitHub incident' board, sliding out the '1' or '2' card, and replacing it with a '0'. I mean, that joke is as old as the universe (heck, in the brief period that I worked in an office, decades ago, I had a "# days since the last person asked a stupid question" sign to enact the exa…

I was half-expecting the "days since last" meme - the one with a person smiling awkwardly while clapping with a large four-digit counter in the background showing only zeroes.

Re: Days since last GitHub incident

#30

Post by ModernMech »

bastardoperator wrote: post #27
llbbdd wrote: post #16

I've gotten accustomed lately to spending a lot of time in the Github Copilot / agent management page. In particular I've been having a lot of fun using agents to browse some of my decade-old throwaway projects; telling it to "setup playwright, write some tests, record screenshots/videos and commit them to the repo" works every time and it's a great way to browse memory lane without spending my own time getting some…

They do, it's called GHES. https://docs.github.com/en/enterprise-server@3.19/admin/over... "GitHub Enterprise Server is a self-hosted version of the GitHub platform"

I've tried getting this set up at my University, it was hell dealing with them. We ended up going with Gitlab.
Post reply on HN