yashap

We use other runners (Blacksmith), and it hasn't helped, still hard down all day long. Brutal outage.

As a side note, I started getting these symptoms (actions staying queued forever or not running at all) at 5pm PDT yesterday, intermittently. And definitely full outage by 8:30pm PDT. So for sure full outage for 7 hours and counting, even if you use other runners, and I strongly believe partial outage for ~15.5+ hrs before that, even if it hasn't been acknowledged by GitHub yet.

It's honestly insane how terrible their reliability is. Over the past 4 weeks, 8 days with GitHub Actions outages, many of them multi-hour outages: >3 hours on each of July 9th, July 20th and today, and 1.5 hrs on July 23rd.

Outages happen, but this many outages so close together, and so many of them so major/long lasting, something is systematically wrong for sure. It's been seriously hamstringing our ability to ship code at my company.

This is great :) Also if anyone else is hitting New Yorker paywalls and can't read this, just disable JavaScript and reload.

Ah brutal. Has it got worse recently? Been years since I’ve taken the train in Germany, but they used to be pretty good IMO.

Huh really? Whenever I’ve taken the train in Germany it’s been pretty punctual, and looking at the board that’s been the case for most trains. But maybe I just got lucky and/or it’s changed over time.

Flakiest trains I’ve experienced anywhere in Europe were in Italy - rolling strikes among train workers are crazy frequent and cause so many delays and cancellations.

I hope so, but for different reasons. Agreed they spit out plenty of gibberish at the moment, but they’ve also progressed so far so fast it’s pretty scary. If we get to a legitimate artificial general super intelligence, I’m about 95% sure that will be terrible for the vast, vast majority of humans, we'll be obsolete. Crossing my fingers that the current AI surge stops well short of that, and the push that eventually does get there is way, way off into the future.

I want to be able to easily read and understand configuration without having to pop it into a converter. The YAML I encounter in the wild is ~80% pure block style, ~20% mixed (within a single file, mostly block style with some flow style). And I just find the block style hard to read, I have to either spend significant mental effort trying to understand where the objects vs. arrays are, or I have to pop it into a converter (to either JSON or flow style) to understand. Whereas JSON/JSON5, it’s immediately clear without any mental overhead.

Don’t have any experience with them.

Fair, YAML has a lot of usability warts, and those suck too. Although personally I really do hate how tough it is to tell apart arrays and objects, at least with the most common YAML array/object style.

I’m a fan of JSON5. A common criticism is “we’ve already got YAML for human readable config with comments,” but IMO YAML’s readability sucks, it’s too hard to tell what’s an object and what’s an array at a glance (at least, with the way it’s often written).

When dealing with large YAML files, I find myself frequently popping them into online “YAML to JSON” tools to actually figure out WTF is going on. JSON5 is much easier to read, at least for me.

They’re probably downloading from a server in the states, being much further away makes a big difference with a massive download.

I think you’re reading way, way too much into this. Read the piece and it seems like just a goofy little oddball story, makes for a light and enjoyable read, I’m really not picking up any political angle in this piece.

The Guardian are certainly a left-leaning, frequently political paper, but that doesn’t mean every story is political, and IMO this one isn’t.