Selecting to not continue an update prints a stack trace

[omentic]

Affected Version

paru -V paru v2.0.1 - libalpm v13.0.2

Description

Have you checked previous issues? yes

Output

[apropos@arch pakku]$ paru -Syu
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 multilib is up to date
 dkp-libs is up to date
 dkp-linux is up to date
 arch4edu is up to date
:: Starting full system upgrade...
 there is nothing to do
:: Looking for PKGBUILD upgrades...
:: Looking for AUR upgrades...
:: Looking for devel upgrades...
:: Resolving dependencies...
:: Calculating conflicts...
:: Calculating inner conflicts...
:: packages not in the AUR: <omitted>
:: marked out of date: <omitted>
:: orphans: <omitted>

Repo (1) <omitted>
Repo Make (15) <omitted>
Aur (40) <omitted>

:: Proceed to review? [Y/n]: n
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: __libc_start_main
  11: <unknown>
[apropos@arch pakku]$

I have RUST_BACKTRACE=full set which might be relevant.

[omentic]

I appear to be seeing this upon every error, too:

fetching devel info...
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: __libc_start_main
  12: <unknown>
error: failed to lookup: olive-git: fatal: Unable to read current working directory: No such file or directory

[omentic]

paru also seems to take ages at the "compressing package" step compared to makepkg, but I don't know if that's my imagination or not... I might run some benchmarks and see if it's reproducible

[Morganamilo]

Paru is going the backtrace. If you set RUST_BACKTRACE=off in the env section of your paru.conf. That would probably be the best solution as it would only turn off for paru.