https://mrshu.github.io/github-statuses/ They're struggling to maintain a single nine these days.
That page shows today (and every day since the 14th) all green, though.
Incident with Github.com [resolved]
921–930 of 1001 posts
Re: Incident with Github.com [resolved]
#922Earlier quoted context omitted.
All the metrics based around how many commits you have made, how many stars your repo has, etc. Why is that info gamified? Its a dopamine addiction channel.
It’s for subset of people who cares about that. You can just blanket-ignore everyone who cares about that, and move on.
Yeah but then VC use these metrics to fund projects and suddenly what was previously a joke now becomes a way to make wealth.
Re: Incident with Github.com [resolved]
#923I think this is the curse of scale, but also of pseudo-leaders who think leadership is "pushing engineering to rapid-fire features for number go up." You tell engineers and engineering leaders to "just add this one feature, it's really important, what's the ETA? No, that's too late, the market will have moved on, this is existential, you're a bottleneck," fire, hire, fire, hire. Meanwhile the CEO feels great, because…
Code.storage is able to handle large scales too: https://code.storage/ +-------------------------+-------------------------------+ | Total storage limit | Unlimited | | Git request rate limits | Unlimited (Seen: 500+/s/repo) | | API rate limits | Unlimited (Seen: 15k+/s) | | Max repos | Unlimited | | Concurrent writes | 30+ | | Repository size limit | 32TB | | Git LFS | Supported | | GitHub/3rd party sync | Supported…
Yeah GitHub could just migrate to your company tonight and everything would be fine by morning
Re: Incident with Github.com [resolved]
#924What is the best Github alternative that has something like Github Actions? What is the easiest to switch to? I do not want to switch but it is having too much of an impact on me. It is time to give up on Github. This is just too much.
Just out of curiousity, do people here have non-business-related need for GHA? I've never really seen the use of it for anything I wanted to make on my own time; it's more than easy enough to run tests locally, even on my 12-year-old office desktop.
(I'm only using it implicitly because it's how the blog publishing system works under the hood, but the SSG still runs locally.)
Re: Incident with Github.com [resolved]
#925I think this is the curse of scale, but also of pseudo-leaders who think leadership is "pushing engineering to rapid-fire features for number go up." You tell engineers and engineering leaders to "just add this one feature, it's really important, what's the ETA? No, that's too late, the market will have moved on, this is existential, you're a bottleneck," fire, hire, fire, hire. Meanwhile the CEO feels great, because…
Code.storage is able to handle large scales too: https://code.storage/ +-------------------------+-------------------------------+ | Total storage limit | Unlimited | | Git request rate limits | Unlimited (Seen: 500+/s/repo) | | API rate limits | Unlimited (Seen: 15k+/s) | | Max repos | Unlimited | | Concurrent writes | 30+ | | Repository size limit | 32TB | | Git LFS | Supported | | GitHub/3rd party sync | Supported…
So you work for them?
Re: Incident with Github.com [resolved]
#926Earlier quoted context omitted.
Please let this not be true :( I mean nothing against vibe coding for hobby and assisting you when you get stuck, but at something important like Github they should have hooks to stop low-quality commits and repeated CI-breaking or issue causing should automatically restrict accounts at such companies I think. Do you think they have such measures in place? I remember when my indention wasn't spotless our university r…
It’s become clear to me that any company acquired by Microsoft should be avoided. All software dev is hard. Software dev within a huge organization is damned hard. And Microsoft is SO HUGE and has so much infighting and finger pointing going on that they’re now, as far as I’m concerned, incapable (let alone unwilling) to ship good software. No faith left. None. They turn everything into a quagmire.
Come on now let’s be fair. They couldn’t possibly fix all of GitHub‘s bugs and deployment problems while maintaining their breakneck pace of mission critical feature deployments. You know, probably something sexy like replacing Win11’s maximize, minimize and close buttons with a chat prompt where you can just tell copilot what you want the window to do.
Re: Incident with Github.com [resolved]
#927Earlier quoted context omitted.
I’m willing to give them a break as I’m assuming they have a lot of scaling problems due to the influx of LLM assisted coding. But maybe I’m wrong?
> scaling problems due to the influx of LLM assisted coding You mean people pushing LLM assisted coding, or github's own coders pushing LLM assisted code to production ? :-). I am more inclined to think that it is the second, but if the reason is the first, what is particular hard to scale ? It's not like everybody is vide-coding into a single repository, so I would expect that most of the load would naturally be sca…
A perfect slop storm - slop bringing down a slopified service.
Re: Incident with Github.com [resolved]
#928incident was just created - https://www.githubstatus.com/incidents/zkxwbgr0cnmx
Hey, only 8 hours from open to close. What's all the complaining about?
(I know, I know, no sarcasm here, but sometimes it feels necessary.)
Re: Incident with Github.com [resolved]
#929Earlier quoted context omitted.
I’m willing to give them a break as I’m assuming they have a lot of scaling problems due to the influx of LLM assisted coding. But maybe I’m wrong?
How many weeks/months can they use this excuse? They are literally are at the forefront of this emerging industry and are capturing untold value. To let their product suffer and potentially lose market share because of it is extremely foolish
Are they really capturing the most value or just burning the most money?
Re: Incident with Github.com [resolved]
#930Earlier quoted context omitted.
Scaling can take time but they've had at least a year to prepare. It's not like any demand increase they've seen was overnight... At most normal companies you monitor your systems and address potential bottlenecks before they reach a tipping point. And generally you want enough headroom that a sudden 2-3x increase in demand wouldn't take out the service. Either Github's technical leadership/talent is completely out o…
I got the impression from a previous thread that the continual issues were largely driven by the required move to Azure, and underlying Azure stability
Rather, lack of Azure stability. ;-)