GitHub: Git operation failures
191–200 of 335 posts
Re: GitHub: Git operation failures
#192I 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…
I suspect (although have not researched) that global traffic is up, by throughput but also by session count.
This contributes to a lot more awareness. Slack being down wasn't impactful when most tech companies didn't use Slack. An AWS outage was less relevant when the 10 apps (used to be websites) you use most didn't rely on a single AZ in AWS or you were on your phone less.
I think as a society it just has more impact than it used to.
Re: GitHub: Git operation failures
#193Re: GitHub: Git operation failures
#194Earlier quoted context omitted.
In the early days of GitHub (like before 2010) outages were extremely common.
I agree, for what that's worth. However, this is an unexpected bell curve. I wonder if GitHub is seeing more frequent adversarial action lately. Alternatively, perhaps there is a premature reliance on new technology at play.
I was trying to do a 1.0 release today. Codeberg went down for "10 minutes maintenance" multiple times while I was running my CI actions.
And then github went down.
Cursed.
Re: GitHub: Git operation failures
#195I thought I was going crazy when I couldn't push changes but now it seems it's time to just call it for the day. Back at it tomorrow.
Same, even started adding new ssh keys to no avail... (I was getting some nondescript user error first, then unhealthy upstream)
Re: GitHub: Git operation failures
#196Earlier quoted context omitted.
You just lose the "hub" of connecting others and providing a way to collaborate with others with rich discussions.
All of those sound achievable by email, which, coincidently, is also decentralized.
You mean, assuming everyone in the conversation is using different email providers. (ie. Not the company wide one, and not gmail... I think that covers 90% of all email accounts in the company...)
Re: GitHub: Git operation failures
#197Earlier quoted context omitted.
Microsoft is also convinced that its works are a net benefit for humanity, so I would take that with a grain of salt.
I think it would be pretty hard to argue against that point of view, at least thus far. If DOS/Windows hadn't become the dominant OS someone would have, and a whole generation of engineers cut their teeth on their parents' windows PCs.
Gary was on a flight when IBM called up the Digital Research looking for an OS for the IBM-PC. Gary’s wife, Dorothy, wouldn’t sign an NDA without it going through Gary, and supposedly they never got negotiations back on track.
Re: GitHub: Git operation failures
#198This is incredibly annoying. I've been trying to fix a deployment action on GitHub for a the past bit, so my entire workflow for today has been push, wait, check... push, wait, check... et cetera.
Re: GitHub: Git operation failures
#199How many more outages until people start to see that farming out every aspect of their operations maybe, might, could have a big effect on their overall business? What's the breaking point?
Then again, the skills to run this stuff properly are getting more and more rare so we'll probably see more and more big incidents popping up more frequently like this as time goes on.
Re: GitHub: Git operation failures
#200Good thing git was designed as a decentralized revision control system, so you don’t really need GitHub. It’s just a nice convenience