Eugene Diachkin

@iainbeeston Not really. When I opened an issue, it just didn't raise exceptions. I can not reproduce it now, version 2.6.1 raises an exception as expected. Maybe it was my...

I can in 0.5.1, following the steps from the initial message.

Of course, but it's not about this specific case. I cannot write helper methods for all external commands :) Another good example is the `test` command. Nu's `path` commands provide...

Another option which just came to my mind is to add a flag to `run-external` which would return true/false based on the argument's exit code, i.e. ``` if (run-external --the-new-flag...

This looks reasonable, however I'm not sure it will work: ``` ~ ❌1 ❯ if ({ || true }) { echo foo} Error: nu::shell::cant_convert × Can't convert to bool. ╭─[entry...

Yes, that's why I'm saying it would require changes to the parser, so the first opening curly bracket won't be treated as "then" block. Not sure it's possible though because...

Not really, in my opinion. First, it doesn't fit semantically. `take` feels like a functional approach, similar to `map`. On the other hand, `each` feels like an imperative approach. In...

Here's the error of `makepkg`: ``` Compiling async-compression v0.4.6 error: failed to run custom build command for `alpm v3.0.4 (https://github.com/archlinux/alpm.rs?rev=306342#306342ef)` Caused by: process didn't exit successfully: `/tmp/tmp.ySDylO6Idj/paru/src/paru-2.0.3/target/release/build/alpm-1d3e607f04a83636/build-script-build` (exit status: 101)...

Sure, if I manage to reliably reproduce a failing migration, I'll post it. But it's not the migration issue I'm concerned about (there's already #2241), it's operations that can not...

An update: I restarted incus on the source host (also updated it from Debian repos, but it's likely unrelated), and rebooted the source host just in case: it removed the...