[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] documenting akitamiabtc/yuv-lightning-ldk-sample against beta-2025-04-13 for beta-1.87-rustdoc-1
[INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fakitamiabtc%2Fyuv-lightning-ldk-sample" "/workspace/builds/worker-4-tc2/source", kill_on_drop: false }`
[INFO] [stderr] Cloning into '/workspace/builds/worker-4-tc2/source'...
[INFO] [stderr] done.
[INFO] validating manifest of git repo https://github.com/akitamiabtc/yuv-lightning-ldk-sample on toolchain beta-2025-04-13
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+beta-2025-04-13" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] removed /workspace/builds/worker-4-tc2/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-4-tc2/source/Cargo.toml
[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" "+beta-2025-04-13" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating git repository `https://github.com/akitamiabtc/yuv-lightning.git`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:b0b074c097205a61b89e8ad263052f976b2b332c4dc5f02aef1fe52501660d6e" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2025-04-13" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 010eefa15f19dd03044d1a0b0ab6f1f9fc559faf03977ac121d3edf95d588571
[INFO] running `Command { std: "docker" "start" "-a" "010eefa15f19dd03044d1a0b0ab6f1f9fc559faf03977ac121d3edf95d588571", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "010eefa15f19dd03044d1a0b0ab6f1f9fc559faf03977ac121d3edf95d588571", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "010eefa15f19dd03044d1a0b0ab6f1f9fc559faf03977ac121d3edf95d588571", kill_on_drop: false }`
[INFO] [stdout] 010eefa15f19dd03044d1a0b0ab6f1f9fc559faf03977ac121d3edf95d588571
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:b0b074c097205a61b89e8ad263052f976b2b332c4dc5f02aef1fe52501660d6e" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2025-04-13" "doc" "--frozen" "--no-deps" "--document-private-items" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 19fa3699b7035aba924e4ea1eeb148e269d938b9a9ffbfa952cb1a9da33f8ecb
[INFO] running `Command { std: "docker" "start" "-a" "19fa3699b7035aba924e4ea1eeb148e269d938b9a9ffbfa952cb1a9da33f8ecb", kill_on_drop: false }`
[INFO] [stderr]    Compiling proc-macro2 v1.0.85
[INFO] [stderr]    Compiling unicode-ident v1.0.12
[INFO] [stderr]     Checking cfg-if v1.0.0
[INFO] [stderr]    Compiling libc v0.2.155
[INFO] [stderr]    Compiling version_check v0.9.4
[INFO] [stderr]    Compiling autocfg v1.3.0
[INFO] [stderr]    Compiling cc v1.0.99
[INFO] [stderr]     Checking once_cell v1.19.0
[INFO] [stderr]    Compiling serde v1.0.203
[INFO] [stderr]     Checking log v0.4.21
[INFO] [stderr]     Checking scopeguard v1.2.0
[INFO] [stderr]     Checking itoa v1.0.11
[INFO] [stderr]     Checking pin-project-lite v0.2.14
[INFO] [stderr]     Checking zerocopy v0.7.34
[INFO] [stderr]     Checking bytes v1.6.0
[INFO] [stderr]     Checking futures-core v0.3.30
[INFO] [stderr]     Checking allocator-api2 v0.2.18
[INFO] [stderr]     Checking ppv-lite86 v0.2.17
[INFO] [stderr]     Checking futures-sink v0.3.30
[INFO] [stderr]    Compiling typenum v1.17.0
[INFO] [stderr]     Checking ryu v1.0.18
[INFO] [stderr]     Checking memchr v2.7.4
[INFO] [stderr]    Compiling serde_json v1.0.117
[INFO] [stderr]     Checking base64 v0.13.1
[INFO] [stderr]    Compiling ahash v0.8.11
[INFO] [stderr]    Compiling generic-array v0.14.7
[INFO] [stderr]     Checking untrusted v0.9.0
[INFO] [stderr]     Checking futures-io v0.3.30
[INFO] [stderr]     Checking futures-channel v0.3.30
[INFO] [stderr]    Compiling lock_api v0.4.12
[INFO] [stderr]    Compiling slab v0.4.9
[INFO] [stderr]     Checking pin-utils v0.1.0
[INFO] [stderr]    Compiling bitcoin-private v0.1.0
[INFO] [stderr]     Checking futures-task v0.3.30
[INFO] [stderr]     Checking tracing-core v0.1.32
[INFO] [stderr]     Checking fnv v1.0.7
[INFO] [stderr]    Compiling httparse v1.9.4
[INFO] [stderr]     Checking http v0.2.12
[INFO] [stderr]     Checking tinyvec_macros v0.1.1
[INFO] [stderr]    Compiling hex_lit v0.1.1
[INFO] [stderr]     Checking percent-encoding v2.3.1
[INFO] [stderr]    Compiling bitcoin v0.30.2
[INFO] [stderr]     Checking tinyvec v1.6.0
[INFO] [stderr]     Checking equivalent v1.0.1
[INFO] [stderr]     Checking form_urlencoded v1.2.1
[INFO] [stderr]     Checking bech32 v0.9.1
[INFO] [stderr]     Checking hashbrown v0.14.5
[INFO] [stderr]     Checking unicode-bidi v0.3.15
[INFO] [stderr]     Checking try-lock v0.2.5
[INFO] [stderr]     Checking tower-service v0.3.2
[INFO] [stderr]     Checking httpdate v1.0.3
[INFO] [stderr]     Checking want v0.3.1
[INFO] [stderr]    Compiling rustls v0.21.12
[INFO] [stderr]     Checking subtle v2.5.0
[INFO] [stderr]     Checking base64 v0.21.7
[INFO] [stderr]    Compiling thiserror v1.0.61
[INFO] [stderr]     Checking openssl-probe v0.1.5
[INFO] [stderr]     Checking rustls-pemfile v1.0.4
[INFO] [stderr]     Checking getrandom v0.2.15
[INFO] [stderr]     Checking mio v0.8.11
[INFO] [stderr]     Checking socket2 v0.5.7
[INFO] [stderr]     Checking num_cpus v1.16.0
[INFO] [stderr]     Checking smallvec v1.13.2
[INFO] [stderr]    Compiling quote v1.0.36
[INFO] [stderr]     Checking spin v0.9.8
[INFO] [stderr]     Checking rustls-native-certs v0.6.3
[INFO] [stderr]     Checking rand_core v0.6.4
[INFO] [stderr]     Checking const-oid v0.9.6
[INFO] [stderr]     Checking encoding_rs v0.8.34
[INFO] [stderr]    Compiling eyre v0.6.12
[INFO] [stderr]     Checking webpki-roots v0.25.4
[INFO] [stderr]     Checking sync_wrapper v0.1.2
[INFO] [stderr]     Checking mime v0.3.17
[INFO] [stderr]    Compiling syn v2.0.66
[INFO] [stderr]     Checking rand_chacha v0.3.1
[INFO] [stderr]     Checking ipnet v2.9.0
[INFO] [stderr]     Checking nanorand v0.7.0
[INFO] [stderr]     Checking typeid v1.0.0
[INFO] [stderr]     Checking indenter v0.3.3
[INFO] [stderr]     Checking core2 v0.3.3
[INFO] [stderr]     Checking cpufeatures v0.2.12
[INFO] [stderr]    Compiling pkg-config v0.3.30
[INFO] [stderr]     Checking hex v0.4.3
[INFO] [stderr]    Compiling vcpkg v0.2.15
[INFO] [stderr]     Checking inventory v0.3.15
[INFO] [stderr]     Checking core2 v0.4.0
[INFO] [stderr]    Compiling radium v0.7.0
[INFO] [stderr]    Compiling parking_lot_core v0.9.10
[INFO] [stderr]     Checking byteorder v1.5.0
[INFO] [stderr]     Checking rand v0.8.5
[INFO] [stderr]    Compiling ring v0.17.8
[INFO] [stderr]    Compiling secp256k1-sys v0.8.1
[INFO] [stderr]     Checking http-body v0.4.6
[INFO] [stderr]     Checking tap v1.0.1
[INFO] [stderr]    Compiling anyhow v1.0.86
[INFO] [stderr]     Checking flume v0.11.0
[INFO] [stderr]     Checking wyz v0.5.1
[INFO] [stderr]     Checking funty v2.0.0
[INFO] [stderr]     Checking opaque-debug v0.3.1
[INFO] [stderr]     Checking unicode-normalization v0.1.23
[INFO] [stderr]    Compiling syn v1.0.109
[INFO] [stderr]     Checking parking_lot v0.12.3
[INFO] [stderr]    Compiling build_const v0.2.2
[INFO] [stderr]     Checking indexmap v2.2.6
[INFO] [stderr]     Checking event-listener v2.5.3
[INFO] [stderr]    Compiling crc v1.8.1
[INFO] [stderr]     Checking async-lock v2.8.0
[INFO] [stderr]     Checking fs2 v0.4.3
[INFO] [stderr]     Checking futures-timer v3.0.3
[INFO] [stderr]    Compiling snap v1.1.1
[INFO] [stderr]     Checking rustc-hash v1.1.0
[INFO] [stderr]     Checking tower-layer v0.3.2
[INFO] [stderr]     Checking hex-conservative v0.1.2
[INFO] [stderr]    Compiling toml_datetime v0.6.6
[INFO] [stderr]     Checking rustls-pki-types v1.7.0
[INFO] [stderr]     Checking bitvec v1.0.1
[INFO] [stderr]    Compiling winnow v0.5.40
[INFO] [stderr]     Checking idna v0.5.0
[INFO] [stderr]    Compiling openssl-sys v0.9.102
[INFO] [stderr]     Checking crc32fast v1.4.2
[INFO] [stderr]     Checking half v2.4.1
[INFO] [stderr]    Compiling rustls v0.22.4
[INFO] [stderr]     Checking base16ct v0.2.0
[INFO] [stderr]     Checking adler v1.0.2
[INFO] [stderr]    Compiling crossbeam-utils v0.8.20
[INFO] [stderr]     Checking ciborium-io v0.2.2
[INFO] [stderr]    Compiling parking_lot_core v0.8.6
[INFO] [stderr]     Checking miniz_oxide v0.7.4
[INFO] [stderr]    Compiling libsqlite3-sys v0.25.2
[INFO] [stderr]     Checking errno v0.2.8
[INFO] [stderr]     Checking instant v0.1.13
[INFO] [stderr]     Checking foreign-types-shared v0.1.1
[INFO] [stderr]    Compiling openssl v0.10.64
[INFO] [stderr]     Checking ciborium-ll v0.2.2
[INFO] [stderr]     Checking bitflags v2.5.0
[INFO] [stderr]     Checking route-recognizer v0.3.1
[INFO] [stderr]     Checking url v2.5.2
[INFO] [stderr]    Compiling heck v0.4.1
[INFO] [stderr]    Compiling rustversion v1.0.17
[INFO] [stderr]    Compiling bitcoin-internals v0.1.0
[INFO] [stderr]     Checking integer-encoding v3.0.4
[INFO] [stderr]     Checking foreign-types v0.3.2
[INFO] [stderr]     Checking webpki-roots v0.26.3
[INFO] [stderr]     Checking socks v0.3.4
[INFO] [stderr]    Compiling ahash v0.7.8
[INFO] [stderr]    Compiling signal-hook v0.3.17
[INFO] [stderr]     Checking base64 v0.22.1
[INFO] [stderr]     Checking crossbeam-epoch v0.9.18
[INFO] [stderr]     Checking parking_lot v0.11.2
[INFO] [stderr]     Checking flate2 v1.0.30
[INFO] [stderr]     Checking hashlink v0.8.4
[INFO] [stderr]     Checking std-shims v0.1.1
[INFO] [stderr]     Checking fxhash v0.2.1
[INFO] [stderr]     Checking signal-hook-registry v1.4.2
[INFO] [stderr]    Compiling num-traits v0.2.19
[INFO] [stderr]     Checking fallible-iterator v0.2.0
[INFO] [stderr]     Checking keccak v0.1.5
[INFO] [stderr]     Checking bitflags v1.3.2
[INFO] [stderr]     Checking fallible-streaming-iterator v0.1.9
[INFO] [stderr]     Checking sled v0.34.7
[INFO] [stderr]     Checking lazy_static v1.4.0
[INFO] [stderr]     Checking signal-hook-mio v0.2.3
[INFO] [stderr]     Checking iana-time-zone v0.1.60
[INFO] [stderr]     Checking chunked_transfer v1.5.0
[INFO] [stderr]     Checking bech32 v0.8.1
[INFO] [stderr]     Checking crossterm v0.27.0
[INFO] [stderr]     Checking rusqlite v0.28.0
[INFO] [stderr]     Checking home v0.5.9
[INFO] [stderr]     Checking bitcoin-bech32 v0.12.1
[INFO] [stderr]    Compiling toml_edit v0.19.15
[INFO] [stderr]     Checking ff v0.13.0
[INFO] [stderr]     Checking group v0.13.0
[INFO] [stderr]     Checking chrono v0.4.38
[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]     Checking event-bus v0.3.5 (https://github.com/akitamiabtc/yuv.git?tag=v0.3.6#7a29c898)
[INFO] [stderr]    Compiling proc-macro-crate v1.3.1
[INFO] [stderr]     Checking sct v0.7.1
[INFO] [stderr]     Checking rustls-webpki v0.101.7
[INFO] [stderr]     Checking rustls-webpki v0.102.4
[INFO] [stderr]     Checking tokio v1.38.0
[INFO] [stderr]     Checking zeroize v1.8.1
[INFO] [stderr]     Checking futures-util v0.3.30
[INFO] [stderr]     Checking der v0.7.9
[INFO] [stderr]     Checking multiexp v0.4.0
[INFO] [stderr]     Checking merlin v3.0.0
[INFO] [stderr]    Compiling jsonrpsee-proc-macros v0.20.3
[INFO] [stderr]    Compiling bdk-macros v0.6.0
[INFO] [stderr]     Checking pin-project v1.1.5
[INFO] [stderr]     Checking tracing v0.1.40
[INFO] [stderr]     Checking spki v0.7.3
[INFO] [stderr]     Checking crypto-common v0.1.6
[INFO] [stderr]     Checking block-buffer v0.10.4
[INFO] [stderr]     Checking block-buffer v0.9.0
[INFO] [stderr]     Checking digest v0.9.0
[INFO] [stderr]     Checking sec1 v0.7.3
[INFO] [stderr]     Checking crypto-bigint v0.5.5
[INFO] [stderr]     Checking sha-1 v0.9.8
[INFO] [stderr]     Checking digest v0.10.7
[INFO] [stderr]     Checking pkcs8 v0.10.2
[INFO] [stderr]     Checking hmac v0.12.1
[INFO] [stderr]     Checking hkdf v0.12.4
[INFO] [stderr]     Checking rfc6979 v0.4.0
[INFO] [stderr]     Checking signature v2.2.0
[INFO] [stderr]     Checking sha2 v0.10.8
[INFO] [stderr]     Checking futures v0.3.30
[INFO] [stderr]     Checking tower v0.4.13
[INFO] [stderr]     Checking soketto v0.7.1
[INFO] [stderr]     Checking tokio-util v0.7.11
[INFO] [stderr]     Checking tokio-rustls v0.24.1
[INFO] [stderr]     Checking tokio-stream v0.1.15
[INFO] [stderr]     Checking rusty-leveldb v3.0.0
[INFO] [stderr]     Checking elliptic-curve v0.13.8
[INFO] [stderr]     Checking h2 v0.3.26
[INFO] [stderr]     Checking ecdsa v0.16.9
[INFO] [stderr]     Checking k256 v0.13.3
[INFO] [stderr]     Checking bitcoin_hashes v0.12.0
[INFO] [stderr]     Checking serde_urlencoded v0.7.1
[INFO] [stderr]     Checking erased-serde v0.4.5
[INFO] [stderr]     Checking beef v0.5.2
[INFO] [stderr]     Checking ciborium v0.2.2
[INFO] [stderr]     Checking serde_bytes v0.11.14
[INFO] [stderr]     Checking typetag v0.2.16
[INFO] [stderr]     Checking jsonrpsee-types v0.20.3
[INFO] [stderr]     Checking ureq v2.9.7
[INFO] [stderr]     Checking jsonrpc v0.13.0
[INFO] [stderr]     Checking secp256k1 v0.27.0
[INFO] [stderr]     Checking hyper v0.14.29
[INFO] [stderr]     Checking hyper-rustls v0.24.2
[INFO] [stderr]     Checking jsonrpsee-core v0.20.3
[INFO] [stderr]     Checking reqwest v0.11.27
[INFO] [stderr]     Checking yuv-pixels v0.3.5 (https://github.com/akitamiabtc/yuv.git?tag=v0.3.6#7a29c898)
[INFO] [stderr]     Checking core-rpc-json v0.17.0
[INFO] [stderr]     Checking electrum-client v0.18.0
[INFO] [stderr]     Checking esplora-client v0.6.0
[INFO] [stderr]     Checking miniscript v10.0.0
[INFO] [stderr]     Checking bulletproof v0.3.5 (https://github.com/akitamiabtc/yuv.git?tag=v0.3.6#7a29c898)
[INFO] [stderr]     Checking jsonrpc v0.3.5 (https://github.com/akitamiabtc/yuv.git?tag=v0.3.6#7a29c898)
[INFO] [stderr]     Checking bitcoin-client v0.3.5 (https://github.com/akitamiabtc/yuv.git?tag=v0.3.6#7a29c898)
[INFO] [stderr]     Checking jsonrpsee-server v0.20.3
[INFO] [stderr]     Checking jsonrpsee-http-client v0.20.3
[INFO] [stderr]     Checking jsonrpsee v0.20.3
[INFO] [stderr]     Checking core-rpc v0.17.0
[INFO] [stderr]     Checking bdk v0.29.0+fix.1 (https://github.com/akitamiabtc/yuv.git?tag=v0.3.6#7a29c898)
[INFO] [stderr]     Checking yuv-types v0.3.5 (https://github.com/akitamiabtc/yuv.git?tag=v0.3.6#7a29c898)
[INFO] [stderr]     Checking lightning v0.3.1 (https://github.com/akitamiabtc/yuv-lightning.git?tag=v0.3.1%2Blightning-0.0.123#259f597c)
[INFO] [stderr]     Checking yuv-storage v0.3.5 (https://github.com/akitamiabtc/yuv.git?tag=v0.3.6#7a29c898)
[INFO] [stderr]     Checking yuv-rpc-api v0.3.5 (https://github.com/akitamiabtc/yuv.git?tag=v0.3.6#7a29c898)
[INFO] [stderr]     Checking ydk v0.3.5 (https://github.com/akitamiabtc/yuv.git?tag=v0.3.6#7a29c898)
[INFO] [stderr]     Checking 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]     Checking lightning-invoice v0.3.1 (https://github.com/akitamiabtc/yuv-lightning.git?tag=v0.3.1%2Blightning-0.0.123#259f597c)
[INFO] [stderr]     Checking lightning-block-sync v0.3.1 (https://github.com/akitamiabtc/yuv-lightning.git?tag=v0.3.1%2Blightning-0.0.123#259f597c)
[INFO] [stderr]     Checking lightning-net-tokio v0.3.1 (https://github.com/akitamiabtc/yuv-lightning.git?tag=v0.3.1%2Blightning-0.0.123#259f597c)
[INFO] [stderr]     Checking lightning-persister v0.3.1 (https://github.com/akitamiabtc/yuv-lightning.git?tag=v0.3.1%2Blightning-0.0.123#259f597c)
[INFO] [stderr]     Checking lightning-background-processor v0.3.1 (https://github.com/akitamiabtc/yuv-lightning.git?tag=v0.3.1%2Blightning-0.0.123#259f597c)
[INFO] [stderr]  Documenting 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] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 1m 21s
[INFO] [stderr]    Generated /opt/rustwide/target/doc/yuv_ln_node/index.html
[INFO] running `Command { std: "docker" "inspect" "19fa3699b7035aba924e4ea1eeb148e269d938b9a9ffbfa952cb1a9da33f8ecb", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "19fa3699b7035aba924e4ea1eeb148e269d938b9a9ffbfa952cb1a9da33f8ecb", kill_on_drop: false }`
[INFO] [stdout] 19fa3699b7035aba924e4ea1eeb148e269d938b9a9ffbfa952cb1a9da33f8ecb