I should make a business selling git hosting. Apparently it's really easy because it doesn't have to actually work.
Sure but first you gotta be Microsoft.
Disruption with Some GitHub Services – Resolved
81–90 of 176 posts
Re: Disruption with Some GitHub Services – Resolved
#82I noticed earlier this week that my URL bar now pre-fills githubstatus.com instead of github.com when I type "gith"
[flagged]
Re: Disruption with Some GitHub Services – Resolved
#83Honestly? If the problem is scalability, just rate limit git commands on free accounts already. Nobody realistically need to push multiple times per minute, and that alone is bound to trickle down to anything that triggers on commits and pushes.
Sure. The problem is just an easy fix that nobody there thought about yet.
Re: Disruption with Some GitHub Services – Resolved
#84GitHub needs to completely bifurcate their enterprise/paid services from their free services at the infra level.
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.
Re: Disruption with Some GitHub Services – Resolved
#85Fun 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.
Azure's going to suffocate github. I'm curious to see what's next. Will self-hosting the code repository come back in vogue or will another social-coding platform take off?
We should worry less about what everyone else uses, and more about what we use. I'm self-hosting Gitea and thinking of upgrading to Forgejo. What are you using?
Re: Disruption with Some GitHub Services – Resolved
#86Things can go wrong, but really, its been a lot and we're normalizing that to an unhealthy degree... I wonder if it was down that much, if users would get credits the way we pay when we use the services - its kind of ridiculous for a critical service to be down that much and all we do is "ah okay, its just github". Like, as if that was normal to be down that much...
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
Re: Disruption with Some GitHub Services – Resolved
#87We can't keep living like this.
Obviously we can because we are choosing to. Because servers are scary.
Re: Disruption with Some GitHub Services – Resolved
#88Honestly? If the problem is scalability, just rate limit git commands on free accounts already. Nobody realistically need to push multiple times per minute, and that alone is bound to trickle down to anything that triggers on commits and pushes.
Sure. The problem is just an easy fix that nobody there thought about yet.
My point is: they blame it on scale. If that's the story they want us to believe, then they have to explain WHY such a simple fix isn't possible.
There may be non technical reasons for it, even: legal, or PR, but if they want me to believe the "scalability excuse" they need to convince me they're trying.
Re: Disruption with Some GitHub Services – Resolved
#89I noticed earlier this week that my URL bar now pre-fills githubstatus.com instead of github.com when I type "gith"
I can tell it’s getting bad because I went to close some Safari tabs and got confused because the tab next to this was [a dupe of] https://news.ycombinator.com/item?id=49330597.
Re: Disruption with Some GitHub Services – Resolved
#90This is unacceptable for paying customers.
Either 1) infrastructure for paying and non paying customers must be separated, 2) excessive load must be ended by not offering the free tier anymore or 3) they must fix their broken monolith but they are seemingly incapable of doing so.