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. inigyou · 1786038849 · focus · HN ↗

      GitHub implements self hosted runners by running a normal runner that passes the environment to your runner and then polls it. That's why they cost as much as the smallest GitHub-hosted runner.

      This is no surprise given standard Microsoft operating procedure - <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=47616242">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=47616242

      1. woodruffw · 1786054891 · focus · HN ↗

         I think they kind of have to operate that way if you want a control plane&#x2F;access to GitHub’s own layered services like caching and artifact storage. There are plenty of things to blame GitHub for, but this one doesn’t seem sinister at all.

         Edit: to be clear, I mean the part where they maintain state on their end. I have no idea if they do that with another runner instance, that seems unlikely.

Unofficial Hacker News client; not affiliated with Y Combinator.