Thread

1. arandomhuman · 1786035573 · focus · HN ↗

   I love how even self hosted workers don't work during these outages - running jobs on their infrastructure being flakey is marginally acceptable, but the API to simply schedule workflows having this availability is mind boggling. Github just doesn't seem like a serious company anymore.

   1. duped · 1786038068 · focus · HN ↗

      I'm not sure that it's that mind boggling. The entire complexity and value of GHA is not in the runners but the scheduler that the GH frontend hooks into and runners subscribe to jobs from. It's the most likely thing to fall over. '

      If the scheduling was self hosted it would be inexcusable but you can always just connect whatever you want to webhooks.

      1. hinkley · 1786038416 · focus · HN ↗

         The entire complexity and value of GHA is rent-seeking to keep the lights on for other things.

         They have a strong motivation (self preservation) to continue to misunderstand the problem. If they did what is best for us, then we could avoid a substantial fraction of all GH subscriptions by using a FOSS tool to hit the Pareto frontier by replicating just enough GH services to watch commits and PRs.

Unofficial Hacker News client; not affiliated with Y Combinator.