Live data from Hacker News

Days since last GitHub incident

github-incidents.pages.dev

81–90 of 142 posts

Re: Days since last GitHub incident

#81
post #25

This is why I keep encouraging folks to a) have a mirror & b) make sure their tools automatically pick up the mirrors. I recently got mirror support upstreamed into Nixpkgs for fetchdarcs & fetchpijul which actually work on my just-alpha-released pinning tool, Nixtamal https://darcs.toastal.in.th/nixtamal/trunk/README.rst >, for just this sort of thing.

That's great for the repository, but what about if you're using ghcr, actions, issues, or copilot?

Re: Days since last GitHub incident

#82
post #42

I found out when Actions started failing again for the Nth time this month. The internal conversation about moving away from Actions or possibly GitHub has been triggered. I didn't like Zig's post about leaving GitHub because it felt immature, but they weren't wrong. It's decaying.

The Zig post has since been updated and the objectionable parts have been removed. I think we can put that part to rest.

I have no problem with their opinions but I don’t think it should have been said in a Foundation post.

It may have been updated, but nobody is reading the update.

Re: Days since last GitHub incident

#83
post #16

I've gotten accustomed lately to spending a lot of time in the Github Copilot / agent management page. In particular I've been having a lot of fun using agents to browse some of my decade-old throwaway projects; telling it to "setup playwright, write some tests, record screenshots/videos and commit them to the repo" works every time and it's a great way to browse memory lane without spending my own time getting some…

An NVIDIA DGX Spark is $4000, pair that with a relatively cheap second box to run GitLab in the corner and you would have pretty good local AI inference setup. (you'd probably have to write a nontrivial amount of software to get your setup where you want) The local models are just right on the edge of being really useful, there's a tipping point to where accuracy is high enough so that getting things done is easy vs…

I can't say I'm not tempted looking at the Spark, I could probably save some cash on heating my house with that thing. Though yeah unless there's some good software already built around a similar LLM workflow I could use it'd probably be wasted on me, or spend its time desperately trying to pay for itself with crypto mining.

Adding Claude to my rotation is starting to look like the option with the least amount of building the universe from scratch. I have to imagine it can be used in a similar or identical workflow to the Copilot one where it can create PRs and make adjustments in response to feedback etc.

Re: Days since last GitHub incident

#84
post #42

I found out when Actions started failing again for the Nth time this month. The internal conversation about moving away from Actions or possibly GitHub has been triggered. I didn't like Zig's post about leaving GitHub because it felt immature, but they weren't wrong. It's decaying.

[dead]

Re: Days since last GitHub incident

#85
post #42

I found out when Actions started failing again for the Nth time this month. The internal conversation about moving away from Actions or possibly GitHub has been triggered. I didn't like Zig's post about leaving GitHub because it felt immature, but they weren't wrong. It's decaying.

If you consider that an American maintainer was cheesed off enough to move an entire project off GitHub two days before Thanksgiving then the tone of the original post was completely in line with the energy involved.

Anger is a communication tool. It should absolutely be used when boundaries are being violated. Otherwise you’ll get walked all over.

Re: Days since last GitHub incident

#86
post #6
post #5

[flagged]

I don't work at Github but I'd read here recently that they've been undergoing a herculean migration from whichever cloud provider they were on to Azure since their Microsoft acquisition, and that it coincides with an increase in outages. I'm guessing that the solution here was probably just to not do that and it's too late.

They weren't on any cloud provider previously. They famously had their own "metal cloud" of managed servers with everything being containerized and managed by Kubernetes. It seemed like it's worked pretty well, especially for their complex git operation tasks which had specific hardware requirements, but the official word is that apparently they're running into scaling limits with finding new datacenter capacity.

Re: Days since last GitHub incident

#87
post #16

I've gotten accustomed lately to spending a lot of time in the Github Copilot / agent management page. In particular I've been having a lot of fun using agents to browse some of my decade-old throwaway projects; telling it to "setup playwright, write some tests, record screenshots/videos and commit them to the repo" works every time and it's a great way to browse memory lane without spending my own time getting some…

An NVIDIA DGX Spark is $4000, pair that with a relatively cheap second box to run GitLab in the corner and you would have pretty good local AI inference setup. (you'd probably have to write a nontrivial amount of software to get your setup where you want) The local models are just right on the edge of being really useful, there's a tipping point to where accuracy is high enough so that getting things done is easy vs…

The DGX Spark is not good for inference though it's very bandwidth limited - around the same as a lower end MacBook Pro. You're much better off with a Apple silicon for performance and memory size at the moment but I'd recommend holding off until the M5 Max comes out early in the early as the M5 has vastly superior performance to any other Apple silicon chip thanks to its matmul instruction set.

Re: Days since last GitHub incident

#89
post #24

This is pretty dishonest because some trivial service no one cares about will reset this counter .

Your definition of "trivial" is not everyone's definition of trivial.

github haters (who still use the platform, for free) are the worst

Re: Days since last GitHub incident

#90

I've been getting some weird cryptocurrency spam notifications on GitHub and they can't be cleared for some reason. Blue dot is gonna be there forever apparently. Some users made an issue out of it but nobody cared to fix it.

Here’s how you can clear it:

https://github.com/orgs/community/discussions/174310#discuss...

I had the same issue too, and this was the only thing that fixed it for me.

Post reply on HN