[INFO] cloning repository https://github.com/akitamiabtc/yuv-lightning-ldk-sample
[INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/akitamiabtc/yuv-lightning-ldk-sample" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fakitamiabtc%2Fyuv-lightning-ldk-sample", kill_on_drop: false }`
[INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fakitamiabtc%2Fyuv-lightning-ldk-sample'...
[INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }`
[INFO] [stdout] e5702518f0404cd5aab24962174c39c3c7fc352b
[INFO] testing akitamiabtc/yuv-lightning-ldk-sample against master#0d162b25edd5bf0dba9a22e83b614f1113e90474 for pr-150681
[INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fakitamiabtc%2Fyuv-lightning-ldk-sample" "/workspace/builds/worker-2-tc1/source", kill_on_drop: false }`
[INFO] [stderr] Cloning into '/workspace/builds/worker-2-tc1/source'...
[INFO] [stderr] done.
[INFO] removed /workspace/builds/worker-2-tc1/source/rust-toolchain.toml
[INFO] started tweaking git repo https://github.com/akitamiabtc/yuv-lightning-ldk-sample
[INFO] finished tweaking git repo https://github.com/akitamiabtc/yuv-lightning-ldk-sample
[INFO] tweaked toml for git repo https://github.com/akitamiabtc/yuv-lightning-ldk-sample written to /workspace/builds/worker-2-tc1/source/Cargo.toml
[INFO] validating manifest of git repo https://github.com/akitamiabtc/yuv-lightning-ldk-sample on toolchain 0d162b25edd5bf0dba9a22e83b614f1113e90474
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+0d162b25edd5bf0dba9a22e83b614f1113e90474" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] crate git repo https://github.com/akitamiabtc/yuv-lightning-ldk-sample 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" "+0d162b25edd5bf0dba9a22e83b614f1113e90474" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating git repository `https://github.com/akitamiabtc/yuv.git`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]     Updating git repository `https://github.com/akitamiabtc/yuv-lightning.git`
[INFO] [stderr]     Updating git repository `https://github.com/arik-so/rust-musig2`
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded typetag v0.2.16
[INFO] [stderr]   Downloaded typetag-impl v0.2.16
[INFO] [stderr]   Downloaded jsonrpsee v0.20.3
[INFO] [stderr]   Downloaded std-shims v0.1.1
[INFO] [stderr]   Downloaded bitcoin-bech32 v0.12.1
[INFO] [stderr]   Downloaded bitcoin-internals v0.1.0
[INFO] [stderr]   Downloaded multiexp v0.4.0
[INFO] [stderr]   Downloaded esplora-client v0.6.0
[INFO] [stderr]   Downloaded core-rpc-json v0.17.0
[INFO] [stderr]   Downloaded electrum-client v0.18.0
[INFO] [stderr]   Downloaded jsonrpsee-proc-macros v0.20.3
[INFO] [stderr]   Downloaded jsonrpsee-core v0.20.3
[INFO] [stderr]   Downloaded rusty-leveldb v3.0.0
[INFO] [stderr]   Downloaded core2 v0.3.3
[INFO] [stderr]   Downloaded ureq v2.9.7
[INFO] [stderr]   Downloaded jsonrpc v0.13.0
[INFO] [stderr]   Downloaded core-rpc v0.17.0
[INFO] [stderr]   Downloaded rustls-webpki v0.102.4
[INFO] [stderr]   Downloaded rusqlite v0.28.0
[INFO] [stderr]   Downloaded jsonrpsee-server v0.20.3
[INFO] [stderr]   Downloaded bdk-macros v0.6.0
[INFO] [stderr]   Downloaded jsonrpsee-http-client v0.20.3
[INFO] [stderr]   Downloaded jsonrpsee-types v0.20.3
[INFO] [stderr]   Downloaded bitcoin v0.30.2
[INFO] [stderr]   Downloaded miniscript v10.0.0
[INFO] [stderr]   Downloaded libsqlite3-sys v0.25.2
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:845e597a41426bbf2703be69acdb67d10b6de511142d05cba7bbe119c898b2c7" "/opt/rustwide/cargo-home/bin/cargo" "+0d162b25edd5bf0dba9a22e83b614f1113e90474" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 77ac426565252785d504aec18c81e0f009560f42e077647dd94a0f4faddcf5c9
[INFO] running `Command { std: "docker" "start" "-a" "77ac426565252785d504aec18c81e0f009560f42e077647dd94a0f4faddcf5c9", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "77ac426565252785d504aec18c81e0f009560f42e077647dd94a0f4faddcf5c9", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "77ac426565252785d504aec18c81e0f009560f42e077647dd94a0f4faddcf5c9", kill_on_drop: false }`
[INFO] [stdout] 77ac426565252785d504aec18c81e0f009560f42e077647dd94a0f4faddcf5c9
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:845e597a41426bbf2703be69acdb67d10b6de511142d05cba7bbe119c898b2c7" "/opt/rustwide/cargo-home/bin/cargo" "+0d162b25edd5bf0dba9a22e83b614f1113e90474" "build" "--frozen" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] dfcf8cb7d8f672e9e1767d2e39deacf2f1d8534d3d6ef8e0e6b5bb4a0be57bac
[INFO] running `Command { std: "docker" "start" "-a" "dfcf8cb7d8f672e9e1767d2e39deacf2f1d8534d3d6ef8e0e6b5bb4a0be57bac", kill_on_drop: false }`
[INFO] [stderr]    Compiling proc-macro2 v1.0.85
[INFO] [stderr]    Compiling cfg-if v1.0.0
[INFO] [stderr]    Compiling cc v1.0.99
[INFO] [stderr]    Compiling once_cell v1.19.0
[INFO] [stderr]    Compiling serde v1.0.203
[INFO] [stderr]    Compiling log v0.4.21
[INFO] [stderr]    Compiling scopeguard v1.2.0
[INFO] [stderr]    Compiling itoa v1.0.11
[INFO] [stderr]    Compiling pin-project-lite v0.2.14
[INFO] [stderr]    Compiling zerocopy v0.7.34
[INFO] [stderr]    Compiling futures-core v0.3.30
[INFO] [stderr]    Compiling allocator-api2 v0.2.18
[INFO] [stderr]    Compiling bytes v1.6.0
[INFO] [stderr]    Compiling libc v0.2.155
[INFO] [stderr]    Compiling ppv-lite86 v0.2.17
[INFO] [stderr]    Compiling futures-sink v0.3.30
[INFO] [stderr]    Compiling ryu v1.0.18
[INFO] [stderr]    Compiling lock_api v0.4.12
[INFO] [stderr]    Compiling base64 v0.13.1
[INFO] [stderr]    Compiling serde_json v1.0.117
[INFO] [stderr]    Compiling memchr v2.7.4
[INFO] [stderr]    Compiling generic-array v0.14.7
[INFO] [stderr]    Compiling untrusted v0.9.0
[INFO] [stderr]    Compiling typenum v1.17.0
[INFO] [stderr]    Compiling futures-io v0.3.30
[INFO] [stderr]    Compiling ahash v0.8.11
[INFO] [stderr]    Compiling slab v0.4.9
[INFO] [stderr]    Compiling futures-channel v0.3.30
[INFO] [stderr]    Compiling spin v0.9.8
[INFO] [stderr]    Compiling futures-task v0.3.30
[INFO] [stderr]    Compiling bitcoin-private v0.1.0
[INFO] [stderr]    Compiling pin-utils v0.1.0
[INFO] [stderr]    Compiling tracing-core v0.1.32
[INFO] [stderr]    Compiling fnv v1.0.7
[INFO] [stderr]    Compiling hashbrown v0.14.5
[INFO] [stderr]    Compiling tinyvec_macros v0.1.1
[INFO] [stderr]    Compiling hex_lit v0.1.1
[INFO] [stderr]    Compiling percent-encoding v2.3.1
[INFO] [stderr]    Compiling bitcoin v0.30.2
[INFO] [stderr]    Compiling equivalent v1.0.1
[INFO] [stderr]    Compiling http v0.2.12
[INFO] [stderr]    Compiling tinyvec v1.6.0
[INFO] [stderr]    Compiling form_urlencoded v1.2.1
[INFO] [stderr]    Compiling httparse v1.9.4
[INFO] [stderr]    Compiling getrandom v0.2.15
[INFO] [stderr]    Compiling mio v0.8.11
[INFO] [stderr]    Compiling num_cpus v1.16.0
[INFO] [stderr]    Compiling socket2 v0.5.7
[INFO] [stderr]    Compiling try-lock v0.2.5
[INFO] [stderr]    Compiling quote v1.0.36
[INFO] [stderr]    Compiling rand_core v0.6.4
[INFO] [stderr]    Compiling unicode-bidi v0.3.15
[INFO] [stderr]    Compiling bech32 v0.9.1
[INFO] [stderr]    Compiling tower-service v0.3.2
[INFO] [stderr]    Compiling want v0.3.1
[INFO] [stderr]    Compiling rand_chacha v0.3.1
[INFO] [stderr]    Compiling subtle v2.5.0
[INFO] [stderr]    Compiling httpdate v1.0.3
[INFO] [stderr]    Compiling syn v2.0.66
[INFO] [stderr]    Compiling base64 v0.21.7
[INFO] [stderr]    Compiling thiserror v1.0.61
[INFO] [stderr]    Compiling openssl-probe v0.1.5
[INFO] [stderr]    Compiling rand v0.8.5
[INFO] [stderr]    Compiling indexmap v2.2.6
[INFO] [stderr]    Compiling const-oid v0.9.6
[INFO] [stderr]    Compiling smallvec v1.13.2
[INFO] [stderr]    Compiling unicode-normalization v0.1.23
[INFO] [stderr]    Compiling encoding_rs v0.8.34
[INFO] [stderr]    Compiling sync_wrapper v0.1.2
[INFO] [stderr]    Compiling mime v0.3.17
[INFO] [stderr]    Compiling ring v0.17.8
[INFO] [stderr]    Compiling secp256k1-sys v0.8.1
[INFO] [stderr]    Compiling ipnet v2.9.0
[INFO] [stderr]    Compiling webpki-roots v0.25.4
[INFO] [stderr]    Compiling rustls-pemfile v1.0.4
[INFO] [stderr]    Compiling nanorand v0.7.0
[INFO] [stderr]    Compiling indenter v0.3.3
[INFO] [stderr]    Compiling typeid v1.0.0
[INFO] [stderr]    Compiling core2 v0.3.3
[INFO] [stderr]    Compiling cpufeatures v0.2.12
[INFO] [stderr]    Compiling inventory v0.3.15
[INFO] [stderr]    Compiling eyre v0.6.12
[INFO] [stderr]    Compiling hex v0.4.3
[INFO] [stderr]    Compiling idna v0.5.0
[INFO] [stderr]    Compiling rustls-native-certs v0.6.3
[INFO] [stderr]    Compiling core2 v0.4.0
[INFO] [stderr]    Compiling radium v0.7.0
[INFO] [stderr]    Compiling byteorder v1.5.0
[INFO] [stderr]    Compiling flume v0.11.0
[INFO] [stderr]    Compiling tap v1.0.1
[INFO] [stderr]    Compiling wyz v0.5.1
[INFO] [stderr]    Compiling parking_lot_core v0.9.10
[INFO] [stderr]    Compiling syn v1.0.109
[INFO] [stderr]    Compiling url v2.5.2
[INFO] [stderr]    Compiling opaque-debug v0.3.1
[INFO] [stderr]    Compiling funty v2.0.0
[INFO] [stderr]    Compiling parking_lot v0.12.3
[INFO] [stderr]    Compiling anyhow v1.0.86
[INFO] [stderr]    Compiling build_const v0.2.2
[INFO] [stderr]    Compiling event-listener v2.5.3
[INFO] [stderr]    Compiling openssl-sys v0.9.102
[INFO] [stderr]    Compiling http-body v0.4.6
[INFO] [stderr]    Compiling async-lock v2.8.0
[INFO] [stderr]    Compiling crc v1.8.1
[INFO] [stderr]    Compiling fs2 v0.4.3
[INFO] [stderr]    Compiling futures-timer v3.0.3
[INFO] [stderr]    Compiling bitvec v1.0.1
[INFO] [stderr]    Compiling hex-conservative v0.1.2
[INFO] [stderr]    Compiling rustls-pki-types v1.7.0
[INFO] [stderr]    Compiling toml_datetime v0.6.6
[INFO] [stderr]    Compiling winnow v0.5.40
[INFO] [stderr]    Compiling rustc-hash v1.1.0
[INFO] [stderr]    Compiling tower-layer v0.3.2
[INFO] [stderr]    Compiling half v2.4.1
[INFO] [stderr]    Compiling crc32fast v1.4.2
[INFO] [stderr]    Compiling adler v1.0.2
[INFO] [stderr]    Compiling ciborium-io v0.2.2
[INFO] [stderr]    Compiling base16ct v0.2.0
[INFO] [stderr]    Compiling parking_lot_core v0.8.6
[INFO] [stderr]    Compiling rustls v0.22.4
[INFO] [stderr]    Compiling miniz_oxide v0.7.4
[INFO] [stderr]    Compiling snap v1.1.1
[INFO] [stderr]    Compiling libsqlite3-sys v0.25.2
[INFO] [stderr]    Compiling ciborium-ll v0.2.2
[INFO] [stderr]    Compiling errno v0.2.8
[INFO] [stderr]    Compiling instant v0.1.13
[INFO] [stderr]    Compiling bitcoin-internals v0.1.0
[INFO] [stderr]    Compiling route-recognizer v0.3.1
[INFO] [stderr]    Compiling integer-encoding v3.0.4
[INFO] [stderr]    Compiling rustversion v1.0.17
[INFO] [stderr]    Compiling foreign-types-shared v0.1.1
[INFO] [stderr]    Compiling openssl v0.10.64
[INFO] [stderr]    Compiling bitflags v2.5.0
[INFO] [stderr]    Compiling foreign-types v0.3.2
[INFO] [stderr]    Compiling crossbeam-utils v0.8.20
[INFO] [stderr]    Compiling webpki-roots v0.26.3
[INFO] [stderr]    Compiling socks v0.3.4
[INFO] [stderr]    Compiling ahash v0.7.8
[INFO] [stderr]    Compiling base64 v0.22.1
[INFO] [stderr]    Compiling parking_lot v0.11.2
[INFO] [stderr]    Compiling fxhash v0.2.1
[INFO] [stderr]    Compiling std-shims v0.1.1
[INFO] [stderr]    Compiling flate2 v1.0.30
[INFO] [stderr]    Compiling hashlink v0.8.4
[INFO] [stderr]    Compiling rustls v0.21.12
[INFO] [stderr]    Compiling signal-hook-registry v1.4.2
[INFO] [stderr]    Compiling num-traits v0.2.19
[INFO] [stderr]    Compiling crossbeam-epoch v0.9.18
[INFO] [stderr]    Compiling bitflags v1.3.2
[INFO] [stderr]    Compiling fallible-streaming-iterator v0.1.9
[INFO] [stderr]    Compiling fallible-iterator v0.2.0
[INFO] [stderr]    Compiling keccak v0.1.5
[INFO] [stderr]    Compiling signal-hook v0.3.17
[INFO] [stderr]    Compiling lazy_static v1.4.0
[INFO] [stderr]    Compiling ff v0.13.0
[INFO] [stderr]    Compiling iana-time-zone v0.1.60
[INFO] [stderr]    Compiling chunked_transfer v1.5.0
[INFO] [stderr]    Compiling signal-hook-mio v0.2.3
[INFO] [stderr]    Compiling bech32 v0.8.1
[INFO] [stderr]    Compiling home v0.5.9
[INFO] [stderr]    Compiling group v0.13.0
[INFO] [stderr]    Compiling sled v0.34.7
[INFO] [stderr]    Compiling crossterm v0.27.0
[INFO] [stderr]    Compiling rusqlite v0.28.0
[INFO] [stderr]    Compiling bitcoin-bech32 v0.12.1
[INFO] [stderr]    Compiling sct v0.7.1
[INFO] [stderr]    Compiling rustls-webpki v0.101.7
[INFO] [stderr]    Compiling rustls-webpki v0.102.4
[INFO] [stderr]    Compiling chrono v0.4.38
[INFO] [stderr]    Compiling toml_edit v0.19.15
[INFO] [stderr]    Compiling bdk-macros v0.6.0
[INFO] [stderr]    Compiling serde_derive v1.0.203
[INFO] [stderr]    Compiling zeroize_derive v1.4.2
[INFO] [stderr]    Compiling tokio-macros v2.3.0
[INFO] [stderr]    Compiling futures-macro v0.3.30
[INFO] [stderr]    Compiling tracing-attributes v0.1.27
[INFO] [stderr]    Compiling thiserror-impl v1.0.61
[INFO] [stderr]    Compiling async-trait v0.1.80
[INFO] [stderr]    Compiling typetag-impl v0.2.16
[INFO] [stderr]    Compiling event-bus-macros v0.3.5 (https://github.com/akitamiabtc/yuv.git?tag=v0.3.6#7a29c898)
[INFO] [stderr]    Compiling pin-project-internal v1.1.5
[INFO] [stderr]    Compiling openssl-macros v0.1.1
[INFO] [stderr]    Compiling event-bus v0.3.5 (https://github.com/akitamiabtc/yuv.git?tag=v0.3.6#7a29c898)
[INFO] [stderr]    Compiling tokio v1.38.0
[INFO] [stderr]    Compiling zeroize v1.8.1
[INFO] [stderr]    Compiling futures-util v0.3.30
[INFO] [stderr]    Compiling proc-macro-crate v1.3.1
[INFO] [stderr]    Compiling pin-project v1.1.5
[INFO] [stderr]    Compiling der v0.7.9
[INFO] [stderr]    Compiling tracing v0.1.40
[INFO] [stderr]    Compiling multiexp v0.4.0
[INFO] [stderr]    Compiling merlin v3.0.0
[INFO] [stderr]    Compiling block-buffer v0.10.4
[INFO] [stderr]    Compiling crypto-common v0.1.6
[INFO] [stderr]    Compiling digest v0.9.0
[INFO] [stderr]    Compiling block-buffer v0.9.0
[INFO] [stderr]    Compiling crypto-bigint v0.5.5
[INFO] [stderr]    Compiling digest v0.10.7
[INFO] [stderr]    Compiling jsonrpsee-proc-macros v0.20.3
[INFO] [stderr]    Compiling sha-1 v0.9.8
[INFO] [stderr]    Compiling hmac v0.12.1
[INFO] [stderr]    Compiling spki v0.7.3
[INFO] [stderr]    Compiling sec1 v0.7.3
[INFO] [stderr]    Compiling signature v2.2.0
[INFO] [stderr]    Compiling sha2 v0.10.8
[INFO] [stderr]    Compiling hkdf v0.12.4
[INFO] [stderr]    Compiling rfc6979 v0.4.0
[INFO] [stderr]    Compiling pkcs8 v0.10.2
[INFO] [stderr]    Compiling elliptic-curve v0.13.8
[INFO] [stderr]    Compiling ecdsa v0.16.9
[INFO] [stderr]    Compiling tokio-util v0.7.11
[INFO] [stderr]    Compiling tokio-rustls v0.24.1
[INFO] [stderr]    Compiling tokio-stream v0.1.15
[INFO] [stderr]    Compiling futures v0.3.30
[INFO] [stderr]    Compiling tower v0.4.13
[INFO] [stderr]    Compiling soketto v0.7.1
[INFO] [stderr]    Compiling k256 v0.13.3
[INFO] [stderr]    Compiling rusty-leveldb v3.0.0
[INFO] [stderr]    Compiling h2 v0.3.26
[INFO] [stderr]    Compiling bitcoin_hashes v0.12.0
[INFO] [stderr]    Compiling serde_urlencoded v0.7.1
[INFO] [stderr]    Compiling erased-serde v0.4.5
[INFO] [stderr]    Compiling beef v0.5.2
[INFO] [stderr]    Compiling ciborium v0.2.2
[INFO] [stderr]    Compiling serde_bytes v0.11.14
[INFO] [stderr]    Compiling typetag v0.2.16
[INFO] [stderr]    Compiling jsonrpsee-types v0.20.3
[INFO] [stderr]    Compiling jsonrpc v0.13.0
[INFO] [stderr]    Compiling ureq v2.9.7
[INFO] [stderr]    Compiling secp256k1 v0.27.0
[INFO] [stderr]    Compiling hyper v0.14.29
[INFO] [stderr]    Compiling yuv-pixels v0.3.5 (https://github.com/akitamiabtc/yuv.git?tag=v0.3.6#7a29c898)
[INFO] [stderr]    Compiling core-rpc-json v0.17.0
[INFO] [stderr]    Compiling electrum-client v0.18.0
[INFO] [stderr]    Compiling miniscript v10.0.0
[INFO] [stderr]    Compiling esplora-client v0.6.0
[INFO] [stderr]    Compiling bulletproof v0.3.5 (https://github.com/akitamiabtc/yuv.git?tag=v0.3.6#7a29c898)
[INFO] [stderr]    Compiling hyper-rustls v0.24.2
[INFO] [stderr]    Compiling jsonrpsee-core v0.20.3
[INFO] [stderr]    Compiling reqwest v0.11.27
[INFO] [stderr]    Compiling jsonrpc v0.3.5 (https://github.com/akitamiabtc/yuv.git?tag=v0.3.6#7a29c898)
[INFO] [stderr]    Compiling jsonrpsee-http-client v0.20.3
[INFO] [stderr]    Compiling jsonrpsee-server v0.20.3
[INFO] [stderr]    Compiling bitcoin-client v0.3.5 (https://github.com/akitamiabtc/yuv.git?tag=v0.3.6#7a29c898)
[INFO] [stderr]    Compiling core-rpc v0.17.0
[INFO] [stderr]    Compiling bdk v0.29.0+fix.1 (https://github.com/akitamiabtc/yuv.git?tag=v0.3.6#7a29c898)
[INFO] [stderr]    Compiling jsonrpsee v0.20.3
[INFO] [stderr]    Compiling yuv-types v0.3.5 (https://github.com/akitamiabtc/yuv.git?tag=v0.3.6#7a29c898)
[INFO] [stderr]    Compiling lightning v0.3.1 (https://github.com/akitamiabtc/yuv-lightning.git?tag=v0.3.1%2Blightning-0.0.123#259f597c)
[INFO] [stderr]    Compiling yuv-storage v0.3.5 (https://github.com/akitamiabtc/yuv.git?tag=v0.3.6#7a29c898)
[INFO] [stderr]    Compiling yuv-rpc-api v0.3.5 (https://github.com/akitamiabtc/yuv.git?tag=v0.3.6#7a29c898)
[INFO] [stderr]    Compiling ydk v0.3.5 (https://github.com/akitamiabtc/yuv.git?tag=v0.3.6#7a29c898)
[INFO] [stderr]    Compiling lightning-rapid-gossip-sync v0.3.1 (https://github.com/akitamiabtc/yuv-lightning.git?tag=v0.3.1%2Blightning-0.0.123#259f597c)
[INFO] [stderr]    Compiling lightning-block-sync v0.3.1 (https://github.com/akitamiabtc/yuv-lightning.git?tag=v0.3.1%2Blightning-0.0.123#259f597c)
[INFO] [stderr]    Compiling lightning-net-tokio v0.3.1 (https://github.com/akitamiabtc/yuv-lightning.git?tag=v0.3.1%2Blightning-0.0.123#259f597c)
[INFO] [stderr]    Compiling lightning-persister v0.3.1 (https://github.com/akitamiabtc/yuv-lightning.git?tag=v0.3.1%2Blightning-0.0.123#259f597c)
[INFO] [stderr]    Compiling lightning-invoice v0.3.1 (https://github.com/akitamiabtc/yuv-lightning.git?tag=v0.3.1%2Blightning-0.0.123#259f597c)
[INFO] [stderr]    Compiling lightning-background-processor v0.3.1 (https://github.com/akitamiabtc/yuv-lightning.git?tag=v0.3.1%2Blightning-0.0.123#259f597c)
[INFO] [stderr]    Compiling yuv-ln-node v0.3.1 (/opt/rustwide/workdir)
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/bitcoind_client.rs:314:7
[INFO] [stdout]     |
[INFO] [stdout] 314 | / ...   log_error!(logger,
[INFO] [stdout] 315 | | ...                  "Warning, failed to broadcast a transaction, this is likely okay but may indicate an error: {}\nTransaction:...
[INFO] [stdout] 316 | | ...                  err_str,
[INFO] [stdout] 317 | | ...                  tx_serialized);
[INFO] [stdout]     | |___________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/bitcoind_client.rs:314:7
[INFO] [stdout]     |
[INFO] [stdout] 314 | / ...   log_error!(logger,
[INFO] [stdout] 315 | | ...                  "Warning, failed to broadcast a transaction, this is likely okay but may indicate an error: {}\nTransaction:...
[INFO] [stdout] 316 | | ...                  err_str,
[INFO] [stdout] 317 | | ...                  tx_serialized);
[INFO] [stdout]     | |___________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/bitcoind_client.rs:314:7
[INFO] [stdout]     |
[INFO] [stdout] 314 | / ...   log_error!(logger,
[INFO] [stdout] 315 | | ...                  "Warning, failed to broadcast a transaction, this is likely okay but may indicate an error: {}\nTransaction:...
[INFO] [stdout] 316 | | ...                  err_str,
[INFO] [stdout] 317 | | ...                  tx_serialized);
[INFO] [stdout]     | |___________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/bitcoind_client.rs:314:7
[INFO] [stdout]     |
[INFO] [stdout] 314 | / ...   log_error!(logger,
[INFO] [stdout] 315 | | ...                  "Warning, failed to broadcast a transaction, this is likely okay but may indicate an error: {}\nTransaction:...
[INFO] [stdout] 316 | | ...                  err_str,
[INFO] [stdout] 317 | | ...                  tx_serialized);
[INFO] [stdout]     | |___________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/bitcoind_client.rs:314:7
[INFO] [stdout]     |
[INFO] [stdout] 314 | / ...   log_error!(logger,
[INFO] [stdout] 315 | | ...                  "Warning, failed to broadcast a transaction, this is likely okay but may indicate an error: {}\nTransaction:...
[INFO] [stdout] 316 | | ...                  err_str,
[INFO] [stdout] 317 | | ...                  tx_serialized);
[INFO] [stdout]     | |___________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/bitcoind_client.rs:314:7
[INFO] [stdout]     |
[INFO] [stdout] 314 | / ...   log_error!(logger,
[INFO] [stdout] 315 | | ...                  "Warning, failed to broadcast a transaction, this is likely okay but may indicate an error: {}\nTransaction:...
[INFO] [stdout] 316 | | ...                  err_str,
[INFO] [stdout] 317 | | ...                  tx_serialized);
[INFO] [stdout]     | |___________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/bitcoind_client.rs:314:7
[INFO] [stdout]     |
[INFO] [stdout] 314 | / ...   log_error!(logger,
[INFO] [stdout] 315 | | ...                  "Warning, failed to broadcast a transaction, this is likely okay but may indicate an error: {}\nTransaction:...
[INFO] [stdout] 316 | | ...                  err_str,
[INFO] [stdout] 317 | | ...                  tx_serialized);
[INFO] [stdout]     | |___________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/bitcoind_client.rs:314:7
[INFO] [stdout]     |
[INFO] [stdout] 314 | / ...   log_error!(logger,
[INFO] [stdout] 315 | | ...                  "Warning, failed to broadcast a transaction, this is likely okay but may indicate an error: {}\nTransaction:...
[INFO] [stdout] 316 | | ...                  err_str,
[INFO] [stdout] 317 | | ...                  tx_serialized);
[INFO] [stdout]     | |___________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/bitcoind_client.rs:314:7
[INFO] [stdout]     |
[INFO] [stdout] 314 | / ...   log_error!(logger,
[INFO] [stdout] 315 | | ...                  "Warning, failed to broadcast a transaction, this is likely okay but may indicate an error: {}\nTransaction:...
[INFO] [stdout] 316 | | ...                  err_str,
[INFO] [stdout] 317 | | ...                  tx_serialized);
[INFO] [stdout]     | |___________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/bitcoind_client.rs:314:7
[INFO] [stdout]     |
[INFO] [stdout] 314 | / ...   log_error!(logger,
[INFO] [stdout] 315 | | ...                  "Warning, failed to broadcast a transaction, this is likely okay but may indicate an error: {}\nTransaction:...
[INFO] [stdout] 316 | | ...                  err_str,
[INFO] [stdout] 317 | | ...                  tx_serialized);
[INFO] [stdout]     | |___________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/bitcoind_client.rs:314:7
[INFO] [stdout]     |
[INFO] [stdout] 314 | / ...   log_error!(logger,
[INFO] [stdout] 315 | | ...                  "Warning, failed to broadcast a transaction, this is likely okay but may indicate an error: {}\nTransaction:...
[INFO] [stdout] 316 | | ...                  err_str,
[INFO] [stdout] 317 | | ...                  tx_serialized);
[INFO] [stdout]     | |___________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/bitcoind_client.rs:314:7
[INFO] [stdout]     |
[INFO] [stdout] 314 | / ...   log_error!(logger,
[INFO] [stdout] 315 | | ...                  "Warning, failed to broadcast a transaction, this is likely okay but may indicate an error: {}\nTransaction:...
[INFO] [stdout] 316 | | ...                  err_str,
[INFO] [stdout] 317 | | ...                  tx_serialized);
[INFO] [stdout]     | |___________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/bitcoind_client.rs:314:7
[INFO] [stdout]     |
[INFO] [stdout] 314 | / ...   log_error!(logger,
[INFO] [stdout] 315 | | ...                  "Warning, failed to broadcast a transaction, this is likely okay but may indicate an error: {}\nTransaction:...
[INFO] [stdout] 316 | | ...                  err_str,
[INFO] [stdout] 317 | | ...                  tx_serialized);
[INFO] [stdout]     | |___________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/bitcoind_client.rs:314:7
[INFO] [stdout]     |
[INFO] [stdout] 314 | / ...   log_error!(logger,
[INFO] [stdout] 315 | | ...                  "Warning, failed to broadcast a transaction, this is likely okay but may indicate an error: {}\nTransaction:...
[INFO] [stdout] 316 | | ...                  err_str,
[INFO] [stdout] 317 | | ...                  tx_serialized);
[INFO] [stdout]     | |___________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/bitcoind_client.rs:314:7
[INFO] [stdout]     |
[INFO] [stdout] 314 | / ...   log_error!(logger,
[INFO] [stdout] 315 | | ...                  "Warning, failed to broadcast a transaction, this is likely okay but may indicate an error: {}\nTransaction:...
[INFO] [stdout] 316 | | ...                  err_str,
[INFO] [stdout] 317 | | ...                  tx_serialized);
[INFO] [stdout]     | |___________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/bitcoind_client.rs:314:7
[INFO] [stdout]     |
[INFO] [stdout] 314 | / ...   log_error!(logger,
[INFO] [stdout] 315 | | ...                  "Warning, failed to broadcast a transaction, this is likely okay but may indicate an error: {}\nTransaction:...
[INFO] [stdout] 316 | | ...                  err_str,
[INFO] [stdout] 317 | | ...                  tx_serialized);
[INFO] [stdout]     | |___________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/bitcoind_client.rs:314:7
[INFO] [stdout]     |
[INFO] [stdout] 314 | / ...   log_error!(logger,
[INFO] [stdout] 315 | | ...                  "Warning, failed to broadcast a transaction, this is likely okay but may indicate an error: {}\nTransaction:...
[INFO] [stdout] 316 | | ...                  err_str,
[INFO] [stdout] 317 | | ...                  tx_serialized);
[INFO] [stdout]     | |___________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/bitcoind_client.rs:314:7
[INFO] [stdout]     |
[INFO] [stdout] 314 | / ...   log_error!(logger,
[INFO] [stdout] 315 | | ...                  "Warning, failed to broadcast a transaction, this is likely okay but may indicate an error: {}\nTransaction:...
[INFO] [stdout] 316 | | ...                  err_str,
[INFO] [stdout] 317 | | ...                  tx_serialized);
[INFO] [stdout]     | |___________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/bitcoind_client.rs:314:7
[INFO] [stdout]     |
[INFO] [stdout] 314 | / ...   log_error!(logger,
[INFO] [stdout] 315 | | ...                  "Warning, failed to broadcast a transaction, this is likely okay but may indicate an error: {}\nTransaction:...
[INFO] [stdout] 316 | | ...                  err_str,
[INFO] [stdout] 317 | | ...                  tx_serialized);
[INFO] [stdout]     | |___________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/bitcoind_client.rs:314:7
[INFO] [stdout]     |
[INFO] [stdout] 314 | / ...   log_error!(logger,
[INFO] [stdout] 315 | | ...                  "Warning, failed to broadcast a transaction, this is likely okay but may indicate an error: {}\nTransaction:...
[INFO] [stdout] 316 | | ...                  err_str,
[INFO] [stdout] 317 | | ...                  tx_serialized);
[INFO] [stdout]     | |___________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/bitcoind_client.rs:314:7
[INFO] [stdout]     |
[INFO] [stdout] 314 | / ...   log_error!(logger,
[INFO] [stdout] 315 | | ...                  "Warning, failed to broadcast a transaction, this is likely okay but may indicate an error: {}\nTransaction:...
[INFO] [stdout] 316 | | ...                  err_str,
[INFO] [stdout] 317 | | ...                  tx_serialized);
[INFO] [stdout]     | |___________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/bitcoind_client.rs:314:7
[INFO] [stdout]     |
[INFO] [stdout] 314 | / ...   log_error!(logger,
[INFO] [stdout] 315 | | ...                  "Warning, failed to broadcast a transaction, this is likely okay but may indicate an error: {}\nTransaction:...
[INFO] [stdout] 316 | | ...                  err_str,
[INFO] [stdout] 317 | | ...                  tx_serialized);
[INFO] [stdout]     | |___________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/bitcoind_client.rs:314:7
[INFO] [stdout]     |
[INFO] [stdout] 314 | / ...   log_error!(logger,
[INFO] [stdout] 315 | | ...                  "Warning, failed to broadcast a transaction, this is likely okay but may indicate an error: {}\nTransaction:...
[INFO] [stdout] 316 | | ...                  err_str,
[INFO] [stdout] 317 | | ...                  tx_serialized);
[INFO] [stdout]     | |___________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/bitcoind_client.rs:314:7
[INFO] [stdout]     |
[INFO] [stdout] 314 | / ...   log_error!(logger,
[INFO] [stdout] 315 | | ...                  "Warning, failed to broadcast a transaction, this is likely okay but may indicate an error: {}\nTransaction:...
[INFO] [stdout] 316 | | ...                  err_str,
[INFO] [stdout] 317 | | ...                  tx_serialized);
[INFO] [stdout]     | |___________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/bitcoind_client.rs:314:7
[INFO] [stdout]     |
[INFO] [stdout] 314 | / ...   log_error!(logger,
[INFO] [stdout] 315 | | ...                  "Warning, failed to broadcast a transaction, this is likely okay but may indicate an error: {}\nTransaction:...
[INFO] [stdout] 316 | | ...                  err_str,
[INFO] [stdout] 317 | | ...                  tx_serialized);
[INFO] [stdout]     | |___________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/bitcoind_client.rs:314:7
[INFO] [stdout]     |
[INFO] [stdout] 314 | / ...   log_error!(logger,
[INFO] [stdout] 315 | | ...                  "Warning, failed to broadcast a transaction, this is likely okay but may indicate an error: {}\nTransaction:...
[INFO] [stdout] 316 | | ...                  err_str,
[INFO] [stdout] 317 | | ...                  tx_serialized);
[INFO] [stdout]     | |___________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/bitcoind_client.rs:314:7
[INFO] [stdout]     |
[INFO] [stdout] 314 | / ...   log_error!(logger,
[INFO] [stdout] 315 | | ...                  "Warning, failed to broadcast a transaction, this is likely okay but may indicate an error: {}\nTransaction:...
[INFO] [stdout] 316 | | ...                  err_str,
[INFO] [stdout] 317 | | ...                  tx_serialized);
[INFO] [stdout]     | |___________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:116:6
[INFO] [stdout]     |
[INFO] [stdout] 116 |                     lightning::log_error!(logger, "Failed to get change YUV pubkey");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:116:6
[INFO] [stdout]     |
[INFO] [stdout] 116 |                     lightning::log_error!(logger, "Failed to get change YUV pubkey");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/sweep.rs:116:6
[INFO] [stdout]     |
[INFO] [stdout] 116 |                     lightning::log_error!(logger, "Failed to get change YUV pubkey");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:116:6
[INFO] [stdout]     |
[INFO] [stdout] 116 |                     lightning::log_error!(logger, "Failed to get change YUV pubkey");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/sweep.rs:116:6
[INFO] [stdout]     |
[INFO] [stdout] 116 |                     lightning::log_error!(logger, "Failed to get change YUV pubkey");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/sweep.rs:116:6
[INFO] [stdout]     |
[INFO] [stdout] 116 |                     lightning::log_error!(logger, "Failed to get change YUV pubkey");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:116:6
[INFO] [stdout]     |
[INFO] [stdout] 116 |                     lightning::log_error!(logger, "Failed to get change YUV pubkey");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/sweep.rs:116:6
[INFO] [stdout]     |
[INFO] [stdout] 116 |                     lightning::log_error!(logger, "Failed to get change YUV pubkey");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/sweep.rs:116:6
[INFO] [stdout]     |
[INFO] [stdout] 116 |                     lightning::log_error!(logger, "Failed to get change YUV pubkey");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/sweep.rs:116:6
[INFO] [stdout]     |
[INFO] [stdout] 116 |                     lightning::log_error!(logger, "Failed to get change YUV pubkey");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:116:6
[INFO] [stdout]     |
[INFO] [stdout] 116 |                     lightning::log_error!(logger, "Failed to get change YUV pubkey");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/sweep.rs:116:6
[INFO] [stdout]     |
[INFO] [stdout] 116 |                     lightning::log_error!(logger, "Failed to get change YUV pubkey");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/sweep.rs:116:6
[INFO] [stdout]     |
[INFO] [stdout] 116 |                     lightning::log_error!(logger, "Failed to get change YUV pubkey");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/sweep.rs:116:6
[INFO] [stdout]     |
[INFO] [stdout] 116 |                     lightning::log_error!(logger, "Failed to get change YUV pubkey");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/sweep.rs:116:6
[INFO] [stdout]     |
[INFO] [stdout] 116 |                     lightning::log_error!(logger, "Failed to get change YUV pubkey");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:116:6
[INFO] [stdout]     |
[INFO] [stdout] 116 |                     lightning::log_error!(logger, "Failed to get change YUV pubkey");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/sweep.rs:116:6
[INFO] [stdout]     |
[INFO] [stdout] 116 |                     lightning::log_error!(logger, "Failed to get change YUV pubkey");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/sweep.rs:116:6
[INFO] [stdout]     |
[INFO] [stdout] 116 |                     lightning::log_error!(logger, "Failed to get change YUV pubkey");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/sweep.rs:116:6
[INFO] [stdout]     |
[INFO] [stdout] 116 |                     lightning::log_error!(logger, "Failed to get change YUV pubkey");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/sweep.rs:116:6
[INFO] [stdout]     |
[INFO] [stdout] 116 |                     lightning::log_error!(logger, "Failed to get change YUV pubkey");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/sweep.rs:116:6
[INFO] [stdout]     |
[INFO] [stdout] 116 |                     lightning::log_error!(logger, "Failed to get change YUV pubkey");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:116:6
[INFO] [stdout]     |
[INFO] [stdout] 116 |                     lightning::log_error!(logger, "Failed to get change YUV pubkey");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/sweep.rs:116:6
[INFO] [stdout]     |
[INFO] [stdout] 116 |                     lightning::log_error!(logger, "Failed to get change YUV pubkey");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/sweep.rs:116:6
[INFO] [stdout]     |
[INFO] [stdout] 116 |                     lightning::log_error!(logger, "Failed to get change YUV pubkey");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/sweep.rs:116:6
[INFO] [stdout]     |
[INFO] [stdout] 116 |                     lightning::log_error!(logger, "Failed to get change YUV pubkey");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/sweep.rs:116:6
[INFO] [stdout]     |
[INFO] [stdout] 116 |                     lightning::log_error!(logger, "Failed to get change YUV pubkey");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/sweep.rs:116:6
[INFO] [stdout]     |
[INFO] [stdout] 116 |                     lightning::log_error!(logger, "Failed to get change YUV pubkey");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:147:9
[INFO] [stdout]     |
[INFO] [stdout] 147 | / ...                   lightning::log_error!(
[INFO] [stdout] 148 | | ...                       logger,
[INFO] [stdout] 149 | | ...                       "Invalid spending YUV tx: {reason}; {:?}, proofs: {:?}",
[INFO] [stdout] 150 | | ...                       yuv_tx.bitcoin_tx.raw_hex(),
[INFO] [stdout] 151 | | ...                       yuv_tx.tx_type,
[INFO] [stdout] 152 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:147:9
[INFO] [stdout]     |
[INFO] [stdout] 147 | / ...                   lightning::log_error!(
[INFO] [stdout] 148 | | ...                       logger,
[INFO] [stdout] 149 | | ...                       "Invalid spending YUV tx: {reason}; {:?}, proofs: {:?}",
[INFO] [stdout] 150 | | ...                       yuv_tx.bitcoin_tx.raw_hex(),
[INFO] [stdout] 151 | | ...                       yuv_tx.tx_type,
[INFO] [stdout] 152 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/sweep.rs:147:9
[INFO] [stdout]     |
[INFO] [stdout] 147 | / ...                   lightning::log_error!(
[INFO] [stdout] 148 | | ...                       logger,
[INFO] [stdout] 149 | | ...                       "Invalid spending YUV tx: {reason}; {:?}, proofs: {:?}",
[INFO] [stdout] 150 | | ...                       yuv_tx.bitcoin_tx.raw_hex(),
[INFO] [stdout] 151 | | ...                       yuv_tx.tx_type,
[INFO] [stdout] 152 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:147:9
[INFO] [stdout]     |
[INFO] [stdout] 147 | / ...                   lightning::log_error!(
[INFO] [stdout] 148 | | ...                       logger,
[INFO] [stdout] 149 | | ...                       "Invalid spending YUV tx: {reason}; {:?}, proofs: {:?}",
[INFO] [stdout] 150 | | ...                       yuv_tx.bitcoin_tx.raw_hex(),
[INFO] [stdout] 151 | | ...                       yuv_tx.tx_type,
[INFO] [stdout] 152 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/sweep.rs:147:9
[INFO] [stdout]     |
[INFO] [stdout] 147 | / ...                   lightning::log_error!(
[INFO] [stdout] 148 | | ...                       logger,
[INFO] [stdout] 149 | | ...                       "Invalid spending YUV tx: {reason}; {:?}, proofs: {:?}",
[INFO] [stdout] 150 | | ...                       yuv_tx.bitcoin_tx.raw_hex(),
[INFO] [stdout] 151 | | ...                       yuv_tx.tx_type,
[INFO] [stdout] 152 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/sweep.rs:147:9
[INFO] [stdout]     |
[INFO] [stdout] 147 | / ...                   lightning::log_error!(
[INFO] [stdout] 148 | | ...                       logger,
[INFO] [stdout] 149 | | ...                       "Invalid spending YUV tx: {reason}; {:?}, proofs: {:?}",
[INFO] [stdout] 150 | | ...                       yuv_tx.bitcoin_tx.raw_hex(),
[INFO] [stdout] 151 | | ...                       yuv_tx.tx_type,
[INFO] [stdout] 152 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:147:9
[INFO] [stdout]     |
[INFO] [stdout] 147 | / ...                   lightning::log_error!(
[INFO] [stdout] 148 | | ...                       logger,
[INFO] [stdout] 149 | | ...                       "Invalid spending YUV tx: {reason}; {:?}, proofs: {:?}",
[INFO] [stdout] 150 | | ...                       yuv_tx.bitcoin_tx.raw_hex(),
[INFO] [stdout] 151 | | ...                       yuv_tx.tx_type,
[INFO] [stdout] 152 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/sweep.rs:147:9
[INFO] [stdout]     |
[INFO] [stdout] 147 | / ...                   lightning::log_error!(
[INFO] [stdout] 148 | | ...                       logger,
[INFO] [stdout] 149 | | ...                       "Invalid spending YUV tx: {reason}; {:?}, proofs: {:?}",
[INFO] [stdout] 150 | | ...                       yuv_tx.bitcoin_tx.raw_hex(),
[INFO] [stdout] 151 | | ...                       yuv_tx.tx_type,
[INFO] [stdout] 152 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/sweep.rs:147:9
[INFO] [stdout]     |
[INFO] [stdout] 147 | / ...                   lightning::log_error!(
[INFO] [stdout] 148 | | ...                       logger,
[INFO] [stdout] 149 | | ...                       "Invalid spending YUV tx: {reason}; {:?}, proofs: {:?}",
[INFO] [stdout] 150 | | ...                       yuv_tx.bitcoin_tx.raw_hex(),
[INFO] [stdout] 151 | | ...                       yuv_tx.tx_type,
[INFO] [stdout] 152 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/sweep.rs:147:9
[INFO] [stdout]     |
[INFO] [stdout] 147 | / ...                   lightning::log_error!(
[INFO] [stdout] 148 | | ...                       logger,
[INFO] [stdout] 149 | | ...                       "Invalid spending YUV tx: {reason}; {:?}, proofs: {:?}",
[INFO] [stdout] 150 | | ...                       yuv_tx.bitcoin_tx.raw_hex(),
[INFO] [stdout] 151 | | ...                       yuv_tx.tx_type,
[INFO] [stdout] 152 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:147:9
[INFO] [stdout]     |
[INFO] [stdout] 147 | / ...                   lightning::log_error!(
[INFO] [stdout] 148 | | ...                       logger,
[INFO] [stdout] 149 | | ...                       "Invalid spending YUV tx: {reason}; {:?}, proofs: {:?}",
[INFO] [stdout] 150 | | ...                       yuv_tx.bitcoin_tx.raw_hex(),
[INFO] [stdout] 151 | | ...                       yuv_tx.tx_type,
[INFO] [stdout] 152 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/sweep.rs:147:9
[INFO] [stdout]     |
[INFO] [stdout] 147 | / ...                   lightning::log_error!(
[INFO] [stdout] 148 | | ...                       logger,
[INFO] [stdout] 149 | | ...                       "Invalid spending YUV tx: {reason}; {:?}, proofs: {:?}",
[INFO] [stdout] 150 | | ...                       yuv_tx.bitcoin_tx.raw_hex(),
[INFO] [stdout] 151 | | ...                       yuv_tx.tx_type,
[INFO] [stdout] 152 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/sweep.rs:147:9
[INFO] [stdout]     |
[INFO] [stdout] 147 | / ...                   lightning::log_error!(
[INFO] [stdout] 148 | | ...                       logger,
[INFO] [stdout] 149 | | ...                       "Invalid spending YUV tx: {reason}; {:?}, proofs: {:?}",
[INFO] [stdout] 150 | | ...                       yuv_tx.bitcoin_tx.raw_hex(),
[INFO] [stdout] 151 | | ...                       yuv_tx.tx_type,
[INFO] [stdout] 152 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/sweep.rs:147:9
[INFO] [stdout]     |
[INFO] [stdout] 147 | / ...                   lightning::log_error!(
[INFO] [stdout] 148 | | ...                       logger,
[INFO] [stdout] 149 | | ...                       "Invalid spending YUV tx: {reason}; {:?}, proofs: {:?}",
[INFO] [stdout] 150 | | ...                       yuv_tx.bitcoin_tx.raw_hex(),
[INFO] [stdout] 151 | | ...                       yuv_tx.tx_type,
[INFO] [stdout] 152 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/sweep.rs:147:9
[INFO] [stdout]     |
[INFO] [stdout] 147 | / ...                   lightning::log_error!(
[INFO] [stdout] 148 | | ...                       logger,
[INFO] [stdout] 149 | | ...                       "Invalid spending YUV tx: {reason}; {:?}, proofs: {:?}",
[INFO] [stdout] 150 | | ...                       yuv_tx.bitcoin_tx.raw_hex(),
[INFO] [stdout] 151 | | ...                       yuv_tx.tx_type,
[INFO] [stdout] 152 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:147:9
[INFO] [stdout]     |
[INFO] [stdout] 147 | / ...                   lightning::log_error!(
[INFO] [stdout] 148 | | ...                       logger,
[INFO] [stdout] 149 | | ...                       "Invalid spending YUV tx: {reason}; {:?}, proofs: {:?}",
[INFO] [stdout] 150 | | ...                       yuv_tx.bitcoin_tx.raw_hex(),
[INFO] [stdout] 151 | | ...                       yuv_tx.tx_type,
[INFO] [stdout] 152 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/sweep.rs:147:9
[INFO] [stdout]     |
[INFO] [stdout] 147 | / ...                   lightning::log_error!(
[INFO] [stdout] 148 | | ...                       logger,
[INFO] [stdout] 149 | | ...                       "Invalid spending YUV tx: {reason}; {:?}, proofs: {:?}",
[INFO] [stdout] 150 | | ...                       yuv_tx.bitcoin_tx.raw_hex(),
[INFO] [stdout] 151 | | ...                       yuv_tx.tx_type,
[INFO] [stdout] 152 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/sweep.rs:147:9
[INFO] [stdout]     |
[INFO] [stdout] 147 | / ...                   lightning::log_error!(
[INFO] [stdout] 148 | | ...                       logger,
[INFO] [stdout] 149 | | ...                       "Invalid spending YUV tx: {reason}; {:?}, proofs: {:?}",
[INFO] [stdout] 150 | | ...                       yuv_tx.bitcoin_tx.raw_hex(),
[INFO] [stdout] 151 | | ...                       yuv_tx.tx_type,
[INFO] [stdout] 152 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/sweep.rs:147:9
[INFO] [stdout]     |
[INFO] [stdout] 147 | / ...                   lightning::log_error!(
[INFO] [stdout] 148 | | ...                       logger,
[INFO] [stdout] 149 | | ...                       "Invalid spending YUV tx: {reason}; {:?}, proofs: {:?}",
[INFO] [stdout] 150 | | ...                       yuv_tx.bitcoin_tx.raw_hex(),
[INFO] [stdout] 151 | | ...                       yuv_tx.tx_type,
[INFO] [stdout] 152 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/sweep.rs:147:9
[INFO] [stdout]     |
[INFO] [stdout] 147 | / ...                   lightning::log_error!(
[INFO] [stdout] 148 | | ...                       logger,
[INFO] [stdout] 149 | | ...                       "Invalid spending YUV tx: {reason}; {:?}, proofs: {:?}",
[INFO] [stdout] 150 | | ...                       yuv_tx.bitcoin_tx.raw_hex(),
[INFO] [stdout] 151 | | ...                       yuv_tx.tx_type,
[INFO] [stdout] 152 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/sweep.rs:147:9
[INFO] [stdout]     |
[INFO] [stdout] 147 | / ...                   lightning::log_error!(
[INFO] [stdout] 148 | | ...                       logger,
[INFO] [stdout] 149 | | ...                       "Invalid spending YUV tx: {reason}; {:?}, proofs: {:?}",
[INFO] [stdout] 150 | | ...                       yuv_tx.bitcoin_tx.raw_hex(),
[INFO] [stdout] 151 | | ...                       yuv_tx.tx_type,
[INFO] [stdout] 152 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:147:9
[INFO] [stdout]     |
[INFO] [stdout] 147 | / ...                   lightning::log_error!(
[INFO] [stdout] 148 | | ...                       logger,
[INFO] [stdout] 149 | | ...                       "Invalid spending YUV tx: {reason}; {:?}, proofs: {:?}",
[INFO] [stdout] 150 | | ...                       yuv_tx.bitcoin_tx.raw_hex(),
[INFO] [stdout] 151 | | ...                       yuv_tx.tx_type,
[INFO] [stdout] 152 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/sweep.rs:147:9
[INFO] [stdout]     |
[INFO] [stdout] 147 | / ...                   lightning::log_error!(
[INFO] [stdout] 148 | | ...                       logger,
[INFO] [stdout] 149 | | ...                       "Invalid spending YUV tx: {reason}; {:?}, proofs: {:?}",
[INFO] [stdout] 150 | | ...                       yuv_tx.bitcoin_tx.raw_hex(),
[INFO] [stdout] 151 | | ...                       yuv_tx.tx_type,
[INFO] [stdout] 152 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/sweep.rs:147:9
[INFO] [stdout]     |
[INFO] [stdout] 147 | / ...                   lightning::log_error!(
[INFO] [stdout] 148 | | ...                       logger,
[INFO] [stdout] 149 | | ...                       "Invalid spending YUV tx: {reason}; {:?}, proofs: {:?}",
[INFO] [stdout] 150 | | ...                       yuv_tx.bitcoin_tx.raw_hex(),
[INFO] [stdout] 151 | | ...                       yuv_tx.tx_type,
[INFO] [stdout] 152 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/sweep.rs:147:9
[INFO] [stdout]     |
[INFO] [stdout] 147 | / ...                   lightning::log_error!(
[INFO] [stdout] 148 | | ...                       logger,
[INFO] [stdout] 149 | | ...                       "Invalid spending YUV tx: {reason}; {:?}, proofs: {:?}",
[INFO] [stdout] 150 | | ...                       yuv_tx.bitcoin_tx.raw_hex(),
[INFO] [stdout] 151 | | ...                       yuv_tx.tx_type,
[INFO] [stdout] 152 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/sweep.rs:147:9
[INFO] [stdout]     |
[INFO] [stdout] 147 | / ...                   lightning::log_error!(
[INFO] [stdout] 148 | | ...                       logger,
[INFO] [stdout] 149 | | ...                       "Invalid spending YUV tx: {reason}; {:?}, proofs: {:?}",
[INFO] [stdout] 150 | | ...                       yuv_tx.bitcoin_tx.raw_hex(),
[INFO] [stdout] 151 | | ...                       yuv_tx.tx_type,
[INFO] [stdout] 152 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/sweep.rs:147:9
[INFO] [stdout]     |
[INFO] [stdout] 147 | / ...                   lightning::log_error!(
[INFO] [stdout] 148 | | ...                       logger,
[INFO] [stdout] 149 | | ...                       "Invalid spending YUV tx: {reason}; {:?}, proofs: {:?}",
[INFO] [stdout] 150 | | ...                       yuv_tx.bitcoin_tx.raw_hex(),
[INFO] [stdout] 151 | | ...                       yuv_tx.tx_type,
[INFO] [stdout] 152 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:163:8
[INFO] [stdout]     |
[INFO] [stdout] 163 | / ...                   log_info!(
[INFO] [stdout] 164 | | ...                       logger,
[INFO] [stdout] 165 | | ...                       "Broadcasted YUV sweep tx: {}",
[INFO] [stdout] 166 | | ...                       yuv_tx.bitcoin_tx.txid()
[INFO] [stdout] 167 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:163:8
[INFO] [stdout]     |
[INFO] [stdout] 163 | / ...                   log_info!(
[INFO] [stdout] 164 | | ...                       logger,
[INFO] [stdout] 165 | | ...                       "Broadcasted YUV sweep tx: {}",
[INFO] [stdout] 166 | | ...                       yuv_tx.bitcoin_tx.txid()
[INFO] [stdout] 167 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/sweep.rs:163:8
[INFO] [stdout]     |
[INFO] [stdout] 163 | / ...                   log_info!(
[INFO] [stdout] 164 | | ...                       logger,
[INFO] [stdout] 165 | | ...                       "Broadcasted YUV sweep tx: {}",
[INFO] [stdout] 166 | | ...                       yuv_tx.bitcoin_tx.txid()
[INFO] [stdout] 167 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:163:8
[INFO] [stdout]     |
[INFO] [stdout] 163 | / ...                   log_info!(
[INFO] [stdout] 164 | | ...                       logger,
[INFO] [stdout] 165 | | ...                       "Broadcasted YUV sweep tx: {}",
[INFO] [stdout] 166 | | ...                       yuv_tx.bitcoin_tx.txid()
[INFO] [stdout] 167 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/sweep.rs:163:8
[INFO] [stdout]     |
[INFO] [stdout] 163 | / ...                   log_info!(
[INFO] [stdout] 164 | | ...                       logger,
[INFO] [stdout] 165 | | ...                       "Broadcasted YUV sweep tx: {}",
[INFO] [stdout] 166 | | ...                       yuv_tx.bitcoin_tx.txid()
[INFO] [stdout] 167 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/sweep.rs:163:8
[INFO] [stdout]     |
[INFO] [stdout] 163 | / ...                   log_info!(
[INFO] [stdout] 164 | | ...                       logger,
[INFO] [stdout] 165 | | ...                       "Broadcasted YUV sweep tx: {}",
[INFO] [stdout] 166 | | ...                       yuv_tx.bitcoin_tx.txid()
[INFO] [stdout] 167 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:163:8
[INFO] [stdout]     |
[INFO] [stdout] 163 | / ...                   log_info!(
[INFO] [stdout] 164 | | ...                       logger,
[INFO] [stdout] 165 | | ...                       "Broadcasted YUV sweep tx: {}",
[INFO] [stdout] 166 | | ...                       yuv_tx.bitcoin_tx.txid()
[INFO] [stdout] 167 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/sweep.rs:163:8
[INFO] [stdout]     |
[INFO] [stdout] 163 | / ...                   log_info!(
[INFO] [stdout] 164 | | ...                       logger,
[INFO] [stdout] 165 | | ...                       "Broadcasted YUV sweep tx: {}",
[INFO] [stdout] 166 | | ...                       yuv_tx.bitcoin_tx.txid()
[INFO] [stdout] 167 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/sweep.rs:163:8
[INFO] [stdout]     |
[INFO] [stdout] 163 | / ...                   log_info!(
[INFO] [stdout] 164 | | ...                       logger,
[INFO] [stdout] 165 | | ...                       "Broadcasted YUV sweep tx: {}",
[INFO] [stdout] 166 | | ...                       yuv_tx.bitcoin_tx.txid()
[INFO] [stdout] 167 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/sweep.rs:163:8
[INFO] [stdout]     |
[INFO] [stdout] 163 | / ...                   log_info!(
[INFO] [stdout] 164 | | ...                       logger,
[INFO] [stdout] 165 | | ...                       "Broadcasted YUV sweep tx: {}",
[INFO] [stdout] 166 | | ...                       yuv_tx.bitcoin_tx.txid()
[INFO] [stdout] 167 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:163:8
[INFO] [stdout]     |
[INFO] [stdout] 163 | / ...                   log_info!(
[INFO] [stdout] 164 | | ...                       logger,
[INFO] [stdout] 165 | | ...                       "Broadcasted YUV sweep tx: {}",
[INFO] [stdout] 166 | | ...                       yuv_tx.bitcoin_tx.txid()
[INFO] [stdout] 167 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/sweep.rs:163:8
[INFO] [stdout]     |
[INFO] [stdout] 163 | / ...                   log_info!(
[INFO] [stdout] 164 | | ...                       logger,
[INFO] [stdout] 165 | | ...                       "Broadcasted YUV sweep tx: {}",
[INFO] [stdout] 166 | | ...                       yuv_tx.bitcoin_tx.txid()
[INFO] [stdout] 167 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/sweep.rs:163:8
[INFO] [stdout]     |
[INFO] [stdout] 163 | / ...                   log_info!(
[INFO] [stdout] 164 | | ...                       logger,
[INFO] [stdout] 165 | | ...                       "Broadcasted YUV sweep tx: {}",
[INFO] [stdout] 166 | | ...                       yuv_tx.bitcoin_tx.txid()
[INFO] [stdout] 167 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/sweep.rs:163:8
[INFO] [stdout]     |
[INFO] [stdout] 163 | / ...                   log_info!(
[INFO] [stdout] 164 | | ...                       logger,
[INFO] [stdout] 165 | | ...                       "Broadcasted YUV sweep tx: {}",
[INFO] [stdout] 166 | | ...                       yuv_tx.bitcoin_tx.txid()
[INFO] [stdout] 167 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/sweep.rs:163:8
[INFO] [stdout]     |
[INFO] [stdout] 163 | / ...                   log_info!(
[INFO] [stdout] 164 | | ...                       logger,
[INFO] [stdout] 165 | | ...                       "Broadcasted YUV sweep tx: {}",
[INFO] [stdout] 166 | | ...                       yuv_tx.bitcoin_tx.txid()
[INFO] [stdout] 167 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:163:8
[INFO] [stdout]     |
[INFO] [stdout] 163 | / ...                   log_info!(
[INFO] [stdout] 164 | | ...                       logger,
[INFO] [stdout] 165 | | ...                       "Broadcasted YUV sweep tx: {}",
[INFO] [stdout] 166 | | ...                       yuv_tx.bitcoin_tx.txid()
[INFO] [stdout] 167 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/sweep.rs:163:8
[INFO] [stdout]     |
[INFO] [stdout] 163 | / ...                   log_info!(
[INFO] [stdout] 164 | | ...                       logger,
[INFO] [stdout] 165 | | ...                       "Broadcasted YUV sweep tx: {}",
[INFO] [stdout] 166 | | ...                       yuv_tx.bitcoin_tx.txid()
[INFO] [stdout] 167 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/sweep.rs:163:8
[INFO] [stdout]     |
[INFO] [stdout] 163 | / ...                   log_info!(
[INFO] [stdout] 164 | | ...                       logger,
[INFO] [stdout] 165 | | ...                       "Broadcasted YUV sweep tx: {}",
[INFO] [stdout] 166 | | ...                       yuv_tx.bitcoin_tx.txid()
[INFO] [stdout] 167 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/sweep.rs:163:8
[INFO] [stdout]     |
[INFO] [stdout] 163 | / ...                   log_info!(
[INFO] [stdout] 164 | | ...                       logger,
[INFO] [stdout] 165 | | ...                       "Broadcasted YUV sweep tx: {}",
[INFO] [stdout] 166 | | ...                       yuv_tx.bitcoin_tx.txid()
[INFO] [stdout] 167 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/sweep.rs:163:8
[INFO] [stdout]     |
[INFO] [stdout] 163 | / ...                   log_info!(
[INFO] [stdout] 164 | | ...                       logger,
[INFO] [stdout] 165 | | ...                       "Broadcasted YUV sweep tx: {}",
[INFO] [stdout] 166 | | ...                       yuv_tx.bitcoin_tx.txid()
[INFO] [stdout] 167 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/sweep.rs:163:8
[INFO] [stdout]     |
[INFO] [stdout] 163 | / ...                   log_info!(
[INFO] [stdout] 164 | | ...                       logger,
[INFO] [stdout] 165 | | ...                       "Broadcasted YUV sweep tx: {}",
[INFO] [stdout] 166 | | ...                       yuv_tx.bitcoin_tx.txid()
[INFO] [stdout] 167 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:163:8
[INFO] [stdout]     |
[INFO] [stdout] 163 | / ...                   log_info!(
[INFO] [stdout] 164 | | ...                       logger,
[INFO] [stdout] 165 | | ...                       "Broadcasted YUV sweep tx: {}",
[INFO] [stdout] 166 | | ...                       yuv_tx.bitcoin_tx.txid()
[INFO] [stdout] 167 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/sweep.rs:163:8
[INFO] [stdout]     |
[INFO] [stdout] 163 | / ...                   log_info!(
[INFO] [stdout] 164 | | ...                       logger,
[INFO] [stdout] 165 | | ...                       "Broadcasted YUV sweep tx: {}",
[INFO] [stdout] 166 | | ...                       yuv_tx.bitcoin_tx.txid()
[INFO] [stdout] 167 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/sweep.rs:163:8
[INFO] [stdout]     |
[INFO] [stdout] 163 | / ...                   log_info!(
[INFO] [stdout] 164 | | ...                       logger,
[INFO] [stdout] 165 | | ...                       "Broadcasted YUV sweep tx: {}",
[INFO] [stdout] 166 | | ...                       yuv_tx.bitcoin_tx.txid()
[INFO] [stdout] 167 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/sweep.rs:163:8
[INFO] [stdout]     |
[INFO] [stdout] 163 | / ...                   log_info!(
[INFO] [stdout] 164 | | ...                       logger,
[INFO] [stdout] 165 | | ...                       "Broadcasted YUV sweep tx: {}",
[INFO] [stdout] 166 | | ...                       yuv_tx.bitcoin_tx.txid()
[INFO] [stdout] 167 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/sweep.rs:163:8
[INFO] [stdout]     |
[INFO] [stdout] 163 | / ...                   log_info!(
[INFO] [stdout] 164 | | ...                       logger,
[INFO] [stdout] 165 | | ...                       "Broadcasted YUV sweep tx: {}",
[INFO] [stdout] 166 | | ...                       yuv_tx.bitcoin_tx.txid()
[INFO] [stdout] 167 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/sweep.rs:163:8
[INFO] [stdout]     |
[INFO] [stdout] 163 | / ...                   log_info!(
[INFO] [stdout] 164 | | ...                       logger,
[INFO] [stdout] 165 | | ...                       "Broadcasted YUV sweep tx: {}",
[INFO] [stdout] 166 | | ...                       yuv_tx.bitcoin_tx.txid()
[INFO] [stdout] 167 | | ...                   );
[INFO] [stdout]     | |_______________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | /                         lightning::log_error!(
[INFO] [stdout] 172 | |                             logger,
[INFO] [stdout] 173 | |                             "Failed to sweep YUV spendable outputs: {}",
[INFO] [stdout] 174 | |                             err
[INFO] [stdout] 175 | |                         );
[INFO] [stdout]     | |_________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | /                         lightning::log_error!(
[INFO] [stdout] 172 | |                             logger,
[INFO] [stdout] 173 | |                             "Failed to sweep YUV spendable outputs: {}",
[INFO] [stdout] 174 | |                             err
[INFO] [stdout] 175 | |                         );
[INFO] [stdout]     | |_________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/sweep.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | /                         lightning::log_error!(
[INFO] [stdout] 172 | |                             logger,
[INFO] [stdout] 173 | |                             "Failed to sweep YUV spendable outputs: {}",
[INFO] [stdout] 174 | |                             err
[INFO] [stdout] 175 | |                         );
[INFO] [stdout]     | |_________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | /                         lightning::log_error!(
[INFO] [stdout] 172 | |                             logger,
[INFO] [stdout] 173 | |                             "Failed to sweep YUV spendable outputs: {}",
[INFO] [stdout] 174 | |                             err
[INFO] [stdout] 175 | |                         );
[INFO] [stdout]     | |_________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/sweep.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | /                         lightning::log_error!(
[INFO] [stdout] 172 | |                             logger,
[INFO] [stdout] 173 | |                             "Failed to sweep YUV spendable outputs: {}",
[INFO] [stdout] 174 | |                             err
[INFO] [stdout] 175 | |                         );
[INFO] [stdout]     | |_________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/sweep.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | /                         lightning::log_error!(
[INFO] [stdout] 172 | |                             logger,
[INFO] [stdout] 173 | |                             "Failed to sweep YUV spendable outputs: {}",
[INFO] [stdout] 174 | |                             err
[INFO] [stdout] 175 | |                         );
[INFO] [stdout]     | |_________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | /                         lightning::log_error!(
[INFO] [stdout] 172 | |                             logger,
[INFO] [stdout] 173 | |                             "Failed to sweep YUV spendable outputs: {}",
[INFO] [stdout] 174 | |                             err
[INFO] [stdout] 175 | |                         );
[INFO] [stdout]     | |_________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/sweep.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | /                         lightning::log_error!(
[INFO] [stdout] 172 | |                             logger,
[INFO] [stdout] 173 | |                             "Failed to sweep YUV spendable outputs: {}",
[INFO] [stdout] 174 | |                             err
[INFO] [stdout] 175 | |                         );
[INFO] [stdout]     | |_________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/sweep.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | /                         lightning::log_error!(
[INFO] [stdout] 172 | |                             logger,
[INFO] [stdout] 173 | |                             "Failed to sweep YUV spendable outputs: {}",
[INFO] [stdout] 174 | |                             err
[INFO] [stdout] 175 | |                         );
[INFO] [stdout]     | |_________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/sweep.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | /                         lightning::log_error!(
[INFO] [stdout] 172 | |                             logger,
[INFO] [stdout] 173 | |                             "Failed to sweep YUV spendable outputs: {}",
[INFO] [stdout] 174 | |                             err
[INFO] [stdout] 175 | |                         );
[INFO] [stdout]     | |_________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | /                         lightning::log_error!(
[INFO] [stdout] 172 | |                             logger,
[INFO] [stdout] 173 | |                             "Failed to sweep YUV spendable outputs: {}",
[INFO] [stdout] 174 | |                             err
[INFO] [stdout] 175 | |                         );
[INFO] [stdout]     | |_________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/sweep.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | /                         lightning::log_error!(
[INFO] [stdout] 172 | |                             logger,
[INFO] [stdout] 173 | |                             "Failed to sweep YUV spendable outputs: {}",
[INFO] [stdout] 174 | |                             err
[INFO] [stdout] 175 | |                         );
[INFO] [stdout]     | |_________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/sweep.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | /                         lightning::log_error!(
[INFO] [stdout] 172 | |                             logger,
[INFO] [stdout] 173 | |                             "Failed to sweep YUV spendable outputs: {}",
[INFO] [stdout] 174 | |                             err
[INFO] [stdout] 175 | |                         );
[INFO] [stdout]     | |_________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/sweep.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | /                         lightning::log_error!(
[INFO] [stdout] 172 | |                             logger,
[INFO] [stdout] 173 | |                             "Failed to sweep YUV spendable outputs: {}",
[INFO] [stdout] 174 | |                             err
[INFO] [stdout] 175 | |                         );
[INFO] [stdout]     | |_________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/sweep.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | /                         lightning::log_error!(
[INFO] [stdout] 172 | |                             logger,
[INFO] [stdout] 173 | |                             "Failed to sweep YUV spendable outputs: {}",
[INFO] [stdout] 174 | |                             err
[INFO] [stdout] 175 | |                         );
[INFO] [stdout]     | |_________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | /                         lightning::log_error!(
[INFO] [stdout] 172 | |                             logger,
[INFO] [stdout] 173 | |                             "Failed to sweep YUV spendable outputs: {}",
[INFO] [stdout] 174 | |                             err
[INFO] [stdout] 175 | |                         );
[INFO] [stdout]     | |_________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/sweep.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | /                         lightning::log_error!(
[INFO] [stdout] 172 | |                             logger,
[INFO] [stdout] 173 | |                             "Failed to sweep YUV spendable outputs: {}",
[INFO] [stdout] 174 | |                             err
[INFO] [stdout] 175 | |                         );
[INFO] [stdout]     | |_________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/sweep.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | /                         lightning::log_error!(
[INFO] [stdout] 172 | |                             logger,
[INFO] [stdout] 173 | |                             "Failed to sweep YUV spendable outputs: {}",
[INFO] [stdout] 174 | |                             err
[INFO] [stdout] 175 | |                         );
[INFO] [stdout]     | |_________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/sweep.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | /                         lightning::log_error!(
[INFO] [stdout] 172 | |                             logger,
[INFO] [stdout] 173 | |                             "Failed to sweep YUV spendable outputs: {}",
[INFO] [stdout] 174 | |                             err
[INFO] [stdout] 175 | |                         );
[INFO] [stdout]     | |_________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/sweep.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | /                         lightning::log_error!(
[INFO] [stdout] 172 | |                             logger,
[INFO] [stdout] 173 | |                             "Failed to sweep YUV spendable outputs: {}",
[INFO] [stdout] 174 | |                             err
[INFO] [stdout] 175 | |                         );
[INFO] [stdout]     | |_________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/sweep.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | /                         lightning::log_error!(
[INFO] [stdout] 172 | |                             logger,
[INFO] [stdout] 173 | |                             "Failed to sweep YUV spendable outputs: {}",
[INFO] [stdout] 174 | |                             err
[INFO] [stdout] 175 | |                         );
[INFO] [stdout]     | |_________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/sweep.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | /                         lightning::log_error!(
[INFO] [stdout] 172 | |                             logger,
[INFO] [stdout] 173 | |                             "Failed to sweep YUV spendable outputs: {}",
[INFO] [stdout] 174 | |                             err
[INFO] [stdout] 175 | |                         );
[INFO] [stdout]     | |_________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/sweep.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | /                         lightning::log_error!(
[INFO] [stdout] 172 | |                             logger,
[INFO] [stdout] 173 | |                             "Failed to sweep YUV spendable outputs: {}",
[INFO] [stdout] 174 | |                             err
[INFO] [stdout] 175 | |                         );
[INFO] [stdout]     | |_________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/sweep.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | /                         lightning::log_error!(
[INFO] [stdout] 172 | |                             logger,
[INFO] [stdout] 173 | |                             "Failed to sweep YUV spendable outputs: {}",
[INFO] [stdout] 174 | |                             err
[INFO] [stdout] 175 | |                         );
[INFO] [stdout]     | |_________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/sweep.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | /                         lightning::log_error!(
[INFO] [stdout] 172 | |                             logger,
[INFO] [stdout] 173 | |                             "Failed to sweep YUV spendable outputs: {}",
[INFO] [stdout] 174 | |                             err
[INFO] [stdout] 175 | |                         );
[INFO] [stdout]     | |_________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/sweep.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | /                         lightning::log_error!(
[INFO] [stdout] 172 | |                             logger,
[INFO] [stdout] 173 | |                             "Failed to sweep YUV spendable outputs: {}",
[INFO] [stdout] 174 | |                             err
[INFO] [stdout] 175 | |                         );
[INFO] [stdout]     | |_________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/sweep.rs:171:7
[INFO] [stdout]     |
[INFO] [stdout] 171 | /                         lightning::log_error!(
[INFO] [stdout] 172 | |                             logger,
[INFO] [stdout] 173 | |                             "Failed to sweep YUV spendable outputs: {}",
[INFO] [stdout] 174 | |                             err
[INFO] [stdout] 175 | |                         );
[INFO] [stdout]     | |_________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/wallet.rs:132:4
[INFO] [stdout]     |
[INFO] [stdout] 132 |             log_error!(&self.logger, "Failed to get list unspent utxos: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/wallet.rs:132:4
[INFO] [stdout]     |
[INFO] [stdout] 132 |             log_error!(&self.logger, "Failed to get list unspent utxos: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/wallet.rs:132:4
[INFO] [stdout]     |
[INFO] [stdout] 132 |             log_error!(&self.logger, "Failed to get list unspent utxos: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/wallet.rs:132:4
[INFO] [stdout]     |
[INFO] [stdout] 132 |             log_error!(&self.logger, "Failed to get list unspent utxos: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/wallet.rs:132:4
[INFO] [stdout]     |
[INFO] [stdout] 132 |             log_error!(&self.logger, "Failed to get list unspent utxos: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/wallet.rs:132:4
[INFO] [stdout]     |
[INFO] [stdout] 132 |             log_error!(&self.logger, "Failed to get list unspent utxos: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/wallet.rs:132:4
[INFO] [stdout]     |
[INFO] [stdout] 132 |             log_error!(&self.logger, "Failed to get list unspent utxos: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/wallet.rs:132:4
[INFO] [stdout]     |
[INFO] [stdout] 132 |             log_error!(&self.logger, "Failed to get list unspent utxos: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/wallet.rs:132:4
[INFO] [stdout]     |
[INFO] [stdout] 132 |             log_error!(&self.logger, "Failed to get list unspent utxos: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/wallet.rs:132:4
[INFO] [stdout]     |
[INFO] [stdout] 132 |             log_error!(&self.logger, "Failed to get list unspent utxos: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/wallet.rs:132:4
[INFO] [stdout]     |
[INFO] [stdout] 132 |             log_error!(&self.logger, "Failed to get list unspent utxos: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/wallet.rs:132:4
[INFO] [stdout]     |
[INFO] [stdout] 132 |             log_error!(&self.logger, "Failed to get list unspent utxos: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/wallet.rs:132:4
[INFO] [stdout]     |
[INFO] [stdout] 132 |             log_error!(&self.logger, "Failed to get list unspent utxos: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/wallet.rs:132:4
[INFO] [stdout]     |
[INFO] [stdout] 132 |             log_error!(&self.logger, "Failed to get list unspent utxos: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/wallet.rs:132:4
[INFO] [stdout]     |
[INFO] [stdout] 132 |             log_error!(&self.logger, "Failed to get list unspent utxos: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/wallet.rs:132:4
[INFO] [stdout]     |
[INFO] [stdout] 132 |             log_error!(&self.logger, "Failed to get list unspent utxos: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/wallet.rs:132:4
[INFO] [stdout]     |
[INFO] [stdout] 132 |             log_error!(&self.logger, "Failed to get list unspent utxos: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/wallet.rs:132:4
[INFO] [stdout]     |
[INFO] [stdout] 132 |             log_error!(&self.logger, "Failed to get list unspent utxos: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/wallet.rs:132:4
[INFO] [stdout]     |
[INFO] [stdout] 132 |             log_error!(&self.logger, "Failed to get list unspent utxos: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/wallet.rs:132:4
[INFO] [stdout]     |
[INFO] [stdout] 132 |             log_error!(&self.logger, "Failed to get list unspent utxos: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/wallet.rs:132:4
[INFO] [stdout]     |
[INFO] [stdout] 132 |             log_error!(&self.logger, "Failed to get list unspent utxos: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/wallet.rs:132:4
[INFO] [stdout]     |
[INFO] [stdout] 132 |             log_error!(&self.logger, "Failed to get list unspent utxos: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/wallet.rs:132:4
[INFO] [stdout]     |
[INFO] [stdout] 132 |             log_error!(&self.logger, "Failed to get list unspent utxos: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/wallet.rs:132:4
[INFO] [stdout]     |
[INFO] [stdout] 132 |             log_error!(&self.logger, "Failed to get list unspent utxos: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/wallet.rs:132:4
[INFO] [stdout]     |
[INFO] [stdout] 132 |             log_error!(&self.logger, "Failed to get list unspent utxos: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/wallet.rs:132:4
[INFO] [stdout]     |
[INFO] [stdout] 132 |             log_error!(&self.logger, "Failed to get list unspent utxos: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/wallet.rs:132:4
[INFO] [stdout]     |
[INFO] [stdout] 132 |             log_error!(&self.logger, "Failed to get list unspent utxos: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/wallet.rs:155:4
[INFO] [stdout]     |
[INFO] [stdout] 155 |             log_error!(&self.logger, "Failed to get address indo: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/wallet.rs:155:4
[INFO] [stdout]     |
[INFO] [stdout] 155 |             log_error!(&self.logger, "Failed to get address indo: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/wallet.rs:155:4
[INFO] [stdout]     |
[INFO] [stdout] 155 |             log_error!(&self.logger, "Failed to get address indo: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/wallet.rs:155:4
[INFO] [stdout]     |
[INFO] [stdout] 155 |             log_error!(&self.logger, "Failed to get address indo: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/wallet.rs:155:4
[INFO] [stdout]     |
[INFO] [stdout] 155 |             log_error!(&self.logger, "Failed to get address indo: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/wallet.rs:155:4
[INFO] [stdout]     |
[INFO] [stdout] 155 |             log_error!(&self.logger, "Failed to get address indo: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/wallet.rs:155:4
[INFO] [stdout]     |
[INFO] [stdout] 155 |             log_error!(&self.logger, "Failed to get address indo: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/wallet.rs:155:4
[INFO] [stdout]     |
[INFO] [stdout] 155 |             log_error!(&self.logger, "Failed to get address indo: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/wallet.rs:155:4
[INFO] [stdout]     |
[INFO] [stdout] 155 |             log_error!(&self.logger, "Failed to get address indo: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/wallet.rs:155:4
[INFO] [stdout]     |
[INFO] [stdout] 155 |             log_error!(&self.logger, "Failed to get address indo: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/wallet.rs:155:4
[INFO] [stdout]     |
[INFO] [stdout] 155 |             log_error!(&self.logger, "Failed to get address indo: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/wallet.rs:155:4
[INFO] [stdout]     |
[INFO] [stdout] 155 |             log_error!(&self.logger, "Failed to get address indo: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/wallet.rs:155:4
[INFO] [stdout]     |
[INFO] [stdout] 155 |             log_error!(&self.logger, "Failed to get address indo: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/wallet.rs:155:4
[INFO] [stdout]     |
[INFO] [stdout] 155 |             log_error!(&self.logger, "Failed to get address indo: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/wallet.rs:155:4
[INFO] [stdout]     |
[INFO] [stdout] 155 |             log_error!(&self.logger, "Failed to get address indo: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/wallet.rs:155:4
[INFO] [stdout]     |
[INFO] [stdout] 155 |             log_error!(&self.logger, "Failed to get address indo: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/wallet.rs:155:4
[INFO] [stdout]     |
[INFO] [stdout] 155 |             log_error!(&self.logger, "Failed to get address indo: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/wallet.rs:155:4
[INFO] [stdout]     |
[INFO] [stdout] 155 |             log_error!(&self.logger, "Failed to get address indo: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/wallet.rs:155:4
[INFO] [stdout]     |
[INFO] [stdout] 155 |             log_error!(&self.logger, "Failed to get address indo: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/wallet.rs:155:4
[INFO] [stdout]     |
[INFO] [stdout] 155 |             log_error!(&self.logger, "Failed to get address indo: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/wallet.rs:155:4
[INFO] [stdout]     |
[INFO] [stdout] 155 |             log_error!(&self.logger, "Failed to get address indo: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/wallet.rs:155:4
[INFO] [stdout]     |
[INFO] [stdout] 155 |             log_error!(&self.logger, "Failed to get address indo: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/wallet.rs:155:4
[INFO] [stdout]     |
[INFO] [stdout] 155 |             log_error!(&self.logger, "Failed to get address indo: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/wallet.rs:155:4
[INFO] [stdout]     |
[INFO] [stdout] 155 |             log_error!(&self.logger, "Failed to get address indo: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/wallet.rs:155:4
[INFO] [stdout]     |
[INFO] [stdout] 155 |             log_error!(&self.logger, "Failed to get address indo: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/wallet.rs:155:4
[INFO] [stdout]     |
[INFO] [stdout] 155 |             log_error!(&self.logger, "Failed to get address indo: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/wallet.rs:155:4
[INFO] [stdout]     |
[INFO] [stdout] 155 |             log_error!(&self.logger, "Failed to get address indo: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/wallet.rs:170:4
[INFO] [stdout]     |
[INFO] [stdout] 170 |             log_error!(&self.logger, "Failed to sign psbt: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/wallet.rs:170:4
[INFO] [stdout]     |
[INFO] [stdout] 170 |             log_error!(&self.logger, "Failed to sign psbt: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/wallet.rs:170:4
[INFO] [stdout]     |
[INFO] [stdout] 170 |             log_error!(&self.logger, "Failed to sign psbt: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/wallet.rs:170:4
[INFO] [stdout]     |
[INFO] [stdout] 170 |             log_error!(&self.logger, "Failed to sign psbt: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/wallet.rs:170:4
[INFO] [stdout]     |
[INFO] [stdout] 170 |             log_error!(&self.logger, "Failed to sign psbt: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/wallet.rs:170:4
[INFO] [stdout]     |
[INFO] [stdout] 170 |             log_error!(&self.logger, "Failed to sign psbt: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/wallet.rs:170:4
[INFO] [stdout]     |
[INFO] [stdout] 170 |             log_error!(&self.logger, "Failed to sign psbt: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/wallet.rs:170:4
[INFO] [stdout]     |
[INFO] [stdout] 170 |             log_error!(&self.logger, "Failed to sign psbt: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/wallet.rs:170:4
[INFO] [stdout]     |
[INFO] [stdout] 170 |             log_error!(&self.logger, "Failed to sign psbt: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/wallet.rs:170:4
[INFO] [stdout]     |
[INFO] [stdout] 170 |             log_error!(&self.logger, "Failed to sign psbt: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/wallet.rs:170:4
[INFO] [stdout]     |
[INFO] [stdout] 170 |             log_error!(&self.logger, "Failed to sign psbt: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/wallet.rs:170:4
[INFO] [stdout]     |
[INFO] [stdout] 170 |             log_error!(&self.logger, "Failed to sign psbt: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/wallet.rs:170:4
[INFO] [stdout]     |
[INFO] [stdout] 170 |             log_error!(&self.logger, "Failed to sign psbt: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/wallet.rs:170:4
[INFO] [stdout]     |
[INFO] [stdout] 170 |             log_error!(&self.logger, "Failed to sign psbt: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/wallet.rs:170:4
[INFO] [stdout]     |
[INFO] [stdout] 170 |             log_error!(&self.logger, "Failed to sign psbt: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/wallet.rs:170:4
[INFO] [stdout]     |
[INFO] [stdout] 170 |             log_error!(&self.logger, "Failed to sign psbt: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/wallet.rs:170:4
[INFO] [stdout]     |
[INFO] [stdout] 170 |             log_error!(&self.logger, "Failed to sign psbt: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/wallet.rs:170:4
[INFO] [stdout]     |
[INFO] [stdout] 170 |             log_error!(&self.logger, "Failed to sign psbt: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/wallet.rs:170:4
[INFO] [stdout]     |
[INFO] [stdout] 170 |             log_error!(&self.logger, "Failed to sign psbt: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/wallet.rs:170:4
[INFO] [stdout]     |
[INFO] [stdout] 170 |             log_error!(&self.logger, "Failed to sign psbt: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/wallet.rs:170:4
[INFO] [stdout]     |
[INFO] [stdout] 170 |             log_error!(&self.logger, "Failed to sign psbt: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/wallet.rs:170:4
[INFO] [stdout]     |
[INFO] [stdout] 170 |             log_error!(&self.logger, "Failed to sign psbt: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/wallet.rs:170:4
[INFO] [stdout]     |
[INFO] [stdout] 170 |             log_error!(&self.logger, "Failed to sign psbt: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/wallet.rs:170:4
[INFO] [stdout]     |
[INFO] [stdout] 170 |             log_error!(&self.logger, "Failed to sign psbt: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/wallet.rs:170:4
[INFO] [stdout]     |
[INFO] [stdout] 170 |             log_error!(&self.logger, "Failed to sign psbt: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/wallet.rs:170:4
[INFO] [stdout]     |
[INFO] [stdout] 170 |             log_error!(&self.logger, "Failed to sign psbt: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/wallet.rs:170:4
[INFO] [stdout]     |
[INFO] [stdout] 170 |             log_error!(&self.logger, "Failed to sign psbt: {err}");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 | /                 log_error!(
[INFO] [stdout] 40 | |                     logger,
[INFO] [stdout] 41 | |                     "Error, failed to getlistrawtransactions: {err}\nTx ids: {:?}",
[INFO] [stdout] 42 | |                     txids,
[INFO] [stdout] 43 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 | /                 log_error!(
[INFO] [stdout] 40 | |                     logger,
[INFO] [stdout] 41 | |                     "Error, failed to getlistrawtransactions: {err}\nTx ids: {:?}",
[INFO] [stdout] 42 | |                     txids,
[INFO] [stdout] 43 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/yuv_client.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 | /                 log_error!(
[INFO] [stdout] 40 | |                     logger,
[INFO] [stdout] 41 | |                     "Error, failed to getlistrawtransactions: {err}\nTx ids: {:?}",
[INFO] [stdout] 42 | |                     txids,
[INFO] [stdout] 43 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 | /                 log_error!(
[INFO] [stdout] 40 | |                     logger,
[INFO] [stdout] 41 | |                     "Error, failed to getlistrawtransactions: {err}\nTx ids: {:?}",
[INFO] [stdout] 42 | |                     txids,
[INFO] [stdout] 43 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/yuv_client.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 | /                 log_error!(
[INFO] [stdout] 40 | |                     logger,
[INFO] [stdout] 41 | |                     "Error, failed to getlistrawtransactions: {err}\nTx ids: {:?}",
[INFO] [stdout] 42 | |                     txids,
[INFO] [stdout] 43 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/yuv_client.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 | /                 log_error!(
[INFO] [stdout] 40 | |                     logger,
[INFO] [stdout] 41 | |                     "Error, failed to getlistrawtransactions: {err}\nTx ids: {:?}",
[INFO] [stdout] 42 | |                     txids,
[INFO] [stdout] 43 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 | /                 log_error!(
[INFO] [stdout] 40 | |                     logger,
[INFO] [stdout] 41 | |                     "Error, failed to getlistrawtransactions: {err}\nTx ids: {:?}",
[INFO] [stdout] 42 | |                     txids,
[INFO] [stdout] 43 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/yuv_client.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 | /                 log_error!(
[INFO] [stdout] 40 | |                     logger,
[INFO] [stdout] 41 | |                     "Error, failed to getlistrawtransactions: {err}\nTx ids: {:?}",
[INFO] [stdout] 42 | |                     txids,
[INFO] [stdout] 43 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/yuv_client.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 | /                 log_error!(
[INFO] [stdout] 40 | |                     logger,
[INFO] [stdout] 41 | |                     "Error, failed to getlistrawtransactions: {err}\nTx ids: {:?}",
[INFO] [stdout] 42 | |                     txids,
[INFO] [stdout] 43 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> src/yuv_client.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 | /                 log_error!(
[INFO] [stdout] 40 | |                     logger,
[INFO] [stdout] 41 | |                     "Error, failed to getlistrawtransactions: {err}\nTx ids: {:?}",
[INFO] [stdout] 42 | |                     txids,
[INFO] [stdout] 43 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 | /                 log_error!(
[INFO] [stdout] 40 | |                     logger,
[INFO] [stdout] 41 | |                     "Error, failed to getlistrawtransactions: {err}\nTx ids: {:?}",
[INFO] [stdout] 42 | |                     txids,
[INFO] [stdout] 43 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/yuv_client.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 | /                 log_error!(
[INFO] [stdout] 40 | |                     logger,
[INFO] [stdout] 41 | |                     "Error, failed to getlistrawtransactions: {err}\nTx ids: {:?}",
[INFO] [stdout] 42 | |                     txids,
[INFO] [stdout] 43 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/yuv_client.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 | /                 log_error!(
[INFO] [stdout] 40 | |                     logger,
[INFO] [stdout] 41 | |                     "Error, failed to getlistrawtransactions: {err}\nTx ids: {:?}",
[INFO] [stdout] 42 | |                     txids,
[INFO] [stdout] 43 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> src/yuv_client.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 | /                 log_error!(
[INFO] [stdout] 40 | |                     logger,
[INFO] [stdout] 41 | |                     "Error, failed to getlistrawtransactions: {err}\nTx ids: {:?}",
[INFO] [stdout] 42 | |                     txids,
[INFO] [stdout] 43 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]   --> src/yuv_client.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 | /                 log_error!(
[INFO] [stdout] 40 | |                     logger,
[INFO] [stdout] 41 | |                     "Error, failed to getlistrawtransactions: {err}\nTx ids: {:?}",
[INFO] [stdout] 42 | |                     txids,
[INFO] [stdout] 43 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 | /                 log_error!(
[INFO] [stdout] 40 | |                     logger,
[INFO] [stdout] 41 | |                     "Error, failed to getlistrawtransactions: {err}\nTx ids: {:?}",
[INFO] [stdout] 42 | |                     txids,
[INFO] [stdout] 43 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/yuv_client.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 | /                 log_error!(
[INFO] [stdout] 40 | |                     logger,
[INFO] [stdout] 41 | |                     "Error, failed to getlistrawtransactions: {err}\nTx ids: {:?}",
[INFO] [stdout] 42 | |                     txids,
[INFO] [stdout] 43 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/yuv_client.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 | /                 log_error!(
[INFO] [stdout] 40 | |                     logger,
[INFO] [stdout] 41 | |                     "Error, failed to getlistrawtransactions: {err}\nTx ids: {:?}",
[INFO] [stdout] 42 | |                     txids,
[INFO] [stdout] 43 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> src/yuv_client.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 | /                 log_error!(
[INFO] [stdout] 40 | |                     logger,
[INFO] [stdout] 41 | |                     "Error, failed to getlistrawtransactions: {err}\nTx ids: {:?}",
[INFO] [stdout] 42 | |                     txids,
[INFO] [stdout] 43 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]   --> src/yuv_client.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 | /                 log_error!(
[INFO] [stdout] 40 | |                     logger,
[INFO] [stdout] 41 | |                     "Error, failed to getlistrawtransactions: {err}\nTx ids: {:?}",
[INFO] [stdout] 42 | |                     txids,
[INFO] [stdout] 43 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]   --> src/yuv_client.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 | /                 log_error!(
[INFO] [stdout] 40 | |                     logger,
[INFO] [stdout] 41 | |                     "Error, failed to getlistrawtransactions: {err}\nTx ids: {:?}",
[INFO] [stdout] 42 | |                     txids,
[INFO] [stdout] 43 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 | /                 log_error!(
[INFO] [stdout] 40 | |                     logger,
[INFO] [stdout] 41 | |                     "Error, failed to getlistrawtransactions: {err}\nTx ids: {:?}",
[INFO] [stdout] 42 | |                     txids,
[INFO] [stdout] 43 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/yuv_client.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 | /                 log_error!(
[INFO] [stdout] 40 | |                     logger,
[INFO] [stdout] 41 | |                     "Error, failed to getlistrawtransactions: {err}\nTx ids: {:?}",
[INFO] [stdout] 42 | |                     txids,
[INFO] [stdout] 43 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/yuv_client.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 | /                 log_error!(
[INFO] [stdout] 40 | |                     logger,
[INFO] [stdout] 41 | |                     "Error, failed to getlistrawtransactions: {err}\nTx ids: {:?}",
[INFO] [stdout] 42 | |                     txids,
[INFO] [stdout] 43 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> src/yuv_client.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 | /                 log_error!(
[INFO] [stdout] 40 | |                     logger,
[INFO] [stdout] 41 | |                     "Error, failed to getlistrawtransactions: {err}\nTx ids: {:?}",
[INFO] [stdout] 42 | |                     txids,
[INFO] [stdout] 43 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]   --> src/yuv_client.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 | /                 log_error!(
[INFO] [stdout] 40 | |                     logger,
[INFO] [stdout] 41 | |                     "Error, failed to getlistrawtransactions: {err}\nTx ids: {:?}",
[INFO] [stdout] 42 | |                     txids,
[INFO] [stdout] 43 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]   --> src/yuv_client.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 | /                 log_error!(
[INFO] [stdout] 40 | |                     logger,
[INFO] [stdout] 41 | |                     "Error, failed to getlistrawtransactions: {err}\nTx ids: {:?}",
[INFO] [stdout] 42 | |                     txids,
[INFO] [stdout] 43 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 | /                 log_error!(
[INFO] [stdout] 58 | |                     logger,
[INFO] [stdout] 59 | |                     "Error, failed to emulateyuvtransaction: {err}\nTransaction: {:?}",
[INFO] [stdout] 60 | |                     yuv_tx,
[INFO] [stdout] 61 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 | /                 log_error!(
[INFO] [stdout] 58 | |                     logger,
[INFO] [stdout] 59 | |                     "Error, failed to emulateyuvtransaction: {err}\nTransaction: {:?}",
[INFO] [stdout] 60 | |                     yuv_tx,
[INFO] [stdout] 61 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/yuv_client.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 | /                 log_error!(
[INFO] [stdout] 58 | |                     logger,
[INFO] [stdout] 59 | |                     "Error, failed to emulateyuvtransaction: {err}\nTransaction: {:?}",
[INFO] [stdout] 60 | |                     yuv_tx,
[INFO] [stdout] 61 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 | /                 log_error!(
[INFO] [stdout] 58 | |                     logger,
[INFO] [stdout] 59 | |                     "Error, failed to emulateyuvtransaction: {err}\nTransaction: {:?}",
[INFO] [stdout] 60 | |                     yuv_tx,
[INFO] [stdout] 61 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/yuv_client.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 | /                 log_error!(
[INFO] [stdout] 58 | |                     logger,
[INFO] [stdout] 59 | |                     "Error, failed to emulateyuvtransaction: {err}\nTransaction: {:?}",
[INFO] [stdout] 60 | |                     yuv_tx,
[INFO] [stdout] 61 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/yuv_client.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 | /                 log_error!(
[INFO] [stdout] 58 | |                     logger,
[INFO] [stdout] 59 | |                     "Error, failed to emulateyuvtransaction: {err}\nTransaction: {:?}",
[INFO] [stdout] 60 | |                     yuv_tx,
[INFO] [stdout] 61 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 | /                 log_error!(
[INFO] [stdout] 58 | |                     logger,
[INFO] [stdout] 59 | |                     "Error, failed to emulateyuvtransaction: {err}\nTransaction: {:?}",
[INFO] [stdout] 60 | |                     yuv_tx,
[INFO] [stdout] 61 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/yuv_client.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 | /                 log_error!(
[INFO] [stdout] 58 | |                     logger,
[INFO] [stdout] 59 | |                     "Error, failed to emulateyuvtransaction: {err}\nTransaction: {:?}",
[INFO] [stdout] 60 | |                     yuv_tx,
[INFO] [stdout] 61 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/yuv_client.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 | /                 log_error!(
[INFO] [stdout] 58 | |                     logger,
[INFO] [stdout] 59 | |                     "Error, failed to emulateyuvtransaction: {err}\nTransaction: {:?}",
[INFO] [stdout] 60 | |                     yuv_tx,
[INFO] [stdout] 61 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> src/yuv_client.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 | /                 log_error!(
[INFO] [stdout] 58 | |                     logger,
[INFO] [stdout] 59 | |                     "Error, failed to emulateyuvtransaction: {err}\nTransaction: {:?}",
[INFO] [stdout] 60 | |                     yuv_tx,
[INFO] [stdout] 61 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 | /                 log_error!(
[INFO] [stdout] 58 | |                     logger,
[INFO] [stdout] 59 | |                     "Error, failed to emulateyuvtransaction: {err}\nTransaction: {:?}",
[INFO] [stdout] 60 | |                     yuv_tx,
[INFO] [stdout] 61 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/yuv_client.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 | /                 log_error!(
[INFO] [stdout] 58 | |                     logger,
[INFO] [stdout] 59 | |                     "Error, failed to emulateyuvtransaction: {err}\nTransaction: {:?}",
[INFO] [stdout] 60 | |                     yuv_tx,
[INFO] [stdout] 61 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/yuv_client.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 | /                 log_error!(
[INFO] [stdout] 58 | |                     logger,
[INFO] [stdout] 59 | |                     "Error, failed to emulateyuvtransaction: {err}\nTransaction: {:?}",
[INFO] [stdout] 60 | |                     yuv_tx,
[INFO] [stdout] 61 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> src/yuv_client.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 | /                 log_error!(
[INFO] [stdout] 58 | |                     logger,
[INFO] [stdout] 59 | |                     "Error, failed to emulateyuvtransaction: {err}\nTransaction: {:?}",
[INFO] [stdout] 60 | |                     yuv_tx,
[INFO] [stdout] 61 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]   --> src/yuv_client.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 | /                 log_error!(
[INFO] [stdout] 58 | |                     logger,
[INFO] [stdout] 59 | |                     "Error, failed to emulateyuvtransaction: {err}\nTransaction: {:?}",
[INFO] [stdout] 60 | |                     yuv_tx,
[INFO] [stdout] 61 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 | /                 log_error!(
[INFO] [stdout] 58 | |                     logger,
[INFO] [stdout] 59 | |                     "Error, failed to emulateyuvtransaction: {err}\nTransaction: {:?}",
[INFO] [stdout] 60 | |                     yuv_tx,
[INFO] [stdout] 61 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/yuv_client.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 | /                 log_error!(
[INFO] [stdout] 58 | |                     logger,
[INFO] [stdout] 59 | |                     "Error, failed to emulateyuvtransaction: {err}\nTransaction: {:?}",
[INFO] [stdout] 60 | |                     yuv_tx,
[INFO] [stdout] 61 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/yuv_client.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 | /                 log_error!(
[INFO] [stdout] 58 | |                     logger,
[INFO] [stdout] 59 | |                     "Error, failed to emulateyuvtransaction: {err}\nTransaction: {:?}",
[INFO] [stdout] 60 | |                     yuv_tx,
[INFO] [stdout] 61 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> src/yuv_client.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 | /                 log_error!(
[INFO] [stdout] 58 | |                     logger,
[INFO] [stdout] 59 | |                     "Error, failed to emulateyuvtransaction: {err}\nTransaction: {:?}",
[INFO] [stdout] 60 | |                     yuv_tx,
[INFO] [stdout] 61 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]   --> src/yuv_client.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 | /                 log_error!(
[INFO] [stdout] 58 | |                     logger,
[INFO] [stdout] 59 | |                     "Error, failed to emulateyuvtransaction: {err}\nTransaction: {:?}",
[INFO] [stdout] 60 | |                     yuv_tx,
[INFO] [stdout] 61 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]   --> src/yuv_client.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 | /                 log_error!(
[INFO] [stdout] 58 | |                     logger,
[INFO] [stdout] 59 | |                     "Error, failed to emulateyuvtransaction: {err}\nTransaction: {:?}",
[INFO] [stdout] 60 | |                     yuv_tx,
[INFO] [stdout] 61 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 | /                 log_error!(
[INFO] [stdout] 58 | |                     logger,
[INFO] [stdout] 59 | |                     "Error, failed to emulateyuvtransaction: {err}\nTransaction: {:?}",
[INFO] [stdout] 60 | |                     yuv_tx,
[INFO] [stdout] 61 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/yuv_client.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 | /                 log_error!(
[INFO] [stdout] 58 | |                     logger,
[INFO] [stdout] 59 | |                     "Error, failed to emulateyuvtransaction: {err}\nTransaction: {:?}",
[INFO] [stdout] 60 | |                     yuv_tx,
[INFO] [stdout] 61 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/yuv_client.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 | /                 log_error!(
[INFO] [stdout] 58 | |                     logger,
[INFO] [stdout] 59 | |                     "Error, failed to emulateyuvtransaction: {err}\nTransaction: {:?}",
[INFO] [stdout] 60 | |                     yuv_tx,
[INFO] [stdout] 61 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> src/yuv_client.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 | /                 log_error!(
[INFO] [stdout] 58 | |                     logger,
[INFO] [stdout] 59 | |                     "Error, failed to emulateyuvtransaction: {err}\nTransaction: {:?}",
[INFO] [stdout] 60 | |                     yuv_tx,
[INFO] [stdout] 61 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]   --> src/yuv_client.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 | /                 log_error!(
[INFO] [stdout] 58 | |                     logger,
[INFO] [stdout] 59 | |                     "Error, failed to emulateyuvtransaction: {err}\nTransaction: {:?}",
[INFO] [stdout] 60 | |                     yuv_tx,
[INFO] [stdout] 61 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]   --> src/yuv_client.rs:57:5
[INFO] [stdout]    |
[INFO] [stdout] 57 | /                 log_error!(
[INFO] [stdout] 58 | |                     logger,
[INFO] [stdout] 59 | |                     "Error, failed to emulateyuvtransaction: {err}\nTransaction: {:?}",
[INFO] [stdout] 60 | |                     yuv_tx,
[INFO] [stdout] 61 | |                 );
[INFO] [stdout]    | |_________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:75:6
[INFO] [stdout]    |
[INFO] [stdout] 75 |                     log_info!(logger, "Successfully broadcasted a YUV transaction")
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:75:6
[INFO] [stdout]    |
[INFO] [stdout] 75 |                     log_info!(logger, "Successfully broadcasted a YUV transaction")
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/yuv_client.rs:75:6
[INFO] [stdout]    |
[INFO] [stdout] 75 |                     log_info!(logger, "Successfully broadcasted a YUV transaction")
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:75:6
[INFO] [stdout]    |
[INFO] [stdout] 75 |                     log_info!(logger, "Successfully broadcasted a YUV transaction")
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/yuv_client.rs:75:6
[INFO] [stdout]    |
[INFO] [stdout] 75 |                     log_info!(logger, "Successfully broadcasted a YUV transaction")
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/yuv_client.rs:75:6
[INFO] [stdout]    |
[INFO] [stdout] 75 |                     log_info!(logger, "Successfully broadcasted a YUV transaction")
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:75:6
[INFO] [stdout]    |
[INFO] [stdout] 75 |                     log_info!(logger, "Successfully broadcasted a YUV transaction")
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/yuv_client.rs:75:6
[INFO] [stdout]    |
[INFO] [stdout] 75 |                     log_info!(logger, "Successfully broadcasted a YUV transaction")
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/yuv_client.rs:75:6
[INFO] [stdout]    |
[INFO] [stdout] 75 |                     log_info!(logger, "Successfully broadcasted a YUV transaction")
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> src/yuv_client.rs:75:6
[INFO] [stdout]    |
[INFO] [stdout] 75 |                     log_info!(logger, "Successfully broadcasted a YUV transaction")
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:75:6
[INFO] [stdout]    |
[INFO] [stdout] 75 |                     log_info!(logger, "Successfully broadcasted a YUV transaction")
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/yuv_client.rs:75:6
[INFO] [stdout]    |
[INFO] [stdout] 75 |                     log_info!(logger, "Successfully broadcasted a YUV transaction")
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/yuv_client.rs:75:6
[INFO] [stdout]    |
[INFO] [stdout] 75 |                     log_info!(logger, "Successfully broadcasted a YUV transaction")
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> src/yuv_client.rs:75:6
[INFO] [stdout]    |
[INFO] [stdout] 75 |                     log_info!(logger, "Successfully broadcasted a YUV transaction")
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]   --> src/yuv_client.rs:75:6
[INFO] [stdout]    |
[INFO] [stdout] 75 |                     log_info!(logger, "Successfully broadcasted a YUV transaction")
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:75:6
[INFO] [stdout]    |
[INFO] [stdout] 75 |                     log_info!(logger, "Successfully broadcasted a YUV transaction")
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/yuv_client.rs:75:6
[INFO] [stdout]    |
[INFO] [stdout] 75 |                     log_info!(logger, "Successfully broadcasted a YUV transaction")
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/yuv_client.rs:75:6
[INFO] [stdout]    |
[INFO] [stdout] 75 |                     log_info!(logger, "Successfully broadcasted a YUV transaction")
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> src/yuv_client.rs:75:6
[INFO] [stdout]    |
[INFO] [stdout] 75 |                     log_info!(logger, "Successfully broadcasted a YUV transaction")
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]   --> src/yuv_client.rs:75:6
[INFO] [stdout]    |
[INFO] [stdout] 75 |                     log_info!(logger, "Successfully broadcasted a YUV transaction")
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]   --> src/yuv_client.rs:75:6
[INFO] [stdout]    |
[INFO] [stdout] 75 |                     log_info!(logger, "Successfully broadcasted a YUV transaction")
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:75:6
[INFO] [stdout]    |
[INFO] [stdout] 75 |                     log_info!(logger, "Successfully broadcasted a YUV transaction")
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/yuv_client.rs:75:6
[INFO] [stdout]    |
[INFO] [stdout] 75 |                     log_info!(logger, "Successfully broadcasted a YUV transaction")
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/yuv_client.rs:75:6
[INFO] [stdout]    |
[INFO] [stdout] 75 |                     log_info!(logger, "Successfully broadcasted a YUV transaction")
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> src/yuv_client.rs:75:6
[INFO] [stdout]    |
[INFO] [stdout] 75 |                     log_info!(logger, "Successfully broadcasted a YUV transaction")
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]   --> src/yuv_client.rs:75:6
[INFO] [stdout]    |
[INFO] [stdout] 75 |                     log_info!(logger, "Successfully broadcasted a YUV transaction")
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]   --> src/yuv_client.rs:75:6
[INFO] [stdout]    |
[INFO] [stdout] 75 |                     log_info!(logger, "Successfully broadcasted a YUV transaction")
[INFO] [stdout]    |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:78:6
[INFO] [stdout]    |
[INFO] [stdout] 78 | /                     log_error!(
[INFO] [stdout] 79 | |                         logger,
[INFO] [stdout] 80 | |                         "Error, failed to provideyuvproof: {err}\nTransaction: {:?}",
[INFO] [stdout] 81 | |                         yuv_tx,
[INFO] [stdout] 82 | |                     )
[INFO] [stdout]    | |_____________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:78:6
[INFO] [stdout]    |
[INFO] [stdout] 78 | /                     log_error!(
[INFO] [stdout] 79 | |                         logger,
[INFO] [stdout] 80 | |                         "Error, failed to provideyuvproof: {err}\nTransaction: {:?}",
[INFO] [stdout] 81 | |                         yuv_tx,
[INFO] [stdout] 82 | |                     )
[INFO] [stdout]    | |_____________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/yuv_client.rs:78:6
[INFO] [stdout]    |
[INFO] [stdout] 78 | /                     log_error!(
[INFO] [stdout] 79 | |                         logger,
[INFO] [stdout] 80 | |                         "Error, failed to provideyuvproof: {err}\nTransaction: {:?}",
[INFO] [stdout] 81 | |                         yuv_tx,
[INFO] [stdout] 82 | |                     )
[INFO] [stdout]    | |_____________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:78:6
[INFO] [stdout]    |
[INFO] [stdout] 78 | /                     log_error!(
[INFO] [stdout] 79 | |                         logger,
[INFO] [stdout] 80 | |                         "Error, failed to provideyuvproof: {err}\nTransaction: {:?}",
[INFO] [stdout] 81 | |                         yuv_tx,
[INFO] [stdout] 82 | |                     )
[INFO] [stdout]    | |_____________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/yuv_client.rs:78:6
[INFO] [stdout]    |
[INFO] [stdout] 78 | /                     log_error!(
[INFO] [stdout] 79 | |                         logger,
[INFO] [stdout] 80 | |                         "Error, failed to provideyuvproof: {err}\nTransaction: {:?}",
[INFO] [stdout] 81 | |                         yuv_tx,
[INFO] [stdout] 82 | |                     )
[INFO] [stdout]    | |_____________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/yuv_client.rs:78:6
[INFO] [stdout]    |
[INFO] [stdout] 78 | /                     log_error!(
[INFO] [stdout] 79 | |                         logger,
[INFO] [stdout] 80 | |                         "Error, failed to provideyuvproof: {err}\nTransaction: {:?}",
[INFO] [stdout] 81 | |                         yuv_tx,
[INFO] [stdout] 82 | |                     )
[INFO] [stdout]    | |_____________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:78:6
[INFO] [stdout]    |
[INFO] [stdout] 78 | /                     log_error!(
[INFO] [stdout] 79 | |                         logger,
[INFO] [stdout] 80 | |                         "Error, failed to provideyuvproof: {err}\nTransaction: {:?}",
[INFO] [stdout] 81 | |                         yuv_tx,
[INFO] [stdout] 82 | |                     )
[INFO] [stdout]    | |_____________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/yuv_client.rs:78:6
[INFO] [stdout]    |
[INFO] [stdout] 78 | /                     log_error!(
[INFO] [stdout] 79 | |                         logger,
[INFO] [stdout] 80 | |                         "Error, failed to provideyuvproof: {err}\nTransaction: {:?}",
[INFO] [stdout] 81 | |                         yuv_tx,
[INFO] [stdout] 82 | |                     )
[INFO] [stdout]    | |_____________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/yuv_client.rs:78:6
[INFO] [stdout]    |
[INFO] [stdout] 78 | /                     log_error!(
[INFO] [stdout] 79 | |                         logger,
[INFO] [stdout] 80 | |                         "Error, failed to provideyuvproof: {err}\nTransaction: {:?}",
[INFO] [stdout] 81 | |                         yuv_tx,
[INFO] [stdout] 82 | |                     )
[INFO] [stdout]    | |_____________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> src/yuv_client.rs:78:6
[INFO] [stdout]    |
[INFO] [stdout] 78 | /                     log_error!(
[INFO] [stdout] 79 | |                         logger,
[INFO] [stdout] 80 | |                         "Error, failed to provideyuvproof: {err}\nTransaction: {:?}",
[INFO] [stdout] 81 | |                         yuv_tx,
[INFO] [stdout] 82 | |                     )
[INFO] [stdout]    | |_____________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:78:6
[INFO] [stdout]    |
[INFO] [stdout] 78 | /                     log_error!(
[INFO] [stdout] 79 | |                         logger,
[INFO] [stdout] 80 | |                         "Error, failed to provideyuvproof: {err}\nTransaction: {:?}",
[INFO] [stdout] 81 | |                         yuv_tx,
[INFO] [stdout] 82 | |                     )
[INFO] [stdout]    | |_____________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/yuv_client.rs:78:6
[INFO] [stdout]    |
[INFO] [stdout] 78 | /                     log_error!(
[INFO] [stdout] 79 | |                         logger,
[INFO] [stdout] 80 | |                         "Error, failed to provideyuvproof: {err}\nTransaction: {:?}",
[INFO] [stdout] 81 | |                         yuv_tx,
[INFO] [stdout] 82 | |                     )
[INFO] [stdout]    | |_____________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/yuv_client.rs:78:6
[INFO] [stdout]    |
[INFO] [stdout] 78 | /                     log_error!(
[INFO] [stdout] 79 | |                         logger,
[INFO] [stdout] 80 | |                         "Error, failed to provideyuvproof: {err}\nTransaction: {:?}",
[INFO] [stdout] 81 | |                         yuv_tx,
[INFO] [stdout] 82 | |                     )
[INFO] [stdout]    | |_____________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> src/yuv_client.rs:78:6
[INFO] [stdout]    |
[INFO] [stdout] 78 | /                     log_error!(
[INFO] [stdout] 79 | |                         logger,
[INFO] [stdout] 80 | |                         "Error, failed to provideyuvproof: {err}\nTransaction: {:?}",
[INFO] [stdout] 81 | |                         yuv_tx,
[INFO] [stdout] 82 | |                     )
[INFO] [stdout]    | |_____________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]   --> src/yuv_client.rs:78:6
[INFO] [stdout]    |
[INFO] [stdout] 78 | /                     log_error!(
[INFO] [stdout] 79 | |                         logger,
[INFO] [stdout] 80 | |                         "Error, failed to provideyuvproof: {err}\nTransaction: {:?}",
[INFO] [stdout] 81 | |                         yuv_tx,
[INFO] [stdout] 82 | |                     )
[INFO] [stdout]    | |_____________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:78:6
[INFO] [stdout]    |
[INFO] [stdout] 78 | /                     log_error!(
[INFO] [stdout] 79 | |                         logger,
[INFO] [stdout] 80 | |                         "Error, failed to provideyuvproof: {err}\nTransaction: {:?}",
[INFO] [stdout] 81 | |                         yuv_tx,
[INFO] [stdout] 82 | |                     )
[INFO] [stdout]    | |_____________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/yuv_client.rs:78:6
[INFO] [stdout]    |
[INFO] [stdout] 78 | /                     log_error!(
[INFO] [stdout] 79 | |                         logger,
[INFO] [stdout] 80 | |                         "Error, failed to provideyuvproof: {err}\nTransaction: {:?}",
[INFO] [stdout] 81 | |                         yuv_tx,
[INFO] [stdout] 82 | |                     )
[INFO] [stdout]    | |_____________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/yuv_client.rs:78:6
[INFO] [stdout]    |
[INFO] [stdout] 78 | /                     log_error!(
[INFO] [stdout] 79 | |                         logger,
[INFO] [stdout] 80 | |                         "Error, failed to provideyuvproof: {err}\nTransaction: {:?}",
[INFO] [stdout] 81 | |                         yuv_tx,
[INFO] [stdout] 82 | |                     )
[INFO] [stdout]    | |_____________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> src/yuv_client.rs:78:6
[INFO] [stdout]    |
[INFO] [stdout] 78 | /                     log_error!(
[INFO] [stdout] 79 | |                         logger,
[INFO] [stdout] 80 | |                         "Error, failed to provideyuvproof: {err}\nTransaction: {:?}",
[INFO] [stdout] 81 | |                         yuv_tx,
[INFO] [stdout] 82 | |                     )
[INFO] [stdout]    | |_____________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]   --> src/yuv_client.rs:78:6
[INFO] [stdout]    |
[INFO] [stdout] 78 | /                     log_error!(
[INFO] [stdout] 79 | |                         logger,
[INFO] [stdout] 80 | |                         "Error, failed to provideyuvproof: {err}\nTransaction: {:?}",
[INFO] [stdout] 81 | |                         yuv_tx,
[INFO] [stdout] 82 | |                     )
[INFO] [stdout]    | |_____________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]   --> src/yuv_client.rs:78:6
[INFO] [stdout]    |
[INFO] [stdout] 78 | /                     log_error!(
[INFO] [stdout] 79 | |                         logger,
[INFO] [stdout] 80 | |                         "Error, failed to provideyuvproof: {err}\nTransaction: {:?}",
[INFO] [stdout] 81 | |                         yuv_tx,
[INFO] [stdout] 82 | |                     )
[INFO] [stdout]    | |_____________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]   --> src/yuv_client.rs:78:6
[INFO] [stdout]    |
[INFO] [stdout] 78 | /                     log_error!(
[INFO] [stdout] 79 | |                         logger,
[INFO] [stdout] 80 | |                         "Error, failed to provideyuvproof: {err}\nTransaction: {:?}",
[INFO] [stdout] 81 | |                         yuv_tx,
[INFO] [stdout] 82 | |                     )
[INFO] [stdout]    | |_____________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]   --> src/yuv_client.rs:78:6
[INFO] [stdout]    |
[INFO] [stdout] 78 | /                     log_error!(
[INFO] [stdout] 79 | |                         logger,
[INFO] [stdout] 80 | |                         "Error, failed to provideyuvproof: {err}\nTransaction: {:?}",
[INFO] [stdout] 81 | |                         yuv_tx,
[INFO] [stdout] 82 | |                     )
[INFO] [stdout]    | |_____________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]   --> src/yuv_client.rs:78:6
[INFO] [stdout]    |
[INFO] [stdout] 78 | /                     log_error!(
[INFO] [stdout] 79 | |                         logger,
[INFO] [stdout] 80 | |                         "Error, failed to provideyuvproof: {err}\nTransaction: {:?}",
[INFO] [stdout] 81 | |                         yuv_tx,
[INFO] [stdout] 82 | |                     )
[INFO] [stdout]    | |_____________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]   --> src/yuv_client.rs:78:6
[INFO] [stdout]    |
[INFO] [stdout] 78 | /                     log_error!(
[INFO] [stdout] 79 | |                         logger,
[INFO] [stdout] 80 | |                         "Error, failed to provideyuvproof: {err}\nTransaction: {:?}",
[INFO] [stdout] 81 | |                         yuv_tx,
[INFO] [stdout] 82 | |                     )
[INFO] [stdout]    | |_____________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]   --> src/yuv_client.rs:78:6
[INFO] [stdout]    |
[INFO] [stdout] 78 | /                     log_error!(
[INFO] [stdout] 79 | |                         logger,
[INFO] [stdout] 80 | |                         "Error, failed to provideyuvproof: {err}\nTransaction: {:?}",
[INFO] [stdout] 81 | |                         yuv_tx,
[INFO] [stdout] 82 | |                     )
[INFO] [stdout]    | |_____________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]   --> src/yuv_client.rs:78:6
[INFO] [stdout]    |
[INFO] [stdout] 78 | /                     log_error!(
[INFO] [stdout] 79 | |                         logger,
[INFO] [stdout] 80 | |                         "Error, failed to provideyuvproof: {err}\nTransaction: {:?}",
[INFO] [stdout] 81 | |                         yuv_tx,
[INFO] [stdout] 82 | |                     )
[INFO] [stdout]    | |_____________________^
[INFO] [stdout]    |
[INFO] [stdout]    = note: no expected values for `feature`
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/yuv_client.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 | /                 log_error!(
[INFO] [stdout] 105 | |                     logger,
[INFO] [stdout] 106 | |                     "Error, failed to getrawyuvtransaction: {err}\nTx id: {:?}",
[INFO] [stdout] 107 | |                     txid,
[INFO] [stdout] 108 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/yuv_client.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 | /                 log_error!(
[INFO] [stdout] 105 | |                     logger,
[INFO] [stdout] 106 | |                     "Error, failed to getrawyuvtransaction: {err}\nTx id: {:?}",
[INFO] [stdout] 107 | |                     txid,
[INFO] [stdout] 108 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/yuv_client.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 | /                 log_error!(
[INFO] [stdout] 105 | |                     logger,
[INFO] [stdout] 106 | |                     "Error, failed to getrawyuvtransaction: {err}\nTx id: {:?}",
[INFO] [stdout] 107 | |                     txid,
[INFO] [stdout] 108 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/yuv_client.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 | /                 log_error!(
[INFO] [stdout] 105 | |                     logger,
[INFO] [stdout] 106 | |                     "Error, failed to getrawyuvtransaction: {err}\nTx id: {:?}",
[INFO] [stdout] 107 | |                     txid,
[INFO] [stdout] 108 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/yuv_client.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 | /                 log_error!(
[INFO] [stdout] 105 | |                     logger,
[INFO] [stdout] 106 | |                     "Error, failed to getrawyuvtransaction: {err}\nTx id: {:?}",
[INFO] [stdout] 107 | |                     txid,
[INFO] [stdout] 108 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/yuv_client.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 | /                 log_error!(
[INFO] [stdout] 105 | |                     logger,
[INFO] [stdout] 106 | |                     "Error, failed to getrawyuvtransaction: {err}\nTx id: {:?}",
[INFO] [stdout] 107 | |                     txid,
[INFO] [stdout] 108 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/yuv_client.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 | /                 log_error!(
[INFO] [stdout] 105 | |                     logger,
[INFO] [stdout] 106 | |                     "Error, failed to getrawyuvtransaction: {err}\nTx id: {:?}",
[INFO] [stdout] 107 | |                     txid,
[INFO] [stdout] 108 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/yuv_client.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 | /                 log_error!(
[INFO] [stdout] 105 | |                     logger,
[INFO] [stdout] 106 | |                     "Error, failed to getrawyuvtransaction: {err}\nTx id: {:?}",
[INFO] [stdout] 107 | |                     txid,
[INFO] [stdout] 108 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/yuv_client.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 | /                 log_error!(
[INFO] [stdout] 105 | |                     logger,
[INFO] [stdout] 106 | |                     "Error, failed to getrawyuvtransaction: {err}\nTx id: {:?}",
[INFO] [stdout] 107 | |                     txid,
[INFO] [stdout] 108 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/yuv_client.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 | /                 log_error!(
[INFO] [stdout] 105 | |                     logger,
[INFO] [stdout] 106 | |                     "Error, failed to getrawyuvtransaction: {err}\nTx id: {:?}",
[INFO] [stdout] 107 | |                     txid,
[INFO] [stdout] 108 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/yuv_client.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 | /                 log_error!(
[INFO] [stdout] 105 | |                     logger,
[INFO] [stdout] 106 | |                     "Error, failed to getrawyuvtransaction: {err}\nTx id: {:?}",
[INFO] [stdout] 107 | |                     txid,
[INFO] [stdout] 108 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/yuv_client.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 | /                 log_error!(
[INFO] [stdout] 105 | |                     logger,
[INFO] [stdout] 106 | |                     "Error, failed to getrawyuvtransaction: {err}\nTx id: {:?}",
[INFO] [stdout] 107 | |                     txid,
[INFO] [stdout] 108 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/yuv_client.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 | /                 log_error!(
[INFO] [stdout] 105 | |                     logger,
[INFO] [stdout] 106 | |                     "Error, failed to getrawyuvtransaction: {err}\nTx id: {:?}",
[INFO] [stdout] 107 | |                     txid,
[INFO] [stdout] 108 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/yuv_client.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 | /                 log_error!(
[INFO] [stdout] 105 | |                     logger,
[INFO] [stdout] 106 | |                     "Error, failed to getrawyuvtransaction: {err}\nTx id: {:?}",
[INFO] [stdout] 107 | |                     txid,
[INFO] [stdout] 108 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/yuv_client.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 | /                 log_error!(
[INFO] [stdout] 105 | |                     logger,
[INFO] [stdout] 106 | |                     "Error, failed to getrawyuvtransaction: {err}\nTx id: {:?}",
[INFO] [stdout] 107 | |                     txid,
[INFO] [stdout] 108 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/yuv_client.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 | /                 log_error!(
[INFO] [stdout] 105 | |                     logger,
[INFO] [stdout] 106 | |                     "Error, failed to getrawyuvtransaction: {err}\nTx id: {:?}",
[INFO] [stdout] 107 | |                     txid,
[INFO] [stdout] 108 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/yuv_client.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 | /                 log_error!(
[INFO] [stdout] 105 | |                     logger,
[INFO] [stdout] 106 | |                     "Error, failed to getrawyuvtransaction: {err}\nTx id: {:?}",
[INFO] [stdout] 107 | |                     txid,
[INFO] [stdout] 108 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/yuv_client.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 | /                 log_error!(
[INFO] [stdout] 105 | |                     logger,
[INFO] [stdout] 106 | |                     "Error, failed to getrawyuvtransaction: {err}\nTx id: {:?}",
[INFO] [stdout] 107 | |                     txid,
[INFO] [stdout] 108 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/yuv_client.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 | /                 log_error!(
[INFO] [stdout] 105 | |                     logger,
[INFO] [stdout] 106 | |                     "Error, failed to getrawyuvtransaction: {err}\nTx id: {:?}",
[INFO] [stdout] 107 | |                     txid,
[INFO] [stdout] 108 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/yuv_client.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 | /                 log_error!(
[INFO] [stdout] 105 | |                     logger,
[INFO] [stdout] 106 | |                     "Error, failed to getrawyuvtransaction: {err}\nTx id: {:?}",
[INFO] [stdout] 107 | |                     txid,
[INFO] [stdout] 108 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/yuv_client.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 | /                 log_error!(
[INFO] [stdout] 105 | |                     logger,
[INFO] [stdout] 106 | |                     "Error, failed to getrawyuvtransaction: {err}\nTx id: {:?}",
[INFO] [stdout] 107 | |                     txid,
[INFO] [stdout] 108 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]    --> src/yuv_client.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 | /                 log_error!(
[INFO] [stdout] 105 | |                     logger,
[INFO] [stdout] 106 | |                     "Error, failed to getrawyuvtransaction: {err}\nTx id: {:?}",
[INFO] [stdout] 107 | |                     txid,
[INFO] [stdout] 108 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]    --> src/yuv_client.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 | /                 log_error!(
[INFO] [stdout] 105 | |                     logger,
[INFO] [stdout] 106 | |                     "Error, failed to getrawyuvtransaction: {err}\nTx id: {:?}",
[INFO] [stdout] 107 | |                     txid,
[INFO] [stdout] 108 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]    --> src/yuv_client.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 | /                 log_error!(
[INFO] [stdout] 105 | |                     logger,
[INFO] [stdout] 106 | |                     "Error, failed to getrawyuvtransaction: {err}\nTx id: {:?}",
[INFO] [stdout] 107 | |                     txid,
[INFO] [stdout] 108 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]    --> src/yuv_client.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 | /                 log_error!(
[INFO] [stdout] 105 | |                     logger,
[INFO] [stdout] 106 | |                     "Error, failed to getrawyuvtransaction: {err}\nTx id: {:?}",
[INFO] [stdout] 107 | |                     txid,
[INFO] [stdout] 108 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]    --> src/yuv_client.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 | /                 log_error!(
[INFO] [stdout] 105 | |                     logger,
[INFO] [stdout] 106 | |                     "Error, failed to getrawyuvtransaction: {err}\nTx id: {:?}",
[INFO] [stdout] 107 | |                     txid,
[INFO] [stdout] 108 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]    --> src/yuv_client.rs:104:5
[INFO] [stdout]     |
[INFO] [stdout] 104 | /                 log_error!(
[INFO] [stdout] 105 | |                     logger,
[INFO] [stdout] 106 | |                     "Error, failed to getrawyuvtransaction: {err}\nTx id: {:?}",
[INFO] [stdout] 107 | |                     txid,
[INFO] [stdout] 108 | |                 );
[INFO] [stdout]     | |_________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: no expected values for `feature`
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `log_error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]     --> src/main.rs:1205:5
[INFO] [stdout]      |
[INFO] [stdout] 1205 |                 lightning::log_trace!(&an_logger, "Node announcement broadcasted");
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: no expected values for `feature`
[INFO] [stdout]      = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]     --> src/main.rs:1205:5
[INFO] [stdout]      |
[INFO] [stdout] 1205 |                 lightning::log_trace!(&an_logger, "Node announcement broadcasted");
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: no expected values for `feature`
[INFO] [stdout]      = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]     --> src/main.rs:1205:5
[INFO] [stdout]      |
[INFO] [stdout] 1205 |                 lightning::log_trace!(&an_logger, "Node announcement broadcasted");
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: no expected values for `feature`
[INFO] [stdout]      = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]     --> src/main.rs:1205:5
[INFO] [stdout]      |
[INFO] [stdout] 1205 |                 lightning::log_trace!(&an_logger, "Node announcement broadcasted");
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: no expected values for `feature`
[INFO] [stdout]      = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]     --> src/main.rs:1205:5
[INFO] [stdout]      |
[INFO] [stdout] 1205 |                 lightning::log_trace!(&an_logger, "Node announcement broadcasted");
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: no expected values for `feature`
[INFO] [stdout]      = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]     --> src/main.rs:1205:5
[INFO] [stdout]      |
[INFO] [stdout] 1205 |                 lightning::log_trace!(&an_logger, "Node announcement broadcasted");
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: no expected values for `feature`
[INFO] [stdout]      = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]     --> src/main.rs:1205:5
[INFO] [stdout]      |
[INFO] [stdout] 1205 |                 lightning::log_trace!(&an_logger, "Node announcement broadcasted");
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: no expected values for `feature`
[INFO] [stdout]      = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]     --> src/main.rs:1205:5
[INFO] [stdout]      |
[INFO] [stdout] 1205 |                 lightning::log_trace!(&an_logger, "Node announcement broadcasted");
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: no expected values for `feature`
[INFO] [stdout]      = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]     --> src/main.rs:1205:5
[INFO] [stdout]      |
[INFO] [stdout] 1205 |                 lightning::log_trace!(&an_logger, "Node announcement broadcasted");
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: no expected values for `feature`
[INFO] [stdout]      = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]     --> src/main.rs:1205:5
[INFO] [stdout]      |
[INFO] [stdout] 1205 |                 lightning::log_trace!(&an_logger, "Node announcement broadcasted");
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: no expected values for `feature`
[INFO] [stdout]      = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]     --> src/main.rs:1205:5
[INFO] [stdout]      |
[INFO] [stdout] 1205 |                 lightning::log_trace!(&an_logger, "Node announcement broadcasted");
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: no expected values for `feature`
[INFO] [stdout]      = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]     --> src/main.rs:1205:5
[INFO] [stdout]      |
[INFO] [stdout] 1205 |                 lightning::log_trace!(&an_logger, "Node announcement broadcasted");
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: no expected values for `feature`
[INFO] [stdout]      = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]     --> src/main.rs:1205:5
[INFO] [stdout]      |
[INFO] [stdout] 1205 |                 lightning::log_trace!(&an_logger, "Node announcement broadcasted");
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: no expected values for `feature`
[INFO] [stdout]      = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]     --> src/main.rs:1205:5
[INFO] [stdout]      |
[INFO] [stdout] 1205 |                 lightning::log_trace!(&an_logger, "Node announcement broadcasted");
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: no expected values for `feature`
[INFO] [stdout]      = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]     --> src/main.rs:1205:5
[INFO] [stdout]      |
[INFO] [stdout] 1205 |                 lightning::log_trace!(&an_logger, "Node announcement broadcasted");
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: no expected values for `feature`
[INFO] [stdout]      = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]     --> src/main.rs:1205:5
[INFO] [stdout]      |
[INFO] [stdout] 1205 |                 lightning::log_trace!(&an_logger, "Node announcement broadcasted");
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: no expected values for `feature`
[INFO] [stdout]      = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]     --> src/main.rs:1205:5
[INFO] [stdout]      |
[INFO] [stdout] 1205 |                 lightning::log_trace!(&an_logger, "Node announcement broadcasted");
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: no expected values for `feature`
[INFO] [stdout]      = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]     --> src/main.rs:1205:5
[INFO] [stdout]      |
[INFO] [stdout] 1205 |                 lightning::log_trace!(&an_logger, "Node announcement broadcasted");
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: no expected values for `feature`
[INFO] [stdout]      = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]     --> src/main.rs:1205:5
[INFO] [stdout]      |
[INFO] [stdout] 1205 |                 lightning::log_trace!(&an_logger, "Node announcement broadcasted");
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: no expected values for `feature`
[INFO] [stdout]      = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]     --> src/main.rs:1205:5
[INFO] [stdout]      |
[INFO] [stdout] 1205 |                 lightning::log_trace!(&an_logger, "Node announcement broadcasted");
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: no expected values for `feature`
[INFO] [stdout]      = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]     --> src/main.rs:1205:5
[INFO] [stdout]      |
[INFO] [stdout] 1205 |                 lightning::log_trace!(&an_logger, "Node announcement broadcasted");
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: no expected values for `feature`
[INFO] [stdout]      = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_off`
[INFO] [stdout]     --> src/main.rs:1205:5
[INFO] [stdout]      |
[INFO] [stdout] 1205 |                 lightning::log_trace!(&an_logger, "Node announcement broadcasted");
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: no expected values for `feature`
[INFO] [stdout]      = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_error`
[INFO] [stdout]     --> src/main.rs:1205:5
[INFO] [stdout]      |
[INFO] [stdout] 1205 |                 lightning::log_trace!(&an_logger, "Node announcement broadcasted");
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: no expected values for `feature`
[INFO] [stdout]      = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_warn`
[INFO] [stdout]     --> src/main.rs:1205:5
[INFO] [stdout]      |
[INFO] [stdout] 1205 |                 lightning::log_trace!(&an_logger, "Node announcement broadcasted");
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: no expected values for `feature`
[INFO] [stdout]      = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_info`
[INFO] [stdout]     --> src/main.rs:1205:5
[INFO] [stdout]      |
[INFO] [stdout] 1205 |                 lightning::log_trace!(&an_logger, "Node announcement broadcasted");
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: no expected values for `feature`
[INFO] [stdout]      = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_debug`
[INFO] [stdout]     --> src/main.rs:1205:5
[INFO] [stdout]      |
[INFO] [stdout] 1205 |                 lightning::log_trace!(&an_logger, "Node announcement broadcasted");
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: no expected values for `feature`
[INFO] [stdout]      = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `max_level_trace`
[INFO] [stdout]     --> src/main.rs:1205:5
[INFO] [stdout]      |
[INFO] [stdout] 1205 |                 lightning::log_trace!(&an_logger, "Node announcement broadcasted");
[INFO] [stdout]      |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: no expected values for `feature`
[INFO] [stdout]      = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]      = help: try referring to `$crate::log_given_level` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]      = help: the macro `$crate::log_given_level` may come from an old version of the `lightning` crate, try updating your dependency with `cargo update -p lightning`
[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 macro `$crate::log_given_level` which comes from the expansion of the macro `lightning::log_trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: direct cast of function item into an integer
[INFO] [stdout]     --> src/main.rs:1292:44
[INFO] [stdout]      |
[INFO] [stdout] 1292 |             new_action.sa_sigaction = dummy_handler as libc::sighandler_t;
[INFO] [stdout]      |                                                     ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: `#[warn(function_casts_as_integer)]` on by default
[INFO] [stdout] help: first cast to a pointer `as *const ()`
[INFO] [stdout]      |
[INFO] [stdout] 1292 |             new_action.sa_sigaction = dummy_handler as *const () as libc::sighandler_t;
[INFO] [stdout]      |                                                     ++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]   --> src/bitcoind_client.rs:53:20
[INFO] [stdout]    |
[INFO] [stdout] 53 |     fn get_best_block(&self) -> AsyncBlockSourceResult<(BlockHash, Option<u32>)> {
[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] 53 |     fn get_best_block(&self) -> AsyncBlockSourceResult<'_, (BlockHash, Option<u32>)> {
[INFO] [stdout]    |                                                        +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 2m 28s
[INFO] [stderr] warning: the following packages contain code that will be rejected by a future version of Rust: lightning v0.3.1 (https://github.com/akitamiabtc/yuv-lightning.git?tag=v0.3.1%2Blightning-0.0.123#259f597c)
[INFO] [stderr] note: to see what the problems were, use the option `--future-incompat-report`, or run `cargo report future-incompatibilities --id 4`
[INFO] running `Command { std: "docker" "inspect" "dfcf8cb7d8f672e9e1767d2e39deacf2f1d8534d3d6ef8e0e6b5bb4a0be57bac", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "dfcf8cb7d8f672e9e1767d2e39deacf2f1d8534d3d6ef8e0e6b5bb4a0be57bac", kill_on_drop: false }`
[INFO] [stdout] dfcf8cb7d8f672e9e1767d2e39deacf2f1d8534d3d6ef8e0e6b5bb4a0be57bac
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:845e597a41426bbf2703be69acdb67d10b6de511142d05cba7bbe119c898b2c7" "/opt/rustwide/cargo-home/bin/cargo" "+0d162b25edd5bf0dba9a22e83b614f1113e90474" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] c7eb6554250c8e7e5c00d3167fe79dbd050564c0902d613295c17f79e8035b63
[INFO] running `Command { std: "docker" "start" "-a" "c7eb6554250c8e7e5c00d3167fe79dbd050564c0902d613295c17f79e8035b63", kill_on_drop: false }`
[INFO] [stderr]    Compiling zerocopy v0.7.34
[INFO] [stderr]    Compiling futures-core v0.3.30
[INFO] [stderr]    Compiling allocator-api2 v0.2.18
[INFO] [stderr]    Compiling futures-sink v0.3.30
[INFO] [stderr]    Compiling base64 v0.13.1
[INFO] [stderr]    Compiling futures-io v0.3.30
[INFO] [stderr]    Compiling getrandom v0.2.15
[INFO] [stderr]    Compiling mio v0.8.11
[INFO] [stderr]    Compiling spin v0.9.8
[INFO] [stderr]    Compiling futures-task v0.3.30
[INFO] [stderr]    Compiling serde v1.0.203
[INFO] [stderr]    Compiling zeroize v1.8.1
[INFO] [stderr]    Compiling tracing v0.1.40
[INFO] [stderr]    Compiling bitcoin-private v0.1.0
[INFO] [stderr]    Compiling secp256k1-sys v0.8.1
[INFO] [stderr]    Compiling hex_lit v0.1.1
[INFO] [stderr]    Compiling futures-channel v0.3.30
[INFO] [stderr]    Compiling unicode-normalization v0.1.23
[INFO] [stderr]    Compiling unicode-bidi v0.3.15
[INFO] [stderr]    Compiling generic-array v0.14.7
[INFO] [stderr]    Compiling bech32 v0.9.1
[INFO] [stderr]    Compiling rand_core v0.6.4
[INFO] [stderr]    Compiling ring v0.17.8
[INFO] [stderr]    Compiling subtle v2.5.0
[INFO] [stderr]    Compiling rustls-native-certs v0.6.3
[INFO] [stderr]    Compiling ahash v0.8.11
[INFO] [stderr]    Compiling thiserror v1.0.61
[INFO] [stderr]    Compiling futures-util v0.3.30
[INFO] [stderr]    Compiling encoding_rs v0.8.34
[INFO] [stderr]    Compiling ipnet v2.9.0
[INFO] [stderr]    Compiling rand_chacha v0.3.1
[INFO] [stderr]    Compiling tokio v1.38.0
[INFO] [stderr]    Compiling nanorand v0.7.0
[INFO] [stderr]    Compiling typeid v1.0.0
[INFO] [stderr]    Compiling core2 v0.3.3
[INFO] [stderr]    Compiling inventory v0.3.15
[INFO] [stderr]    Compiling hashbrown v0.14.5
[INFO] [stderr]    Compiling idna v0.5.0
[INFO] [stderr]    Compiling rand v0.8.5
[INFO] [stderr]    Compiling flume v0.11.0
[INFO] [stderr]    Compiling core2 v0.4.0
[INFO] [stderr]    Compiling wyz v0.5.1
[INFO] [stderr]    Compiling radium v0.7.0
[INFO] [stderr]    Compiling funty v2.0.0
[INFO] [stderr]    Compiling block-buffer v0.10.4
[INFO] [stderr]    Compiling event-bus v0.3.5 (https://github.com/akitamiabtc/yuv.git?tag=v0.3.6#7a29c898)
[INFO] [stderr]    Compiling crypto-common v0.1.6
[INFO] [stderr]    Compiling block-buffer v0.9.0
[INFO] [stderr]    Compiling digest v0.9.0
[INFO] [stderr]    Compiling der v0.7.9
[INFO] [stderr]    Compiling event-listener v2.5.3
[INFO] [stderr]    Compiling url v2.5.2
[INFO] [stderr]    Compiling digest v0.10.7
[INFO] [stderr]    Compiling sha-1 v0.9.8
[INFO] [stderr]    Compiling indexmap v2.2.6
[INFO] [stderr]    Compiling async-lock v2.8.0
[INFO] [stderr]    Compiling pin-project v1.1.5
[INFO] [stderr]    Compiling bitvec v1.0.1
[INFO] [stderr]    Compiling hmac v0.12.1
[INFO] [stderr]    Compiling sct v0.7.1
[INFO] [stderr]    Compiling rustls-webpki v0.101.7
[INFO] [stderr]    Compiling fs2 v0.4.3
[INFO] [stderr]    Compiling futures-timer v3.0.3
[INFO] [stderr]    Compiling rustls-pki-types v1.7.0
[INFO] [stderr]    Compiling hex-conservative v0.1.2
[INFO] [stderr]    Compiling toml_edit v0.19.15
[INFO] [stderr]    Compiling half v2.4.1
[INFO] [stderr]    Compiling rustls v0.21.12
[INFO] [stderr]    Compiling spki v0.7.3
[INFO] [stderr]    Compiling base16ct v0.2.0
[INFO] [stderr]    Compiling ciborium-io v0.2.2
[INFO] [stderr]    Compiling ciborium-ll v0.2.2
[INFO] [stderr]    Compiling miniz_oxide v0.7.4
[INFO] [stderr]    Compiling pkcs8 v0.10.2
[INFO] [stderr]    Compiling sec1 v0.7.3
[INFO] [stderr]    Compiling rustls-webpki v0.102.4
[INFO] [stderr]    Compiling crc v1.8.1
[INFO] [stderr]    Compiling hkdf v0.12.4
[INFO] [stderr]    Compiling crypto-bigint v0.5.5
[INFO] [stderr]    Compiling errno v0.2.8
[INFO] [stderr]    Compiling instant v0.1.13
[INFO] [stderr]    Compiling route-recognizer v0.3.1
[INFO] [stderr]    Compiling flate2 v1.0.30
[INFO] [stderr]    Compiling webpki-roots v0.26.3
[INFO] [stderr]    Compiling parking_lot_core v0.8.6
[INFO] [stderr]    Compiling openssl-sys v0.9.102
[INFO] [stderr]    Compiling rfc6979 v0.4.0
[INFO] [stderr]    Compiling signature v2.2.0
[INFO] [stderr]    Compiling socks v0.3.4
[INFO] [stderr]    Compiling serde_json v1.0.117
[INFO] [stderr]    Compiling bitcoin_hashes v0.12.0
[INFO] [stderr]    Compiling serde_urlencoded v0.7.1
[INFO] [stderr]    Compiling erased-serde v0.4.5
[INFO] [stderr]    Compiling beef v0.5.2
[INFO] [stderr]    Compiling proc-macro-crate v1.3.1
[INFO] [stderr]    Compiling rustls v0.22.4
[INFO] [stderr]    Compiling serde_bytes v0.11.14
[INFO] [stderr]    Compiling ciborium v0.2.2
[INFO] [stderr]    Compiling parking_lot v0.11.2
[INFO] [stderr]    Compiling futures v0.3.30
[INFO] [stderr]    Compiling soketto v0.7.1
[INFO] [stderr]    Compiling ff v0.13.0
[INFO] [stderr]    Compiling tower v0.4.13
[INFO] [stderr]    Compiling openssl v0.10.64
[INFO] [stderr]    Compiling typetag v0.2.16
[INFO] [stderr]    Compiling crossbeam-epoch v0.9.18
[INFO] [stderr]    Compiling group v0.13.0
[INFO] [stderr]    Compiling libsqlite3-sys v0.25.2
[INFO] [stderr]    Compiling bitcoin-internals v0.1.0
[INFO] [stderr]    Compiling jsonrpsee-types v0.20.3
[INFO] [stderr]    Compiling secp256k1 v0.27.0
[INFO] [stderr]    Compiling elliptic-curve v0.13.8
[INFO] [stderr]    Compiling jsonrpc v0.13.0
[INFO] [stderr]    Compiling sha2 v0.10.8
[INFO] [stderr]    Compiling std-shims v0.1.1
[INFO] [stderr]    Compiling hashlink v0.8.4
[INFO] [stderr]    Compiling fallible-iterator v0.2.0
[INFO] [stderr]    Compiling merlin v3.0.0
[INFO] [stderr]    Compiling signal-hook v0.3.17
[INFO] [stderr]    Compiling sled v0.34.7
[INFO] [stderr]    Compiling tokio-util v0.7.11
[INFO] [stderr]    Compiling bitcoin v0.30.2
[INFO] [stderr]    Compiling tokio-rustls v0.24.1
[INFO] [stderr] error: could not compile `tokio` (lib)
[INFO] [stderr] 
[INFO] [stderr] Caused by:
[INFO] [stderr]   process didn't exit successfully: `/opt/rustwide/rustup-home/toolchains/0d162b25edd5bf0dba9a22e83b614f1113e90474/bin/rustc --crate-name tokio --edition=2021 /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/tokio-1.38.0/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debuginfo=2 --cfg 'feature="bytes"' --cfg 'feature="default"' --cfg 'feature="io-util"' --cfg 'feature="libc"' --cfg 'feature="macros"' --cfg 'feature="mio"' --cfg 'feature="net"' --cfg 'feature="num_cpus"' --cfg 'feature="rt"' --cfg 'feature="rt-multi-thread"' --cfg 'feature="socket2"' --cfg 'feature="sync"' --cfg 'feature="time"' --cfg 'feature="tokio-macros"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("bytes", "default", "fs", "full", "io-std", "io-util", "libc", "macros", "mio", "net", "num_cpus", "parking_lot", "process", "rt", "rt-multi-thread", "signal", "signal-hook-registry", "socket2", "sync", "test-util", "time", "tokio-macros", "tracing", "windows-sys"))' -C metadata=62a7c2e2c400aeb3 -C extra-filename=-9e3fa13d542e51aa --out-dir /opt/rustwide/target/debug/deps -L dependency=/opt/rustwide/target/debug/deps --extern bytes=/opt/rustwide/target/debug/deps/libbytes-9c2a396be262bdae.rmeta --extern libc=/opt/rustwide/target/debug/deps/liblibc-ae7c44f539cff960.rmeta --extern mio=/opt/rustwide/target/debug/deps/libmio-9416a1a306dc8954.rmeta --extern num_cpus=/opt/rustwide/target/debug/deps/libnum_cpus-bfcfefbecb97c767.rmeta --extern pin_project_lite=/opt/rustwide/target/debug/deps/libpin_project_lite-e0c50e8704e39276.rmeta --extern socket2=/opt/rustwide/target/debug/deps/libsocket2-58d39aa049a8f195.rmeta --extern tokio_macros=/opt/rustwide/target/debug/deps/libtokio_macros-591a9edfb3626284.so --cap-lints allow --cap-lints=forbid` (signal: 9, SIGKILL: kill)
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] running `Command { std: "docker" "inspect" "c7eb6554250c8e7e5c00d3167fe79dbd050564c0902d613295c17f79e8035b63", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "c7eb6554250c8e7e5c00d3167fe79dbd050564c0902d613295c17f79e8035b63", kill_on_drop: false }`
[INFO] [stdout] c7eb6554250c8e7e5c00d3167fe79dbd050564c0902d613295c17f79e8035b63
