Hacker News new | ask | show | jobs
by mrclean8586 1728 days ago
Product manager on the GitHub Actions team reporting in, we're sorry to hear about this issue with the rollout of ephemeral runners. Our engineering team is aware of this issue and is heavily prioritizing the investigation and fix.

We'd love to look into your specific case if you want shoot me an email: thejoebourneidentity@github.com
2 comments
sascha_sl 1728 days ago
One, our githubcustomers/ contact is already forwarding anything / setting up a call with the team as needed, and two, that is not a twitter profile I'd ever send a DM to in a professional context, considering you retweet a lot of people diametrically opposed to my existence.
link
mrclean8586 1728 days ago
I will check in with our githubcustomers group to help accelerate. I can also directly inform our engineering team if you're open to sending me your information at

thejoebourneidentity@github.com

Either way, we're looking into this issue and I'll post an update here once we've learned more.

link
p8952 1728 days ago
Asking end users of your product to report issues via DM'ing your personal Twitter account, an account which is full of retweets of homophobic garbage, is really REALLY bad.

Quietly editing your comment after being called out to hide it is even worse.

link
encryptluks2 1728 days ago
Agreed. Thanks for pointing this out. I'm genuinely curious now what their Twitter profile is, but my guess is they'll delete the tweets or remove the Twitter account.

Microsoft notoriously hires a lot of people from the Federal Sector who unfortunately appear to be mostly right-wing religious zealots.

link
newman314 1728 days ago
One issue that I've been dealing with over the last 48hrs is that pushing Docker images to GHCR has been randomly failing with 403 errors.

AFAIK, there has been no communication/acknowledgement of this as an issue. It makes it hard to decide to pick GHCR as a registry of choice.

link
thomasmcfarlane 1728 days ago
We recently faced this; if you are using the docker/login action I'd give that a check as it turned out it was logging us out by default at the end of each job; resulting in some race conditions when running multiple runners on the same machine (sharing the same docker daemon).

Simple fix was to add `logout: false` to the action options.

link