[INFO] cloning repository https://github.com/Rexifyo/testing1
[INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/Rexifyo/testing1" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FRexifyo%2Ftesting1", kill_on_drop: false }`
[INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FRexifyo%2Ftesting1'...
[INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }`
[INFO] [stdout] 246e55d3e37d950021788ddfc0124b977d9c0be0
[INFO] testing Rexifyo/testing1 against beta-2025-09-21 for beta-1.91-2
[INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FRexifyo%2Ftesting1" "/workspace/builds/worker-7-tc2/source", kill_on_drop: false }`
[INFO] [stderr] Cloning into '/workspace/builds/worker-7-tc2/source'...
[INFO] [stderr] done.
[INFO] removed /workspace/builds/worker-7-tc2/source/.cargo/config.toml
[INFO] removed /workspace/builds/worker-7-tc2/source/rust-toolchain.toml
[INFO] started tweaking git repo https://github.com/Rexifyo/testing1
[INFO] finished tweaking git repo https://github.com/Rexifyo/testing1
[INFO] tweaked toml for git repo https://github.com/Rexifyo/testing1 written to /workspace/builds/worker-7-tc2/source/Cargo.toml
[INFO] validating manifest of git repo https://github.com/Rexifyo/testing1 on toolchain beta-2025-09-21
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+beta-2025-09-21" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] crate git repo https://github.com/Rexifyo/testing1 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" "+beta-2025-09-21" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-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:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2025-09-21" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 77ba1264041013c138666330610492b1124c07cbbb7f2cd92c3a38831a642b65
[INFO] running `Command { std: "docker" "start" "-a" "77ba1264041013c138666330610492b1124c07cbbb7f2cd92c3a38831a642b65", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "77ba1264041013c138666330610492b1124c07cbbb7f2cd92c3a38831a642b65", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "77ba1264041013c138666330610492b1124c07cbbb7f2cd92c3a38831a642b65", kill_on_drop: false }`
[INFO] [stdout] 77ba1264041013c138666330610492b1124c07cbbb7f2cd92c3a38831a642b65
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-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=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-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:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2025-09-21" "build" "--frozen" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] fce6c1c08f56fef11315c49c0fb384901707097934b95d01438a3aaee7a90f6a
[INFO] running `Command { std: "docker" "start" "-a" "fce6c1c08f56fef11315c49c0fb384901707097934b95d01438a3aaee7a90f6a", kill_on_drop: false }`
[INFO] [stderr]    Compiling libc v0.2.139
[INFO] [stderr]    Compiling proc-macro2 v1.0.59
[INFO] [stderr]    Compiling unicode-ident v1.0.6
[INFO] [stderr]    Compiling quote v1.0.28
[INFO] [stderr]    Compiling syn v1.0.107
[INFO] [stderr]    Compiling tap v1.0.1
[INFO] [stderr]    Compiling unicode-xid v0.2.4
[INFO] [stderr]    Compiling funty v2.0.0
[INFO] [stderr]    Compiling scopeguard v1.1.0
[INFO] [stderr]    Compiling crossbeam-utils v0.8.14
[INFO] [stderr]    Compiling memoffset v0.7.1
[INFO] [stderr]    Compiling crossbeam-epoch v0.9.13
[INFO] [stderr]    Compiling serde_derive v1.0.152
[INFO] [stderr]    Compiling radium v0.7.0
[INFO] [stderr]    Compiling generic-array v0.14.6
[INFO] [stderr]    Compiling rayon-core v1.10.1
[INFO] [stderr]    Compiling wyz v0.5.1
[INFO] [stderr]    Compiling arrayvec v0.7.2
[INFO] [stderr]    Compiling arrayref v0.3.6
[INFO] [stderr]    Compiling byteorder v1.4.3
[INFO] [stderr]    Compiling cc v1.0.78
[INFO] [stderr]    Compiling serde v1.0.152
[INFO] [stderr]    Compiling either v1.8.0
[INFO] [stderr]    Compiling once_cell v1.17.0
[INFO] [stderr]    Compiling thiserror v1.0.38
[INFO] [stderr]    Compiling log v0.4.17
[INFO] [stderr]    Compiling rand_core v0.6.4
[INFO] [stderr]    Compiling bitvec v1.0.1
[INFO] [stderr]    Compiling blake2b_simd v1.0.0
[INFO] [stderr]    Compiling num-traits v0.2.15
[INFO] [stderr]    Compiling lock_api v0.4.10
[INFO] [stderr]    Compiling execute-command-tokens v0.1.6
[INFO] [stderr]    Compiling blake2s_simd v1.0.0
[INFO] [stderr]    Compiling byte-slice-cast v1.2.2
[INFO] [stderr]    Compiling rand_xorshift v0.3.0
[INFO] [stderr]    Compiling block-buffer v0.10.3
[INFO] [stderr]    Compiling digest v0.9.0
[INFO] [stderr]    Compiling cipher v0.3.0
[INFO] [stderr]    Compiling crypto-common v0.1.6
[INFO] [stderr]    Compiling rand v0.8.5
[INFO] [stderr]    Compiling spin v0.9.8
[INFO] [stderr]    Compiling syn v2.0.18
[INFO] [stderr]    Compiling digest v0.10.6
[INFO] [stderr]    Compiling static_assertions v1.1.0
[INFO] [stderr]    Compiling universal-hash v0.4.1
[INFO] [stderr]    Compiling block-buffer v0.9.0
[INFO] [stderr]    Compiling num-integer v0.1.45
[INFO] [stderr]    Compiling crunchy v0.2.2
[INFO] [stderr]    Compiling ec-gpu-gen v0.5.2
[INFO] [stderr]    Compiling sha2 v0.10.6
[INFO] [stderr]    Compiling flume v0.10.14
[INFO] [stderr]    Compiling poly1305 v0.7.2
[INFO] [stderr]    Compiling sha2 v0.9.9
[INFO] [stderr]    Compiling aead v0.4.3
[INFO] [stderr]    Compiling getrandom v0.2.8
[INFO] [stderr]    Compiling num_cpus v1.15.0
[INFO] [stderr]    Compiling crossbeam-channel v0.5.8
[INFO] [stderr]    Compiling yastl v0.1.2
[INFO] [stderr]    Compiling blst v0.3.10
[INFO] [stderr]    Compiling rand_chacha v0.3.1
[INFO] [stderr]    Compiling threadpool v1.8.1
[INFO] [stderr]    Compiling crossbeam-deque v0.8.2
[INFO] [stderr]    Compiling tracing-core v0.1.30
[INFO] [stderr]    Compiling num-bigint v0.4.3
[INFO] [stderr]    Compiling rustversion v1.0.12
[INFO] [stderr]    Compiling libm v0.2.6
[INFO] [stderr]    Compiling nonempty v0.7.0
[INFO] [stderr]    Compiling ec-gpu v0.2.0
[INFO] [stderr]    Compiling getrandom v0.1.16
[INFO] [stderr]    Compiling crypto-mac v0.11.1
[INFO] [stderr]    Compiling base64ct v1.0.1
[INFO] [stderr]    Compiling block-modes v0.8.1
[INFO] [stderr]    Compiling rand_core v0.5.1
[INFO] [stderr]    Compiling password-hash v0.3.2
[INFO] [stderr]    Compiling uint v0.9.5
[INFO] [stderr]    Compiling unicode-normalization v0.1.22
[INFO] [stderr]    Compiling inout v0.1.3
[INFO] [stderr]    Compiling hmac v0.11.0
[INFO] [stderr]    Compiling zcash_encoding v0.1.0 (https://github.com/iron-fish/librustzcash.git?branch=blstrs#d5518200)
[INFO] [stderr]    Compiling rayon v1.6.1
[INFO] [stderr]    Compiling memuse v0.2.1
[INFO] [stderr]    Compiling bs58 v0.4.0
[INFO] [stderr]    Compiling pbkdf2 v0.9.0
[INFO] [stderr]    Compiling f4jumble v0.1.0 (https://github.com/iron-fish/librustzcash.git?branch=blstrs#d5518200)
[INFO] [stderr]    Compiling aes v0.7.5
[INFO] [stderr]    Compiling bech32 v0.8.1
[INFO] [stderr]    Compiling universal-hash v0.5.1
[INFO] [stderr]    Compiling equihash v0.2.0 (https://github.com/iron-fish/librustzcash.git?branch=blstrs#d5518200)
[INFO] [stderr]    Compiling dirs-sys v0.3.7
[INFO] [stderr]    Compiling memmap2 v0.5.10
[INFO] [stderr]    Compiling zcash_address v0.1.0 (https://github.com/iron-fish/librustzcash.git?branch=blstrs#d5518200)
[INFO] [stderr]    Compiling memchr v2.5.0
[INFO] [stderr]    Compiling poly1305 v0.8.0
[INFO] [stderr]    Compiling aead v0.5.2
[INFO] [stderr]    Compiling ff v0.13.0
[INFO] [stderr]    Compiling directories v4.0.1
[INFO] [stderr]    Compiling crypto-mac v0.8.0
[INFO] [stderr]    Compiling anyhow v1.0.68
[INFO] [stderr]    Compiling ff v0.12.1
[INFO] [stderr]    Compiling group v0.13.0
[INFO] [stderr]    Compiling group v0.12.1
[INFO] [stderr]    Compiling rand_chacha v0.2.2
[INFO] [stderr]    Compiling blake2 v0.10.6
[INFO] [stderr]    Compiling blake3 v1.3.3
[INFO] [stderr]    Compiling indexmap v1.9.3
[INFO] [stderr]    Compiling pairing v0.22.0
[INFO] [stderr]    Compiling bls12_381 v0.7.1
[INFO] [stderr]    Compiling pasta_curves v0.4.1
[INFO] [stderr]    Compiling semver v1.0.17
[INFO] [stderr]    Compiling serde_json v1.0.96
[INFO] [stderr]    Compiling pairing v0.23.0
[INFO] [stderr]    Compiling rand v0.7.3
[INFO] [stderr]    Compiling pbkdf2 v0.4.0
[INFO] [stderr]    Compiling hmac v0.8.1
[INFO] [stderr]    Compiling ironfish v0.3.0 (/opt/rustwide/workdir/ironfish-rust)
[INFO] [stderr]    Compiling rand_seeder v0.2.3
[INFO] [stderr]    Compiling ciborium-io v0.2.0
[INFO] [stderr]    Compiling constant_time_eq v0.2.4
[INFO] [stderr]    Compiling aho-corasick v0.7.20
[INFO] [stderr]    Compiling os_str_bytes v6.5.0
[INFO] [stderr]    Compiling fpe v0.5.1
[INFO] [stderr]    Compiling itoa v1.0.6
[INFO] [stderr]    Compiling ryu v1.0.13
[INFO] [stderr]    Compiling regex-syntax v0.6.28
[INFO] [stderr]    Compiling unicode-segmentation v1.10.1
[INFO] [stderr]    Compiling jubjub v0.9.0
[INFO] [stderr]    Compiling half v1.8.2
[INFO] [stderr]    Compiling plotters-backend v0.3.4
[INFO] [stderr]    Compiling convert_case v0.6.0
[INFO] [stderr]    Compiling ciborium-ll v0.2.0
[INFO] [stderr]    Compiling plotters-svg v0.3.3
[INFO] [stderr]    Compiling clap_lex v0.2.4
[INFO] [stderr]    Compiling itertools v0.10.5
[INFO] [stderr]    Compiling textwrap v0.16.0
[INFO] [stderr]    Compiling bellman v0.13.1 (https://github.com/iron-fish/bellman?rev=1cc52ca33e6db14233f1cbc0c9c5b7c822b229ec#1cc52ca3)
[INFO] [stderr]    Compiling xxhash-rust v0.8.6
[INFO] [stderr]    Compiling execute-command-macro-impl v0.1.9
[INFO] [stderr]    Compiling cast v0.3.0
[INFO] [stderr]    Compiling napi-build v2.0.1
[INFO] [stderr]    Compiling walkdir v2.3.3
[INFO] [stderr]    Compiling ctor v0.2.2
[INFO] [stderr]    Compiling synstructure v0.12.6
[INFO] [stderr]    Compiling clap v3.2.25
[INFO] [stderr]    Compiling ironfish-rust-nodejs v0.1.0 (/opt/rustwide/workdir/ironfish-rust-nodejs)
[INFO] [stderr]    Compiling plotters v0.3.4
[INFO] [stderr]    Compiling execute-command-macro v0.1.8
[INFO] [stderr]    Compiling execute v0.2.12
[INFO] [stderr]    Compiling atty v0.2.14
[INFO] [stderr]    Compiling bitflags v2.3.3
[INFO] [stderr]    Compiling oorandom v11.1.3
[INFO] [stderr]    Compiling anes v0.1.6
[INFO] [stderr]    Compiling napi-sys v2.2.3
[INFO] [stderr]    Compiling base64 v0.13.1
[INFO] [stderr]    Compiling regex v1.7.1
[INFO] [stderr]    Compiling napi v2.13.2
[INFO] [stderr]    Compiling zeroize_derive v1.3.3
[INFO] [stderr]    Compiling thiserror-impl v1.0.38
[INFO] [stderr]    Compiling tracing-attributes v0.1.23
[INFO] [stderr]    Compiling zeroize v1.6.0
[INFO] [stderr]    Compiling chacha20 v0.8.2
[INFO] [stderr]    Compiling chacha20poly1305 v0.9.1
[INFO] [stderr]    Compiling cipher v0.4.4
[INFO] [stderr]    Compiling zcash_note_encryption v0.1.0
[INFO] [stderr]    Compiling tracing v0.1.37
[INFO] [stderr]    Compiling zcash_note_encryption v0.1.0 (https://github.com/iron-fish/librustzcash.git?branch=blstrs#d5518200)
[INFO] [stderr]    Compiling bip0039 v0.9.0
[INFO] [stderr]    Compiling salsa20 v0.10.2
[INFO] [stderr]    Compiling chacha20 v0.9.1
[INFO] [stderr]    Compiling curve25519-dalek v3.2.0
[INFO] [stderr]    Compiling xsalsa20poly1305 v0.9.1
[INFO] [stderr]    Compiling chacha20poly1305 v0.10.1
[INFO] [stderr]    Compiling ironfish-phase2 v0.2.2 (/opt/rustwide/workdir/ironfish-phase2)
[INFO] [stderr]    Compiling napi-derive-backend v1.0.52
[INFO] [stderr]    Compiling halo2_proofs v0.2.0
[INFO] [stderr]    Compiling criterion-plot v0.5.0
[INFO] [stderr]    Compiling x25519-dalek v1.1.1
[INFO] [stderr]    Compiling tiny-bip39 v0.8.2
[INFO] [stderr]    Compiling ironfish_mpc v0.2.0 (/opt/rustwide/workdir/ironfish-mpc)
[INFO] [stderr]    Compiling crypto_box v0.8.2
[INFO] [stderr]    Compiling napi-derive v2.13.0
[INFO] [stderr]    Compiling halo2_gadgets v0.2.0
[INFO] [stderr]    Compiling blstrs v0.6.1
[INFO] [stderr]    Compiling reddsa v0.3.0
[INFO] [stderr]    Compiling incrementalmerkletree v0.3.0
[INFO] [stderr]    Compiling bincode v1.3.3
[INFO] [stderr]    Compiling redjubjub v0.5.0
[INFO] [stderr]    Compiling ciborium v0.2.0
[INFO] [stderr]    Compiling tinytemplate v1.2.1
[INFO] [stderr]    Compiling criterion v0.4.0
[INFO] [stderr]    Compiling jubjub v0.9.0 (https://github.com/iron-fish/jubjub.git?branch=blstrs#a1a0c2ed)
[INFO] [stderr]    Compiling bellperson v0.24.1 (https://github.com/iron-fish/bellperson.git?branch=blstrs#37b9976b)
[INFO] [stderr]    Compiling orchard v0.2.0
[INFO] [stderr]    Compiling zcash_primitives v0.7.0 (https://github.com/iron-fish/librustzcash.git?branch=blstrs#d5518200)
[INFO] [stderr]    Compiling zcash_proofs v0.7.1 (https://github.com/iron-fish/librustzcash.git?branch=blstrs#d5518200)
[INFO] [stderr]    Compiling ironfish_zkp v0.2.0 (/opt/rustwide/workdir/ironfish-zkp)
[INFO] [stdout] warning: creating a mutable reference to mutable static
[INFO] [stdout]   --> ironfish-rust/src/signal_catcher.rs:23:33
[INFO] [stdout]    |
[INFO] [stdout] 23 |     let depth = libc::backtrace(STACK_TRACE.as_mut_ptr(), MAX_FRAMES as i32);
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]    |
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/static-mut-references.html>
[INFO] [stdout]    = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives
[INFO] [stdout]    = note: `#[warn(static_mut_refs)]` (part of `#[warn(rust_2024_compatibility)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a shared reference to mutable static
[INFO] [stdout]   --> ironfish-rust/src/signal_catcher.rs:24:26
[INFO] [stdout]    |
[INFO] [stdout] 24 |     backtrace_symbols_fd(STACK_TRACE.as_ptr(), depth, 2);
[INFO] [stdout]    |                          ^^^^^^^^^^^^^^^^^^^^ shared reference to mutable static
[INFO] [stdout]    |
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/static-mut-references.html>
[INFO] [stdout]    = note: shared references to mutable statics are dangerous; it's undefined behavior if the static is mutated or if a mutable reference is created for it while the shared reference lives
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> ironfish-rust/src/transaction/mod.rs:627:24
[INFO] [stdout]     |
[INFO] [stdout] 627 |     pub fn iter_spends(&self) -> Iter<SpendDescription> {
[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] 627 |     pub fn iter_spends(&self) -> Iter<'_, SpendDescription> {
[INFO] [stdout]     |                                       +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> ironfish-rust/src/transaction/mod.rs:636:25
[INFO] [stdout]     |
[INFO] [stdout] 636 |     pub fn iter_outputs(&self) -> Iter<OutputDescription> {
[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] 636 |     pub fn iter_outputs(&self) -> Iter<'_, OutputDescription> {
[INFO] [stdout]     |                                        +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]   --> ironfish-rust/src/transaction/value_balances.rs:50:17
[INFO] [stdout]    |
[INFO] [stdout] 50 |     pub fn iter(&self) -> hash_map::Iter<AssetIdentifier, i64> {
[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] 50 |     pub fn iter(&self) -> hash_map::Iter<'_, AssetIdentifier, i64> {
[INFO] [stdout]    |                                          +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Compiling benchmarks v0.1.0 (/opt/rustwide/workdir/benchmarks)
[INFO] [stdout] warning: unexpected `cfg` condition value: `noop`
[INFO] [stdout]   --> ironfish-rust-nodejs/src/lib.rs:31:1
[INFO] [stdout]    |
[INFO] [stdout] 31 | #[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]   --> ironfish-rust-nodejs/src/lib.rs:31:1
[INFO] [stdout]    |
[INFO] [stdout] 31 | #[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]   --> ironfish-rust-nodejs/src/lib.rs:66:1
[INFO] [stdout]    |
[INFO] [stdout] 66 | #[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]   --> ironfish-rust-nodejs/src/lib.rs:66:1
[INFO] [stdout]    |
[INFO] [stdout] 66 | #[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]   --> ironfish-rust-nodejs/src/lib.rs:79:1
[INFO] [stdout]    |
[INFO] [stdout] 79 | #[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]   --> ironfish-rust-nodejs/src/lib.rs:79:1
[INFO] [stdout]    |
[INFO] [stdout] 79 | #[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]   --> ironfish-rust-nodejs/src/lib.rs:86:1
[INFO] [stdout]    |
[INFO] [stdout] 86 | #[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]   --> ironfish-rust-nodejs/src/lib.rs:86:1
[INFO] [stdout]    |
[INFO] [stdout] 86 | #[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]   --> ironfish-rust-nodejs/src/lib.rs:92:1
[INFO] [stdout]    |
[INFO] [stdout] 92 | #[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]   --> ironfish-rust-nodejs/src/lib.rs:92:1
[INFO] [stdout]    |
[INFO] [stdout] 92 | #[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]    --> ironfish-rust-nodejs/src/lib.rs:105:1
[INFO] [stdout]     |
[INFO] [stdout] 105 | #[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]    --> ironfish-rust-nodejs/src/lib.rs:105:1
[INFO] [stdout]     |
[INFO] [stdout] 105 | #[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]    --> ironfish-rust-nodejs/src/lib.rs:166:1
[INFO] [stdout]     |
[INFO] [stdout] 166 | #[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]    --> ironfish-rust-nodejs/src/lib.rs:166:1
[INFO] [stdout]     |
[INFO] [stdout] 166 | #[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]   --> ironfish-rust-nodejs/src/mpc.rs:33:1
[INFO] [stdout]    |
[INFO] [stdout] 33 | #[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]   --> ironfish-rust-nodejs/src/mpc.rs:33:1
[INFO] [stdout]    |
[INFO] [stdout] 33 | #[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]   --> ironfish-rust-nodejs/src/mpc.rs:66:1
[INFO] [stdout]    |
[INFO] [stdout] 66 | #[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]   --> ironfish-rust-nodejs/src/mpc.rs:66:1
[INFO] [stdout]    |
[INFO] [stdout] 66 | #[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]   --> ironfish-rust-nodejs/src/mpc.rs:19:1
[INFO] [stdout]    |
[INFO] [stdout] 19 | #[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]   --> ironfish-rust-nodejs/src/mpc.rs:19:1
[INFO] [stdout]    |
[INFO] [stdout] 19 | #[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]   --> ironfish-rust-nodejs/src/mpc.rs:51:1
[INFO] [stdout]    |
[INFO] [stdout] 51 | #[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]   --> ironfish-rust-nodejs/src/mpc.rs:51:1
[INFO] [stdout]    |
[INFO] [stdout] 51 | #[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]   --> ironfish-rust-nodejs/src/nacl.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | #[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]   --> ironfish-rust-nodejs/src/nacl.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | #[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]   --> ironfish-rust-nodejs/src/nacl.rs:17:1
[INFO] [stdout]    |
[INFO] [stdout] 17 | #[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]   --> ironfish-rust-nodejs/src/nacl.rs:17:1
[INFO] [stdout]    |
[INFO] [stdout] 17 | #[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]   --> ironfish-rust-nodejs/src/nacl.rs:63:1
[INFO] [stdout]    |
[INFO] [stdout] 63 | #[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]   --> ironfish-rust-nodejs/src/nacl.rs:63:1
[INFO] [stdout]    |
[INFO] [stdout] 63 | #[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]   --> ironfish-rust-nodejs/src/nacl.rs:74:1
[INFO] [stdout]    |
[INFO] [stdout] 74 | #[napi(js_name = "boxMessage")]
[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]   --> ironfish-rust-nodejs/src/nacl.rs:74:1
[INFO] [stdout]    |
[INFO] [stdout] 74 | #[napi(js_name = "boxMessage")]
[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]    --> ironfish-rust-nodejs/src/nacl.rs:101:1
[INFO] [stdout]     |
[INFO] [stdout] 101 | #[napi(js_name = "unboxMessage")]
[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]    --> ironfish-rust-nodejs/src/nacl.rs:101:1
[INFO] [stdout]     |
[INFO] [stdout] 101 | #[napi(js_name = "unboxMessage")]
[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]   --> ironfish-rust-nodejs/src/nacl.rs:20:1
[INFO] [stdout]    |
[INFO] [stdout] 20 | #[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]   --> ironfish-rust-nodejs/src/nacl.rs:20:1
[INFO] [stdout]    |
[INFO] [stdout] 20 | #[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]   --> ironfish-rust-nodejs/src/nacl.rs:26:1
[INFO] [stdout]    |
[INFO] [stdout] 26 | #[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]   --> ironfish-rust-nodejs/src/nacl.rs:26:1
[INFO] [stdout]    |
[INFO] [stdout] 26 | #[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]  --> ironfish-rust-nodejs/src/rolling_filter.rs:9:1
[INFO] [stdout]   |
[INFO] [stdout] 9 | #[napi(js_name = "RollingFilter")]
[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]  --> ironfish-rust-nodejs/src/rolling_filter.rs:9:1
[INFO] [stdout]   |
[INFO] [stdout] 9 | #[napi(js_name = "RollingFilter")]
[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]   --> ironfish-rust-nodejs/src/rolling_filter.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | #[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]   --> ironfish-rust-nodejs/src/rolling_filter.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | #[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]   --> ironfish-rust-nodejs/src/signal_catcher.rs:10:1
[INFO] [stdout]    |
[INFO] [stdout] 10 | #[napi(js_name = "initSignalHandler")]
[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]   --> ironfish-rust-nodejs/src/signal_catcher.rs:10:1
[INFO] [stdout]    |
[INFO] [stdout] 10 | #[napi(js_name = "initSignalHandler")]
[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]   --> ironfish-rust-nodejs/src/signal_catcher.rs:17:1
[INFO] [stdout]    |
[INFO] [stdout] 17 | #[napi(js_name = "triggerSegfault")]
[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]   --> ironfish-rust-nodejs/src/signal_catcher.rs:17:1
[INFO] [stdout]    |
[INFO] [stdout] 17 | #[napi(js_name = "triggerSegfault")]
[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]   --> ironfish-rust-nodejs/src/structs/asset.rs:22:1
[INFO] [stdout]    |
[INFO] [stdout] 22 | #[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]   --> ironfish-rust-nodejs/src/structs/asset.rs:22:1
[INFO] [stdout]    |
[INFO] [stdout] 22 | #[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]   --> ironfish-rust-nodejs/src/structs/asset.rs:25:1
[INFO] [stdout]    |
[INFO] [stdout] 25 | #[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]   --> ironfish-rust-nodejs/src/structs/asset.rs:25:1
[INFO] [stdout]    |
[INFO] [stdout] 25 | #[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]   --> ironfish-rust-nodejs/src/structs/asset.rs:28:1
[INFO] [stdout]    |
[INFO] [stdout] 28 | #[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]   --> ironfish-rust-nodejs/src/structs/asset.rs:28:1
[INFO] [stdout]    |
[INFO] [stdout] 28 | #[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]   --> ironfish-rust-nodejs/src/structs/asset.rs:31:1
[INFO] [stdout]    |
[INFO] [stdout] 31 | #[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]   --> ironfish-rust-nodejs/src/structs/asset.rs:31:1
[INFO] [stdout]    |
[INFO] [stdout] 31 | #[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]   --> ironfish-rust-nodejs/src/structs/asset.rs:34:1
[INFO] [stdout]    |
[INFO] [stdout] 34 | #[napi(js_name = "Asset")]
[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]   --> ironfish-rust-nodejs/src/structs/asset.rs:34:1
[INFO] [stdout]    |
[INFO] [stdout] 34 | #[napi(js_name = "Asset")]
[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]   --> ironfish-rust-nodejs/src/structs/asset.rs:39:1
[INFO] [stdout]    |
[INFO] [stdout] 39 | #[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]   --> ironfish-rust-nodejs/src/structs/asset.rs:39:1
[INFO] [stdout]    |
[INFO] [stdout] 39 | #[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]   --> ironfish-rust-nodejs/src/structs/note_encrypted.rs:19:1
[INFO] [stdout]    |
[INFO] [stdout] 19 | #[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]   --> ironfish-rust-nodejs/src/structs/note_encrypted.rs:19:1
[INFO] [stdout]    |
[INFO] [stdout] 19 | #[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]   --> ironfish-rust-nodejs/src/structs/note_encrypted.rs:22:1
[INFO] [stdout]    |
[INFO] [stdout] 22 | #[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]   --> ironfish-rust-nodejs/src/structs/note_encrypted.rs:22:1
[INFO] [stdout]    |
[INFO] [stdout] 22 | #[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]   --> ironfish-rust-nodejs/src/structs/note_encrypted.rs:25:1
[INFO] [stdout]    |
[INFO] [stdout] 25 | #[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]   --> ironfish-rust-nodejs/src/structs/note_encrypted.rs:25:1
[INFO] [stdout]    |
[INFO] [stdout] 25 | #[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]   --> ironfish-rust-nodejs/src/structs/note_encrypted.rs:28:1
[INFO] [stdout]    |
[INFO] [stdout] 28 | #[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]   --> ironfish-rust-nodejs/src/structs/note_encrypted.rs:28:1
[INFO] [stdout]    |
[INFO] [stdout] 28 | #[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]   --> ironfish-rust-nodejs/src/structs/note_encrypted.rs:32:1
[INFO] [stdout]    |
[INFO] [stdout] 32 | #[napi(js_name = "NoteEncrypted")]
[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]   --> ironfish-rust-nodejs/src/structs/note_encrypted.rs:32:1
[INFO] [stdout]    |
[INFO] [stdout] 32 | #[napi(js_name = "NoteEncrypted")]
[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]   --> ironfish-rust-nodejs/src/structs/note_encrypted.rs:37:1
[INFO] [stdout]    |
[INFO] [stdout] 37 | #[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]   --> ironfish-rust-nodejs/src/structs/note_encrypted.rs:37:1
[INFO] [stdout]    |
[INFO] [stdout] 37 | #[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]   --> ironfish-rust-nodejs/src/structs/note.rs:19:1
[INFO] [stdout]    |
[INFO] [stdout] 19 | #[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]   --> ironfish-rust-nodejs/src/structs/note.rs:19:1
[INFO] [stdout]    |
[INFO] [stdout] 19 | #[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]   --> ironfish-rust-nodejs/src/structs/note.rs:22:1
[INFO] [stdout]    |
[INFO] [stdout] 22 | #[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]   --> ironfish-rust-nodejs/src/structs/note.rs:22:1
[INFO] [stdout]    |
[INFO] [stdout] 22 | #[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]   --> ironfish-rust-nodejs/src/structs/note.rs:25:1
[INFO] [stdout]    |
[INFO] [stdout] 25 | #[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]   --> ironfish-rust-nodejs/src/structs/note.rs:25:1
[INFO] [stdout]    |
[INFO] [stdout] 25 | #[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]   --> ironfish-rust-nodejs/src/structs/note.rs:28:1
[INFO] [stdout]    |
[INFO] [stdout] 28 | #[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]   --> ironfish-rust-nodejs/src/structs/note.rs:28:1
[INFO] [stdout]    |
[INFO] [stdout] 28 | #[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]   --> ironfish-rust-nodejs/src/structs/note.rs:31:1
[INFO] [stdout]    |
[INFO] [stdout] 31 | #[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]   --> ironfish-rust-nodejs/src/structs/note.rs:31:1
[INFO] [stdout]    |
[INFO] [stdout] 31 | #[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]   --> ironfish-rust-nodejs/src/structs/note.rs:46:1
[INFO] [stdout]    |
[INFO] [stdout] 46 | #[napi(js_name = "Note")]
[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]   --> ironfish-rust-nodejs/src/structs/note.rs:46:1
[INFO] [stdout]    |
[INFO] [stdout] 46 | #[napi(js_name = "Note")]
[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]   --> ironfish-rust-nodejs/src/structs/note.rs:51:1
[INFO] [stdout]    |
[INFO] [stdout] 51 | #[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]   --> ironfish-rust-nodejs/src/structs/note.rs:51:1
[INFO] [stdout]    |
[INFO] [stdout] 51 | #[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]   --> ironfish-rust-nodejs/src/structs/transaction.rs:28:1
[INFO] [stdout]    |
[INFO] [stdout] 28 | #[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]   --> ironfish-rust-nodejs/src/structs/transaction.rs:28:1
[INFO] [stdout]    |
[INFO] [stdout] 28 | #[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]   --> ironfish-rust-nodejs/src/structs/transaction.rs:31:1
[INFO] [stdout]    |
[INFO] [stdout] 31 | #[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]   --> ironfish-rust-nodejs/src/structs/transaction.rs:31:1
[INFO] [stdout]    |
[INFO] [stdout] 31 | #[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]   --> ironfish-rust-nodejs/src/structs/transaction.rs:34:1
[INFO] [stdout]    |
[INFO] [stdout] 34 | #[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]   --> ironfish-rust-nodejs/src/structs/transaction.rs:34:1
[INFO] [stdout]    |
[INFO] [stdout] 34 | #[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]   --> ironfish-rust-nodejs/src/structs/transaction.rs:37:1
[INFO] [stdout]    |
[INFO] [stdout] 37 | #[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]   --> ironfish-rust-nodejs/src/structs/transaction.rs:37:1
[INFO] [stdout]    |
[INFO] [stdout] 37 | #[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]   --> ironfish-rust-nodejs/src/structs/transaction.rs:40:1
[INFO] [stdout]    |
[INFO] [stdout] 40 | #[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]   --> ironfish-rust-nodejs/src/structs/transaction.rs:40:1
[INFO] [stdout]    |
[INFO] [stdout] 40 | #[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]   --> ironfish-rust-nodejs/src/structs/transaction.rs:43:1
[INFO] [stdout]    |
[INFO] [stdout] 43 | #[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]   --> ironfish-rust-nodejs/src/structs/transaction.rs:43:1
[INFO] [stdout]    |
[INFO] [stdout] 43 | #[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]    --> ironfish-rust-nodejs/src/structs/transaction.rs:310:1
[INFO] [stdout]     |
[INFO] [stdout] 310 | #[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]    --> ironfish-rust-nodejs/src/structs/transaction.rs:310:1
[INFO] [stdout]     |
[INFO] [stdout] 310 | #[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]   --> ironfish-rust-nodejs/src/structs/transaction.rs:46:1
[INFO] [stdout]    |
[INFO] [stdout] 46 | #[napi(js_name = "TransactionPosted")]
[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]   --> ironfish-rust-nodejs/src/structs/transaction.rs:46:1
[INFO] [stdout]    |
[INFO] [stdout] 46 | #[napi(js_name = "TransactionPosted")]
[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]   --> ironfish-rust-nodejs/src/structs/transaction.rs:51:1
[INFO] [stdout]    |
[INFO] [stdout] 51 | #[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]   --> ironfish-rust-nodejs/src/structs/transaction.rs:51:1
[INFO] [stdout]    |
[INFO] [stdout] 51 | #[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]    --> ironfish-rust-nodejs/src/structs/transaction.rs:162:1
[INFO] [stdout]     |
[INFO] [stdout] 162 | #[napi(js_name = "Transaction")]
[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]    --> ironfish-rust-nodejs/src/structs/transaction.rs:162:1
[INFO] [stdout]     |
[INFO] [stdout] 162 | #[napi(js_name = "Transaction")]
[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]    --> ironfish-rust-nodejs/src/structs/transaction.rs:167:1
[INFO] [stdout]     |
[INFO] [stdout] 167 | #[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]    --> ironfish-rust-nodejs/src/structs/transaction.rs:167:1
[INFO] [stdout]     |
[INFO] [stdout] 167 | #[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]    --> ironfish-rust-nodejs/src/lib.rs:110:1
[INFO] [stdout]     |
[INFO] [stdout] 110 | #[napi(constructor)]
[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]    --> ironfish-rust-nodejs/src/lib.rs:110:1
[INFO] [stdout]     |
[INFO] [stdout] 110 | #[napi(constructor)]
[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]    --> ironfish-rust-nodejs/src/lib.rs:116:1
[INFO] [stdout]     |
[INFO] [stdout] 116 | #[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]    --> ironfish-rust-nodejs/src/lib.rs:116:1
[INFO] [stdout]     |
[INFO] [stdout] 116 | #[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]    --> ironfish-rust-nodejs/src/lib.rs:120:1
[INFO] [stdout]     |
[INFO] [stdout] 120 | #[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]    --> ironfish-rust-nodejs/src/lib.rs:120:1
[INFO] [stdout]     |
[INFO] [stdout] 120 | #[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] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 1m 13s
[INFO] running `Command { std: "docker" "inspect" "fce6c1c08f56fef11315c49c0fb384901707097934b95d01438a3aaee7a90f6a", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "fce6c1c08f56fef11315c49c0fb384901707097934b95d01438a3aaee7a90f6a", kill_on_drop: false }`
[INFO] [stdout] fce6c1c08f56fef11315c49c0fb384901707097934b95d01438a3aaee7a90f6a
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-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=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-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:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2025-09-21" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] dd87b07f61c446dbc42b4f34edaf2d4643d3b4058fe91e4d763370ba6f407d7d
[INFO] running `Command { std: "docker" "start" "-a" "dd87b07f61c446dbc42b4f34edaf2d4643d3b4058fe91e4d763370ba6f407d7d", kill_on_drop: false }`
[INFO] [stdout] warning: creating a mutable reference to mutable static
[INFO] [stdout]   --> ironfish-rust/src/signal_catcher.rs:23:33
[INFO] [stdout]    |
[INFO] [stdout] 23 |     let depth = libc::backtrace(STACK_TRACE.as_mut_ptr(), MAX_FRAMES as i32);
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]    |
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/static-mut-references.html>
[INFO] [stdout]    = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives
[INFO] [stdout]    = note: `#[warn(static_mut_refs)]` (part of `#[warn(rust_2024_compatibility)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a shared reference to mutable static
[INFO] [stdout]   --> ironfish-rust/src/signal_catcher.rs:24:26
[INFO] [stdout]    |
[INFO] [stdout] 24 |     backtrace_symbols_fd(STACK_TRACE.as_ptr(), depth, 2);
[INFO] [stdout]    |                          ^^^^^^^^^^^^^^^^^^^^ shared reference to mutable static
[INFO] [stdout]    |
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/static-mut-references.html>
[INFO] [stdout]    = note: shared references to mutable statics are dangerous; it's undefined behavior if the static is mutated or if a mutable reference is created for it while the shared reference lives
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> ironfish-rust/src/transaction/mod.rs:627:24
[INFO] [stdout]     |
[INFO] [stdout] 627 |     pub fn iter_spends(&self) -> Iter<SpendDescription> {
[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] 627 |     pub fn iter_spends(&self) -> Iter<'_, SpendDescription> {
[INFO] [stdout]     |                                       +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> ironfish-rust/src/transaction/mod.rs:636:25
[INFO] [stdout]     |
[INFO] [stdout] 636 |     pub fn iter_outputs(&self) -> Iter<OutputDescription> {
[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] 636 |     pub fn iter_outputs(&self) -> Iter<'_, OutputDescription> {
[INFO] [stdout]     |                                        +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Compiling hex-literal v0.4.1
[INFO] [stderr]    Compiling ironfish_mpc v0.2.0 (/opt/rustwide/workdir/ironfish-mpc)
[INFO] [stderr]    Compiling ironfish_zkp v0.2.0 (/opt/rustwide/workdir/ironfish-zkp)
[INFO] [stderr]    Compiling benchmarks v0.1.0 (/opt/rustwide/workdir/benchmarks)
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]   --> ironfish-rust/src/transaction/value_balances.rs:50:17
[INFO] [stdout]    |
[INFO] [stdout] 50 |     pub fn iter(&self) -> hash_map::Iter<AssetIdentifier, i64> {
[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] 50 |     pub fn iter(&self) -> hash_map::Iter<'_, AssetIdentifier, i64> {
[INFO] [stdout]    |                                          +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Compiling ironfish-phase2 v0.2.2 (/opt/rustwide/workdir/ironfish-phase2)
[INFO] [stderr]    Compiling ironfish-rust-nodejs v0.1.0 (/opt/rustwide/workdir/ironfish-rust-nodejs)
[INFO] [stderr]    Compiling ironfish v0.3.0 (/opt/rustwide/workdir/ironfish-rust)
[INFO] [stdout] warning: unexpected `cfg` condition value: `noop`
[INFO] [stdout]   --> ironfish-rust-nodejs/src/lib.rs:31:1
[INFO] [stdout]    |
[INFO] [stdout] 31 | #[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]   --> ironfish-rust-nodejs/src/lib.rs:66:1
[INFO] [stdout]    |
[INFO] [stdout] 66 | #[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]   --> ironfish-rust-nodejs/src/lib.rs:79:1
[INFO] [stdout]    |
[INFO] [stdout] 79 | #[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]   --> ironfish-rust-nodejs/src/lib.rs:86:1
[INFO] [stdout]    |
[INFO] [stdout] 86 | #[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]   --> ironfish-rust-nodejs/src/lib.rs:92:1
[INFO] [stdout]    |
[INFO] [stdout] 92 | #[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]    --> ironfish-rust-nodejs/src/lib.rs:105:1
[INFO] [stdout]     |
[INFO] [stdout] 105 | #[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]    --> ironfish-rust-nodejs/src/lib.rs:166:1
[INFO] [stdout]     |
[INFO] [stdout] 166 | #[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]   --> ironfish-rust-nodejs/src/mpc.rs:33:1
[INFO] [stdout]    |
[INFO] [stdout] 33 | #[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]   --> ironfish-rust-nodejs/src/mpc.rs:66:1
[INFO] [stdout]    |
[INFO] [stdout] 66 | #[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]   --> ironfish-rust-nodejs/src/mpc.rs:19:1
[INFO] [stdout]    |
[INFO] [stdout] 19 | #[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]   --> ironfish-rust-nodejs/src/mpc.rs:51:1
[INFO] [stdout]    |
[INFO] [stdout] 51 | #[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]   --> ironfish-rust-nodejs/src/nacl.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | #[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]   --> ironfish-rust-nodejs/src/nacl.rs:17:1
[INFO] [stdout]    |
[INFO] [stdout] 17 | #[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]   --> ironfish-rust-nodejs/src/nacl.rs:63:1
[INFO] [stdout]    |
[INFO] [stdout] 63 | #[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]   --> ironfish-rust-nodejs/src/nacl.rs:74:1
[INFO] [stdout]    |
[INFO] [stdout] 74 | #[napi(js_name = "boxMessage")]
[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]    --> ironfish-rust-nodejs/src/nacl.rs:101:1
[INFO] [stdout]     |
[INFO] [stdout] 101 | #[napi(js_name = "unboxMessage")]
[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]   --> ironfish-rust-nodejs/src/nacl.rs:20:1
[INFO] [stdout]    |
[INFO] [stdout] 20 | #[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]   --> ironfish-rust-nodejs/src/nacl.rs:26:1
[INFO] [stdout]    |
[INFO] [stdout] 26 | #[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]  --> ironfish-rust-nodejs/src/rolling_filter.rs:9:1
[INFO] [stdout]   |
[INFO] [stdout] 9 | #[napi(js_name = "RollingFilter")]
[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]   --> ironfish-rust-nodejs/src/rolling_filter.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | #[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]   --> ironfish-rust-nodejs/src/signal_catcher.rs:10:1
[INFO] [stdout]    |
[INFO] [stdout] 10 | #[napi(js_name = "initSignalHandler")]
[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]   --> ironfish-rust-nodejs/src/signal_catcher.rs:17:1
[INFO] [stdout]    |
[INFO] [stdout] 17 | #[napi(js_name = "triggerSegfault")]
[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]   --> ironfish-rust-nodejs/src/structs/asset.rs:22:1
[INFO] [stdout]    |
[INFO] [stdout] 22 | #[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]   --> ironfish-rust-nodejs/src/structs/asset.rs:25:1
[INFO] [stdout]    |
[INFO] [stdout] 25 | #[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]   --> ironfish-rust-nodejs/src/structs/asset.rs:28:1
[INFO] [stdout]    |
[INFO] [stdout] 28 | #[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]   --> ironfish-rust-nodejs/src/structs/asset.rs:31:1
[INFO] [stdout]    |
[INFO] [stdout] 31 | #[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]   --> ironfish-rust-nodejs/src/structs/asset.rs:34:1
[INFO] [stdout]    |
[INFO] [stdout] 34 | #[napi(js_name = "Asset")]
[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]   --> ironfish-rust-nodejs/src/structs/asset.rs:39:1
[INFO] [stdout]    |
[INFO] [stdout] 39 | #[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]   --> ironfish-rust-nodejs/src/structs/note_encrypted.rs:19:1
[INFO] [stdout]    |
[INFO] [stdout] 19 | #[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]   --> ironfish-rust-nodejs/src/structs/note_encrypted.rs:22:1
[INFO] [stdout]    |
[INFO] [stdout] 22 | #[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]   --> ironfish-rust-nodejs/src/structs/note_encrypted.rs:25:1
[INFO] [stdout]    |
[INFO] [stdout] 25 | #[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]   --> ironfish-rust-nodejs/src/structs/note_encrypted.rs:28:1
[INFO] [stdout]    |
[INFO] [stdout] 28 | #[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]   --> ironfish-rust-nodejs/src/structs/note_encrypted.rs:32:1
[INFO] [stdout]    |
[INFO] [stdout] 32 | #[napi(js_name = "NoteEncrypted")]
[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]   --> ironfish-rust-nodejs/src/structs/note_encrypted.rs:37:1
[INFO] [stdout]    |
[INFO] [stdout] 37 | #[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]   --> ironfish-rust-nodejs/src/structs/note.rs:19:1
[INFO] [stdout]    |
[INFO] [stdout] 19 | #[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]   --> ironfish-rust-nodejs/src/structs/note.rs:22:1
[INFO] [stdout]    |
[INFO] [stdout] 22 | #[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]   --> ironfish-rust-nodejs/src/structs/note.rs:25:1
[INFO] [stdout]    |
[INFO] [stdout] 25 | #[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]   --> ironfish-rust-nodejs/src/structs/note.rs:28:1
[INFO] [stdout]    |
[INFO] [stdout] 28 | #[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]   --> ironfish-rust-nodejs/src/structs/note.rs:31:1
[INFO] [stdout]    |
[INFO] [stdout] 31 | #[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]   --> ironfish-rust-nodejs/src/structs/note.rs:46:1
[INFO] [stdout]    |
[INFO] [stdout] 46 | #[napi(js_name = "Note")]
[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]   --> ironfish-rust-nodejs/src/structs/note.rs:51:1
[INFO] [stdout]    |
[INFO] [stdout] 51 | #[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]   --> ironfish-rust-nodejs/src/structs/transaction.rs:28:1
[INFO] [stdout]    |
[INFO] [stdout] 28 | #[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]   --> ironfish-rust-nodejs/src/structs/transaction.rs:31:1
[INFO] [stdout]    |
[INFO] [stdout] 31 | #[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]   --> ironfish-rust-nodejs/src/structs/transaction.rs:34:1
[INFO] [stdout]    |
[INFO] [stdout] 34 | #[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]   --> ironfish-rust-nodejs/src/structs/transaction.rs:37:1
[INFO] [stdout]    |
[INFO] [stdout] 37 | #[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]   --> ironfish-rust-nodejs/src/structs/transaction.rs:40:1
[INFO] [stdout]    |
[INFO] [stdout] 40 | #[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]   --> ironfish-rust-nodejs/src/structs/transaction.rs:43:1
[INFO] [stdout]    |
[INFO] [stdout] 43 | #[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]    --> ironfish-rust-nodejs/src/structs/transaction.rs:310:1
[INFO] [stdout]     |
[INFO] [stdout] 310 | #[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]   --> ironfish-rust-nodejs/src/structs/transaction.rs:46:1
[INFO] [stdout]    |
[INFO] [stdout] 46 | #[napi(js_name = "TransactionPosted")]
[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]   --> ironfish-rust-nodejs/src/structs/transaction.rs:51:1
[INFO] [stdout]    |
[INFO] [stdout] 51 | #[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]    --> ironfish-rust-nodejs/src/structs/transaction.rs:162:1
[INFO] [stdout]     |
[INFO] [stdout] 162 | #[napi(js_name = "Transaction")]
[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]    --> ironfish-rust-nodejs/src/structs/transaction.rs:167:1
[INFO] [stdout]     |
[INFO] [stdout] 167 | #[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]    --> ironfish-rust-nodejs/src/lib.rs:110:1
[INFO] [stdout]     |
[INFO] [stdout] 110 | #[napi(constructor)]
[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]    --> ironfish-rust-nodejs/src/lib.rs:116:1
[INFO] [stdout]     |
[INFO] [stdout] 116 | #[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]    --> ironfish-rust-nodejs/src/lib.rs:120:1
[INFO] [stdout]     |
[INFO] [stdout] 120 | #[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: creating a mutable reference to mutable static
[INFO] [stdout]   --> ironfish-rust/src/signal_catcher.rs:23:33
[INFO] [stdout]    |
[INFO] [stdout] 23 |     let depth = libc::backtrace(STACK_TRACE.as_mut_ptr(), MAX_FRAMES as i32);
[INFO] [stdout]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stdout]    |
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/static-mut-references.html>
[INFO] [stdout]    = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives
[INFO] [stdout]    = note: `#[warn(static_mut_refs)]` (part of `#[warn(rust_2024_compatibility)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: creating a shared reference to mutable static
[INFO] [stdout]   --> ironfish-rust/src/signal_catcher.rs:24:26
[INFO] [stdout]    |
[INFO] [stdout] 24 |     backtrace_symbols_fd(STACK_TRACE.as_ptr(), depth, 2);
[INFO] [stdout]    |                          ^^^^^^^^^^^^^^^^^^^^ shared reference to mutable static
[INFO] [stdout]    |
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/static-mut-references.html>
[INFO] [stdout]    = note: shared references to mutable statics are dangerous; it's undefined behavior if the static is mutated or if a mutable reference is created for it while the shared reference lives
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> ironfish-rust/src/transaction/mod.rs:627:24
[INFO] [stdout]     |
[INFO] [stdout] 627 |     pub fn iter_spends(&self) -> Iter<SpendDescription> {
[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] 627 |     pub fn iter_spends(&self) -> Iter<'_, SpendDescription> {
[INFO] [stdout]     |                                       +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> ironfish-rust/src/transaction/mod.rs:636:25
[INFO] [stdout]     |
[INFO] [stdout] 636 |     pub fn iter_outputs(&self) -> Iter<OutputDescription> {
[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] 636 |     pub fn iter_outputs(&self) -> Iter<'_, OutputDescription> {
[INFO] [stdout]     |                                        +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]   --> ironfish-rust/src/transaction/value_balances.rs:50:17
[INFO] [stdout]    |
[INFO] [stdout] 50 |     pub fn iter(&self) -> hash_map::Iter<AssetIdentifier, i64> {
[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] 50 |     pub fn iter(&self) -> hash_map::Iter<'_, AssetIdentifier, i64> {
[INFO] [stdout]    |                                          +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `test` profile [unoptimized + debuginfo] target(s) in 4.85s
[INFO] running `Command { std: "docker" "inspect" "dd87b07f61c446dbc42b4f34edaf2d4643d3b4058fe91e4d763370ba6f407d7d", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "dd87b07f61c446dbc42b4f34edaf2d4643d3b4058fe91e4d763370ba6f407d7d", kill_on_drop: false }`
[INFO] [stdout] dd87b07f61c446dbc42b4f34edaf2d4643d3b4058fe91e4d763370ba6f407d7d
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-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=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-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:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2025-09-21" "test" "--frozen", kill_on_drop: false }`
[INFO] [stdout] c63d42a942f04fbbe135bfee43a4cca6616682e0bb455c9a1a28144462ac7ba9
[INFO] running `Command { std: "docker" "start" "-a" "c63d42a942f04fbbe135bfee43a4cca6616682e0bb455c9a1a28144462ac7ba9", kill_on_drop: false }`
[INFO] [stderr] warning: creating a mutable reference to mutable static
[INFO] [stderr]   --> ironfish-rust/src/signal_catcher.rs:23:33
[INFO] [stderr]    |
[INFO] [stderr] 23 |     let depth = libc::backtrace(STACK_TRACE.as_mut_ptr(), MAX_FRAMES as i32);
[INFO] [stderr]    |                                 ^^^^^^^^^^^^^^^^^^^^^^^^ mutable reference to mutable static
[INFO] [stderr]    |
[INFO] [stderr]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/static-mut-references.html>
[INFO] [stderr]    = note: mutable references to mutable statics are dangerous; it's undefined behavior if any other pointer to the static is used or if any other reference is created for the static while the mutable reference lives
[INFO] [stderr]    = note: `#[warn(static_mut_refs)]` (part of `#[warn(rust_2024_compatibility)]`) on by default
[INFO] [stderr] 
[INFO] [stderr] warning: creating a shared reference to mutable static
[INFO] [stderr]   --> ironfish-rust/src/signal_catcher.rs:24:26
[INFO] [stderr]    |
[INFO] [stderr] 24 |     backtrace_symbols_fd(STACK_TRACE.as_ptr(), depth, 2);
[INFO] [stderr]    |                          ^^^^^^^^^^^^^^^^^^^^ shared reference to mutable static
[INFO] [stderr]    |
[INFO] [stderr]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/static-mut-references.html>
[INFO] [stderr]    = note: shared references to mutable statics are dangerous; it's undefined behavior if the static is mutated or if a mutable reference is created for it while the shared reference lives
[INFO] [stderr] 
[INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stderr]    --> ironfish-rust/src/transaction/mod.rs:627:24
[INFO] [stderr]     |
[INFO] [stderr] 627 |     pub fn iter_spends(&self) -> Iter<SpendDescription> {
[INFO] [stderr]     |                        ^^^^^     ^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stderr]     |                        |
[INFO] [stderr]     |                        the lifetime is elided here
[INFO] [stderr]     |
[INFO] [stderr]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stderr]     = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stderr] help: use `'_` for type paths
[INFO] [stderr]     |
[INFO] [stderr] 627 |     pub fn iter_spends(&self) -> Iter<'_, SpendDescription> {
[INFO] [stderr]     |                                       +++
[INFO] [stderr] 
[INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stderr]    --> ironfish-rust/src/transaction/mod.rs:636:25
[INFO] [stderr]     |
[INFO] [stderr] 636 |     pub fn iter_outputs(&self) -> Iter<OutputDescription> {
[INFO] [stderr]     |                         ^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stderr]     |                         |
[INFO] [stderr]     |                         the lifetime is elided here
[INFO] [stderr]     |
[INFO] [stderr]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stderr] help: use `'_` for type paths
[INFO] [stderr]     |
[INFO] [stderr] 636 |     pub fn iter_outputs(&self) -> Iter<'_, OutputDescription> {
[INFO] [stderr]     |                                        +++
[INFO] [stderr] 
[INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stderr]   --> ironfish-rust/src/transaction/value_balances.rs:50:17
[INFO] [stderr]    |
[INFO] [stderr] 50 |     pub fn iter(&self) -> hash_map::Iter<AssetIdentifier, i64> {
[INFO] [stderr]    |                 ^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stderr]    |                 |
[INFO] [stderr]    |                 the lifetime is elided here
[INFO] [stderr]    |
[INFO] [stderr]    = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stderr] help: use `'_` for type paths
[INFO] [stderr]    |
[INFO] [stderr] 50 |     pub fn iter(&self) -> hash_map::Iter<'_, AssetIdentifier, i64> {
[INFO] [stderr]    |                                          +++
[INFO] [stderr] 
[INFO] [stderr] warning: `ironfish` (lib) generated 5 warnings (run `cargo fix --lib -p ironfish` to apply 3 suggestions)
[INFO] [stderr] warning: `ironfish` (lib test) generated 5 warnings (5 duplicates)
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/lib.rs:31:1
[INFO] [stderr]    |
[INFO] [stderr] 31 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/lib.rs:66:1
[INFO] [stderr]    |
[INFO] [stderr] 66 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/lib.rs:79:1
[INFO] [stderr]    |
[INFO] [stderr] 79 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/lib.rs:86:1
[INFO] [stderr]    |
[INFO] [stderr] 86 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/lib.rs:92:1
[INFO] [stderr]    |
[INFO] [stderr] 92 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]    --> ironfish-rust-nodejs/src/lib.rs:105:1
[INFO] [stderr]     |
[INFO] [stderr] 105 | #[napi]
[INFO] [stderr]     | ^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: no expected values for `feature`
[INFO] [stderr]     = 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] [stderr]     = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]    --> ironfish-rust-nodejs/src/lib.rs:166:1
[INFO] [stderr]     |
[INFO] [stderr] 166 | #[napi]
[INFO] [stderr]     | ^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: no expected values for `feature`
[INFO] [stderr]     = 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] [stderr]     = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/mpc.rs:33:1
[INFO] [stderr]    |
[INFO] [stderr] 33 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/mpc.rs:66:1
[INFO] [stderr]    |
[INFO] [stderr] 66 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/mpc.rs:19:1
[INFO] [stderr]    |
[INFO] [stderr] 19 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/mpc.rs:51:1
[INFO] [stderr]    |
[INFO] [stderr] 51 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/nacl.rs:14:1
[INFO] [stderr]    |
[INFO] [stderr] 14 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/nacl.rs:17:1
[INFO] [stderr]    |
[INFO] [stderr] 17 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/nacl.rs:63:1
[INFO] [stderr]    |
[INFO] [stderr] 63 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/nacl.rs:74:1
[INFO] [stderr]    |
[INFO] [stderr] 74 | #[napi(js_name = "boxMessage")]
[INFO] [stderr]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]    --> ironfish-rust-nodejs/src/nacl.rs:101:1
[INFO] [stderr]     |
[INFO] [stderr] 101 | #[napi(js_name = "unboxMessage")]
[INFO] [stderr]     | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: no expected values for `feature`
[INFO] [stderr]     = 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] [stderr]     = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/nacl.rs:20:1
[INFO] [stderr]    |
[INFO] [stderr] 20 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/nacl.rs:26:1
[INFO] [stderr]    |
[INFO] [stderr] 26 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]  --> ironfish-rust-nodejs/src/rolling_filter.rs:9:1
[INFO] [stderr]   |
[INFO] [stderr] 9 | #[napi(js_name = "RollingFilter")]
[INFO] [stderr]   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]   |
[INFO] [stderr]   = note: no expected values for `feature`
[INFO] [stderr]   = 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] [stderr]   = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]   = 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] [stderr]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]   = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/rolling_filter.rs:14:1
[INFO] [stderr]    |
[INFO] [stderr] 14 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/signal_catcher.rs:10:1
[INFO] [stderr]    |
[INFO] [stderr] 10 | #[napi(js_name = "initSignalHandler")]
[INFO] [stderr]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/signal_catcher.rs:17:1
[INFO] [stderr]    |
[INFO] [stderr] 17 | #[napi(js_name = "triggerSegfault")]
[INFO] [stderr]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/structs/asset.rs:22:1
[INFO] [stderr]    |
[INFO] [stderr] 22 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/structs/asset.rs:25:1
[INFO] [stderr]    |
[INFO] [stderr] 25 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/structs/asset.rs:28:1
[INFO] [stderr]    |
[INFO] [stderr] 28 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/structs/asset.rs:31:1
[INFO] [stderr]    |
[INFO] [stderr] 31 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/structs/asset.rs:34:1
[INFO] [stderr]    |
[INFO] [stderr] 34 | #[napi(js_name = "Asset")]
[INFO] [stderr]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/structs/asset.rs:39:1
[INFO] [stderr]    |
[INFO] [stderr] 39 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/structs/note_encrypted.rs:19:1
[INFO] [stderr]    |
[INFO] [stderr] 19 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/structs/note_encrypted.rs:22:1
[INFO] [stderr]    |
[INFO] [stderr] 22 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/structs/note_encrypted.rs:25:1
[INFO] [stderr]    |
[INFO] [stderr] 25 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/structs/note_encrypted.rs:28:1
[INFO] [stderr]    |
[INFO] [stderr] 28 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/structs/note_encrypted.rs:32:1
[INFO] [stderr]    |
[INFO] [stderr] 32 | #[napi(js_name = "NoteEncrypted")]
[INFO] [stderr]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/structs/note_encrypted.rs:37:1
[INFO] [stderr]    |
[INFO] [stderr] 37 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/structs/note.rs:19:1
[INFO] [stderr]    |
[INFO] [stderr] 19 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/structs/note.rs:22:1
[INFO] [stderr]    |
[INFO] [stderr] 22 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/structs/note.rs:25:1
[INFO] [stderr]    |
[INFO] [stderr] 25 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/structs/note.rs:28:1
[INFO] [stderr]    |
[INFO] [stderr] 28 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/structs/note.rs:31:1
[INFO] [stderr]    |
[INFO] [stderr] 31 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/structs/note.rs:46:1
[INFO] [stderr]    |
[INFO] [stderr] 46 | #[napi(js_name = "Note")]
[INFO] [stderr]    | ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/structs/note.rs:51:1
[INFO] [stderr]    |
[INFO] [stderr] 51 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/structs/transaction.rs:28:1
[INFO] [stderr]    |
[INFO] [stderr] 28 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/structs/transaction.rs:31:1
[INFO] [stderr]    |
[INFO] [stderr] 31 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/structs/transaction.rs:34:1
[INFO] [stderr]    |
[INFO] [stderr] 34 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/structs/transaction.rs:37:1
[INFO] [stderr]    |
[INFO] [stderr] 37 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/structs/transaction.rs:40:1
[INFO] [stderr]    |
[INFO] [stderr] 40 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/structs/transaction.rs:43:1
[INFO] [stderr]    |
[INFO] [stderr] 43 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]    --> ironfish-rust-nodejs/src/structs/transaction.rs:310:1
[INFO] [stderr]     |
[INFO] [stderr] 310 | #[napi]
[INFO] [stderr]     | ^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: no expected values for `feature`
[INFO] [stderr]     = 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] [stderr]     = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/structs/transaction.rs:46:1
[INFO] [stderr]    |
[INFO] [stderr] 46 | #[napi(js_name = "TransactionPosted")]
[INFO] [stderr]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]   --> ironfish-rust-nodejs/src/structs/transaction.rs:51:1
[INFO] [stderr]    |
[INFO] [stderr] 51 | #[napi]
[INFO] [stderr]    | ^^^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: no expected values for `feature`
[INFO] [stderr]    = 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] [stderr]    = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]    = 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] [stderr]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]    = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]    --> ironfish-rust-nodejs/src/structs/transaction.rs:162:1
[INFO] [stderr]     |
[INFO] [stderr] 162 | #[napi(js_name = "Transaction")]
[INFO] [stderr]     | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: no expected values for `feature`
[INFO] [stderr]     = 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] [stderr]     = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]    --> ironfish-rust-nodejs/src/structs/transaction.rs:167:1
[INFO] [stderr]     |
[INFO] [stderr] 167 | #[napi]
[INFO] [stderr]     | ^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: no expected values for `feature`
[INFO] [stderr]     = 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] [stderr]     = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]    --> ironfish-rust-nodejs/src/lib.rs:110:1
[INFO] [stderr]     |
[INFO] [stderr] 110 | #[napi(constructor)]
[INFO] [stderr]     | ^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: no expected values for `feature`
[INFO] [stderr]     = 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] [stderr]     = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]    --> ironfish-rust-nodejs/src/lib.rs:116:1
[INFO] [stderr]     |
[INFO] [stderr] 116 | #[napi]
[INFO] [stderr]     | ^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: no expected values for `feature`
[INFO] [stderr]     = 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] [stderr]     = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: unexpected `cfg` condition value: `noop`
[INFO] [stderr]    --> ironfish-rust-nodejs/src/lib.rs:120:1
[INFO] [stderr]     |
[INFO] [stderr] 120 | #[napi]
[INFO] [stderr]     | ^^^^^^^
[INFO] [stderr]     |
[INFO] [stderr]     = note: no expected values for `feature`
[INFO] [stderr]     = 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] [stderr]     = help: try referring to `napi` crate for guidance on how handle this unexpected cfg
[INFO] [stderr]     = 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] [stderr]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stderr]     = note: this warning originates in the attribute macro `napi` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: `ironfish-rust-nodejs` (lib test) generated 55 warnings
[INFO] [stderr]     Finished `test` profile [unoptimized + debuginfo] target(s) in 0.20s
[INFO] [stderr]      Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/benchmarks-962819cec0d543df)
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
[INFO] [stdout] 
[INFO] [stderr]      Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/ironfish-5d1eec38b9cd8418)
[INFO] [stdout] 
[INFO] [stdout] running 69 tests
[INFO] [stdout] test assets::asset::test::test_asset_new_with_nonce ... ok
[INFO] [stdout] test keys::ephemeral::test::test_ephemeral_key_pair ... ok
[INFO] [stdout] test assets::asset::test::test_asset_new_with_nonce_invalid_nonce ... ok
[INFO] [stdout] test assets::asset::test::test_asset_name_must_be_set ... ok
[INFO] [stdout] test assets::asset::test::test_serialization ... ok
[INFO] [stdout] test keys::public_address::test::public_address_generation ... ok
[INFO] [stdout] test assets::asset_identifier::test::test_asset_native_identifier ... ok
[INFO] [stdout] test mining::mine::test::test_mine_batch_match ... ok
[INFO] [stdout] test keys::public_address::test::public_address_validation ... ok
[INFO] [stdout] test mining::mine::test::test_mine_batch_step_size ... ok
[INFO] [stdout] test keys::test::test_diffie_hellman_shared_key ... ok
[INFO] [stdout] test mining::mine::test::test_mine_bytes_lte ... ok
[INFO] [stdout] test nacl::test::test_random_bytes ... ok
[INFO] [stdout] test keys::view_keys::test::test_view_key ... ok
[INFO] [stdout] test nacl::test::test_secret_key ... ok
[INFO] [stdout] test note::test::construct_memo_from_string ... ok
[INFO] [stdout] test keys::test::test_key_generation_and_construction ... ok
[INFO] [stdout] test assets::asset::test::test_asset_new ... ok
[INFO] [stdout] test nacl::test::test_box_unbox ... ok
[INFO] [stdout] test keys::test::test_diffie_hellman_shared_key_with_other_key ... ok
[INFO] [stdout] test mining::mine::test::test_mine_batch_no_match ... ok
[INFO] [stdout] test note::test::test_plaintext_serialization ... ok
[INFO] [stdout] test keys::test::test_from_and_to_words ... ok
[INFO] [stdout] test keys::test::test_serialization ... ok
[INFO] [stdout] test note::test::test_note_encryption ... ok
[INFO] [stdout] test keys::test::test_hex_conversion ... ok
[INFO] [stdout] test serializing::aead::test::test_aead_facade ... ok
[INFO] [stdout] test serializing::test::hex_serde ... ok
[INFO] [stdout] test transaction::burns::test::test_burn_builder ... ok
[INFO] [stdout] test transaction::burns::test::test_burn_description_serialization ... ok
[INFO] [stdout] test merkle_note::test::test_new_miners_fee_key ... ok
[INFO] [stdout] test merkle_note::test::test_new_not_miners_fee_key ... ok
[INFO] [stdout] test merkle_note::test::test_view_key_encryption_with_other_key ... ok
[INFO] [stdout] test merkle_note::test::test_view_key_encryption ... ok
[INFO] [stdout] test merkle_note::test::test_output_invalid_commitment ... ok
[INFO] [stdout] test rolling_filter::test::test_rolling_filter ... ok
[INFO] [stdout] test transaction::mints::test::test_mint_builder ... ok
[INFO] [stdout] test transaction::mints::test::test_mint_description_serialization_v2_without_transfer ... ok
[INFO] [stdout] test transaction::outputs::test::test_output_round_trip ... ok
[INFO] [stdout] test transaction::mints::test::test_mint_invalid_id ... ok
[INFO] [stdout] test transaction::mints::test::test_mint_description_v1_invalid_owner ... ok
[INFO] [stdout] test transaction::mints::test::test_mint_description_serialization_v2_with_different_owner ... ok
[INFO] [stdout] test transaction::tests::test_transaction_value_overflows ... ok
[INFO] [stdout] test transaction::tests::test_transaction_version_is_checked ... ok
[INFO] [stdout] test transaction::value_balances::test::test_value_balances_checks_overflows_add ... ok
[INFO] [stdout] test transaction::value_balances::test::test_value_balances_checks_overflows_sub ... ok
[INFO] [stdout] test transaction::value_balances::test::test_value_balances_fee ... ok
[INFO] [stdout] test transaction::value_balances::test::test_value_balances_has_native_asset ... ok
[INFO] [stdout] test transaction::value_balances::test::test_value_balances_multiple_assets ... ok
[INFO] [stdout] test transaction::version::tests::test_as_u8 ... ok
[INFO] [stdout] test transaction::version::tests::test_from_u8 ... ok
[INFO] [stdout] test transaction::version::tests::test_ordering ... ok
[INFO] [stdout] test util::test::test_str_to_array_string_fits ... ok
[INFO] [stdout] test util::test::test_str_to_array_string_too_long ... ok
[INFO] [stdout] test transaction::mints::test::test_mint_description_serialization_v2_with_transfer ... ok
[INFO] [stdout] test transaction::mints::test::test_mint_description_serialization_v1 ... ok
[INFO] [stdout] test transaction::mints::test::test_mint_description_serialization_v2_with_creator_owner ... ok
[INFO] [stdout] test transaction::outputs::test::test_output_miners_fee ... ok
[INFO] [stdout] test transaction::outputs::test::test_output_not_miners_fee ... ok
[INFO] [stdout] test transaction::outputs::test::test_output_builder has been running for over 60 seconds
[INFO] [stdout] test transaction::spends::test::test_spend_builder has been running for over 60 seconds
[INFO] [stdout] test transaction::spends::test::test_spend_round_trip has been running for over 60 seconds
[INFO] [stdout] test transaction::tests::test_batch_verify has been running for over 60 seconds
[INFO] [stdout] test transaction::tests::test_batch_verify_wrong_params has been running for over 60 seconds
[INFO] [stdout] test transaction::tests::test_miners_fee has been running for over 60 seconds
[INFO] [stdout] test transaction::tests::test_transaction has been running for over 60 seconds
[INFO] [stdout] test transaction::tests::test_transaction_created_with_version_1 has been running for over 60 seconds
[INFO] [stdout] test transaction::tests::test_transaction_signature has been running for over 60 seconds
[INFO] [stdout] test transaction::tests::test_transaction_simple has been running for over 60 seconds
[INFO] [stdout] test transaction::spends::test::test_spend_round_trip ... ok
[INFO] [stdout] test transaction::tests::test_miners_fee ... ok
[INFO] [stdout] test transaction::outputs::test::test_output_builder ... ok
[INFO] [stdout] test transaction::tests::test_transaction_created_with_version_1 ... ok
[INFO] [stdout] test transaction::tests::test_transaction_simple ... ok
[INFO] [stdout] test transaction::tests::test_transaction_signature ... ok
[INFO] [stdout] test transaction::spends::test::test_spend_builder ... ok
[INFO] [stdout] test transaction::tests::test_transaction ... ok
[INFO] [stdout] test transaction::tests::test_batch_verify ... ok
[INFO] [stdout] test transaction::tests::test_batch_verify_wrong_params ... ok
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 69 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 405.55s
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]      Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/ironfish_phase2-eb95bf90a52f3531)
[INFO] [stdout] running 0 tests
[INFO] [stderr]      Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/ironfish_rust_nodejs-469b64a8481f9395)
[INFO] [stdout] 
[INFO] [stderr]      Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/ironfish_mpc-e85fc184c406140f)
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
[INFO] [stderr]      Running unittests src/bin/compute.rs (/opt/rustwide/target/debug/deps/compute-53e0995fa62f61de)
[INFO] [stdout] 
[INFO] [stderr]      Running unittests src/bin/split_params.rs (/opt/rustwide/target/debug/deps/split_params-9f28ad15156d075c)
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
[INFO] [stdout] 
[INFO] [stderr]      Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/ironfish_zkp-23735d456b14c853)
[INFO] [stdout] 
[INFO] [stdout] running 9 tests
[INFO] [stdout] test primitives::value_commitment::test::test_value_commitments_different_randomness ... ok
[INFO] [stdout] test primitives::value_commitment::test::test_value_commitments_different_value ... ok
[INFO] [stdout] test primitives::value_commitment::test::test_value_commitment ... ok
[INFO] [stdout] test primitives::value_commitment::test::test_value_commitment_new ... ok
[INFO] [stdout] test primitives::value_commitment::test::test_value_commitments_different_assets ... ok
[INFO] [stdout] test circuits::mint_asset::test::test_mint_asset_circuit ... ok
[INFO] [stdout] test circuits::output::test::test_output_circuit_with_blstrs ... ok
[INFO] [stdout] test circuits::spend::test::test_spend_circuit_with_blstrs_external_test_vectors ... ok
[INFO] [stdout] test circuits::spend::test::test_spend_circuit_with_blstrs ... ok
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 9 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 38.20s
[INFO] [stdout] 
[INFO] [stderr]      Running unittests src/bin/generate_params.rs (/opt/rustwide/target/debug/deps/generate_params-8048e77841cc33b7)
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
[INFO] [stdout] 
[INFO] [stderr]    Doc-tests benchmarks
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
[INFO] [stdout] 
[INFO] [stderr]    Doc-tests ironfish
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
[INFO] [stdout] 
[INFO] [stderr]    Doc-tests ironfish_phase2
[INFO] [stdout] 
[INFO] [stdout] running 5 tests
[INFO] [stdout] test ironfish-phase2/src/lib.rs - (line 152) ... ignored
[INFO] [stdout] test ironfish-phase2/src/lib.rs - (line 168) ... ignored
[INFO] [stdout] test ironfish-phase2/src/lib.rs - (line 184) ... ignored
[INFO] [stdout] test ironfish-phase2/src/lib.rs - (line 85) ... ignored
[INFO] [stdout] test ironfish-phase2/src/lib.rs - (line 13) ... FAILED
[INFO] [stdout] 
[INFO] [stdout] failures:
[INFO] [stdout] 
[INFO] [stdout] ---- ironfish-phase2/src/lib.rs - (line 13) stdout ----
[INFO] [stdout] error[E0432]: unresolved import `pairing::Field`
[INFO] [stdout]  --> ironfish-phase2/src/lib.rs:16:23
[INFO] [stdout]   |
[INFO] [stdout] 5 | use pairing::{Engine, Field};
[INFO] [stdout]   |                       ^^^^^ no `Field` in the root
[INFO] [stdout]   |
[INFO] [stdout]   = help: consider importing this trait instead:
[INFO] [stdout]           ff::Field
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `E: PrimeField` is not satisfied
[INFO] [stdout]    --> ironfish-phase2/src/lib.rs:27:17
[INFO] [stdout]     |
[INFO] [stdout]  16 | impl<E: Engine> Circuit<E> for CubeRoot<E> {
[INFO] [stdout]     |                 ^^^^^^^^^^ the trait `PrimeField` is not implemented for `E`
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `Circuit`
[INFO] [stdout]    --> /opt/rustwide/cargo-home/git/checkouts/bellman-25a53e31703b9ecd/1cc52ca/src/lib.rs:159:27
[INFO] [stdout]     |
[INFO] [stdout] 159 | pub trait Circuit<Scalar: PrimeField> {
[INFO] [stdout]     |                           ^^^^^^^^^^ required by this bound in `Circuit`
[INFO] [stdout] help: consider further restricting type parameter `E` with trait `PrimeField`
[INFO] [stdout]     |
[INFO] [stdout]  16 | impl<E: Engine + pairing::group::ff::PrimeField> Circuit<E> for CubeRoot<E> {
[INFO] [stdout]     |                ++++++++++++++++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `E: PrimeField` is not satisfied
[INFO] [stdout]    --> ironfish-phase2/src/lib.rs:28:23
[INFO] [stdout]     |
[INFO] [stdout]  17 |     fn synthesize<CS: ConstraintSystem<E>>(
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^ the trait `PrimeField` is not implemented for `E`
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `ConstraintSystem`
[INFO] [stdout]    --> /opt/rustwide/cargo-home/git/checkouts/bellman-25a53e31703b9ecd/1cc52ca/src/lib.rs:377:36
[INFO] [stdout]     |
[INFO] [stdout] 377 | pub trait ConstraintSystem<Scalar: PrimeField>: Sized {
[INFO] [stdout]     |                                    ^^^^^^^^^^ required by this bound in `ConstraintSystem`
[INFO] [stdout] help: consider further restricting type parameter `E` with trait `PrimeField`
[INFO] [stdout]     |
[INFO] [stdout]  16 | impl<E: Engine + pairing::group::ff::PrimeField> Circuit<E> for CubeRoot<E> {
[INFO] [stdout]     |                ++++++++++++++++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `E: PrimeField` is not satisfied
[INFO] [stdout]    --> ironfish-phase2/src/lib.rs:34:23
[INFO] [stdout]     |
[INFO] [stdout]  23 |         let root = cs.alloc(|| "root", || {
[INFO] [stdout]     |                       ^^^^^ the trait `PrimeField` is not implemented for `E`
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `bellman::ConstraintSystem::alloc`
[INFO] [stdout]    --> /opt/rustwide/cargo-home/git/checkouts/bellman-25a53e31703b9ecd/1cc52ca/src/lib.rs:377:36
[INFO] [stdout]     |
[INFO] [stdout] 377 | pub trait ConstraintSystem<Scalar: PrimeField>: Sized {
[INFO] [stdout]     |                                    ^^^^^^^^^^ required by this bound in `ConstraintSystem::alloc`
[INFO] [stdout] ...
[INFO] [stdout] 391 |     fn alloc<F, A, AR>(&mut self, annotation: A, f: F) -> Result<Variable, SynthesisError>
[INFO] [stdout]     |        ----- required by a bound in this associated function
[INFO] [stdout] help: consider further restricting type parameter `E` with trait `PrimeField`
[INFO] [stdout]     |
[INFO] [stdout]  16 | impl<E: Engine + pairing::group::ff::PrimeField> Circuit<E> for CubeRoot<E> {
[INFO] [stdout]     |                ++++++++++++++++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] error[E0308]: mismatched types
[INFO] [stdout]   --> ironfish-phase2/src/lib.rs:35:13
[INFO] [stdout]    |
[INFO] [stdout] 16 | impl<E: Engine> Circuit<E> for CubeRoot<E> {
[INFO] [stdout]    |      - expected this type parameter
[INFO] [stdout] ...
[INFO] [stdout] 24 |             self.cube_root.ok_or(SynthesisError::AssignmentMissing)
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `Result<E, SynthesisError>`, found `Result<<E as Engine>::Fr, ...>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected enum `Result<E, _>`
[INFO] [stdout]               found enum `Result<<E as Engine>::Fr, _>`
[INFO] [stdout] help: consider further restricting this bound
[INFO] [stdout]    |
[INFO] [stdout] 16 | impl<E: Engine<Fr = E>> Circuit<E> for CubeRoot<E> {
[INFO] [stdout]    |               ++++++++
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `E: PrimeField` is not satisfied
[INFO] [stdout]    --> ironfish-phase2/src/lib.rs:39:25
[INFO] [stdout]     |
[INFO] [stdout]  28 |         let square = cs.alloc(|| "square", || {
[INFO] [stdout]     |                         ^^^^^ the trait `PrimeField` is not implemented for `E`
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `bellman::ConstraintSystem::alloc`
[INFO] [stdout]    --> /opt/rustwide/cargo-home/git/checkouts/bellman-25a53e31703b9ecd/1cc52ca/src/lib.rs:377:36
[INFO] [stdout]     |
[INFO] [stdout] 377 | pub trait ConstraintSystem<Scalar: PrimeField>: Sized {
[INFO] [stdout]     |                                    ^^^^^^^^^^ required by this bound in `ConstraintSystem::alloc`
[INFO] [stdout] ...
[INFO] [stdout] 391 |     fn alloc<F, A, AR>(&mut self, annotation: A, f: F) -> Result<Variable, SynthesisError>
[INFO] [stdout]     |        ----- required by a bound in this associated function
[INFO] [stdout] help: consider further restricting type parameter `E` with trait `PrimeField`
[INFO] [stdout]     |
[INFO] [stdout]  16 | impl<E: Engine + pairing::group::ff::PrimeField> Circuit<E> for CubeRoot<E> {
[INFO] [stdout]     |                ++++++++++++++++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `square` found for associated type `<E as Engine>::Fr` in the current scope
[INFO] [stdout]   --> ironfish-phase2/src/lib.rs:42:39
[INFO] [stdout]    |
[INFO] [stdout] 31 |                 .map(|mut root| {root.square(); root })
[INFO] [stdout]    |                                       ^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ff-0.12.1/src/lib.rs:88:8
[INFO] [stdout]    |
[INFO] [stdout] 88 |     fn square(&self) -> Self;
[INFO] [stdout]    |        ------ the method is available for `<E as Engine>::Fr` here
[INFO] [stdout]    |
[INFO] [stdout]    = help: items from traits can only be used if the trait is in scope
[INFO] [stdout] help: trait `Field` which provides `square` is implemented but not in scope; perhaps you want to import it
[INFO] [stdout]    |
[INFO] [stdout]  2 + use crate::pairing::group::ff::Field;
[INFO] [stdout]    |
[INFO] [stdout] help: there is a method `sqrt` with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 31 -                 .map(|mut root| {root.square(); root })
[INFO] [stdout] 31 +                 .map(|mut root| {root.sqrt(); root })
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] error[E0308]: mismatched types
[INFO] [stdout]   --> ironfish-phase2/src/lib.rs:40:13
[INFO] [stdout]    |
[INFO] [stdout] 16 |   impl<E: Engine> Circuit<E> for CubeRoot<E> {
[INFO] [stdout]    |        - expected this type parameter
[INFO] [stdout] ...
[INFO] [stdout] 29 | /             self.cube_root
[INFO] [stdout] 30 | |                 .ok_or(SynthesisError::AssignmentMissing)
[INFO] [stdout] 31 | |                 .map(|mut root| {root.square(); root })
[INFO] [stdout]    | |_______________________________________________________^ expected `Result<E, SynthesisError>`, found `Result<<E as Engine>::Fr, ...>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected enum `Result<E, _>`
[INFO] [stdout]               found enum `Result<<E as Engine>::Fr, _>`
[INFO] [stdout] help: consider further restricting this bound
[INFO] [stdout]    |
[INFO] [stdout] 16 | impl<E: Engine<Fr = E>> Circuit<E> for CubeRoot<E> {
[INFO] [stdout]    |               ++++++++
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `E: PrimeField` is not satisfied
[INFO] [stdout]    --> ironfish-phase2/src/lib.rs:46:12
[INFO] [stdout]     |
[INFO] [stdout]  35 |         cs.enforce(
[INFO] [stdout]     |            ^^^^^^^ the trait `PrimeField` is not implemented for `E`
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `enforce`
[INFO] [stdout]    --> /opt/rustwide/cargo-home/git/checkouts/bellman-25a53e31703b9ecd/1cc52ca/src/lib.rs:377:36
[INFO] [stdout]     |
[INFO] [stdout] 377 | pub trait ConstraintSystem<Scalar: PrimeField>: Sized {
[INFO] [stdout]     |                                    ^^^^^^^^^^ required by this bound in `ConstraintSystem::enforce`
[INFO] [stdout] ...
[INFO] [stdout] 407 |     fn enforce<A, AR, LA, LB, LC>(&mut self, annotation: A, a: LA, b: LB, c: LC)
[INFO] [stdout]     |        ------- required by a bound in this associated function
[INFO] [stdout] help: consider further restricting type parameter `E` with trait `PrimeField`
[INFO] [stdout]     |
[INFO] [stdout]  16 | impl<E: Engine + pairing::group::ff::PrimeField> Circuit<E> for CubeRoot<E> {
[INFO] [stdout]     |                ++++++++++++++++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `E: PrimeField` is not satisfied
[INFO] [stdout]    --> ironfish-phase2/src/lib.rs:48:14
[INFO] [stdout]     |
[INFO] [stdout]  37 |             |lc| lc + root,
[INFO] [stdout]     |              ^^ the trait `PrimeField` is not implemented for `E`
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `LinearCombination`
[INFO] [stdout]    --> /opt/rustwide/cargo-home/git/checkouts/bellman-25a53e31703b9ecd/1cc52ca/src/lib.rs:193:38
[INFO] [stdout]     |
[INFO] [stdout] 193 | pub struct LinearCombination<Scalar: PrimeField>(Vec<(Variable, Scalar)>);
[INFO] [stdout]     |                                      ^^^^^^^^^^ required by this bound in `LinearCombination`
[INFO] [stdout] help: consider further restricting type parameter `E` with trait `PrimeField`
[INFO] [stdout]     |
[INFO] [stdout]  16 | impl<E: Engine + pairing::group::ff::PrimeField> Circuit<E> for CubeRoot<E> {
[INFO] [stdout]     |                ++++++++++++++++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] error[E0369]: cannot add `Variable` to `LinearCombination<E>`
[INFO] [stdout]   --> ironfish-phase2/src/lib.rs:48:21
[INFO] [stdout]    |
[INFO] [stdout] 37 |             |lc| lc + root,
[INFO] [stdout]    |                  -- ^ ---- Variable
[INFO] [stdout]    |                  |
[INFO] [stdout]    |                  LinearCombination<E>
[INFO] [stdout]    |
[INFO] [stdout] help: consider further restricting type parameter `E` with trait `PrimeField`
[INFO] [stdout]    |
[INFO] [stdout] 16 | impl<E: Engine + pairing::group::ff::PrimeField> Circuit<E> for CubeRoot<E> {
[INFO] [stdout]    |                ++++++++++++++++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `E: PrimeField` is not satisfied
[INFO] [stdout]    --> ironfish-phase2/src/lib.rs:49:14
[INFO] [stdout]     |
[INFO] [stdout]  38 |             |lc| lc + root,
[INFO] [stdout]     |              ^^ the trait `PrimeField` is not implemented for `E`
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `LinearCombination`
[INFO] [stdout]    --> /opt/rustwide/cargo-home/git/checkouts/bellman-25a53e31703b9ecd/1cc52ca/src/lib.rs:193:38
[INFO] [stdout]     |
[INFO] [stdout] 193 | pub struct LinearCombination<Scalar: PrimeField>(Vec<(Variable, Scalar)>);
[INFO] [stdout]     |                                      ^^^^^^^^^^ required by this bound in `LinearCombination`
[INFO] [stdout] help: consider further restricting type parameter `E` with trait `PrimeField`
[INFO] [stdout]     |
[INFO] [stdout]  16 | impl<E: Engine + pairing::group::ff::PrimeField> Circuit<E> for CubeRoot<E> {
[INFO] [stdout]     |                ++++++++++++++++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] error[E0369]: cannot add `Variable` to `LinearCombination<E>`
[INFO] [stdout]   --> ironfish-phase2/src/lib.rs:49:21
[INFO] [stdout]    |
[INFO] [stdout] 38 |             |lc| lc + root,
[INFO] [stdout]    |                  -- ^ ---- Variable
[INFO] [stdout]    |                  |
[INFO] [stdout]    |                  LinearCombination<E>
[INFO] [stdout]    |
[INFO] [stdout] help: consider further restricting type parameter `E` with trait `PrimeField`
[INFO] [stdout]    |
[INFO] [stdout] 16 | impl<E: Engine + pairing::group::ff::PrimeField> Circuit<E> for CubeRoot<E> {
[INFO] [stdout]    |                ++++++++++++++++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `E: PrimeField` is not satisfied
[INFO] [stdout]    --> ironfish-phase2/src/lib.rs:50:14
[INFO] [stdout]     |
[INFO] [stdout]  39 |             |lc| lc + square
[INFO] [stdout]     |              ^^ the trait `PrimeField` is not implemented for `E`
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `LinearCombination`
[INFO] [stdout]    --> /opt/rustwide/cargo-home/git/checkouts/bellman-25a53e31703b9ecd/1cc52ca/src/lib.rs:193:38
[INFO] [stdout]     |
[INFO] [stdout] 193 | pub struct LinearCombination<Scalar: PrimeField>(Vec<(Variable, Scalar)>);
[INFO] [stdout]     |                                      ^^^^^^^^^^ required by this bound in `LinearCombination`
[INFO] [stdout] help: consider further restricting type parameter `E` with trait `PrimeField`
[INFO] [stdout]     |
[INFO] [stdout]  16 | impl<E: Engine + pairing::group::ff::PrimeField> Circuit<E> for CubeRoot<E> {
[INFO] [stdout]     |                ++++++++++++++++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] error[E0369]: cannot add `Variable` to `LinearCombination<E>`
[INFO] [stdout]   --> ironfish-phase2/src/lib.rs:50:21
[INFO] [stdout]    |
[INFO] [stdout] 39 |             |lc| lc + square
[INFO] [stdout]    |                  -- ^ ------ Variable
[INFO] [stdout]    |                  |
[INFO] [stdout]    |                  LinearCombination<E>
[INFO] [stdout]    |
[INFO] [stdout] help: consider further restricting type parameter `E` with trait `PrimeField`
[INFO] [stdout]    |
[INFO] [stdout] 16 | impl<E: Engine + pairing::group::ff::PrimeField> Circuit<E> for CubeRoot<E> {
[INFO] [stdout]    |                ++++++++++++++++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `E: PrimeField` is not satisfied
[INFO] [stdout]    --> ironfish-phase2/src/lib.rs:54:23
[INFO] [stdout]     |
[INFO] [stdout]  43 |         let cube = cs.alloc_input(|| "cube", || {
[INFO] [stdout]     |                       ^^^^^^^^^^^ the trait `PrimeField` is not implemented for `E`
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `alloc_input`
[INFO] [stdout]    --> /opt/rustwide/cargo-home/git/checkouts/bellman-25a53e31703b9ecd/1cc52ca/src/lib.rs:377:36
[INFO] [stdout]     |
[INFO] [stdout] 377 | pub trait ConstraintSystem<Scalar: PrimeField>: Sized {
[INFO] [stdout]     |                                    ^^^^^^^^^^ required by this bound in `ConstraintSystem::alloc_input`
[INFO] [stdout] ...
[INFO] [stdout] 399 |     fn alloc_input<F, A, AR>(&mut self, annotation: A, f: F) -> Result<Variable, SynthesisError>
[INFO] [stdout]     |        ----------- required by a bound in this associated function
[INFO] [stdout] help: consider further restricting type parameter `E` with trait `PrimeField`
[INFO] [stdout]     |
[INFO] [stdout]  16 | impl<E: Engine + pairing::group::ff::PrimeField> Circuit<E> for CubeRoot<E> {
[INFO] [stdout]     |                ++++++++++++++++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `square` found for associated type `<E as Engine>::Fr` in the current scope
[INFO] [stdout]   --> ironfish-phase2/src/lib.rs:59:25
[INFO] [stdout]    |
[INFO] [stdout] 48 |                     tmp.square();
[INFO] [stdout]    |                         ^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ff-0.12.1/src/lib.rs:88:8
[INFO] [stdout]    |
[INFO] [stdout] 88 |     fn square(&self) -> Self;
[INFO] [stdout]    |        ------ the method is available for `<E as Engine>::Fr` here
[INFO] [stdout]    |
[INFO] [stdout]    = help: items from traits can only be used if the trait is in scope
[INFO] [stdout] help: trait `Field` which provides `square` is implemented but not in scope; perhaps you want to import it
[INFO] [stdout]    |
[INFO] [stdout]  2 + use crate::pairing::group::ff::Field;
[INFO] [stdout]    |
[INFO] [stdout] help: there is a method `sqrt` with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 48 -                     tmp.square();
[INFO] [stdout] 48 +                     tmp.sqrt();
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `mul_assign` found for associated type `<E as Engine>::Fr` in the current scope
[INFO] [stdout]   --> ironfish-phase2/src/lib.rs:60:25
[INFO] [stdout]    |
[INFO] [stdout] 49 |                     tmp.mul_assign(&root);
[INFO] [stdout]    |                         ^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   --> /rustc/bb624dcb4c8ab987e10c0808d92d76f3b84dd117/library/core/src/ops/arith.rs:913:8
[INFO] [stdout]    |
[INFO] [stdout]    = note: the method is available for `<E as Engine>::Fr` here
[INFO] [stdout]    |
[INFO] [stdout]    = help: items from traits can only be used if the trait is in scope
[INFO] [stdout] help: trait `MulAssign` which provides `mul_assign` is implemented but not in scope; perhaps you want to import it
[INFO] [stdout]    |
[INFO] [stdout]  2 + use std::ops::MulAssign;
[INFO] [stdout]    |
[INFO] [stdout] help: there is a method `sub_assign` with a similar name
[INFO] [stdout]    |
[INFO] [stdout] 49 -                     tmp.mul_assign(&root);
[INFO] [stdout] 49 +                     tmp.sub_assign(&root);
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] error[E0308]: mismatched types
[INFO] [stdout]   --> ironfish-phase2/src/lib.rs:55:13
[INFO] [stdout]    |
[INFO] [stdout] 16 |   impl<E: Engine> Circuit<E> for CubeRoot<E> {
[INFO] [stdout]    |        - expected this type parameter
[INFO] [stdout] ...
[INFO] [stdout] 44 | /             self.cube_root
[INFO] [stdout] 45 | |                 .ok_or(SynthesisError::AssignmentMissing)
[INFO] [stdout] 46 | |                 .map(|root| {
[INFO] [stdout] 47 | |                     let mut tmp = root;
[INFO] [stdout] ...  |
[INFO] [stdout] 50 | |                     tmp
[INFO] [stdout] 51 | |                 })
[INFO] [stdout]    | |__________________^ expected `Result<E, SynthesisError>`, found `Result<<E as Engine>::Fr, ...>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected enum `Result<E, _>`
[INFO] [stdout]               found enum `Result<<E as Engine>::Fr, _>`
[INFO] [stdout] help: consider further restricting this bound
[INFO] [stdout]    |
[INFO] [stdout] 16 | impl<E: Engine<Fr = E>> Circuit<E> for CubeRoot<E> {
[INFO] [stdout]    |               ++++++++
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `E: PrimeField` is not satisfied
[INFO] [stdout]    --> ironfish-phase2/src/lib.rs:67:12
[INFO] [stdout]     |
[INFO] [stdout]  56 |         cs.enforce(
[INFO] [stdout]     |            ^^^^^^^ the trait `PrimeField` is not implemented for `E`
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `enforce`
[INFO] [stdout]    --> /opt/rustwide/cargo-home/git/checkouts/bellman-25a53e31703b9ecd/1cc52ca/src/lib.rs:377:36
[INFO] [stdout]     |
[INFO] [stdout] 377 | pub trait ConstraintSystem<Scalar: PrimeField>: Sized {
[INFO] [stdout]     |                                    ^^^^^^^^^^ required by this bound in `ConstraintSystem::enforce`
[INFO] [stdout] ...
[INFO] [stdout] 407 |     fn enforce<A, AR, LA, LB, LC>(&mut self, annotation: A, a: LA, b: LB, c: LC)
[INFO] [stdout]     |        ------- required by a bound in this associated function
[INFO] [stdout] help: consider further restricting type parameter `E` with trait `PrimeField`
[INFO] [stdout]     |
[INFO] [stdout]  16 | impl<E: Engine + pairing::group::ff::PrimeField> Circuit<E> for CubeRoot<E> {
[INFO] [stdout]     |                ++++++++++++++++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `E: PrimeField` is not satisfied
[INFO] [stdout]    --> ironfish-phase2/src/lib.rs:69:14
[INFO] [stdout]     |
[INFO] [stdout]  58 |             |lc| lc + root,
[INFO] [stdout]     |              ^^ the trait `PrimeField` is not implemented for `E`
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `LinearCombination`
[INFO] [stdout]    --> /opt/rustwide/cargo-home/git/checkouts/bellman-25a53e31703b9ecd/1cc52ca/src/lib.rs:193:38
[INFO] [stdout]     |
[INFO] [stdout] 193 | pub struct LinearCombination<Scalar: PrimeField>(Vec<(Variable, Scalar)>);
[INFO] [stdout]     |                                      ^^^^^^^^^^ required by this bound in `LinearCombination`
[INFO] [stdout] help: consider further restricting type parameter `E` with trait `PrimeField`
[INFO] [stdout]     |
[INFO] [stdout]  16 | impl<E: Engine + pairing::group::ff::PrimeField> Circuit<E> for CubeRoot<E> {
[INFO] [stdout]     |                ++++++++++++++++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] error[E0369]: cannot add `Variable` to `LinearCombination<E>`
[INFO] [stdout]   --> ironfish-phase2/src/lib.rs:69:21
[INFO] [stdout]    |
[INFO] [stdout] 58 |             |lc| lc + root,
[INFO] [stdout]    |                  -- ^ ---- Variable
[INFO] [stdout]    |                  |
[INFO] [stdout]    |                  LinearCombination<E>
[INFO] [stdout]    |
[INFO] [stdout] help: consider further restricting type parameter `E` with trait `PrimeField`
[INFO] [stdout]    |
[INFO] [stdout] 16 | impl<E: Engine + pairing::group::ff::PrimeField> Circuit<E> for CubeRoot<E> {
[INFO] [stdout]    |                ++++++++++++++++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `E: PrimeField` is not satisfied
[INFO] [stdout]    --> ironfish-phase2/src/lib.rs:70:14
[INFO] [stdout]     |
[INFO] [stdout]  59 |             |lc| lc + square,
[INFO] [stdout]     |              ^^ the trait `PrimeField` is not implemented for `E`
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `LinearCombination`
[INFO] [stdout]    --> /opt/rustwide/cargo-home/git/checkouts/bellman-25a53e31703b9ecd/1cc52ca/src/lib.rs:193:38
[INFO] [stdout]     |
[INFO] [stdout] 193 | pub struct LinearCombination<Scalar: PrimeField>(Vec<(Variable, Scalar)>);
[INFO] [stdout]     |                                      ^^^^^^^^^^ required by this bound in `LinearCombination`
[INFO] [stdout] help: consider further restricting type parameter `E` with trait `PrimeField`
[INFO] [stdout]     |
[INFO] [stdout]  16 | impl<E: Engine + pairing::group::ff::PrimeField> Circuit<E> for CubeRoot<E> {
[INFO] [stdout]     |                ++++++++++++++++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] error[E0369]: cannot add `Variable` to `LinearCombination<E>`
[INFO] [stdout]   --> ironfish-phase2/src/lib.rs:70:21
[INFO] [stdout]    |
[INFO] [stdout] 59 |             |lc| lc + square,
[INFO] [stdout]    |                  -- ^ ------ Variable
[INFO] [stdout]    |                  |
[INFO] [stdout]    |                  LinearCombination<E>
[INFO] [stdout]    |
[INFO] [stdout] help: consider further restricting type parameter `E` with trait `PrimeField`
[INFO] [stdout]    |
[INFO] [stdout] 16 | impl<E: Engine + pairing::group::ff::PrimeField> Circuit<E> for CubeRoot<E> {
[INFO] [stdout]    |                ++++++++++++++++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `E: PrimeField` is not satisfied
[INFO] [stdout]    --> ironfish-phase2/src/lib.rs:71:14
[INFO] [stdout]     |
[INFO] [stdout]  60 |             |lc| lc + cube
[INFO] [stdout]     |              ^^ the trait `PrimeField` is not implemented for `E`
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `LinearCombination`
[INFO] [stdout]    --> /opt/rustwide/cargo-home/git/checkouts/bellman-25a53e31703b9ecd/1cc52ca/src/lib.rs:193:38
[INFO] [stdout]     |
[INFO] [stdout] 193 | pub struct LinearCombination<Scalar: PrimeField>(Vec<(Variable, Scalar)>);
[INFO] [stdout]     |                                      ^^^^^^^^^^ required by this bound in `LinearCombination`
[INFO] [stdout] help: consider further restricting type parameter `E` with trait `PrimeField`
[INFO] [stdout]     |
[INFO] [stdout]  16 | impl<E: Engine + pairing::group::ff::PrimeField> Circuit<E> for CubeRoot<E> {
[INFO] [stdout]     |                ++++++++++++++++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] error[E0369]: cannot add `Variable` to `LinearCombination<E>`
[INFO] [stdout]   --> ironfish-phase2/src/lib.rs:71:21
[INFO] [stdout]    |
[INFO] [stdout] 60 |             |lc| lc + cube
[INFO] [stdout]    |                  -- ^ ---- Variable
[INFO] [stdout]    |                  |
[INFO] [stdout]    |                  LinearCombination<E>
[INFO] [stdout]    |
[INFO] [stdout] help: consider further restricting type parameter `E` with trait `PrimeField`
[INFO] [stdout]    |
[INFO] [stdout] 16 | impl<E: Engine + pairing::group::ff::PrimeField> Circuit<E> for CubeRoot<E> {
[INFO] [stdout]    |                ++++++++++++++++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] error: aborting due to 26 previous errors
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0277, E0308, E0369, E0432, E0599.
[INFO] [stdout] For more information about an error, try `rustc --explain E0277`.
[INFO] [stdout] Couldn't compile the test.
[INFO] [stdout] 
[INFO] [stdout] failures:
[INFO] [stdout]     ironfish-phase2/src/lib.rs - (line 13)
[INFO] [stdout] 
[INFO] [stdout] test result: FAILED. 0 passed; 1 failed; 4 ignored; 0 measured; 0 filtered out; finished in 0.23s
[INFO] [stdout] 
[INFO] [stderr] error: doctest failed, to rerun pass `-p ironfish-phase2 --doc`
[INFO] running `Command { std: "docker" "inspect" "c63d42a942f04fbbe135bfee43a4cca6616682e0bb455c9a1a28144462ac7ba9", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "c63d42a942f04fbbe135bfee43a4cca6616682e0bb455c9a1a28144462ac7ba9", kill_on_drop: false }`
[INFO] [stdout] c63d42a942f04fbbe135bfee43a4cca6616682e0bb455c9a1a28144462ac7ba9
