Can't suppress error in #12585 with a try

[NotTheDr01ds]

Describe the bug

I came across this when answering Question #12560, but I believe there are two issues at play. This is the second part of the issue. The first part is in #12585.

Given the error condition in #12585, I had hoped to suppress it with try { rm -rf $in.name}, but it occurs anyway.

How to reproduce

Using a slightly modified version of the test code in #12585, wrap the rm attempt in a try:

for _ in 1..10 {
  let dir = mktemp -d
  cd $dir
  mkdir foo
  touch foo/fru
  print (ls **/*)
  ls **/*
  | par-each {
      let filename = $in.name
      # print $'Deleting ($filename)'
      try { rm -rf $filename }
    }
  cd -
  rm -rf $dir
}

However, the error still appears.

Expected behavior

Just as with try { rm fileDoesntExist }, I would expect to be able to suppress the error.

Screenshots

No response

Configuration

key	value
version	0.92.2
branch
commit_hash
build_os	linux-x86_64
build_target	x86_64-unknown-linux-gnu
rust_version	rustc 1.77.2 (25ef9e3d8 2024-04-09)
rust_channel	1.77.2-x86_64-unknown-linux-gnu
cargo_version	cargo 1.77.2 (e52e36006 2024-03-26)
build_time	2024-04-12 20:02:27 -04:00
build_rust_channel	release
allocator	mimalloc
features	dataframe, default, sqlite, trash, which
installed_plugins

Additional context

Perhaps this is just expected, since it is an internal error condition rather than a script error. However, given the formatting of the error, it "looks like" an error that could be handled with try.