It's a testbed for Azure since they started GitHub Actions. Since Azure is mismanaged and doomed https://news.ycombinator.com/item?id=47616242 such outages are normal. I think they hired cheap staff to manually fix overprovisioned boxes on demand. Microsoft Quality at work
GitHub is having issues now
121–130 of 132 posts
Re: GitHub is having issues now
#122Reminder to all OSS projects: it is extraordinarily easy to setup a simple CI job to keep your code in sync between multiple Forges. And getting email notifications from a second Forge is 0 extra effort. At least give people the option to start moving away from GitHub to contribute to your project. It will, ultimately, be better for the ecosystem.
Syncing is trivial, the CI is the deal. GH actions are the best option still. Neither the FSF nor any other OSS lab didn't come up with a proper CI for us open source maintainers. The CI load also increased massively since.
Re: GitHub is having issues now
#123Earlier quoted context omitted.
If you want a GitHub-like UI (with org/repo structure limitations) use either Forgejo or Gitea. If you want a similar but different experience use GitLab. If you want something more akin to the kernel experience (i.e. hosting, flexible repository structure, user auth via ssh keys, and a simple web UI) use gitolite with cgit, or alternatively gitweb.
I love gitea, and I use it for my homelab, but the permissions system needs a lot of work. There’s still an open bug which doesn’t let anyone but the repo owner read CI logs regardless of settings.
I used Gitea for a while, but eventually switched to gitolite+cgit. That was down to the org/repo structure not fitting my git hierarchy (I'm using a topic/repo, topic/subtopic/repo style structure) and the lack of organization/topic wide issue tracking/management.
Re: GitHub is having issues now
#124Seems it was resolved in less than an hour
Re: GitHub is having issues now
#125Earlier quoted context omitted.
Without reaching for my tin foil hat, I have a feeling MS is able to suppress these incidents somehow, because yeah, that one was pretty bad.
Wrapping my face in tinfoil: across the board, Amazon, Microsoft, GitHub, Anthropic and OpenAI, I’m seeing a lot of top-level service issues that sound an awful lot like code hitting production that hasn’t been fully tested. Breaking buttons on the website is one thing, kinda, but Enterprise used to mean a certain degree of robustness and seriousness in product management.
Devs are expected to ship slop 10x faster. The AI tools genuinely help a bit, like maybe 2x, but the 10x "improvement" comes from not thinking about anything else than shipping your assigned features, not testing your code carefully, not getting proper code reviews, not dogfooding your stuff, and releasing carelessly.
Re: GitHub is having issues now
#126Earlier quoted context omitted.
I'm surprised GitLab isn't getting more attention. Yes, its not a carbon copy, but it is close. Apples and pears instead of oranges.
It's close in the sense that it's also Jabbascript SPA crap that needs a supercomputer just to (try and fail to) display a diff of a few thousands lines, you mean? We're using it at work and it sucks massively.
I run GitLab and its CI on a Xeon server from 2010. It's fine. It runs exactly as fast as anything else on that machine. I've also run it on a tiny AWS instance. Also fine.
I don't like that the idle CPU load is high (for really inane reasons) but it performs perfectly well.
Re: GitHub is having issues now
#127We're barely starting to see AI's impact on infra - probably (FWIW https://diversion.dev is at 100% uptime. Different scale, obviously, but also we're not Microsoft.)
I suggest testing your website with uBlock (and all its filter lists enabled). All I see is an almost empty page. Don't point to JS or CSS on third-party CDNs because due to the changes in cross-site sharing, neither Chrome nor Firefox will benefit from cacheing.
caching not cacheing
Re: GitHub is having issues now
#128Why not use Claude to fix it.
Re: GitHub is having issues now
#129Earlier quoted context omitted.
They're moving to Azure and had to fix up Azure first to be stable enough for GH to even consider moving. I'm guessing its a combo of Azure still not being stable enough and a byproduct of trying to move an entire company's operations from a physical DC into a cloud while its running.
Speculation from afar: clouds are not commensurate, and high-volume cloud services are going to anchor key architectural decisions around technical benefits/realities of the cloud environment they target. Moving GitHub isn’t a tech decision, and it’s broadly a Dumb Idea. I think GitHub is well past the complexity threshold where the reflective architecting that happens during cloud development can’t be separated from…
Yeah idk why they're so intent on doing this migration it seems silly and wasteful and bad for their image.
Re: GitHub is having issues now
#130Earlier quoted context omitted.
I suggest testing your website with uBlock (and all its filter lists enabled). All I see is an almost empty page. Don't point to JS or CSS on third-party CDNs because due to the changes in cross-site sharing, neither Chrome nor Firefox will benefit from cacheing.
caching not cacheing
Nope.