3 ms·
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 awa
by mrclean8586 5y 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
- sascha_sl 5y agoOne, 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.
- mrclean8586 5y agoI 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.
- p8952 5y agoAsking 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.
- encryptluks2 5y agoAgreed. 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.
- encryptluks2 5y agoNm, found it: https://twitter.com/JoeB_in_NC https://twitter.com/JoeB_in_NC First thing is a retweet from Ben Shapiro.
- geofft 5y agoThis is the same company whose sales team celebrated their ICE contract with little American flag and eagle emoji (https://www.latimes.com/business/technology/story/2019-10-31/github-ice-contract-defense https://www.latimes.com/business/technology/story/2019-10-31...) and eventually decided to donate all their proceeds from the ICE contract (i.e., their motivation was helping ICE, not making money). Everyone here lives under capitalism. Making money is fine. Saying "If you pay us, we'll take your money" is totally expected. But that's not what they're doing here. But GitHub is now a MAGA-converged organization pushing a social agenda, and you can see it in the quality of their engineering.
- hnarn 5y agoYikes. This is the strangest thing I've seen on HN in a long time. How can someone responsible for product at Github (!) think posting your private twitter account in a context like this is acceptable, and even more so when it's filled with this garbage.
- subsection1h 5y agoJoe Borne works at GitHub only because it was acquired by Microsoft. He's been in the industry for more than a decade but his GitHub account was created only in 2016, and this is his sole public repo: https://github.com/thejoebourneidentity/vm-stats https://github.com/thejoebourneidentity/vm-stats I know multiple people who left GitHub after it was acquired by Microsoft because of unsatisfying experiences they previously had with Microsofties. It seems that they made the right call.
- vegadw 5y agoI didn't actually see anything overtly homophobic/transphobic, though there's some border control posts he liked/retweeted that go a bit into the racist side. Not someone I'd want to hang out with, but I don't see anything like what was being said. Still, what could possibly make anyone think posting a personal twitter handle for this was a good idea. That alone makes me question that he should have the role he does at GitHub.
- newman314 5y agoOne 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.
- thomasmcfarlane 5y agoWe 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.