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

Disruption with Some GitHub Services – Resolved

githubstatus.com

Post reply on HN
Print view View original

121–130 of 176 posts

Re: Disruption with Some GitHub Services – Resolved

#121

Post by embedding-shape »

jmb99 wrote: post #119
embedding-shape wrote: post #106

Earlier quoted context omitted.

Another useful disclaimer: all of these lets the developers push updates to your computer as they wish by default in most setups, these days you might want to decrease that kind of attack surface and just check the status in the official website when "git push" suddenly stop working. Especially when extensions and stuff sometimes changes hand and it's kind of hard to keep track of it, except for when something bad ha…

Well, the alternatives are: > It would be really cool if someone built an extension to show GitHub status live "These already exist, why wouldn't you search before posting?" > There exist quite a few extensions to show live GitHub status "Why would you not post them if you know they exist?" Or, what actually happened: > Here are some extensions that might work for you to show live GitHub status "Why would you recomme…

> "Why would you recommend extensions to do this?"

This is not my complaint though, my complain is:

Why would you recommend extensions you haven't tried nor even read about yourself?

The goal isn't to pick apart the message to piss someone off, the goal is prevent someone else than the author from getting hacked because they install some random extension, not understanding what kind of access you're giving others when doing so.

Re: Disruption with Some GitHub Services – Resolved

#122

Post by creshal »

pocksuppet wrote: post #86
zaik wrote: post #52

Earlier quoted context omitted.

I think the authors of SMTP had a healthy attitude towards server uptimes: Retries continue until the message is transmitted or the sender gives up; the give-up time generally needs to be at least 4-5 days. https://datatracker.ietf.org/doc/html/rfc5321#section-4.5.4....

At the time, most email was either local to the host (big mainframe in the basement) or transferred once a day through scheduled dial-up connections during off-peak phone hours

Which is a good fit to a distributed, offline first version control system, if you use it like that.

Re: Disruption with Some GitHub Services – Resolved

#123

Post by creshal »

herpdyderp wrote: post #84
saxonww wrote: post #29

Earlier quoted context omitted.

They have that-ish as an option: https://docs.github.com/en/enterprise-cloud@latest/admin/dat... I'm told that GitHub has asserted to us that moving to this model means we would not be exposed to github.com outages. It's not at feature parity with github.com though.

Do you have any meaningful level of faith in GitHub's ability to deliver on stability? At this point, I have none.

A lot of the stability problems come from trying to scale a free product on a still WIP cloud solution without costing too much; the same software running on separate, paid for infra has a lot better odds.

Re: Disruption with Some GitHub Services – Resolved

#124

Post by slices »

shepardrtc wrote: post #44

Fun read about Azure and having 173 agents running a node: https://isolveproblems.substack.com/p/how-microsoft-vaporize... Probably just a coincidence that Github started to have issues after beginning their move to Azure at the end of last year.

"fun"

I thought I was cynical enough about goings on at Microsoft / Azure, but apparently not.

Re: Disruption with Some GitHub Services – Resolved

#125

Post by rglover »

Good. Now everyone is getting to see what over-investment in complexity nets you. This bad of reliability screams "tangled spaghetti shit show" behind the scenes.

It's a shame that this is happening and hopefully Microsoft do the right thing and spin it back off into a private entity with its own leadership and resources.

Also, self-serving: this is why the whole "big company means better" thing is bs. We need to aggressively go back to a culture that rewards and supports independent teams who actually give a damn about what they're building and responsible for. Otherwise, this is just a preview of everything everywhere in a few years.

Re: Disruption with Some GitHub Services – Resolved

#126

Post by sandermvanvliet »

frenchie4111 wrote: post #11

I noticed earlier this week that my URL bar now pre-fills githubstatus.com instead of github.com when I type "gith"

As a joke I built an extension to the GitHub CLI called “omens” so you can run “gh omens” before you’re planning to use GitHub and it’ll tell you if it’s likely to work in idiomatic Aussie.

As an example:

$> gh omens

reckon github's about to go full bin chicken

—-

You can find it here: https://github.com/sandermvanvliet-stack/gh-omens

Re: Disruption with Some GitHub Services – Resolved

#127

Post by NewJazz »

Melatonic wrote: post #111
roastedfunction wrote: post #54

Earlier quoted context omitted.

“GitHub Enterprise Cloud with data residency” is hosted on separate infrastructure and dedicated subdomains under *.ghe.com. It’s been around since November 2024z It’s not the same thing as GitHub Enterprise Cloud hosted on the shared global network on github.com. https://docs.github.com/en/enterprise-cloud@latest/admin/dat...

So confusing and so Microsoft. They love to have licensing so complicated their own sales people aren't up to date and have to rely on third party spreadsheets. Edit: Read that document - why do more people not do the self hosted option with GitHub Enterprise Server ?

At the point you are self hosting, you have many more options ranging from a simple ssh git server with pick your favorite cicd, to gitlab ce, to forgejo, and more.

Re: Disruption with Some GitHub Services – Resolved

#128

Post by rglover »

firatsarlar wrote: post #95

Scaling is a dream or theory we think we solved. Distance between ... to practice. So ... should be reconsidered again.

This level of scale is extreme but it can be handled with proper time investment and careful engineering.

But that doesn't fit into the "spend gobs of money as fast as possible so you can be a hypothetical feudal lord in a sci-fi dystopia novel you read when you were twelve" line of thinking.

Re: Disruption with Some GitHub Services – Resolved

#129

Post by saxonww »

nr378 wrote: post #67
saxonww wrote: post #29

Earlier quoted context omitted.

They have that-ish as an option: https://docs.github.com/en/enterprise-cloud@latest/admin/dat... I'm told that GitHub has asserted to us that moving to this model means we would not be exposed to github.com outages. It's not at feature parity with github.com though.

Thanks, this option is good to know. We're currently on "GitHub Enterprise Cloud" on github.com and are affected by this outage (even though we use self-hosted runners!), but we're not on "GitHub Enterprise Cloud with data residency" on *.ghe.com, which I understand is/may not be affected by this outage?

This is what they've told us. It's represented as basically a separate deployment of the entire GHEC stack, so you're not exposed to the load/scaling issues they believe are the underlying cause of all the github.com outages today.

Re: Disruption with Some GitHub Services – Resolved

#130

Post by NewJazz »

roncesvalles wrote: post #120
pydry wrote: post #98

Earlier quoted context omitted.

realistically the problem is vibe coding.

The problem is when you stuff your codebase with so much unreviewed vibecoded slop that engineers lose their grasp on how it all works.

Keep pulling the lever, uptime has to improve eventually!
Post reply on HN