Live data from Hacker News

GitHub Incident

githubstatus.com

21–30 of 99 posts

Re: GitHub Incident

#21
post #14

Perhaps the gemini-cli bot arguing with itself is taking its toll https://github.com/google-gemini/gemini-cli/issues/16750

Jeez, what a mess. Some of those issues have over 5000 events on them.

I really hope that didn't send emails out to people.

Re: GitHub Incident

#22
post #14

Perhaps the gemini-cli bot arguing with itself is taking its toll https://github.com/google-gemini/gemini-cli/issues/16750

Haha, reminds me off bringing down office mail servers by accidentally creating loops of emails back in the day... What is old is new again, but this time with probabilities :)

Re: GitHub Incident

#23
post #11

Github's recent reliability has honestly been abysmal. Not surprised.

Unless some major customers are moving away, I don't think they are going to seriously care about it.

I suspect some companies may already be considering it. Especially with the wealth of alternatives today.

Re: GitHub Incident

#25
post #8

helm repo add gitlab https://charts.gitlab.io/ && helm upgrade --install gitlab gitlab/gitlab I did this in 2019, it avoided so many headaches. CI is better too since there's a nice clean mapping of build -> pod for everything and I can just exec in if something's borked.

Things would have to get really bad before I considered managing my own repositories. Trading someone else's headaches for my own.

^ this. the last thing i want is to add to my workload. take my money and make my life easier, even if it means that for one hour every couple months i can't do anything

Re: GitHub Incident

#26
Fixed in about 30m to an hour.

Definitely annoying, but I'll try the hot take that, contrary to popular belief, GH is not critical infrastructure - or so I hope.

Please tell me no part of the Ukrainian air defense system depends on a gh action hook.

Re: GitHub Incident

#27
post #14

Perhaps the gemini-cli bot arguing with itself is taking its toll https://github.com/google-gemini/gemini-cli/issues/16750

I could not resist to put my sarcastic comment about RAM price increases serving a good cause in there.

Re: GitHub Incident

#29
post #8

helm repo add gitlab https://charts.gitlab.io/ && helm upgrade --install gitlab gitlab/gitlab I did this in 2019, it avoided so many headaches. CI is better too since there's a nice clean mapping of build -> pod for everything and I can just exec in if something's borked.

Things would have to get really bad before I considered managing my own repositories. Trading someone else's headaches for my own.

It's not as bad as you think, I run the helm upgrade when patches come out, the backing store is S3 or managed SQL, it runs a nightly k8s cron called gitlab-backup which tarballs the whole thing into an s3 bucket with a single command restore should disaster strike. (This is part of the product, not a thing I wrote.)

I probably only babysit it for 30 minutes per year, including all the upgrades.

Re: GitHub Incident

#30

Fixed in about 30m to an hour. Definitely annoying, but I'll try the hot take that, contrary to popular belief, GH is not critical infrastructure - or so I hope. Please tell me no part of the Ukrainian air defense system depends on a gh action hook.

You've heard of infrastructure as code, now presenting air strikes as code!

Need a new secret offensive operation? Create a new JSON file with the coordinates, make a merge request and get Commander approval, merge it, and our new proprietary GitHub action runner will deploy a drone in seconds!

Post reply on HN