Microslop happens.
Incident with Issues and Webhooks – Resolved
171–180 of 275 posts
Re: Incident with Issues and Webhooks – Resolved
#172This is reaching an unacceptable level of performance. There isn't a week that work isn't interrupted by GH.
AI agents have changed the scalability properties of basically the entire internet. It used to be that GitHub could rely on a finite number of people interacting with their platform in real human ways in real observable patterns. So I'm assuming that they scale for those patterns, and optimize for the UI and UX hotspots. But now everyone's got a moltbot running 24/7, sometimes many, and it's completely overloading a…
GH was going down before AI explosion. The start of the trend is MS buying it, not AI explosion, that is just final nail
Re: Incident with Issues and Webhooks – Resolved
#173Earlier quoted context omitted.
Your claim is incorrect. Something purely AI generated may not be covered by copyright in the US. That would make it more valuable to MS as you can reuse it as you like. However, works with significant human input are covered by copyright, and most code does have such input. Human review, and correction is very common. There is a lot of AI generated code out there, and there are no cases challenging the copyright on…
> However, works with significant human input are covered by copyright, and most code does have such input. Human review, and correction is very common. There is a lot of AI generated code out there, and there are no cases challenging the copyright on it. Legislation and court decisions still pending. There are numerous lawsuits about copyrigtability of output, and right of use of copyrighted work by LLMs, and both c…
If that function is all you ask it to write as a one off, maybe. However, if that function is part of a larger system that is human designed it is very different. If you review and correct the code in the system it is very different.
Pages 27 and 28 of this are relevant to this: https://www.copyright.gov/ai/Copyright-and-Artificial-Intell...
Re: Incident with Issues and Webhooks – Resolved
#174Reduce the free tier. I’ve made 4000 commits in the last 2.5 months. That’s just to main. And I push up tons of artifacts daily for regression testing. For $0.
That's like 2 minutes of CPU usage for the repo part
Re: Incident with Issues and Webhooks – Resolved
#175Re: Incident with Issues and Webhooks – Resolved
#176Github has published some incredible usage rate increase numbers, which they ascribe to the rise of agentic coding. At some point, they are going to have to change rate limits, cut free-tier usage, or find some other path to reducing load. It's clear that their infrastructure can't keep up with this significant increase, and it's unlikely that they're going to just absorb the increased costs themselves. Very curious…
IMO, they're reaching the point of no return. I don't think they can horizontally-scale their way out of the hole they dug themselves unless they separate their free and paid infra maybe... which doesn't seem likely considering how their other infra changes are going. In the same way you need to be 10x better for someone to consider switching to your product, if you get 10x worse your competitors get a free 10x by ju…
IIRC back in the day they used to have an on-prem Enterprise product? I've never heard of anyone who actually used it though. IMO that would make a lot of sense for a medium-large organization--you still get the familiar Github product but you can take responsibility for your own uptime--like with Jira, Jenkins (nee Hudson), PyPI/Maven/etc.
Re: Incident with Issues and Webhooks – Resolved
#177Earlier quoted context omitted.
I don't think commits per se puts pressure on the infrastructure. More likely pulls and pushes, and, naturally, the ci minutes they identify as the main issue.
But CI only increased by a factor of 2 since last year. Did they really not foresee that happening? And how does that affect git and api operations.
It really shouldn't. The technical summary they released[1] is a very interesting read from a software engineering perspective. It seems to be blindsided by the increased traffic and gives stats related to commits/PRs (which should be relatively cheap for github to process) without any insight into their web traffic or details on how much actions are costing them. If they were super transparent they'd release information about their request response time and resourcing to fulfill that.
Their current path to resolution is to migrate their codebase to a new language[2], continue to drop their inhouse ops for Azure resources and get off MySQL. Maybe one or two of those steps are legitimately a good idea - I don't have an inside scope - but technology migrations are always fraught with issues. It's quite possible these changes are just a result of them vibe-coding a mature codebase into a new language.
1. https://github.blog/news-insights/company-news/an-update-on-...
2. I'll grant that Ruby isn't the best language to use as scale but I think we're all old enough to realize that language choice is far less impactful on performance than code quality.
Re: Incident with Issues and Webhooks – Resolved
#178Earlier quoted context omitted.
Flawed reasoning all around. Machine code and object code will look the same given the same source code, target platform, compilation and linkin params etc. How is AI-Slop-Code even close to that?
"looking same" is not the requirement. "Working same" is. With proper test harness, the generated code can be controlled to "work the same".
:) :) Sure buddy - mind showing me yours ?
Re: Incident with Issues and Webhooks – Resolved
#179Earlier quoted context omitted.
Everyone producing magnitude more code with AI agents. Numbers from GH COO here: https://x.com/kdaigle/status/2040164759836778878
So why aren't we seeing an explosion in feature shipping rate, or tech startups? If there is so much extra code, where is it going? Is everyone just creating giant piles of throwaway slop?
> Is everyone just creating giant piles of throwaway slop?
yes, like the crypto or productivity 'industry', where every project exists to manage your other crypto and productivity projects, the dynamic of 'AI programming' seems to be to make software to manage your other two dozen AI things
mysteriously enough, big open source projects that people actually use in the real world aren't seeing their issues closed at any higher rates, almost as if that requires actual maintenance and programming (which Fred Brooks told us this half a century ago)
Re: Incident with Issues and Webhooks – Resolved
#180Is this trending in relation to Ghostty moving away from github?