[brink]

I'm not sure about the technical details behind their outages since they're a little vague on that, but it's funny how every Rails developer champions Github as a Ruby on Rails shop as why Rails should continue living on when their availability is some of the worst in the tech scene. Lazy evaluation is great until it's not.

[tenderlove]

You're not sure about the technical details, but it's clearly the technology's fault?

[cheshire137]

What, do you know anything about Rails?

[pizza234]

All the incidents seem to be platform-agnostic:

- improper database validation

- older component not tested against configuration change

- uncontrolled automation DOS

- incompletely distributed secrets

[o_m]

Isn't it GitHub Actions that has been having the availability problems for a while now? It started having problems after Microsoft acquired GitHub and there has been speculation that it is because it was ported to .NET and Azure. Is codespaces created with Rails?

[jabart]

It tends to have a lot of abuse where people try to run crypto miners on free github action accounts. Azure has been more stable the past few years and .NET wouldn't have any issues with stability at scale. Likely just a hard problem to solve at the scale they run at.

[c2h5oh]

IDK what is the reason, all I know it's been down so much we've blacklisted it for anything of importance and migrated projects already using it to something else.

[JoyrexJ9]

Trust me, nothing has been ported to .NET, nothing would be gained from such a move. That's not how Microsoft works. Source: I work at Microsoft

[erk__]

Actions was not a thing until after GitHub was acquired, but idk if they used something else in the early days of actions.