Anybody having similar issues with Github Actions again? Jobs are failing to connect to external services, or take extremely long time to do so for me.
> Update - Git Operations is experiencing degraded performance. We are continuing to investigate.<p>I hate that companies are saying <i>degraded performance</i> for "its not working at all" (even if only for some people). That's not degraded performance, that's broken.<p>At least the status grid says <i>Partial Outage</i>, but stop with the degraded performance bullshit.
Please disregard the following offtopic rant; I'm not sure if I'm just getting older and jaded or if Github (and the web at large, if I might be frank) is having these issues more often as of late.<p>Is it that what we are doing is becoming more complex, or are we, as a web, moving faster and breaking more things? I wonder sometimes if the advancement and affordability of our hardware and the systems we can run on them has decreased our reliance on optimization and correctness as a requirement of deploying on affordable hardware. Basic functions used to have to be combined with great rigor to run on the same machine for swaths of users. Now we are so far from that we have 1000 layers of abstraction, and it isn't hard to imagine how lots of tiny inefficiencies stacked on top of each other may be adding up to bigger issues.<p>In my org we have a term for this, where you're encumbered by faults deep in the toolchain - getting 'middlewared'.
The title of the incident has been updated to: "Incident with GitHub Actions, API Requests, Issues, GitHub Packages, GitHub Pages, Pull Requests, and Webhooks". Basically all core functionality is down at the moment.
I also noticed that starring repos was not working. At that time, a couple of hours ago, only GitHub Actions was listed as having problems on githubstatus. So I was unsure whether being able to star things was malfunctioning for more people or just me. And I was also thinking about how much cruft has been added to the GitHub web UI lately, ever since the acquisition of GitHub by Microsoft. And I yearn for GitHub as it used to be. But the greatest value in GitHub for me is browsing and starring stuff that others have made, so it's not like I can just set up my own instance either. But I wonder about the future of GitHub. I think it will be more and more geared towards big enterprise users, and less and less a place that will be what it used to feel like for individual developers.
I was on the phone with them getting a demo of Enterprise Managed Users at the time and the demo was failing too, ha. So we looked at the status page together and saw all yellow.<p>Doesn't matter, I wanted EMUs without the demo anyway. Still was funny to happen when I was talking to an engineer at the time.
Two months since the last time a serious issue like this happened. [0]<p>Not really good if you don't have a backup method to avoid this. Unlike those who went all in.<p>[0] <a href="https://news.ycombinator.com/item?id=27366805" rel="nofollow">https://news.ycombinator.com/item?id=27366805</a>
Anyone got any good tips on how to run github action workflows locally or self-hosted? Incidents like this make me want to self-host our CI/CD.<p>I'm confused as to the difference between <a href="https://github.com/nektos/act" rel="nofollow">https://github.com/nektos/act</a> and <a href="https://github.com/actions/runner" rel="nofollow">https://github.com/actions/runner</a><p>Is it not possible to use 'runner' to run github actions locally? The docs for this seem like they are extremely sparse - probably because this competes with the paid option?
I was invited to a party Saturday hosted by the GH CEO, and while this is likely just a huge coincidence, I wonder if some key engineer(s) came down with covid. The friend who invited me said there would be rapid testing at the party.