Nah, if there’s one thing they thoroughly test, it’s the spying.

No, it’s a panic, so it’s more similar to a segfault, but with some amount of unwinding. It can be “caught” but only at a thread boundary.

It is unwrap’s fault. If they did it properly, they would’ve had to explicitly deal with the problem, which could clarify exactly what the problem is. In this case, I’d probably use expect() to add context. Also, when doing anything with strict size requirements, I would also explicitly check the size to make sure it’ll fit, again, for better error reporting.

Proper error reporting could’ve made this a 5-min investigation.

Also, the problem in the first place should’ve been caught with unit tests and a test deploy. Our process here is:

1. Any significant change to queries is tested with a copy of production data
2. All changes are tested in a staging environment similar to production
3. All hotfixes are tested with a copy of production data

And we’re not a massive software shop, we have a few dozen devs in a company of thousands of people. If I worked at Cloudflare, I’d have more rigorous standards given the global impact of a bug (we have a few hundred users, not billions like Cloudflare).

Ift is precious and beyond compare. It has tools that most other languages lack to prove certain classes of bugs are impossible.

You can still introduce bugs, especially when you use certain features that “standard” linter (clippy) catches by default and no team would silence globally. .unwrap() is very controversial in Rust and should never be used without clear justification in production code. Even in my pet projects, it’s the first thing I clear out once basic functionality is there.

This issue should’ve been caught at three separate stages:

1. git pre-commit or pre-push should run the linter on the devs machine
2. Static analysis checks should catch this both before getting reviews and when deploying the change
3. Human code review

The fact that it made it past all three makes me very concerned about how they do development over there. We’re a much smaller company and we’re not even a software company (software dev is <1% of the total company), and we do this. We don’t even use Rust, we’re a Python shop, yet we have robust static analysis for every change. It’s standard, and any company doing anything more than a small in-house tool used by 3 people should have these standards in place.

It’s Steam Deck verified, no need to check ProtonDB.

Use something like Backblaze or Hetzner storage boxes for off-site backups. There are a number of tools for making this painless, so pick your favorite. If you have the means, I recommend doing a disaster recovery scenario every so often (i.e. disconnect existing drives, reinstall the OS, and load everything from remote backup).

Generally speaking, follow the 3-2-1 rule:

• 3 copies of everything on
• 2 different types of media with
• 1 copy off site (at least)

For your situation, this could be:

• 3 copies - your computer (NVMe?), TrueNas (HDD?), off-site backup; ideally have a third local device (second computer?)
• 2 media - NVMe and HDD
• 1 copy off site - Backblaze, Hetzner, etc

You could rent a cloud server, but it’ll be a lot more expensive vs just renting storage.

Glad you got it fixed. 🙂

Almost every reply is also explaining what the runtime is.

I boosted it up a bit for other people who come along w/ a similar concern. You seemed mistaken at first until a few threads deep, so there’s likely someone else who is just as, if not more, confused.

Usually when steam refuses to launch, it’s because there’s some Steam process that’s borked but still running. Most of the time, a simple pkill steam fixes it (yes, that includes for flstpak`).

As mentioned down thread, the runtime isn’t your problem. The runtime is what’s needed for native Linux games and I think is also used by proton (not used by Steam itself), so it’s kind of like proton for native games. Steam doesn’t use the runtime at all to launch.

If killing Steam doesn’t work, try rebooting. If that doesn’t work, try updating the flatpak. If that doesn’t work, I suppose reinstall Steam.

Usually it’s because Steam is still running in the background, so a simple pkill steam should close all the processes and allow it to launch. No need to reboot.

OpenSUSE is the same, the 32-bit stuff is completely separate from the 64-bit stuff, so you won’t get conflicts between them.

The new VR headset runs ARM, so presumably it’ll launch with that.

And we Americans trash talk France. I don’t know why though, they’ve been nothing but helpful, what with the Revolutionary War and the Louisiana purchase.

Headlander was surprisingly fun. Probably not my favorite, but certainly up there.

And my kid wants a fingerboard. What’s next, pogs?

I miss them. But I guess I’m in the minority on that one.

Exactly.

There’s a difference between gatekeeping and being transparent about what’s expected. I’m not suggesting people do it the hard way as some kind of hazing ritual, but because there’s a lot of practical value to maintaining your system there. Arch is simple, and their definition of simple means the devs aren’t going to do a ton for you outside of providing good documentation. If your system breaks, that’s on you, and it’s on you to fix it.

If reading through the docs isn’t your first instinct when something goes wrong, you’ll probably have a better experience with something else. There are plenty of other distros that will let you offload a large amount of that responsibility, and that’s the right choice for most people because most people don’t want to mess with their system, they want to use it.

Again, it’s not gatekeeping. I’m happy to help anyone work through the install process. I won’t do it for you, but I’ll answer any questions you might have by showing you where in the docs it is.

If you have reasonable practices, git blame will show you the original ticket, a link to the code review, and relevant information about the change.

Then just do it in your greenhouse. If you don’t have one, ask your help to build one.

I want to use their launcher, but can’t, because they refuse to support it on Linux. That doesn’t feel great. Yeah, I can use Heroic, but I can use that for EGS as well. Offline installers aren’t nearly as valuable if that means I need to mess with WINE myself.

Steam eliminates all of that headache for me and gives me a first class experience. Buying from GOG feels like so much of a downgrade, so I have to convince myself to do it every time. I like that they’re DRM-free, but many of my Steam games at DRM-free as well, so it’s not a huge value add for me.

Ooh, maybe they’ll make a Linux client next! That was 2013 for Steam.