[INFO] cloning repository https://github.com/jrasky/bis
[INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/jrasky/bis" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fjrasky%2Fbis", kill_on_drop: false }`
[INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fjrasky%2Fbis'...
[INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }`
[INFO] [stdout] bdba862e0b1c6ad0e80148e239c50350b220397f
[INFO] testing jrasky/bis against 1.90.0 for beta-1.91-3
[INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fjrasky%2Fbis" "/workspace/builds/worker-0-tc1/source", kill_on_drop: false }`
[INFO] [stderr] Cloning into '/workspace/builds/worker-0-tc1/source'...
[INFO] [stderr] done.
[INFO] started tweaking git repo https://github.com/jrasky/bis
[INFO] finished tweaking git repo https://github.com/jrasky/bis
[INFO] tweaked toml for git repo https://github.com/jrasky/bis written to /workspace/builds/worker-0-tc1/source/Cargo.toml
[INFO] validating manifest of git repo https://github.com/jrasky/bis on toolchain 1.90.0
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+1.90.0" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] crate git repo https://github.com/jrasky/bis 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" "+1.90.0" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr] warning: no edition set: defaulting to the 2015 edition while the latest is 2024
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded libc v0.1.8
[INFO] [stderr]   Downloaded advapi32-sys v0.1.2
[INFO] [stderr]   Downloaded gcc v0.3.11
[INFO] [stderr]   Downloaded term v0.2.11
[INFO] [stderr]   Downloaded kernel32-sys v0.1.3
[INFO] [stderr]   Downloaded env_logger v0.3.1
[INFO] [stderr]   Downloaded memchr v0.1.3
[INFO] [stderr]   Downloaded winapi-build v0.1.0
[INFO] [stderr]   Downloaded regex v0.1.41
[INFO] [stderr]   Downloaded winapi v0.2.1
[INFO] [stderr]   Downloaded unicode-width v0.1.2
[INFO] [stderr]   Downloaded aho-corasick v0.3.0
[INFO] [stderr]   Downloaded regex-syntax v0.2.1
[INFO] [stderr]   Downloaded log v0.3.1
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+1.90.0" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] f4e1ca59e78d5fa2682bd6cde271016f262b71d25335e2531ed10209aff833c9
[INFO] running `Command { std: "docker" "start" "-a" "f4e1ca59e78d5fa2682bd6cde271016f262b71d25335e2531ed10209aff833c9", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "f4e1ca59e78d5fa2682bd6cde271016f262b71d25335e2531ed10209aff833c9", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "f4e1ca59e78d5fa2682bd6cde271016f262b71d25335e2531ed10209aff833c9", kill_on_drop: false }`
[INFO] [stdout] f4e1ca59e78d5fa2682bd6cde271016f262b71d25335e2531ed10209aff833c9
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+1.90.0" "build" "--frozen" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 924b7380d0bd0bfc0d64f3a9e9d1c5cc18998acfe29132aad55cd706a26e7368
[INFO] running `Command { std: "docker" "start" "-a" "924b7380d0bd0bfc0d64f3a9e9d1c5cc18998acfe29132aad55cd706a26e7368", kill_on_drop: false }`
[INFO] [stderr] warning: no edition set: defaulting to the 2015 edition while the latest is 2024
[INFO] [stderr]    Compiling libc v0.1.8
[INFO] [stderr]    Compiling winapi-build v0.1.0
[INFO] [stderr]    Compiling winapi v0.2.1
[INFO] [stderr]    Compiling gcc v0.3.11
[INFO] [stderr]    Compiling regex-syntax v0.2.1
[INFO] [stderr]    Compiling unicode-width v0.1.2
[INFO] [stderr]    Compiling kernel32-sys v0.1.3
[INFO] [stderr]    Compiling memchr v0.1.3
[INFO] [stderr]    Compiling log v0.3.1
[INFO] [stderr]    Compiling aho-corasick v0.3.0
[INFO] [stderr]    Compiling term v0.2.11
[INFO] [stderr]    Compiling bis v0.1.0 (/opt/rustwide/workdir)
[INFO] [stderr]    Compiling regex v0.1.41
[INFO] [stderr]    Compiling env_logger v0.3.1
[INFO] [stdout] error[E0432]: unresolved import `std::borrow::IntoCow`
[INFO] [stdout]   --> src/search.rs:18:24
[INFO] [stdout]    |
[INFO] [stdout] 18 | use std::borrow::{Cow, IntoCow};
[INFO] [stdout]    |                        ^^^^^^^ no `IntoCow` in `borrow`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: cannot find macro `select` in this scope
[INFO] [stdout]    --> src/ui.rs:354:13
[INFO] [stdout]     |
[INFO] [stdout] 354 |             select! {
[INFO] [stdout]     |             ^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0554]: `#![feature]` may not be used on the stable release channel
[INFO] [stdout]   --> src/main.rs:14:1
[INFO] [stdout]    |
[INFO] [stdout] 14 | #![feature(cstr_to_str)]
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0554]: `#![feature]` may not be used on the stable release channel
[INFO] [stdout]   --> src/main.rs:15:1
[INFO] [stdout]    |
[INFO] [stdout] 15 | #![feature(convert)]
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0554]: `#![feature]` may not be used on the stable release channel
[INFO] [stdout]   --> src/main.rs:16:1
[INFO] [stdout]    |
[INFO] [stdout] 16 | #![feature(collections)]
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0554]: `#![feature]` may not be used on the stable release channel
[INFO] [stdout]   --> src/main.rs:17:1
[INFO] [stdout]    |
[INFO] [stdout] 17 | #![feature(into_cow)]
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0554]: `#![feature]` may not be used on the stable release channel
[INFO] [stdout]   --> src/main.rs:18:1
[INFO] [stdout]    |
[INFO] [stdout] 18 | #![feature(iter_arith)]
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0554]: `#![feature]` may not be used on the stable release channel
[INFO] [stdout]   --> src/main.rs:19:1
[INFO] [stdout]    |
[INFO] [stdout] 19 | #![feature(io)]
[INFO] [stdout]    | ^^^^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0554]: `#![feature]` may not be used on the stable release channel
[INFO] [stdout]   --> src/main.rs:20:1
[INFO] [stdout]    |
[INFO] [stdout] 20 | #![feature(mpsc_select)]
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/search.rs:267:17
[INFO] [stdout]     |
[INFO] [stdout] 267 |                 trace!("Skipping whitespace character");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: expected names are: `docsrs`, `feature`, and `test` and 31 more
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = 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 `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/search.rs:267:17
[INFO] [stdout]     |
[INFO] [stdout] 267 |                 trace!("Skipping whitespace character");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/search.rs:267:17
[INFO] [stdout]     |
[INFO] [stdout] 267 |                 trace!("Skipping whitespace character");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/search.rs:267:17
[INFO] [stdout]     |
[INFO] [stdout] 267 |                 trace!("Skipping whitespace character");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/search.rs:267:17
[INFO] [stdout]     |
[INFO] [stdout] 267 |                 trace!("Skipping whitespace character");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/search.rs:272:13
[INFO] [stdout]     |
[INFO] [stdout] 272 |             trace!("Matching character: {:?}", c);
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/search.rs:272:13
[INFO] [stdout]     |
[INFO] [stdout] 272 |             trace!("Matching character: {:?}", c);
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/search.rs:272:13
[INFO] [stdout]     |
[INFO] [stdout] 272 |             trace!("Matching character: {:?}", c);
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/search.rs:272:13
[INFO] [stdout]     |
[INFO] [stdout] 272 |             trace!("Matching character: {:?}", c);
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/search.rs:272:13
[INFO] [stdout]     |
[INFO] [stdout] 272 |             trace!("Matching character: {:?}", c);
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/bis_c.rs:84:17
[INFO] [stdout]    |
[INFO] [stdout] 84 |                 trace!("Successfully restored terminal");
[INFO] [stdout]    |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/bis_c.rs:84:17
[INFO] [stdout]    |
[INFO] [stdout] 84 |                 trace!("Successfully restored terminal");
[INFO] [stdout]    |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/bis_c.rs:84:17
[INFO] [stdout]    |
[INFO] [stdout] 84 |                 trace!("Successfully restored terminal");
[INFO] [stdout]    |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/bis_c.rs:84:17
[INFO] [stdout]    |
[INFO] [stdout] 84 |                 trace!("Successfully restored terminal");
[INFO] [stdout]    |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/bis_c.rs:84:17
[INFO] [stdout]    |
[INFO] [stdout] 84 |                 trace!("Successfully restored terminal");
[INFO] [stdout]    |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/bis_c.rs:87:17
[INFO] [stdout]    |
[INFO] [stdout] 87 |                 error!("Error restoring terminal: {}", e);
[INFO] [stdout]    |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/bis_c.rs:87:17
[INFO] [stdout]    |
[INFO] [stdout] 87 |                 error!("Error restoring terminal: {}", e);
[INFO] [stdout]    |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/bis_c.rs:87:17
[INFO] [stdout]    |
[INFO] [stdout] 87 |                 error!("Error restoring terminal: {}", e);
[INFO] [stdout]    |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/bis_c.rs:87:17
[INFO] [stdout]    |
[INFO] [stdout] 87 |                 error!("Error restoring terminal: {}", e);
[INFO] [stdout]    |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/bis_c.rs:87:17
[INFO] [stdout]    |
[INFO] [stdout] 87 |                 error!("Error restoring terminal: {}", e);
[INFO] [stdout]    |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/bis_c.rs:95:9
[INFO] [stdout]    |
[INFO] [stdout] 95 |         debug!("Preparing terminal");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/bis_c.rs:95:9
[INFO] [stdout]    |
[INFO] [stdout] 95 |         debug!("Preparing terminal");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/bis_c.rs:95:9
[INFO] [stdout]    |
[INFO] [stdout] 95 |         debug!("Preparing terminal");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/bis_c.rs:95:9
[INFO] [stdout]    |
[INFO] [stdout] 95 |         debug!("Preparing terminal");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/bis_c.rs:95:9
[INFO] [stdout]    |
[INFO] [stdout] 95 |         debug!("Preparing terminal");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/bis_c.rs:103:9
[INFO] [stdout]     |
[INFO] [stdout] 103 |         debug!("Restoring terminal");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/bis_c.rs:103:9
[INFO] [stdout]     |
[INFO] [stdout] 103 |         debug!("Restoring terminal");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/bis_c.rs:103:9
[INFO] [stdout]     |
[INFO] [stdout] 103 |         debug!("Restoring terminal");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/bis_c.rs:103:9
[INFO] [stdout]     |
[INFO] [stdout] 103 |         debug!("Restoring terminal");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/bis_c.rs:103:9
[INFO] [stdout]     |
[INFO] [stdout] 103 |         debug!("Restoring terminal");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/bis_c.rs:111:9
[INFO] [stdout]     |
[INFO] [stdout] 111 |         debug!("Getting terminal size");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/bis_c.rs:111:9
[INFO] [stdout]     |
[INFO] [stdout] 111 |         debug!("Getting terminal size");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/bis_c.rs:111:9
[INFO] [stdout]     |
[INFO] [stdout] 111 |         debug!("Getting terminal size");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/bis_c.rs:111:9
[INFO] [stdout]     |
[INFO] [stdout] 111 |         debug!("Getting terminal size");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/bis_c.rs:111:9
[INFO] [stdout]     |
[INFO] [stdout] 111 |         debug!("Getting terminal size");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/bis_c.rs:128:5
[INFO] [stdout]     |
[INFO] [stdout] 128 |     debug!("Masking sigint");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/bis_c.rs:128:5
[INFO] [stdout]     |
[INFO] [stdout] 128 |     debug!("Masking sigint");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/bis_c.rs:128:5
[INFO] [stdout]     |
[INFO] [stdout] 128 |     debug!("Masking sigint");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/bis_c.rs:128:5
[INFO] [stdout]     |
[INFO] [stdout] 128 |     debug!("Masking sigint");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/bis_c.rs:128:5
[INFO] [stdout]     |
[INFO] [stdout] 128 |     debug!("Masking sigint");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/bis_c.rs:136:5
[INFO] [stdout]     |
[INFO] [stdout] 136 |     debug!("Waiting for sigint");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/bis_c.rs:136:5
[INFO] [stdout]     |
[INFO] [stdout] 136 |     debug!("Waiting for sigint");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/bis_c.rs:136:5
[INFO] [stdout]     |
[INFO] [stdout] 136 |     debug!("Waiting for sigint");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/bis_c.rs:136:5
[INFO] [stdout]     |
[INFO] [stdout] 136 |     debug!("Waiting for sigint");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/bis_c.rs:136:5
[INFO] [stdout]     |
[INFO] [stdout] 136 |     debug!("Waiting for sigint");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused import: `unicode_width::*`
[INFO] [stdout]   --> src/ui.rs:17:5
[INFO] [stdout]    |
[INFO] [stdout] 17 | use unicode_width::*;
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: `#[warn(unused_imports)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/ui.rs:67:9
[INFO] [stdout]    |
[INFO] [stdout] 67 |         debug!("Getting terminal info");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/ui.rs:67:9
[INFO] [stdout]    |
[INFO] [stdout] 67 |         debug!("Getting terminal info");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/ui.rs:67:9
[INFO] [stdout]    |
[INFO] [stdout] 67 |         debug!("Getting terminal info");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/ui.rs:67:9
[INFO] [stdout]    |
[INFO] [stdout] 67 |         debug!("Getting terminal info");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/ui.rs:67:9
[INFO] [stdout]    |
[INFO] [stdout] 67 |         debug!("Getting terminal info");
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/ui.rs:73:9
[INFO] [stdout]    |
[INFO] [stdout] 73 |         trace!("Got terminfo: {:?}", info);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/ui.rs:73:9
[INFO] [stdout]    |
[INFO] [stdout] 73 |         trace!("Got terminfo: {:?}", info);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/ui.rs:73:9
[INFO] [stdout]    |
[INFO] [stdout] 73 |         trace!("Got terminfo: {:?}", info);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/ui.rs:73:9
[INFO] [stdout]    |
[INFO] [stdout] 73 |         trace!("Got terminfo: {:?}", info);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/ui.rs:73:9
[INFO] [stdout]    |
[INFO] [stdout] 73 |         trace!("Got terminfo: {:?}", info);
[INFO] [stdout]    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/ui.rs:94:17
[INFO] [stdout]    |
[INFO] [stdout] 94 |                 trace!("No match for string: {:?}", name.borrow());
[INFO] [stdout]    |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/ui.rs:94:17
[INFO] [stdout]    |
[INFO] [stdout] 94 |                 trace!("No match for string: {:?}", name.borrow());
[INFO] [stdout]    |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/ui.rs:94:17
[INFO] [stdout]    |
[INFO] [stdout] 94 |                 trace!("No match for string: {:?}", name.borrow());
[INFO] [stdout]    |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/ui.rs:94:17
[INFO] [stdout]    |
[INFO] [stdout] 94 |                 trace!("No match for string: {:?}", name.borrow());
[INFO] [stdout]    |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/ui.rs:94:17
[INFO] [stdout]    |
[INFO] [stdout] 94 |                 trace!("No match for string: {:?}", name.borrow());
[INFO] [stdout]    |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/ui.rs:98:17
[INFO] [stdout]    |
[INFO] [stdout] 98 |                 trace!("Matched string: {:?}", s);
[INFO] [stdout]    |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/ui.rs:98:17
[INFO] [stdout]    |
[INFO] [stdout] 98 |                 trace!("Matched string: {:?}", s);
[INFO] [stdout]    |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/ui.rs:98:17
[INFO] [stdout]    |
[INFO] [stdout] 98 |                 trace!("Matched string: {:?}", s);
[INFO] [stdout]    |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/ui.rs:98:17
[INFO] [stdout]    |
[INFO] [stdout] 98 |                 trace!("Matched string: {:?}", s);
[INFO] [stdout]    |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/ui.rs:98:17
[INFO] [stdout]    |
[INFO] [stdout] 98 |                 trace!("Matched string: {:?}", s);
[INFO] [stdout]    |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:124:29
[INFO] [stdout]     |
[INFO] [stdout] 124 | ...                   error!("Numeric print on non-numeric type: {:?}", o);
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:124:29
[INFO] [stdout]     |
[INFO] [stdout] 124 | ...                   error!("Numeric print on non-numeric type: {:?}", o);
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:124:29
[INFO] [stdout]     |
[INFO] [stdout] 124 | ...                   error!("Numeric print on non-numeric type: {:?}", o);
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:124:29
[INFO] [stdout]     |
[INFO] [stdout] 124 | ...                   error!("Numeric print on non-numeric type: {:?}", o);
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:124:29
[INFO] [stdout]     |
[INFO] [stdout] 124 | ...                   error!("Numeric print on non-numeric type: {:?}", o);
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:127:29
[INFO] [stdout]     |
[INFO] [stdout] 127 | ...                   error!("Stack was empty on print");
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:127:29
[INFO] [stdout]     |
[INFO] [stdout] 127 | ...                   error!("Stack was empty on print");
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:127:29
[INFO] [stdout]     |
[INFO] [stdout] 127 | ...                   error!("Stack was empty on print");
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:127:29
[INFO] [stdout]     |
[INFO] [stdout] 127 | ...                   error!("Stack was empty on print");
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:127:29
[INFO] [stdout]     |
[INFO] [stdout] 127 | ...                   error!("Stack was empty on print");
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:135:21
[INFO] [stdout]     |
[INFO] [stdout] 135 |                     error!("Unknown escape character: {:?}", c);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:135:21
[INFO] [stdout]     |
[INFO] [stdout] 135 |                     error!("Unknown escape character: {:?}", c);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:135:21
[INFO] [stdout]     |
[INFO] [stdout] 135 |                     error!("Unknown escape character: {:?}", c);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:135:21
[INFO] [stdout]     |
[INFO] [stdout] 135 |                     error!("Unknown escape character: {:?}", c);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:135:21
[INFO] [stdout]     |
[INFO] [stdout] 135 |                     error!("Unknown escape character: {:?}", c);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:148:41
[INFO] [stdout]     |
[INFO] [stdout] 148 | ...                   error!("There was no parameter {}", idx);
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:148:41
[INFO] [stdout]     |
[INFO] [stdout] 148 | ...                   error!("There was no parameter {}", idx);
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:148:41
[INFO] [stdout]     |
[INFO] [stdout] 148 | ...                   error!("There was no parameter {}", idx);
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:148:41
[INFO] [stdout]     |
[INFO] [stdout] 148 | ...                   error!("There was no parameter {}", idx);
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:148:41
[INFO] [stdout]     |
[INFO] [stdout] 148 | ...                   error!("There was no parameter {}", idx);
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:152:33
[INFO] [stdout]     |
[INFO] [stdout] 152 | ...                   error!("Tried to print 0th paramater");
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:152:33
[INFO] [stdout]     |
[INFO] [stdout] 152 | ...                   error!("Tried to print 0th paramater");
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:152:33
[INFO] [stdout]     |
[INFO] [stdout] 152 | ...                   error!("Tried to print 0th paramater");
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:152:33
[INFO] [stdout]     |
[INFO] [stdout] 152 | ...                   error!("Tried to print 0th paramater");
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:152:33
[INFO] [stdout]     |
[INFO] [stdout] 152 | ...                   error!("Tried to print 0th paramater");
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:156:29
[INFO] [stdout]     |
[INFO] [stdout] 156 | ...                   error!("Paramater number was not a digit");
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:156:29
[INFO] [stdout]     |
[INFO] [stdout] 156 | ...                   error!("Paramater number was not a digit");
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:156:29
[INFO] [stdout]     |
[INFO] [stdout] 156 | ...                   error!("Paramater number was not a digit");
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:156:29
[INFO] [stdout]     |
[INFO] [stdout] 156 | ...                   error!("Paramater number was not a digit");
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:156:29
[INFO] [stdout]     |
[INFO] [stdout] 156 | ...                   error!("Paramater number was not a digit");
[INFO] [stdout]     |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:163:21
[INFO] [stdout]     |
[INFO] [stdout] 163 |                     error!("Unknown escape sequence: {:?}", escape);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:163:21
[INFO] [stdout]     |
[INFO] [stdout] 163 |                     error!("Unknown escape sequence: {:?}", escape);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:163:21
[INFO] [stdout]     |
[INFO] [stdout] 163 |                     error!("Unknown escape sequence: {:?}", escape);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:163:21
[INFO] [stdout]     |
[INFO] [stdout] 163 |                     error!("Unknown escape sequence: {:?}", escape);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:163:21
[INFO] [stdout]     |
[INFO] [stdout] 163 |                     error!("Unknown escape sequence: {:?}", escape);
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:170:9
[INFO] [stdout]     |
[INFO] [stdout] 170 |         trace!("Returning result: {:?}", result);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:170:9
[INFO] [stdout]     |
[INFO] [stdout] 170 |         trace!("Returning result: {:?}", result);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:170:9
[INFO] [stdout]     |
[INFO] [stdout] 170 |         trace!("Returning result: {:?}", result);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:170:9
[INFO] [stdout]     |
[INFO] [stdout] 170 |         trace!("Returning result: {:?}", result);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:170:9
[INFO] [stdout]     |
[INFO] [stdout] 170 |         trace!("Returning result: {:?}", result);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:179:9
[INFO] [stdout]     |
[INFO] [stdout] 179 |         debug!("Creating TermControl");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:179:9
[INFO] [stdout]     |
[INFO] [stdout] 179 |         debug!("Creating TermControl");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:179:9
[INFO] [stdout]     |
[INFO] [stdout] 179 |         debug!("Creating TermControl");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:179:9
[INFO] [stdout]     |
[INFO] [stdout] 179 |         debug!("Creating TermControl");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:179:9
[INFO] [stdout]     |
[INFO] [stdout] 179 |         debug!("Creating TermControl");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead
[INFO] [stdout]    --> src/ui.rs:180:23
[INFO] [stdout]     |
[INFO] [stdout] 180 |         let control = try!(TermControl::create());
[INFO] [stdout]     |                       ^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(deprecated)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:182:9
[INFO] [stdout]     |
[INFO] [stdout] 182 |         trace!("Got TermControl: {:?}", control);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:182:9
[INFO] [stdout]     |
[INFO] [stdout] 182 |         trace!("Got TermControl: {:?}", control);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:182:9
[INFO] [stdout]     |
[INFO] [stdout] 182 |         trace!("Got TermControl: {:?}", control);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:182:9
[INFO] [stdout]     |
[INFO] [stdout] 182 |         trace!("Got TermControl: {:?}", control);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:182:9
[INFO] [stdout]     |
[INFO] [stdout] 182 |         trace!("Got TermControl: {:?}", control);
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:186:9
[INFO] [stdout]     |
[INFO] [stdout] 186 |         debug!("Getting terminal size");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:186:9
[INFO] [stdout]     |
[INFO] [stdout] 186 |         debug!("Getting terminal size");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:186:9
[INFO] [stdout]     |
[INFO] [stdout] 186 |         debug!("Getting terminal size");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:186:9
[INFO] [stdout]     |
[INFO] [stdout] 186 |         debug!("Getting terminal size");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:186:9
[INFO] [stdout]     |
[INFO] [stdout] 186 |         debug!("Getting terminal size");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:190:17
[INFO] [stdout]     |
[INFO] [stdout] 190 |                 trace!("Terminal size: {:?}", s);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:190:17
[INFO] [stdout]     |
[INFO] [stdout] 190 |                 trace!("Terminal size: {:?}", s);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:190:17
[INFO] [stdout]     |
[INFO] [stdout] 190 |                 trace!("Terminal size: {:?}", s);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:190:17
[INFO] [stdout]     |
[INFO] [stdout] 190 |                 trace!("Terminal size: {:?}", s);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:190:17
[INFO] [stdout]     |
[INFO] [stdout] 190 |                 trace!("Terminal size: {:?}", s);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:195:9
[INFO] [stdout]     |
[INFO] [stdout] 195 |         debug!("Preparing terminal");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:195:9
[INFO] [stdout]     |
[INFO] [stdout] 195 |         debug!("Preparing terminal");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:195:9
[INFO] [stdout]     |
[INFO] [stdout] 195 |         debug!("Preparing terminal");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:195:9
[INFO] [stdout]     |
[INFO] [stdout] 195 |         debug!("Preparing terminal");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:195:9
[INFO] [stdout]     |
[INFO] [stdout] 195 |         debug!("Preparing terminal");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:199:17
[INFO] [stdout]     |
[INFO] [stdout] 199 |                 trace!("Terminal prepared successfully");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:199:17
[INFO] [stdout]     |
[INFO] [stdout] 199 |                 trace!("Terminal prepared successfully");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:199:17
[INFO] [stdout]     |
[INFO] [stdout] 199 |                 trace!("Terminal prepared successfully");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:199:17
[INFO] [stdout]     |
[INFO] [stdout] 199 |                 trace!("Terminal prepared successfully");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:199:17
[INFO] [stdout]     |
[INFO] [stdout] 199 |                 trace!("Terminal prepared successfully");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:203:9
[INFO] [stdout]     |
[INFO] [stdout] 203 |         debug!("Masking sigint on main thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:203:9
[INFO] [stdout]     |
[INFO] [stdout] 203 |         debug!("Masking sigint on main thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:203:9
[INFO] [stdout]     |
[INFO] [stdout] 203 |         debug!("Masking sigint on main thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:203:9
[INFO] [stdout]     |
[INFO] [stdout] 203 |         debug!("Masking sigint on main thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:203:9
[INFO] [stdout]     |
[INFO] [stdout] 203 |         debug!("Masking sigint on main thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:207:17
[INFO] [stdout]     |
[INFO] [stdout] 207 |                 trace!("Set signal mask successfully");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:207:17
[INFO] [stdout]     |
[INFO] [stdout] 207 |                 trace!("Set signal mask successfully");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:207:17
[INFO] [stdout]     |
[INFO] [stdout] 207 |                 trace!("Set signal mask successfully");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:207:17
[INFO] [stdout]     |
[INFO] [stdout] 207 |                 trace!("Set signal mask successfully");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:207:17
[INFO] [stdout]     |
[INFO] [stdout] 207 |                 trace!("Set signal mask successfully");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:212:9
[INFO] [stdout]     |
[INFO] [stdout] 212 |         debug!("Starting search thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:212:9
[INFO] [stdout]     |
[INFO] [stdout] 212 |         debug!("Starting search thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:212:9
[INFO] [stdout]     |
[INFO] [stdout] 212 |         debug!("Starting search thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:212:9
[INFO] [stdout]     |
[INFO] [stdout] 212 |         debug!("Starting search thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:212:9
[INFO] [stdout]     |
[INFO] [stdout] 212 |         debug!("Starting search thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:214:9
[INFO] [stdout]     |
[INFO] [stdout] 214 |         trace!("Creating thread primitives");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:214:9
[INFO] [stdout]     |
[INFO] [stdout] 214 |         trace!("Creating thread primitives");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:214:9
[INFO] [stdout]     |
[INFO] [stdout] 214 |         trace!("Creating thread primitives");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:214:9
[INFO] [stdout]     |
[INFO] [stdout] 214 |         trace!("Creating thread primitives");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:214:9
[INFO] [stdout]     |
[INFO] [stdout] 214 |         trace!("Creating thread primitives");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:218:9
[INFO] [stdout]     |
[INFO] [stdout] 218 |         trace!("Starting thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:218:9
[INFO] [stdout]     |
[INFO] [stdout] 218 |         trace!("Starting thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:218:9
[INFO] [stdout]     |
[INFO] [stdout] 218 |         trace!("Starting thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:218:9
[INFO] [stdout]     |
[INFO] [stdout] 218 |         trace!("Starting thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:218:9
[INFO] [stdout]     |
[INFO] [stdout] 218 |         trace!("Starting thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:223:9
[INFO] [stdout]     |
[INFO] [stdout] 223 |         debug!("Starting input thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:223:9
[INFO] [stdout]     |
[INFO] [stdout] 223 |         debug!("Starting input thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:223:9
[INFO] [stdout]     |
[INFO] [stdout] 223 |         debug!("Starting input thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:223:9
[INFO] [stdout]     |
[INFO] [stdout] 223 |         debug!("Starting input thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:223:9
[INFO] [stdout]     |
[INFO] [stdout] 223 |         debug!("Starting input thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:225:9
[INFO] [stdout]     |
[INFO] [stdout] 225 |         trace!("Creating thread primitives");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:225:9
[INFO] [stdout]     |
[INFO] [stdout] 225 |         trace!("Creating thread primitives");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:225:9
[INFO] [stdout]     |
[INFO] [stdout] 225 |         trace!("Creating thread primitives");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:225:9
[INFO] [stdout]     |
[INFO] [stdout] 225 |         trace!("Creating thread primitives");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:225:9
[INFO] [stdout]     |
[INFO] [stdout] 225 |         trace!("Creating thread primitives");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:229:9
[INFO] [stdout]     |
[INFO] [stdout] 229 |         trace!("Starting thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:229:9
[INFO] [stdout]     |
[INFO] [stdout] 229 |         trace!("Starting thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:229:9
[INFO] [stdout]     |
[INFO] [stdout] 229 |         trace!("Starting thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:229:9
[INFO] [stdout]     |
[INFO] [stdout] 229 |         trace!("Starting thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:229:9
[INFO] [stdout]     |
[INFO] [stdout] 229 |         trace!("Starting thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:234:9
[INFO] [stdout]     |
[INFO] [stdout] 234 |         debug!("Starting signal thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:234:9
[INFO] [stdout]     |
[INFO] [stdout] 234 |         debug!("Starting signal thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:234:9
[INFO] [stdout]     |
[INFO] [stdout] 234 |         debug!("Starting signal thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:234:9
[INFO] [stdout]     |
[INFO] [stdout] 234 |         debug!("Starting signal thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:234:9
[INFO] [stdout]     |
[INFO] [stdout] 234 |         debug!("Starting signal thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:236:9
[INFO] [stdout]     |
[INFO] [stdout] 236 |         trace!("Creating thread primitives");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:236:9
[INFO] [stdout]     |
[INFO] [stdout] 236 |         trace!("Creating thread primitives");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:236:9
[INFO] [stdout]     |
[INFO] [stdout] 236 |         trace!("Creating thread primitives");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:236:9
[INFO] [stdout]     |
[INFO] [stdout] 236 |         trace!("Creating thread primitives");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:236:9
[INFO] [stdout]     |
[INFO] [stdout] 236 |         trace!("Creating thread primitives");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:239:9
[INFO] [stdout]     |
[INFO] [stdout] 239 |         trace!("Starting thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:239:9
[INFO] [stdout]     |
[INFO] [stdout] 239 |         trace!("Starting thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:239:9
[INFO] [stdout]     |
[INFO] [stdout] 239 |         trace!("Starting thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:239:9
[INFO] [stdout]     |
[INFO] [stdout] 239 |         trace!("Starting thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:239:9
[INFO] [stdout]     |
[INFO] [stdout] 239 |         trace!("Starting thread");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:244:9
[INFO] [stdout]     |
[INFO] [stdout] 244 |         debug!("Creating UI instance");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:244:9
[INFO] [stdout]     |
[INFO] [stdout] 244 |         debug!("Creating UI instance");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:244:9
[INFO] [stdout]     |
[INFO] [stdout] 244 |         debug!("Creating UI instance");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:244:9
[INFO] [stdout]     |
[INFO] [stdout] 244 |         debug!("Creating UI instance");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:244:9
[INFO] [stdout]     |
[INFO] [stdout] 244 |         debug!("Creating UI instance");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:256:9
[INFO] [stdout]     |
[INFO] [stdout] 256 |         trace!("Instance creation successful");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:256:9
[INFO] [stdout]     |
[INFO] [stdout] 256 |         trace!("Instance creation successful");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:256:9
[INFO] [stdout]     |
[INFO] [stdout] 256 |         trace!("Instance creation successful");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:256:9
[INFO] [stdout]     |
[INFO] [stdout] 256 |         trace!("Instance creation successful");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:256:9
[INFO] [stdout]     |
[INFO] [stdout] 256 |         trace!("Instance creation successful");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:264:17
[INFO] [stdout]     |
[INFO] [stdout] 264 |                 trace!("Successfully sent stop to input thread");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:264:17
[INFO] [stdout]     |
[INFO] [stdout] 264 |                 trace!("Successfully sent stop to input thread");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:264:17
[INFO] [stdout]     |
[INFO] [stdout] 264 |                 trace!("Successfully sent stop to input thread");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:264:17
[INFO] [stdout]     |
[INFO] [stdout] 264 |                 trace!("Successfully sent stop to input thread");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:264:17
[INFO] [stdout]     |
[INFO] [stdout] 264 |                 trace!("Successfully sent stop to input thread");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:274:17
[INFO] [stdout]     |
[INFO] [stdout] 274 |                 trace!("Successfully simulated input");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:274:17
[INFO] [stdout]     |
[INFO] [stdout] 274 |                 trace!("Successfully simulated input");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:274:17
[INFO] [stdout]     |
[INFO] [stdout] 274 |                 trace!("Successfully simulated input");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:274:17
[INFO] [stdout]     |
[INFO] [stdout] 274 |                 trace!("Successfully simulated input");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:274:17
[INFO] [stdout]     |
[INFO] [stdout] 274 |                 trace!("Successfully simulated input");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:285:21
[INFO] [stdout]     |
[INFO] [stdout] 285 |                     trace!("Draining input thread");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:285:21
[INFO] [stdout]     |
[INFO] [stdout] 285 |                     trace!("Draining input thread");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:285:21
[INFO] [stdout]     |
[INFO] [stdout] 285 |                     trace!("Draining input thread");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:285:21
[INFO] [stdout]     |
[INFO] [stdout] 285 |                     trace!("Draining input thread");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:285:21
[INFO] [stdout]     |
[INFO] [stdout] 285 |                     trace!("Draining input thread");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:288:21
[INFO] [stdout]     |
[INFO] [stdout] 288 |                     trace!("Thread has exited");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:288:21
[INFO] [stdout]     |
[INFO] [stdout] 288 |                     trace!("Thread has exited");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:288:21
[INFO] [stdout]     |
[INFO] [stdout] 288 |                     trace!("Thread has exited");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:288:21
[INFO] [stdout]     |
[INFO] [stdout] 288 |                     trace!("Thread has exited");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:288:21
[INFO] [stdout]     |
[INFO] [stdout] 288 |                     trace!("Thread has exited");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:296:17
[INFO] [stdout]     |
[INFO] [stdout] 296 |                 trace!("Successfully inserted best match");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:296:17
[INFO] [stdout]     |
[INFO] [stdout] 296 |                 trace!("Successfully inserted best match");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:296:17
[INFO] [stdout]     |
[INFO] [stdout] 296 |                 trace!("Successfully inserted best match");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:296:17
[INFO] [stdout]     |
[INFO] [stdout] 296 |                 trace!("Successfully inserted best match");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:296:17
[INFO] [stdout]     |
[INFO] [stdout] 296 |                 trace!("Successfully inserted best match");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:318:17
[INFO] [stdout]     |
[INFO] [stdout] 318 |                 trace!("Successfully created space on terminal");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:318:17
[INFO] [stdout]     |
[INFO] [stdout] 318 |                 trace!("Successfully created space on terminal");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:318:17
[INFO] [stdout]     |
[INFO] [stdout] 318 |                 trace!("Successfully created space on terminal");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:318:17
[INFO] [stdout]     |
[INFO] [stdout] 318 |                 trace!("Successfully created space on terminal");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:318:17
[INFO] [stdout]     |
[INFO] [stdout] 318 |                 trace!("Successfully created space on terminal");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:323:9
[INFO] [stdout]     |
[INFO] [stdout] 323 |         debug!("Drawing prompt");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:323:9
[INFO] [stdout]     |
[INFO] [stdout] 323 |         debug!("Drawing prompt");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:323:9
[INFO] [stdout]     |
[INFO] [stdout] 323 |         debug!("Drawing prompt");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:323:9
[INFO] [stdout]     |
[INFO] [stdout] 323 |         debug!("Drawing prompt");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:323:9
[INFO] [stdout]     |
[INFO] [stdout] 323 |         debug!("Drawing prompt");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:328:17
[INFO] [stdout]     |
[INFO] [stdout] 328 |                 trace!("Drew prompt successfully");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:328:17
[INFO] [stdout]     |
[INFO] [stdout] 328 |                 trace!("Drew prompt successfully");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:328:17
[INFO] [stdout]     |
[INFO] [stdout] 328 |                 trace!("Drew prompt successfully");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:328:17
[INFO] [stdout]     |
[INFO] [stdout] 328 |                 trace!("Drew prompt successfully");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:328:17
[INFO] [stdout]     |
[INFO] [stdout] 328 |                 trace!("Drew prompt successfully");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:333:9
[INFO] [stdout]     |
[INFO] [stdout] 333 |         debug!("Flushing output");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:333:9
[INFO] [stdout]     |
[INFO] [stdout] 333 |         debug!("Flushing output");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:333:9
[INFO] [stdout]     |
[INFO] [stdout] 333 |         debug!("Flushing output");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:333:9
[INFO] [stdout]     |
[INFO] [stdout] 333 |         debug!("Flushing output");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:333:9
[INFO] [stdout]     |
[INFO] [stdout] 333 |         debug!("Flushing output");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:336:17
[INFO] [stdout]     |
[INFO] [stdout] 336 |                 trace!("Successfully flushed output");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:336:17
[INFO] [stdout]     |
[INFO] [stdout] 336 |                 trace!("Successfully flushed output");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:336:17
[INFO] [stdout]     |
[INFO] [stdout] 336 |                 trace!("Successfully flushed output");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:336:17
[INFO] [stdout]     |
[INFO] [stdout] 336 |                 trace!("Successfully flushed output");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:336:17
[INFO] [stdout]     |
[INFO] [stdout] 336 |                 trace!("Successfully flushed output");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:513:21
[INFO] [stdout]     |
[INFO] [stdout] 513 |                     trace!("Successfully flushed output");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:513:21
[INFO] [stdout]     |
[INFO] [stdout] 513 |                     trace!("Successfully flushed output");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:513:21
[INFO] [stdout]     |
[INFO] [stdout] 513 |                     trace!("Successfully flushed output");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:513:21
[INFO] [stdout]     |
[INFO] [stdout] 513 |                     trace!("Successfully flushed output");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:513:21
[INFO] [stdout]     |
[INFO] [stdout] 513 |                     trace!("Successfully flushed output");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:528:25
[INFO] [stdout]     |
[INFO] [stdout] 528 |                         trace!("Drew best match successfully");
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:528:25
[INFO] [stdout]     |
[INFO] [stdout] 528 |                         trace!("Drew best match successfully");
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:528:25
[INFO] [stdout]     |
[INFO] [stdout] 528 |                         trace!("Drew best match successfully");
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:528:25
[INFO] [stdout]     |
[INFO] [stdout] 528 |                         trace!("Drew best match successfully");
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:528:25
[INFO] [stdout]     |
[INFO] [stdout] 528 |                         trace!("Drew best match successfully");
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:533:17
[INFO] [stdout]     |
[INFO] [stdout] 533 |                 trace!("Not redrawing best match");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:533:17
[INFO] [stdout]     |
[INFO] [stdout] 533 |                 trace!("Not redrawing best match");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:533:17
[INFO] [stdout]     |
[INFO] [stdout] 533 |                 trace!("Not redrawing best match");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:533:17
[INFO] [stdout]     |
[INFO] [stdout] 533 |                 trace!("Not redrawing best match");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:533:17
[INFO] [stdout]     |
[INFO] [stdout] 533 |                 trace!("Not redrawing best match");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:542:17
[INFO] [stdout]     |
[INFO] [stdout] 542 |                 trace!("Cleared screen successfully");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:542:17
[INFO] [stdout]     |
[INFO] [stdout] 542 |                 trace!("Cleared screen successfully");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:542:17
[INFO] [stdout]     |
[INFO] [stdout] 542 |                 trace!("Cleared screen successfully");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:542:17
[INFO] [stdout]     |
[INFO] [stdout] 542 |                 trace!("Cleared screen successfully");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:542:17
[INFO] [stdout]     |
[INFO] [stdout] 542 |                 trace!("Cleared screen successfully");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:549:17
[INFO] [stdout]     |
[INFO] [stdout] 549 |                 trace!("Successfully flushed output");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:549:17
[INFO] [stdout]     |
[INFO] [stdout] 549 |                 trace!("Successfully flushed output");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:549:17
[INFO] [stdout]     |
[INFO] [stdout] 549 |                 trace!("Successfully flushed output");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:549:17
[INFO] [stdout]     |
[INFO] [stdout] 549 |                 trace!("Successfully flushed output");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:549:17
[INFO] [stdout]     |
[INFO] [stdout] 549 |                 trace!("Successfully flushed output");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead
[INFO] [stdout]    --> src/ui.rs:559:21
[INFO] [stdout]     |
[INFO] [stdout] 559 |                     try!(self.insert_match(m.into_owned()));
[INFO] [stdout]     |                     ^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:562:21
[INFO] [stdout]     |
[INFO] [stdout] 562 |                     trace!("Not inserting best match");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:562:21
[INFO] [stdout]     |
[INFO] [stdout] 562 |                     trace!("Not inserting best match");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:562:21
[INFO] [stdout]     |
[INFO] [stdout] 562 |                     trace!("Not inserting best match");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:562:21
[INFO] [stdout]     |
[INFO] [stdout] 562 |                     trace!("Not inserting best match");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:562:21
[INFO] [stdout]     |
[INFO] [stdout] 562 |                     trace!("Not inserting best match");
[INFO] [stdout]     |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:576:5
[INFO] [stdout]     |
[INFO] [stdout] 576 |     debug!("Starting query thread");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:576:5
[INFO] [stdout]     |
[INFO] [stdout] 576 |     debug!("Starting query thread");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:576:5
[INFO] [stdout]     |
[INFO] [stdout] 576 |     debug!("Starting query thread");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:576:5
[INFO] [stdout]     |
[INFO] [stdout] 576 |     debug!("Starting query thread");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:576:5
[INFO] [stdout]     |
[INFO] [stdout] 576 |     debug!("Starting query thread");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:578:5
[INFO] [stdout]     |
[INFO] [stdout] 578 |     debug!("Getting history path");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:578:5
[INFO] [stdout]     |
[INFO] [stdout] 578 |     debug!("Getting history path");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:578:5
[INFO] [stdout]     |
[INFO] [stdout] 578 |     debug!("Getting history path");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:578:5
[INFO] [stdout]     |
[INFO] [stdout] 578 |     debug!("Getting history path");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:578:5
[INFO] [stdout]     |
[INFO] [stdout] 578 |     debug!("Getting history path");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:581:13
[INFO] [stdout]     |
[INFO] [stdout] 581 |             trace!("Got history path: {:?}", p);
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:581:13
[INFO] [stdout]     |
[INFO] [stdout] 581 |             trace!("Got history path: {:?}", p);
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:581:13
[INFO] [stdout]     |
[INFO] [stdout] 581 |             trace!("Got history path: {:?}", p);
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:581:13
[INFO] [stdout]     |
[INFO] [stdout] 581 |             trace!("Got history path: {:?}", p);
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:581:13
[INFO] [stdout]     |
[INFO] [stdout] 581 |             trace!("Got history path: {:?}", p);
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:590:5
[INFO] [stdout]     |
[INFO] [stdout] 590 |     info!("Reading history");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:590:5
[INFO] [stdout]     |
[INFO] [stdout] 590 |     info!("Reading history");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:590:5
[INFO] [stdout]     |
[INFO] [stdout] 590 |     info!("Reading history");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:590:5
[INFO] [stdout]     |
[INFO] [stdout] 590 |     info!("Reading history");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:590:5
[INFO] [stdout]     |
[INFO] [stdout] 590 |     info!("Reading history");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:600:5
[INFO] [stdout]     |
[INFO] [stdout] 600 |     debug!("Starting query loop");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:600:5
[INFO] [stdout]     |
[INFO] [stdout] 600 |     debug!("Starting query loop");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:600:5
[INFO] [stdout]     |
[INFO] [stdout] 600 |     debug!("Starting query loop");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:600:5
[INFO] [stdout]     |
[INFO] [stdout] 600 |     debug!("Starting query loop");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:600:5
[INFO] [stdout]     |
[INFO] [stdout] 600 |     debug!("Starting query loop");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:603:9
[INFO] [stdout]     |
[INFO] [stdout] 603 |         trace!("Waiting for a query");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:603:9
[INFO] [stdout]     |
[INFO] [stdout] 603 |         trace!("Waiting for a query");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:603:9
[INFO] [stdout]     |
[INFO] [stdout] 603 |         trace!("Waiting for a query");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:603:9
[INFO] [stdout]     |
[INFO] [stdout] 603 |         trace!("Waiting for a query");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:603:9
[INFO] [stdout]     |
[INFO] [stdout] 603 |         trace!("Waiting for a query");
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:606:17
[INFO] [stdout]     |
[INFO] [stdout] 606 |                 debug!("Search thread exiting: {}", e);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:606:17
[INFO] [stdout]     |
[INFO] [stdout] 606 |                 debug!("Search thread exiting: {}", e);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:606:17
[INFO] [stdout]     |
[INFO] [stdout] 606 |                 debug!("Search thread exiting: {}", e);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:606:17
[INFO] [stdout]     |
[INFO] [stdout] 606 |                 debug!("Search thread exiting: {}", e);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:606:17
[INFO] [stdout]     |
[INFO] [stdout] 606 |                 debug!("Search thread exiting: {}", e);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:610:17
[INFO] [stdout]     |
[INFO] [stdout] 610 |                 debug!("Got query: {:?}", q);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:610:17
[INFO] [stdout]     |
[INFO] [stdout] 610 |                 debug!("Got query: {:?}", q);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:610:17
[INFO] [stdout]     |
[INFO] [stdout] 610 |                 debug!("Got query: {:?}", q);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:610:17
[INFO] [stdout]     |
[INFO] [stdout] 610 |                 debug!("Got query: {:?}", q);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:610:17
[INFO] [stdout]     |
[INFO] [stdout] 610 |                 debug!("Got query: {:?}", q);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:612:17
[INFO] [stdout]     |
[INFO] [stdout] 612 |                 debug!("Got result: {:?}", result);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:612:17
[INFO] [stdout]     |
[INFO] [stdout] 612 |                 debug!("Got result: {:?}", result);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:612:17
[INFO] [stdout]     |
[INFO] [stdout] 612 |                 debug!("Got result: {:?}", result);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:612:17
[INFO] [stdout]     |
[INFO] [stdout] 612 |                 debug!("Got result: {:?}", result);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:612:17
[INFO] [stdout]     |
[INFO] [stdout] 612 |                 debug!("Got result: {:?}", result);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:615:25
[INFO] [stdout]     |
[INFO] [stdout] 615 |                         debug!("Search thread exiting: {}", e);
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:615:25
[INFO] [stdout]     |
[INFO] [stdout] 615 |                         debug!("Search thread exiting: {}", e);
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:615:25
[INFO] [stdout]     |
[INFO] [stdout] 615 |                         debug!("Search thread exiting: {}", e);
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:615:25
[INFO] [stdout]     |
[INFO] [stdout] 615 |                         debug!("Search thread exiting: {}", e);
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:615:25
[INFO] [stdout]     |
[INFO] [stdout] 615 |                         debug!("Search thread exiting: {}", e);
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:619:25
[INFO] [stdout]     |
[INFO] [stdout] 619 |                         trace!("Matches sent successfully");
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:619:25
[INFO] [stdout]     |
[INFO] [stdout] 619 |                         trace!("Matches sent successfully");
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:619:25
[INFO] [stdout]     |
[INFO] [stdout] 619 |                         trace!("Matches sent successfully");
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:619:25
[INFO] [stdout]     |
[INFO] [stdout] 619 |                         trace!("Matches sent successfully");
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:619:25
[INFO] [stdout]     |
[INFO] [stdout] 619 |                         trace!("Matches sent successfully");
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:629:5
[INFO] [stdout]     |
[INFO] [stdout] 629 |     debug!("Starting input thread");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:629:5
[INFO] [stdout]     |
[INFO] [stdout] 629 |     debug!("Starting input thread");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:629:5
[INFO] [stdout]     |
[INFO] [stdout] 629 |     debug!("Starting input thread");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:629:5
[INFO] [stdout]     |
[INFO] [stdout] 629 |     debug!("Starting input thread");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:629:5
[INFO] [stdout]     |
[INFO] [stdout] 629 |     debug!("Starting input thread");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:631:5
[INFO] [stdout]     |
[INFO] [stdout] 631 |     debug!("Getting stdin lock");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:631:5
[INFO] [stdout]     |
[INFO] [stdout] 631 |     debug!("Getting stdin lock");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:631:5
[INFO] [stdout]     |
[INFO] [stdout] 631 |     debug!("Getting stdin lock");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:631:5
[INFO] [stdout]     |
[INFO] [stdout] 631 |     debug!("Getting stdin lock");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:631:5
[INFO] [stdout]     |
[INFO] [stdout] 631 |     debug!("Getting stdin lock");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:639:17
[INFO] [stdout]     |
[INFO] [stdout] 639 |                 trace!("Not stopping thread");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:639:17
[INFO] [stdout]     |
[INFO] [stdout] 639 |                 trace!("Not stopping thread");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:639:17
[INFO] [stdout]     |
[INFO] [stdout] 639 |                 trace!("Not stopping thread");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:639:17
[INFO] [stdout]     |
[INFO] [stdout] 639 |                 trace!("Not stopping thread");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:639:17
[INFO] [stdout]     |
[INFO] [stdout] 639 |                 trace!("Not stopping thread");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:642:17
[INFO] [stdout]     |
[INFO] [stdout] 642 |                 debug!("Input thread exiting");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:642:17
[INFO] [stdout]     |
[INFO] [stdout] 642 |                 debug!("Input thread exiting");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:642:17
[INFO] [stdout]     |
[INFO] [stdout] 642 |                 debug!("Input thread exiting");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:642:17
[INFO] [stdout]     |
[INFO] [stdout] 642 |                 debug!("Input thread exiting");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:642:17
[INFO] [stdout]     |
[INFO] [stdout] 642 |                 debug!("Input thread exiting");
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:649:17
[INFO] [stdout]     |
[INFO] [stdout] 649 |                 debug!("Input thread exiting: {}", e);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:649:17
[INFO] [stdout]     |
[INFO] [stdout] 649 |                 debug!("Input thread exiting: {}", e);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:649:17
[INFO] [stdout]     |
[INFO] [stdout] 649 |                 debug!("Input thread exiting: {}", e);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:649:17
[INFO] [stdout]     |
[INFO] [stdout] 649 |                 debug!("Input thread exiting: {}", e);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:649:17
[INFO] [stdout]     |
[INFO] [stdout] 649 |                 debug!("Input thread exiting: {}", e);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:653:17
[INFO] [stdout]     |
[INFO] [stdout] 653 |                 debug!("Got character: {:?}", c);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:653:17
[INFO] [stdout]     |
[INFO] [stdout] 653 |                 debug!("Got character: {:?}", c);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:653:17
[INFO] [stdout]     |
[INFO] [stdout] 653 |                 debug!("Got character: {:?}", c);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:653:17
[INFO] [stdout]     |
[INFO] [stdout] 653 |                 debug!("Got character: {:?}", c);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:653:17
[INFO] [stdout]     |
[INFO] [stdout] 653 |                 debug!("Got character: {:?}", c);
[INFO] [stdout]     |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:656:25
[INFO] [stdout]     |
[INFO] [stdout] 656 |                         debug!("Search thread exiting: {:?}", e);
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:656:25
[INFO] [stdout]     |
[INFO] [stdout] 656 |                         debug!("Search thread exiting: {:?}", e);
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:656:25
[INFO] [stdout]     |
[INFO] [stdout] 656 |                         debug!("Search thread exiting: {:?}", e);
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:656:25
[INFO] [stdout]     |
[INFO] [stdout] 656 |                         debug!("Search thread exiting: {:?}", e);
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:656:25
[INFO] [stdout]     |
[INFO] [stdout] 656 |                         debug!("Search thread exiting: {:?}", e);
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:659:25
[INFO] [stdout]     |
[INFO] [stdout] 659 |                         trace!("Character sent successfully");
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:659:25
[INFO] [stdout]     |
[INFO] [stdout] 659 |                         trace!("Character sent successfully");
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:659:25
[INFO] [stdout]     |
[INFO] [stdout] 659 |                         trace!("Character sent successfully");
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:659:25
[INFO] [stdout]     |
[INFO] [stdout] 659 |                         trace!("Character sent successfully");
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:659:25
[INFO] [stdout]     |
[INFO] [stdout] 659 |                         trace!("Character sent successfully");
[INFO] [stdout]     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:666:5
[INFO] [stdout]     |
[INFO] [stdout] 666 |     debug!("Input thread ran out of input");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:666:5
[INFO] [stdout]     |
[INFO] [stdout] 666 |     debug!("Input thread ran out of input");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:666:5
[INFO] [stdout]     |
[INFO] [stdout] 666 |     debug!("Input thread ran out of input");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:666:5
[INFO] [stdout]     |
[INFO] [stdout] 666 |     debug!("Input thread ran out of input");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:666:5
[INFO] [stdout]     |
[INFO] [stdout] 666 |     debug!("Input thread ran out of input");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:671:5
[INFO] [stdout]     |
[INFO] [stdout] 671 |     debug!("Starting signal thread");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:671:5
[INFO] [stdout]     |
[INFO] [stdout] 671 |     debug!("Starting signal thread");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:671:5
[INFO] [stdout]     |
[INFO] [stdout] 671 |     debug!("Starting signal thread");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:671:5
[INFO] [stdout]     |
[INFO] [stdout] 671 |     debug!("Starting signal thread");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:671:5
[INFO] [stdout]     |
[INFO] [stdout] 671 |     debug!("Starting signal thread");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:675:13
[INFO] [stdout]     |
[INFO] [stdout] 675 |             trace!("Set signal mask successfully");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:675:13
[INFO] [stdout]     |
[INFO] [stdout] 675 |             trace!("Set signal mask successfully");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:675:13
[INFO] [stdout]     |
[INFO] [stdout] 675 |             trace!("Set signal mask successfully");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:675:13
[INFO] [stdout]     |
[INFO] [stdout] 675 |             trace!("Set signal mask successfully");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:675:13
[INFO] [stdout]     |
[INFO] [stdout] 675 |             trace!("Set signal mask successfully");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:684:13
[INFO] [stdout]     |
[INFO] [stdout] 684 |             trace!("Waited for signal successfully");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:684:13
[INFO] [stdout]     |
[INFO] [stdout] 684 |             trace!("Waited for signal successfully");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:684:13
[INFO] [stdout]     |
[INFO] [stdout] 684 |             trace!("Waited for signal successfully");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:684:13
[INFO] [stdout]     |
[INFO] [stdout] 684 |             trace!("Waited for signal successfully");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:684:13
[INFO] [stdout]     |
[INFO] [stdout] 684 |             trace!("Waited for signal successfully");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:693:13
[INFO] [stdout]     |
[INFO] [stdout] 693 |             trace!("Sent stop signal successfully");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:693:13
[INFO] [stdout]     |
[INFO] [stdout] 693 |             trace!("Sent stop signal successfully");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:693:13
[INFO] [stdout]     |
[INFO] [stdout] 693 |             trace!("Sent stop signal successfully");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:693:13
[INFO] [stdout]     |
[INFO] [stdout] 693 |             trace!("Sent stop signal successfully");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:693:13
[INFO] [stdout]     |
[INFO] [stdout] 693 |             trace!("Sent stop signal successfully");
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:697:13
[INFO] [stdout]     |
[INFO] [stdout] 697 |             debug!("Stop thread failed to send: {:?}", e);
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:697:13
[INFO] [stdout]     |
[INFO] [stdout] 697 |             debug!("Stop thread failed to send: {:?}", e);
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:697:13
[INFO] [stdout]     |
[INFO] [stdout] 697 |             debug!("Stop thread failed to send: {:?}", e);
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:697:13
[INFO] [stdout]     |
[INFO] [stdout] 697 |             debug!("Stop thread failed to send: {:?}", e);
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:697:13
[INFO] [stdout]     |
[INFO] [stdout] 697 |             debug!("Stop thread failed to send: {:?}", e);
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:701:5
[INFO] [stdout]     |
[INFO] [stdout] 701 |     debug!("Thread got interrupt signal, exiting");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:701:5
[INFO] [stdout]     |
[INFO] [stdout] 701 |     debug!("Thread got interrupt signal, exiting");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:701:5
[INFO] [stdout]     |
[INFO] [stdout] 701 |     debug!("Thread got interrupt signal, exiting");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:701:5
[INFO] [stdout]     |
[INFO] [stdout] 701 |     debug!("Thread got interrupt signal, exiting");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/ui.rs:701:5
[INFO] [stdout]     |
[INFO] [stdout] 701 |     debug!("Thread got interrupt signal, exiting");
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/main.rs:40:13
[INFO] [stdout]    |
[INFO] [stdout] 40 |             trace!("Logging initialized successfully");
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/main.rs:40:13
[INFO] [stdout]    |
[INFO] [stdout] 40 |             trace!("Logging initialized successfully");
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/main.rs:40:13
[INFO] [stdout]    |
[INFO] [stdout] 40 |             trace!("Logging initialized successfully");
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/main.rs:40:13
[INFO] [stdout]    |
[INFO] [stdout] 40 |             trace!("Logging initialized successfully");
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/main.rs:40:13
[INFO] [stdout]    |
[INFO] [stdout] 40 |             trace!("Logging initialized successfully");
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/main.rs:48:5
[INFO] [stdout]    |
[INFO] [stdout] 48 |     debug!("Creating UI instance");
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/main.rs:48:5
[INFO] [stdout]    |
[INFO] [stdout] 48 |     debug!("Creating UI instance");
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/main.rs:48:5
[INFO] [stdout]    |
[INFO] [stdout] 48 |     debug!("Creating UI instance");
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/main.rs:48:5
[INFO] [stdout]    |
[INFO] [stdout] 48 |     debug!("Creating UI instance");
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/main.rs:48:5
[INFO] [stdout]    |
[INFO] [stdout] 48 |     debug!("Creating UI instance");
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/main.rs:55:13
[INFO] [stdout]    |
[INFO] [stdout] 55 |             trace!("UI instance created successfully");
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/main.rs:55:13
[INFO] [stdout]    |
[INFO] [stdout] 55 |             trace!("UI instance created successfully");
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/main.rs:55:13
[INFO] [stdout]    |
[INFO] [stdout] 55 |             trace!("UI instance created successfully");
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/main.rs:55:13
[INFO] [stdout]    |
[INFO] [stdout] 55 |             trace!("UI instance created successfully");
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/main.rs:55:13
[INFO] [stdout]    |
[INFO] [stdout] 55 |             trace!("UI instance created successfully");
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/main.rs:61:5
[INFO] [stdout]    |
[INFO] [stdout] 61 |     debug!("Starting UI");
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/main.rs:61:5
[INFO] [stdout]    |
[INFO] [stdout] 61 |     debug!("Starting UI");
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/main.rs:61:5
[INFO] [stdout]    |
[INFO] [stdout] 61 |     debug!("Starting UI");
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/main.rs:61:5
[INFO] [stdout]    |
[INFO] [stdout] 61 |     debug!("Starting UI");
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/main.rs:61:5
[INFO] [stdout]    |
[INFO] [stdout] 61 |     debug!("Starting UI");
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/main.rs:65:13
[INFO] [stdout]    |
[INFO] [stdout] 65 |             debug!("UI finished successfully");
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/main.rs:65:13
[INFO] [stdout]    |
[INFO] [stdout] 65 |             debug!("UI finished successfully");
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/main.rs:65:13
[INFO] [stdout]    |
[INFO] [stdout] 65 |             debug!("UI finished successfully");
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/main.rs:65:13
[INFO] [stdout]    |
[INFO] [stdout] 65 |             debug!("UI finished successfully");
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/main.rs:65:13
[INFO] [stdout]    |
[INFO] [stdout] 65 |             debug!("UI finished successfully");
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `log` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the feature `cstr_to_str` has been stable since 1.4.0 and no longer requires an attribute to enable
[INFO] [stdout]   --> src/main.rs:14:12
[INFO] [stdout]    |
[INFO] [stdout] 14 | #![feature(cstr_to_str)]
[INFO] [stdout]    |            ^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: `#[warn(stable_features)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the feature `iter_arith` has been stable since 1.11.0 and no longer requires an attribute to enable
[INFO] [stdout]   --> src/main.rs:18:12
[INFO] [stdout]    |
[INFO] [stdout] 18 | #![feature(iter_arith)]
[INFO] [stdout]    |            ^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0635]: unknown feature `mpsc_select`
[INFO] [stdout]   --> src/main.rs:20:12
[INFO] [stdout]    |
[INFO] [stdout] 20 | #![feature(mpsc_select)]
[INFO] [stdout]    |            ^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0635]: unknown feature `convert`
[INFO] [stdout]   --> src/main.rs:15:12
[INFO] [stdout]    |
[INFO] [stdout] 15 | #![feature(convert)]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0635]: unknown feature `collections`
[INFO] [stdout]   --> src/main.rs:16:12
[INFO] [stdout]    |
[INFO] [stdout] 16 | #![feature(collections)]
[INFO] [stdout]    |            ^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0635]: unknown feature `into_cow`
[INFO] [stdout]   --> src/main.rs:17:12
[INFO] [stdout]    |
[INFO] [stdout] 17 | #![feature(into_cow)]
[INFO] [stdout]    |            ^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0635]: unknown feature `io`
[INFO] [stdout]   --> src/main.rs:19:12
[INFO] [stdout]    |
[INFO] [stdout] 19 | #![feature(io)]
[INFO] [stdout]    |            ^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: trait objects without an explicit `dyn` are deprecated
[INFO] [stdout]   --> src/error.rs:21:23
[INFO] [stdout]    |
[INFO] [stdout] 21 |     cause: Option<Box<Error>>
[INFO] [stdout]    |                       ^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this is accepted in the current edition (Rust 2015) but is a hard error in Rust 2021!
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/warnings-promoted-to-error.html>
[INFO] [stdout]    = note: `#[warn(bare_trait_objects)]` on by default
[INFO] [stdout] help: if this is a dyn-compatible trait, use `dyn`
[INFO] [stdout]    |
[INFO] [stdout] 21 |     cause: Option<Box<dyn Error>>
[INFO] [stdout]    |                       +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: trait objects without an explicit `dyn` are deprecated
[INFO] [stdout]   --> src/error.rs:35:32
[INFO] [stdout]    |
[INFO] [stdout] 35 |     fn cause(&self) -> Option<&Error> {
[INFO] [stdout]    |                                ^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this is accepted in the current edition (Rust 2015) but is a hard error in Rust 2021!
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/warnings-promoted-to-error.html>
[INFO] [stdout] help: if this is a dyn-compatible trait, use `dyn`
[INFO] [stdout]    |
[INFO] [stdout] 35 |     fn cause(&self) -> Option<&dyn Error> {
[INFO] [stdout]    |                                +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: trait objects without an explicit `dyn` are deprecated
[INFO] [stdout]   --> src/error.rs:44:67
[INFO] [stdout]    |
[INFO] [stdout] 44 |     pub fn new<T: Into<String>>(description: T, cause: Option<Box<Error>>) -> StringError {
[INFO] [stdout]    |                                                                   ^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this is accepted in the current edition (Rust 2015) but is a hard error in Rust 2021!
[INFO] [stdout]    = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2021/warnings-promoted-to-error.html>
[INFO] [stdout] help: if this is a dyn-compatible trait, use `dyn`
[INFO] [stdout]    |
[INFO] [stdout] 44 |     pub fn new<T: Into<String>>(description: T, cause: Option<Box<dyn Error>>) -> StringError {
[INFO] [stdout]    |                                                                   +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `into_cow` found for struct `String` in the current scope
[INFO] [stdout]    --> src/search.rs:108:36
[INFO] [stdout]     |
[INFO] [stdout] 108 |             self.lines.insert(line.into_cow(), info);
[INFO] [stdout]     |                                    ^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout] help: there is a method `into` with a similar name
[INFO] [stdout]     |
[INFO] [stdout] 108 -             self.lines.insert(line.into_cow(), info);
[INFO] [stdout] 108 +             self.lines.insert(line.into(), info);
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `push_pop` found for mutable reference `&mut BinaryHeap<LineMatch>` in the current scope
[INFO] [stdout]    --> src/search.rs:152:29
[INFO] [stdout]     |
[INFO] [stdout] 152 |                     matches.push_pop(match_item);
[INFO] [stdout]     |                             ^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout] help: there is a method `push` with a similar name
[INFO] [stdout]     |
[INFO] [stdout] 152 -                     matches.push_pop(match_item);
[INFO] [stdout] 152 +                     matches.push(match_item);
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unreachable statement
[INFO] [stdout]    --> src/ui.rs:522:9
[INFO] [stdout]     |
[INFO] [stdout] 351 | /         loop {
[INFO] [stdout] 352 | |             // this macro is bad and the rust people should feel bad
[INFO] [stdout] 353 | |             // on the other hand, multi-threaded UI! Yay!
[INFO] [stdout] 354 | |             select! {
[INFO] [stdout] ...   |
[INFO] [stdout] 519 | |         }
[INFO] [stdout]     | |_________- any code following this expression is unreachable
[INFO] [stdout] ...
[INFO] [stdout] 522 | /         match best_match {
[INFO] [stdout] 523 | |             Some(ref m) => {
[INFO] [stdout] 524 | |                 // redraw the best match
[INFO] [stdout] 525 | |                 match write!(output, " -> {}", m) {
[INFO] [stdout] ...   |
[INFO] [stdout] 535 | |         }
[INFO] [stdout]     | |_________^ unreachable statement
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(unreachable_code)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: no method named `chars` found for struct `StdinLock` in the current scope
[INFO] [stdout]    --> src/ui.rs:635:28
[INFO] [stdout]     |
[INFO] [stdout] 635 |     for maybe_chr in input.chars() {
[INFO] [stdout]     |                            ^^^^^ method not found in `StdinLock<'_>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0432, E0554, E0599, E0635.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0432`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `bis` (bin "bis") due to 17 previous errors; 444 warnings emitted
[INFO] running `Command { std: "docker" "inspect" "924b7380d0bd0bfc0d64f3a9e9d1c5cc18998acfe29132aad55cd706a26e7368", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "924b7380d0bd0bfc0d64f3a9e9d1c5cc18998acfe29132aad55cd706a26e7368", kill_on_drop: false }`
[INFO] [stdout] 924b7380d0bd0bfc0d64f3a9e9d1c5cc18998acfe29132aad55cd706a26e7368
