[INFO] cloning repository https://github.com/mtgatool/mtga-reader
[INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/mtgatool/mtga-reader" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fmtgatool%2Fmtga-reader", kill_on_drop: false }`
[INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fmtgatool%2Fmtga-reader'...
[INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }`
[INFO] [stdout] 4d4bfd059aec1c545378f1fbb9a794fe421bb677
[INFO] checking mtgatool/mtga-reader against try#0c70cfbec949d241375e31c5a42066be70c720fc for pr-149681
[INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fmtgatool%2Fmtga-reader" "/workspace/builds/worker-0-tc2/source", kill_on_drop: false }`
[INFO] [stderr] Cloning into '/workspace/builds/worker-0-tc2/source'...
[INFO] [stderr] done.
[INFO] removed /workspace/builds/worker-0-tc2/source/.cargo/config.toml
[INFO] started tweaking git repo https://github.com/mtgatool/mtga-reader
[INFO] finished tweaking git repo https://github.com/mtgatool/mtga-reader
[INFO] tweaked toml for git repo https://github.com/mtgatool/mtga-reader written to /workspace/builds/worker-0-tc2/source/Cargo.toml
[INFO] validating manifest of git repo https://github.com/mtgatool/mtga-reader on toolchain 0c70cfbec949d241375e31c5a42066be70c720fc
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+0c70cfbec949d241375e31c5a42066be70c720fc" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] crate git repo https://github.com/mtgatool/mtga-reader already has a lockfile, it will not be regenerated
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+0c70cfbec949d241375e31c5a42066be70c720fc" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded sudo v0.6.0
[INFO] [stderr]   Downloaded process-memory v0.5.0
[INFO] [stderr]   Downloaded read-process-memory v0.1.6
[INFO] [stderr]   Downloaded napi-sys v2.4.0
[INFO] [stderr]   Downloaded napi-build v2.1.3
[INFO] [stderr]   Downloaded proc_mem v0.1.6
[INFO] [stderr]   Downloaded napi-derive v2.16.3
[INFO] [stderr]   Downloaded is_elevated v0.1.2
[INFO] [stderr]   Downloaded napi v2.16.4
[INFO] [stderr]   Downloaded napi-derive-backend v1.0.65
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:845e597a41426bbf2703be69acdb67d10b6de511142d05cba7bbe119c898b2c7" "/opt/rustwide/cargo-home/bin/cargo" "+0c70cfbec949d241375e31c5a42066be70c720fc" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] bb97bcf699b72395b62ed0262354940ea2c9b881af4642b4f4702d0589f54bec
[INFO] running `Command { std: "docker" "start" "-a" "bb97bcf699b72395b62ed0262354940ea2c9b881af4642b4f4702d0589f54bec", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "bb97bcf699b72395b62ed0262354940ea2c9b881af4642b4f4702d0589f54bec", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "bb97bcf699b72395b62ed0262354940ea2c9b881af4642b4f4702d0589f54bec", kill_on_drop: false }`
[INFO] [stdout] bb97bcf699b72395b62ed0262354940ea2c9b881af4642b4f4702d0589f54bec
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:845e597a41426bbf2703be69acdb67d10b6de511142d05cba7bbe119c898b2c7" "/opt/rustwide/cargo-home/bin/cargo" "+0c70cfbec949d241375e31c5a42066be70c720fc" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 9e0b197341ccff5817e56b289afe2f8b21df43df62056c4036a1863a21ba8888
[INFO] running `Command { std: "docker" "start" "-a" "9e0b197341ccff5817e56b289afe2f8b21df43df62056c4036a1863a21ba8888", kill_on_drop: false }`
[INFO] [stderr]    Compiling proc-macro2 v1.0.81
[INFO] [stderr]    Compiling memchr v2.7.2
[INFO] [stderr]    Compiling serde v1.0.198
[INFO] [stderr]    Compiling regex-syntax v0.8.3
[INFO] [stderr]    Compiling semver v1.0.22
[INFO] [stderr]    Compiling unicode-segmentation v1.11.0
[INFO] [stderr]    Compiling serde_json v1.0.116
[INFO] [stderr]    Compiling winapi v0.3.9
[INFO] [stderr]    Compiling napi-build v2.1.3
[INFO] [stderr]     Checking log v0.4.21
[INFO] [stderr]     Checking either v1.11.0
[INFO] [stderr]     Checking bitflags v2.5.0
[INFO] [stderr]     Checking napi-sys v2.4.0
[INFO] [stderr]     Checking process-memory v0.5.0
[INFO] [stderr]    Compiling mtga-reader v0.0.0 (/opt/rustwide/workdir)
[INFO] [stderr]     Checking sudo v0.6.0
[INFO] [stderr]     Checking read-process-memory v0.1.6
[INFO] [stderr]     Checking rayon v1.10.0
[INFO] [stderr]    Compiling convert_case v0.6.0
[INFO] [stderr]     Checking is_elevated v0.1.2
[INFO] [stderr]    Compiling aho-corasick v1.1.3
[INFO] [stderr]    Compiling quote v1.0.36
[INFO] [stderr]    Compiling syn v2.0.60
[INFO] [stderr]    Compiling regex-automata v0.4.6
[INFO] [stderr]     Checking sysinfo v0.30.11
[INFO] [stderr]    Compiling regex v1.10.4
[INFO] [stderr]    Compiling napi-derive-backend v1.0.65
[INFO] [stderr]    Compiling ctor v0.2.8
[INFO] [stderr]     Checking napi v2.16.4
[INFO] [stderr]    Compiling napi-derive v2.16.3
[INFO] [stdout] warning: unexpected `cfg` condition value: `noop`
[INFO] [stdout]   --> src/lib.rs:48:1
[INFO] [stdout]    |
[INFO] [stdout] 48 | #[napi]
[INFO] [stdout]    | ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the attribute macro `napi` may come from an old version of the `napi_derive` crate, try updating your dependency with `cargo update -p napi_derive`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `used_linker`
[INFO] [stdout]   --> src/lib.rs:48:1
[INFO] [stdout]    |
[INFO] [stdout] 48 | #[napi]
[INFO] [stdout]    | ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `napi::bindgen_prelude::ctor` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the attribute macro `napi::bindgen_prelude::ctor` may come from an old version of the `ctor` crate, try updating your dependency with `cargo update -p ctor`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the attribute macro `napi::bindgen_prelude::ctor` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `noop`
[INFO] [stdout]    --> src/lib.rs:130:1
[INFO] [stdout]     |
[INFO] [stdout] 130 | #[napi]
[INFO] [stdout]     | ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `napi` may come from an old version of the `napi_derive` crate, try updating your dependency with `cargo update -p napi_derive`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `used_linker`
[INFO] [stdout]    --> src/lib.rs:130:1
[INFO] [stdout]     |
[INFO] [stdout] 130 | #[napi]
[INFO] [stdout]     | ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `napi::bindgen_prelude::ctor` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `napi::bindgen_prelude::ctor` may come from an old version of the `ctor` crate, try updating your dependency with `cargo update -p ctor`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the attribute macro `napi::bindgen_prelude::ctor` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `noop`
[INFO] [stdout]    --> src/lib.rs:160:1
[INFO] [stdout]     |
[INFO] [stdout] 160 | #[napi]
[INFO] [stdout]     | ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `napi` may come from an old version of the `napi_derive` crate, try updating your dependency with `cargo update -p napi_derive`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `used_linker`
[INFO] [stdout]    --> src/lib.rs:160:1
[INFO] [stdout]     |
[INFO] [stdout] 160 | #[napi]
[INFO] [stdout]     | ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `napi::bindgen_prelude::ctor` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `napi::bindgen_prelude::ctor` may come from an old version of the `ctor` crate, try updating your dependency with `cargo update -p ctor`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the attribute macro `napi::bindgen_prelude::ctor` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `noop`
[INFO] [stdout]    --> src/lib.rs:190:1
[INFO] [stdout]     |
[INFO] [stdout] 190 | #[napi]
[INFO] [stdout]     | ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `napi` may come from an old version of the `napi_derive` crate, try updating your dependency with `cargo update -p napi_derive`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `used_linker`
[INFO] [stdout]    --> src/lib.rs:190:1
[INFO] [stdout]     |
[INFO] [stdout] 190 | #[napi]
[INFO] [stdout]     | ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `napi::bindgen_prelude::ctor` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `napi::bindgen_prelude::ctor` may come from an old version of the `ctor` crate, try updating your dependency with `cargo update -p ctor`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the attribute macro `napi::bindgen_prelude::ctor` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `noop`
[INFO] [stdout]    --> src/lib.rs:200:1
[INFO] [stdout]     |
[INFO] [stdout] 200 | #[napi]
[INFO] [stdout]     | ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `napi` may come from an old version of the `napi_derive` crate, try updating your dependency with `cargo update -p napi_derive`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `used_linker`
[INFO] [stdout]    --> src/lib.rs:200:1
[INFO] [stdout]     |
[INFO] [stdout] 200 | #[napi]
[INFO] [stdout]     | ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `napi::bindgen_prelude::ctor` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `napi::bindgen_prelude::ctor` may come from an old version of the `ctor` crate, try updating your dependency with `cargo update -p ctor`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the attribute macro `napi::bindgen_prelude::ctor` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `noop`
[INFO] [stdout]   --> src/lib.rs:48:1
[INFO] [stdout]    |
[INFO] [stdout] 48 | #[napi]
[INFO] [stdout]    | ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the attribute macro `napi` may come from an old version of the `napi_derive` crate, try updating your dependency with `cargo update -p napi_derive`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `noop`
[INFO] [stdout]    --> src/lib.rs:130:1
[INFO] [stdout]     |
[INFO] [stdout] 130 | #[napi]
[INFO] [stdout]     | ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `napi` may come from an old version of the `napi_derive` crate, try updating your dependency with `cargo update -p napi_derive`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `noop`
[INFO] [stdout]    --> src/lib.rs:160:1
[INFO] [stdout]     |
[INFO] [stdout] 160 | #[napi]
[INFO] [stdout]     | ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `napi` may come from an old version of the `napi_derive` crate, try updating your dependency with `cargo update -p napi_derive`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `noop`
[INFO] [stdout]    --> src/lib.rs:190:1
[INFO] [stdout]     |
[INFO] [stdout] 190 | #[napi]
[INFO] [stdout]     | ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `napi` may come from an old version of the `napi_derive` crate, try updating your dependency with `cargo update -p napi_derive`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `noop`
[INFO] [stdout]    --> src/lib.rs:200:1
[INFO] [stdout]     |
[INFO] [stdout] 200 | #[napi]
[INFO] [stdout]     | ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the attribute macro `napi` may come from an old version of the `napi_derive` crate, try updating your dependency with `cargo update -p napi_derive`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 14.66s
[INFO] [stdout] warning: field `pid` is never read
[INFO] [stdout]   --> src/mono_reader.rs:18:5
[INFO] [stdout]    |
[INFO] [stdout] 17 | pub struct MonoReader {
[INFO] [stdout]    |            ---------- field in this struct
[INFO] [stdout] 18 |     pid: u32,
[INFO] [stdout]    |     ^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/managed.rs:102:23
[INFO] [stdout]     |
[INFO] [stdout] 102 |     pub fn read_class(&self) -> TypeDefinition {
[INFO] [stdout]     |                       ^^^^^     ^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |                       |
[INFO] [stdout]     |                       the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 102 |     pub fn read_class(&self) -> TypeDefinition<'_> {
[INFO] [stdout]     |                                               ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/managed.rs:107:27
[INFO] [stdout]     |
[INFO] [stdout] 107 |     pub fn read_raw_class(&self) -> TypeDefinition {
[INFO] [stdout]     |                           ^^^^^     ^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |                           |
[INFO] [stdout]     |                           the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 107 |     pub fn read_raw_class(&self) -> TypeDefinition<'_> {
[INFO] [stdout]     |                                                   ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/managed.rs:111:34
[INFO] [stdout]     |
[INFO] [stdout] 111 |     pub fn read_generic_instance(&self, type_info: TypeInfo) -> TypeDefinition {
[INFO] [stdout]     |                                  ^^^^^                          ^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 111 |     pub fn read_generic_instance(&self, type_info: TypeInfo) -> TypeDefinition<'_> {
[INFO] [stdout]     |                                                                               ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: field `pid` is never read
[INFO] [stdout]   --> src/mono_reader.rs:18:5
[INFO] [stdout]    |
[INFO] [stdout] 17 | pub struct MonoReader {
[INFO] [stdout]    |            ---------- field in this struct
[INFO] [stdout] 18 |     pid: u32,
[INFO] [stdout]    |     ^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/managed.rs:102:23
[INFO] [stdout]     |
[INFO] [stdout] 102 |     pub fn read_class(&self) -> TypeDefinition {
[INFO] [stdout]     |                       ^^^^^     ^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |                       |
[INFO] [stdout]     |                       the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 102 |     pub fn read_class(&self) -> TypeDefinition<'_> {
[INFO] [stdout]     |                                               ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/managed.rs:107:27
[INFO] [stdout]     |
[INFO] [stdout] 107 |     pub fn read_raw_class(&self) -> TypeDefinition {
[INFO] [stdout]     |                           ^^^^^     ^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |                           |
[INFO] [stdout]     |                           the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 107 |     pub fn read_raw_class(&self) -> TypeDefinition<'_> {
[INFO] [stdout]     |                                                   ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/managed.rs:111:34
[INFO] [stdout]     |
[INFO] [stdout] 111 |     pub fn read_generic_instance(&self, type_info: TypeInfo) -> TypeDefinition {
[INFO] [stdout]     |                                  ^^^^^                          ^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |                                  |
[INFO] [stdout]     |                                  the lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 111 |     pub fn read_generic_instance(&self, type_info: TypeInfo) -> TypeDefinition<'_> {
[INFO] [stdout]     |                                                                               ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] running `Command { std: "docker" "inspect" "9e0b197341ccff5817e56b289afe2f8b21df43df62056c4036a1863a21ba8888", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "9e0b197341ccff5817e56b289afe2f8b21df43df62056c4036a1863a21ba8888", kill_on_drop: false }`
[INFO] [stdout] 9e0b197341ccff5817e56b289afe2f8b21df43df62056c4036a1863a21ba8888
