cargo_auditable.rs:40:39: called `Option::unwrap()` on a `None` value

[PRESFIL]

Description

cargo_auditable fails on checking rustdesk in NixOS. Only warnings found in rustdesk's codebase,
but cargo_auditable crashes. I don't know how to show the backtrace yet...

nix-store -l /nix/store/18p3y3rxms2m60kdjd1djpv843fz0qds-rustdesk-1.3.8.drv

warning: field `0` is never read
  --> src/hbbs_http.rs:16:11
   |
16 |     Error(String),
   |     ----- ^^^^^^
   |     |
   |     field in this variant
   |
   = note: `HbbHttpResponse` has a derived impl for the trait `Debug`, but this is intentionally ignored during dead code analysis
help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field
   |
16 -     Error(String),
16 +     Error(()),
   |

warning: `rustdesk` (lib) generated 48 warnings (run `cargo fix --lib -p rustdesk` to apply 14 suggestions)

thread 'main' panicked at cargo-auditable/src/cargo_auditable.rs:40:39:
called `Option::unwrap()` on a `None` value
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

[Shnatsel]

The error happens on this line:

cargo-auditable/cargo-auditable/src/cargo_auditable.rs

Line 40 in 117dbc1

std::process::exit(results.code().unwrap());

According to the documentation on .status(), the status is set to None if the process was terminated by a signal. I'll expand the error reporting to provide a more detailed error message, but I don't think cargo auditable is the culprit for the build failure here: Cargo itself is getting terminated by a signal from the OS.

I tried cargo auditable install rustdesk as well as building the latest rustdesk from git in its original workspace with cargo auditable, but I could not reproduce the issue in either of those setups. The issue seems to be specific to Nix.

[PRESFIL]

You was right. The problem fixed itself after some changes in nixpkgs.
I thought it was a continuation of NixOS/nixpkgs#389638 , because those fixes helped,
but problem described in this issue appeared.

[Shnatsel]

I've improved the error message for this situation in #199