Incident with GitHub Actions, API requests, Codespaces, Git operations, Issues

Post by TimWolla » Thu, Mar 17, 2022, 3:42 PM UTC

egberts1 wrote: post #59

kortex wrote: post #51

Earlier quoted context omitted.

It's yellow lights across the board, literally nothing is green. That's usually indicative of some sort of software infrastructure level failure or cascade failure, not an application-level failure, which usually manifests as one or two specific services going down (depending on how you define "infrastructure" and "application" - with IAC, arguably the software defined infrastructure _is_ an application). I doubt its…

Only load balancer (as an infrastructure) can hit the lights across the board. Not much else.

Post by Sydneyco » Thu, Mar 17, 2022, 3:50 PM UTC

Post by mkoubaa » Thu, Mar 17, 2022, 3:52 PM UTC

avar wrote: post #35

I'm finding that pushes do go through eventually, this is probably grossly irresponsible, so I don't recommend its use, but I remembered I had this old alias to "push harder" in my ~/.gitconfig: [alias] thrust = "!f() { until git push $@; do sleep 0.5; done; }; f" I've done a few pushes so far, and found that it's going through in <10 tries or so.

Post by Serow225 » Thu, Mar 17, 2022, 3:54 PM UTC

zinekeller wrote: post #53

arpinum wrote: post #20

These incidents have to hurt Azure's brand value. It's a monster task to run something as big as GitHub, if they ever get it stable it will lend a lot of credibility to Microsoft's cloud skills.

Serious questions: 1) Is GitHub runing under Azure's technology stack? 2) Is GitHub under Azure's mamagement (in contrast to Visual Studio's team)? I'm not sure about two but I'm pretty sure that GitHub doesn't run under Azure at all, considering that GitHub has fully separate networking from MSN's/Azure's (and GitHub's machines do pingback unlike most of Microsoft's machines which don't).

Post by fritzo » Thu, Mar 17, 2022, 3:59 PM UTC

bloopernova wrote: post #32

And of course my developer teammates are still trying to merge PRs. I don't care that it works "some of the time"! Don't mess with the repos when the repo host is having seemingly random issues.