Incident with Issues and Webhooks – Resolved
141–150 of 275 posts
Re: Incident with Issues and Webhooks – Resolved
#142Github 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…
Re: Incident with Issues and Webhooks – Resolved
#143Is Git decentralized?
Personally (but who am I) I don’t need to check whether my changes work on Windows 7 and SunOS in order to continue on a project most of the time.
Re: Incident with Issues and Webhooks – Resolved
#144pre-edit: They just removed the incident and set the status page to all green as of 10:01 PT???
Re: Incident with Issues and Webhooks – Resolved
#145Github has 84.92% uptime in the last 90 days according to https://mrshu.github.io/github-statuses I don't know how this is even remotely close to acceptable.
Re: Incident with Issues and Webhooks – Resolved
#146I keep wondering what causing such a bad service from GH lately, is it the overuse of AI generated code? Are they trying to cut costs with the infrastructure?
Everyone producing magnitude more code with AI agents. Numbers from GH COO here: https://x.com/kdaigle/status/2040164759836778878
If there is so much extra code, where is it going? Is everyone just creating giant piles of throwaway slop?
Re: Incident with Issues and Webhooks – Resolved
#147Earlier quoted context omitted.
For literally decades, I’ve observed that there are systems that make each operation cheap and systems that work hard to scale out. The former frequently seems to wildly outperform the latter. GitHub, for example, seems to implement the main repository /pulls page as a search query, which is hinted at by the prefilled search bar and was mostly confirmed last week when the search backend failed and pull requests didn’…
I think you need to broaden your focus here - I can't really remember any significant downtime before the Microsoft acquisition and the data supports my memories. Microsoft bought Github and migrated to Azure, which is explains the findings. The query performance was fine before they started serving from Azure. I mean honestly, as though there isn't one single person competent enough to read some logs and horizontall…
Re: Incident with Issues and Webhooks – Resolved
#148Github has 84.92% uptime in the last 90 days according to https://mrshu.github.io/github-statuses I don't know how this is even remotely close to acceptable.
It isn't. Lots of unacceptable things going on these days and everyone seems to be accepting them just fine.
Re: Incident with Issues and Webhooks – Resolved
#149Edit: the status page is still all green for today, but the incident is there. pre-edit: They just removed the incident and set the status page to all green as of 10:01 PT???
Re: Incident with Issues and Webhooks – Resolved
#150I have been writing lots of code lately And I still only have local git repository. I do not like why git doesn't have a built in bug or issue tracker and a kanban board or something. I wished Git and Fossil hybrid should have won. I thought about using fossil many times but it seems codex and claude have deeper integration with git. I don't like installing software which keeps growing into infinite feature Monster.…
Don't let "agentic" "coding" be the reason to avoid fossil.
Fossil and other VCS are much easier for humans to use than Git is; there's no reason to have an LLM burning up tokens and the environment to do tasks you'd do yourself quickly and correctly.