What is today and who do I blame for it
Computers are great at solving problems that wouldn’t have existed without computers
GitHub: Git operation failures
91–100 of 335 posts
Re: GitHub: Git operation failures
#92Re: GitHub: Git operation failures
#93I didn't really want to work today anyways. First cloudflare, now this... Seems like a sign to get some fresh air
we depend too much on usa centralized tech. we need more soverenity and decentralization.
The underlying tech is still decentralized, but what good does that do when we've made everything that uses it dependent on a few centralized services?
Re: GitHub: Git operation failures
#94Re: GitHub: Git operation failures
#95Earlier quoted context omitted.
FYI in an emergency you can `git push` to and `git pull` from any SSH-capable host without the need to use GitHub.
FYI in an emergency you can SSH to your server and edit files and the DB directly. Where is your god now, proponents of immutable filesystems?!
I actually had the privilege of being sent to the server.
Re: GitHub: Git operation failures
#96 * jobs not being picked up
* jobs not being able to be cancelled
* jobs running but showing up as failed
* jobs showing up as failed but not running
* jobs showing containers as pushed successfully to GitHub's registry, but then we get errors while pulling them
* ID token failures (E_FAIL) and timeouts.
I don't know if this is related to GitHub moving to Azure, or because they're allowing more AI generated code to pass through without proper reviews, or something else, but as a paying customer I am not happy.Re: GitHub: Git operation failures
#97Earlier quoted context omitted.
Been on GitHub for a long time. It feels like they're more often. It used to be yearly if at all that GitHub was noticably impacted. Now it's monthly, and recently, seemingly weekly.
In the early days of GitHub (like before 2010) outages were extremely common.
Re: GitHub: Git operation failures
#98I have a serious question, not trying to start a flame war. A. Are these major issues with cloud/SaaS tools becoming more common, or is it just that they get a lot more coverage now? It seems like we see major issues across AWS, GCP, Azure, Github, etc. at least monthly now and I don't remember that being the case in the past. B. If it's becoming more common, what are the reasons? I can think of a few, but I don't kn…
One possibility is increased monitoring. In the past, issues that happened weren't reported because they went under the radar. Whereas now, those same issues which only impact a small percentage of users would still result in a status update and postmortem. But take this with a grain of salt because it's just a theory and doesn't reflect any actual data. A lot of people are pointing to AI vibe coding as the cause, bu…
Re: GitHub: Git operation failures
#99I have a serious question, not trying to start a flame war. A. Are these major issues with cloud/SaaS tools becoming more common, or is it just that they get a lot more coverage now? It seems like we see major issues across AWS, GCP, Azure, Github, etc. at least monthly now and I don't remember that being the case in the past. B. If it's becoming more common, what are the reasons? I can think of a few, but I don't kn…
FWIW Microsoft is convinced moving Github to Azure will fix these outages
Re: GitHub: Git operation failures
#100Obviously just speculation, but maybe don't let AI write your code... Microsoft CEO says up to 30% of the company’s code was written by AI https://techcrunch.com/2025/04/29/microsoft-ceo-says-up-to-3...
It's degraded availability of Git operations. The enterprise cloud in EU, US, and Australia has no issues. If you look at the incident history disruptions happen often in the public cloud for years already. Before AI wrote code for them.