I see you ignored my entire comment.

No, I responded to the relevant part. I was using segfault as a metaphor, not arguing that it’s actually the same mechanism underneath. If you’re getting panics in production code, I consider that just as much of an emergency to fix as a segfault, and Rust helpfully gives you stack trace info with it. It’s not the same idea as an exception, which could signify an unrecoverable error or an expected issue that can be recovered from.

I don’t know what is more explicit about expect

It forces you to write a message, so most temporary uses will be unwrap(). I use unwrap() all the time when prototyping for the happy path, and then do proper error handling later. This is especially true in larger projects where I can’t just throw in anyhow or something and actually need to map error types and whatnot. I don’t use expect() much (current hobby project has 4 uses, 3 for startup issues and 1 for hopefully impossible condition) but I think it makes sense when there’s no way to continue.

But yes, unwrap() is perhaps the first thing I look for as a reviewer, which is why it’s so surprising that this is the issue. At the very least, it should have been something like expect("exceeds max file size"). I personally prefer explicit panics in production code, but expect is close enough that it’s personal preference.

Yes, it’s not the same since you get a stacktrace (if enabled) and a message, but it’s the closest thing you get in safe rust (outside compiler bugs). I compare it to a segfault because it’s almost as unhandleble.

Basically, you don’t want a panic to crash your program in most cases. If you do, make it explicit (i.e. with expect()). unwrap() tells me the value is absolutely there or the dev is lazy, and I always assume the latter unless there’s an explanation (or it’s obvious from context) otherwise.

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.

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.

Yes, Arch is really stable and has been for about 10 years. In fact, I started using Arch just before they became really stable (the /usr merge), and stuck with it for a few years after. It’s a fantastic distro! If openSUSE Tumbleweed stopped working for me, I’d probably go back to Arch. I ran it on multiple systems, and my main reason for switching is I wanted something with a stable release cycle for servers and rolling on desktop so I can use the same tools on both.

It has fantastic documentation, true, but most likely a new user isn’t going to go there, they’ll go to a forum post from a year ago and change something important. The whole point of going through the Arch install process is to force you to get familiar with the documentation. It’s really not that hard, and after the first install (which took a couple hours), the second took like 20 min. I learned far more in that initial install than I did in the 3-ish years I’d used other distros before trying Arch.

CachyOS being easy to setup defeats the whole purpose since users won’t get familiar with the wiki. By all means, go install CachyOS immediately after the Arch install, buy so yourself a favor and go through it. You’ll understand everything from the boot process to managing system services so much better.

I 100% agree. If you want the Arch experience, you should have the full Arch experience IMO, and that includes the installation process. I don’t mean this in a gatekeepy way, I just mean that’s the target audience and that’s what the distro is expecting.

For a new user, I just cannot recommend Arch because, chances are, that’s not what they actually want. Most new users want to customize stuff, and you can do that with pretty much every distro.

For new users, I recommend Debian, Mint, or Fedora. They’re release based, which is what you want when starting out so stuff doesn’t change on you, and they have vibrant communities. After using it for a year or two, you’ll figure out what you don’t like about the distro and can pick something else.

I disagree. If you want to use Arch for the first time, install it the Arch way. It’s going to be hard, and that’s the point. Arch will need manual intervention at some point, and you’ll be expected to fix it.

If you use something like Manjaro or CachyOS, you’ll look up commands online and maybe it’ll work, but it might not. There’s a decent chance you’ll break something, and you’ll get mad.

Arch expects you to take responsibility for your system, and going through the official install process shows you can do that. Once you get through that once, go ahead and use an installer or fork. You know where to find documentation when something inevitably breaks, so you’re good to go.

If you’re unwilling to do the Arch install process but still want a rolling release, consider OpenSUSE Tumbleweed. It’s the trunk for several projects, some of them commercial, so you’re getting a lot of professional eyeballs on it. There’s a test suite any change needs to pass, and I’ve seen plenty of cases where they hold off on a change because a test fails. And when it does fail (and it probably will), you just snapper rollback and wait a few days. The community isn’t as big as other distros, so I don’t recommend it for a first distro, but they’re also not nearly as impatient as Arch forums.

Arch is a great distro, I used it for a few years without any major issues, but I did need to intervene several times. I’ve been on Tumbleweed about as long and I’ve only had to snapper rollback a few times, and that was the extent of the intervention.

All of them? Maybe an international consortium that pays devs in their home currency.