[INFO] cloning repository https://github.com/TartanLlama/lines-of-action [INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/TartanLlama/lines-of-action" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FTartanLlama%2Flines-of-action", kill_on_drop: false }` [INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FTartanLlama%2Flines-of-action'... [INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }` [INFO] [stdout] 4d757dd5a5f6b2ab72074cfd64eaaa64318ce220 [INFO] building TartanLlama/lines-of-action against master#11663cd3bfefef7d34e8f0892c250bf698049392+rustflags=-Dtail-expr-drop-order for pr-134523 [INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FTartanLlama%2Flines-of-action" "/workspace/builds/worker-0-tc1/source", kill_on_drop: false }` [INFO] [stderr] Cloning into '/workspace/builds/worker-0-tc1/source'... [INFO] [stderr] done. [INFO] validating manifest of git repo https://github.com/TartanLlama/lines-of-action on toolchain 11663cd3bfefef7d34e8f0892c250bf698049392 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+11663cd3bfefef7d34e8f0892c250bf698049392" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] started tweaking git repo https://github.com/TartanLlama/lines-of-action [INFO] finished tweaking git repo https://github.com/TartanLlama/lines-of-action [INFO] tweaked toml for git repo https://github.com/TartanLlama/lines-of-action written to /workspace/builds/worker-0-tc1/source/Cargo.toml [INFO] crate git repo https://github.com/TartanLlama/lines-of-action 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" "+11663cd3bfefef7d34e8f0892c250bf698049392" "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 memchr v0.1.6 [INFO] [stderr] Downloaded rand v0.3.11 [INFO] [stderr] Downloaded env_logger v0.3.1 [INFO] [stderr] Downloaded aho-corasick v0.3.2 [INFO] [stderr] Downloaded log v0.3.2 [INFO] [stderr] Downloaded libc v0.1.10 [INFO] [stderr] Downloaded regex v0.1.41 [INFO] [stderr] Downloaded regex-syntax v0.2.1 [INFO] [stderr] Downloaded winapi v0.2.2 [INFO] [stderr] Downloaded sfml v0.9.3 [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:f3a9d4ad9d972b27faf3965f35b62e55ba32bbce8f20bc8fe909558a86702fde" "/opt/rustwide/cargo-home/bin/cargo" "+11663cd3bfefef7d34e8f0892c250bf698049392" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] facaf2384e32e9375dbe0ef81d7f5466a1e5e39b73a89e369be6c3bcdf18e797 [INFO] running `Command { std: "docker" "start" "-a" "facaf2384e32e9375dbe0ef81d7f5466a1e5e39b73a89e369be6c3bcdf18e797", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "facaf2384e32e9375dbe0ef81d7f5466a1e5e39b73a89e369be6c3bcdf18e797", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "facaf2384e32e9375dbe0ef81d7f5466a1e5e39b73a89e369be6c3bcdf18e797", kill_on_drop: false }` [INFO] [stdout] facaf2384e32e9375dbe0ef81d7f5466a1e5e39b73a89e369be6c3bcdf18e797 [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=forbid -Dtail-expr-drop-order" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:f3a9d4ad9d972b27faf3965f35b62e55ba32bbce8f20bc8fe909558a86702fde" "/opt/rustwide/cargo-home/bin/cargo" "+11663cd3bfefef7d34e8f0892c250bf698049392" "build" "--frozen" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] a64b0fe0be68d359c58ac98ae6f157b3980342613b0b3b0958b4b6e241f7d87f [INFO] running `Command { std: "docker" "start" "-a" "a64b0fe0be68d359c58ac98ae6f157b3980342613b0b3b0958b4b6e241f7d87f", 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.10 [INFO] [stderr] Compiling winapi-build v0.1.1 [INFO] [stderr] Compiling winapi v0.2.2 [INFO] [stderr] Compiling regex-syntax v0.2.1 [INFO] [stderr] Compiling advapi32-sys v0.1.2 [INFO] [stderr] Compiling memchr v0.1.6 [INFO] [stderr] Compiling log v0.3.2 [INFO] [stderr] Compiling aho-corasick v0.3.2 [INFO] [stderr] Compiling rand v0.3.11 [INFO] [stderr] Compiling regex v0.1.41 [INFO] [stderr] Compiling sfml v0.9.3 [INFO] [stderr] Compiling env_logger v0.3.1 [INFO] [stderr] Compiling lines-of-action v0.1.0 (/opt/rustwide/workdir) [INFO] [stdout] warning: unused imports: `Display`, `Error`, and `Formatter` [INFO] [stdout] --> src/board.rs:2:16 [INFO] [stdout] | [INFO] [stdout] 2 | use std::fmt::{Formatter,Error,Display}; [INFO] [stdout] | ^^^^^^^^^ ^^^^^ ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_imports)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused import: `SocketAddr` [INFO] [stdout] --> src/server.rs:44:40 [INFO] [stdout] | [INFO] [stdout] 44 | use std::net::{TcpListener, TcpStream, SocketAddr}; [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused import: `Captures` [INFO] [stdout] --> src/server.rs:47:25 [INFO] [stdout] | [INFO] [stdout] 47 | use self::regex::{Regex,Captures}; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/server.rs:161:5 [INFO] [stdout] | [INFO] [stdout] 161 | debug!("Accepted"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `fmt_debug`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, and `windows` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see 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 `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/server.rs:161:5 [INFO] [stdout] | [INFO] [stdout] 161 | debug!("Accepted"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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/server.rs:161:5 [INFO] [stdout] | [INFO] [stdout] 161 | debug!("Accepted"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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/server.rs:161:5 [INFO] [stdout] | [INFO] [stdout] 161 | debug!("Accepted"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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/server.rs:161:5 [INFO] [stdout] | [INFO] [stdout] 161 | debug!("Accepted"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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: `Captures` [INFO] [stdout] --> src/api.rs:3:25 [INFO] [stdout] | [INFO] [stdout] 3 | use self::regex::{Regex,Captures}; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused import: `SocketAddr` [INFO] [stdout] --> src/api.rs:4:27 [INFO] [stdout] | [INFO] [stdout] 4 | use std::net::{TcpStream, SocketAddr, ToSocketAddrs}; [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `handle` is never read [INFO] [stdout] --> src/server.rs:180:5 [INFO] [stdout] | [INFO] [stdout] 178 | pub struct GameServer { [INFO] [stdout] | ---------- field in this struct [INFO] [stdout] 179 | command_receiver: Receiver, [INFO] [stdout] 180 | handle: thread::JoinHandle<()>, [INFO] [stdout] | ^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(dead_code)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/server.rs:82:15 [INFO] [stdout] | [INFO] [stdout] 82 | { stream.write(b"Move successful;\n"); }, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] = note: `#[warn(unused_must_use)]` on by default [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 82 | { let _ = stream.write(b"Move successful;\n"); }, [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/server.rs:84:15 [INFO] [stdout] | [INFO] [stdout] 84 | { stream.write(b"You can't move air, ya numpty;\n"); }, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 84 | { let _ = stream.write(b"You can't move air, ya numpty;\n"); }, [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/server.rs:86:15 [INFO] [stdout] | [INFO] [stdout] 86 | { stream.write(b"Stick to your own pieces!;\n"); }, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 86 | { let _ = stream.write(b"Stick to your own pieces!;\n"); }, [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/server.rs:101:15 [INFO] [stdout] | [INFO] [stdout] 101 | { stream.write(format!("Oh, hai {}!;\n",name).as_bytes()); }, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 101 | { let _ = stream.write(format!("Oh, hai {}!;\n",name).as_bytes()); }, [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/server.rs:103:15 [INFO] [stdout] | [INFO] [stdout] 103 | { stream.write(b"You've already registered, you asshat;\n"); }, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 103 | { let _ = stream.write(b"You've already registered, you asshat;\n"); }, [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/server.rs:105:15 [INFO] [stdout] | [INFO] [stdout] 105 | { stream.write(b"The game is full, get tae;\n"); }, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 105 | { let _ = stream.write(b"The game is full, get tae;\n"); }, [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/server.rs:106:49 [INFO] [stdout] | [INFO] [stdout] 106 | Err(CommandErr::Other(s)) => panic!(s), [INFO] [stdout] | ^ [INFO] [stdout] | [INFO] [stdout] = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: `#[warn(non_fmt_panics)]` on by default [INFO] [stdout] help: add a "{}" format string to `Display` the message [INFO] [stdout] | [INFO] [stdout] 106 | Err(CommandErr::Other(s)) => panic!("{}", s), [INFO] [stdout] | +++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/server.rs:146:15 [INFO] [stdout] | [INFO] [stdout] 146 | { stream.write(format!("You are {:?} and {} wants to batter you;\n",col,opponent).as_bytes()); }, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 146 | { let _ = stream.write(format!("You are {:?} and {} wants to batter you;\n",col,opponent).as_bytes()); }, [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/server.rs:148:15 [INFO] [stdout] | [INFO] [stdout] 148 | { stream.write(b"Who even are you?;\n"); }, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 148 | { let _ = stream.write(b"Who even are you?;\n"); }, [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/server.rs:156:9 [INFO] [stdout] | [INFO] [stdout] 156 | stream.write(b"You wot m8?;\n"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 156 | let _ = stream.write(b"You wot m8?;\n"); [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/server.rs:173:30 [INFO] [stdout] | [INFO] [stdout] 173 | Err(e) => panic!(e), [INFO] [stdout] | ^ [INFO] [stdout] | [INFO] [stdout] = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] help: add a "{}" format string to `Display` the message [INFO] [stdout] | [INFO] [stdout] 173 | Err(e) => panic!("{}", e), [INFO] [stdout] | +++++ [INFO] [stdout] help: or use std::panic::panic_any instead [INFO] [stdout] | [INFO] [stdout] 173 | Err(e) => std::panic::panic_any(e), [INFO] [stdout] | ~~~~~~~~~~~~~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/server.rs:201:40 [INFO] [stdout] | [INFO] [stdout] 201 | Err(e) => { panic!(e); } [INFO] [stdout] | ^ [INFO] [stdout] | [INFO] [stdout] = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] help: add a "{}" format string to `Display` the message [INFO] [stdout] | [INFO] [stdout] 201 | Err(e) => { panic!("{}", e); } [INFO] [stdout] | +++++ [INFO] [stdout] help: or use std::panic::panic_any instead [INFO] [stdout] | [INFO] [stdout] 201 | Err(e) => { std::panic::panic_any(e); } [INFO] [stdout] | ~~~~~~~~~~~~~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/api.rs:23:9 [INFO] [stdout] | [INFO] [stdout] 23 | stream.read(&mut c); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 23 | let _ = stream.read(&mut c); [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/api.rs:26:13 [INFO] [stdout] | [INFO] [stdout] 26 | stream.read(&mut c); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 26 | let _ = stream.read(&mut c); [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/api.rs:29:9 [INFO] [stdout] | [INFO] [stdout] 29 | stream.read(&mut c); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 29 | let _ = stream.read(&mut c); [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:116:9 [INFO] [stdout] | [INFO] [stdout] 116 | debug!("{} requested a move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `fmt_debug`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, and `windows` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see 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 `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:116:9 [INFO] [stdout] | [INFO] [stdout] 116 | debug!("{} requested a move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:116:9 [INFO] [stdout] | [INFO] [stdout] 116 | debug!("{} requested a move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:116:9 [INFO] [stdout] | [INFO] [stdout] 116 | debug!("{} requested a move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:116:9 [INFO] [stdout] | [INFO] [stdout] 116 | debug!("{} requested a move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:119:13 [INFO] [stdout] | [INFO] [stdout] 119 | debug!("{} already has a move waiting.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:119:13 [INFO] [stdout] | [INFO] [stdout] 119 | debug!("{} already has a move waiting.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:119:13 [INFO] [stdout] | [INFO] [stdout] 119 | debug!("{} already has a move waiting.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:119:13 [INFO] [stdout] | [INFO] [stdout] 119 | debug!("{} already has a move waiting.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:119:13 [INFO] [stdout] | [INFO] [stdout] 119 | debug!("{} already has a move waiting.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:121:17 [INFO] [stdout] | [INFO] [stdout] 121 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:121:17 [INFO] [stdout] | [INFO] [stdout] 121 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:121:17 [INFO] [stdout] | [INFO] [stdout] 121 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:121:17 [INFO] [stdout] | [INFO] [stdout] 121 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:121:17 [INFO] [stdout] | [INFO] [stdout] 121 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:126:17 [INFO] [stdout] | [INFO] [stdout] 126 | debug!("{} waiting on move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:126:17 [INFO] [stdout] | [INFO] [stdout] 126 | debug!("{} waiting on move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:126:17 [INFO] [stdout] | [INFO] [stdout] 126 | debug!("{} waiting on move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:126:17 [INFO] [stdout] | [INFO] [stdout] 126 | debug!("{} waiting on move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:126:17 [INFO] [stdout] | [INFO] [stdout] 126 | debug!("{} waiting on move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:131:13 [INFO] [stdout] | [INFO] [stdout] 131 | debug!("{} waiting on move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:131:13 [INFO] [stdout] | [INFO] [stdout] 131 | debug!("{} waiting on move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:131:13 [INFO] [stdout] | [INFO] [stdout] 131 | debug!("{} waiting on move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:131:13 [INFO] [stdout] | [INFO] [stdout] 131 | debug!("{} waiting on move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:131:13 [INFO] [stdout] | [INFO] [stdout] 131 | debug!("{} waiting on move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:138:9 [INFO] [stdout] | [INFO] [stdout] 138 | debug!("{} sent a move.", self.players.get(&id).unwrap().name); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:138:9 [INFO] [stdout] | [INFO] [stdout] 138 | debug!("{} sent a move.", self.players.get(&id).unwrap().name); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:138:9 [INFO] [stdout] | [INFO] [stdout] 138 | debug!("{} sent a move.", self.players.get(&id).unwrap().name); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:138:9 [INFO] [stdout] | [INFO] [stdout] 138 | debug!("{} sent a move.", self.players.get(&id).unwrap().name); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:138:9 [INFO] [stdout] | [INFO] [stdout] 138 | debug!("{} sent a move.", self.players.get(&id).unwrap().name); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:154:21 [INFO] [stdout] | [INFO] [stdout] 154 | debug!("{} is waiting on move.", other.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:154:21 [INFO] [stdout] | [INFO] [stdout] 154 | debug!("{} is waiting on move.", other.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:154:21 [INFO] [stdout] | [INFO] [stdout] 154 | debug!("{} is waiting on move.", other.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:154:21 [INFO] [stdout] | [INFO] [stdout] 154 | debug!("{} is waiting on move.", other.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:154:21 [INFO] [stdout] | [INFO] [stdout] 154 | debug!("{} is waiting on move.", other.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:155:21 [INFO] [stdout] | [INFO] [stdout] 155 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:155:21 [INFO] [stdout] | [INFO] [stdout] 155 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:155:21 [INFO] [stdout] | [INFO] [stdout] 155 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:155:21 [INFO] [stdout] | [INFO] [stdout] 155 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:155:21 [INFO] [stdout] | [INFO] [stdout] 155 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:160:21 [INFO] [stdout] | [INFO] [stdout] 160 | debug!("Caching move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:160:21 [INFO] [stdout] | [INFO] [stdout] 160 | debug!("Caching move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:160:21 [INFO] [stdout] | [INFO] [stdout] 160 | debug!("Caching move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:160:21 [INFO] [stdout] | [INFO] [stdout] 160 | debug!("Caching move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:160:21 [INFO] [stdout] | [INFO] [stdout] 160 | debug!("Caching move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:164:17 [INFO] [stdout] | [INFO] [stdout] 164 | debug!("Caching move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:164:17 [INFO] [stdout] | [INFO] [stdout] 164 | debug!("Caching move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:164:17 [INFO] [stdout] | [INFO] [stdout] 164 | debug!("Caching move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:164:17 [INFO] [stdout] | [INFO] [stdout] 164 | debug!("Caching move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:164:17 [INFO] [stdout] | [INFO] [stdout] 164 | debug!("Caching move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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: unnecessary parentheses around method argument [INFO] [stdout] --> src/main.rs:179:40 [INFO] [stdout] | [INFO] [stdout] 179 | self.players.insert(id,(Player::new(name.to_string()))); [INFO] [stdout] | ^ ^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_parens)]` on by default [INFO] [stdout] help: remove these parentheses [INFO] [stdout] | [INFO] [stdout] 179 - self.players.insert(id,(Player::new(name.to_string()))); [INFO] [stdout] 179 + self.players.insert(id,Player::new(name.to_string())); [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:180:17 [INFO] [stdout] | [INFO] [stdout] 180 | debug!("Registered new player: {}", name); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:180:17 [INFO] [stdout] | [INFO] [stdout] 180 | debug!("Registered new player: {}", name); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:180:17 [INFO] [stdout] | [INFO] [stdout] 180 | debug!("Registered new player: {}", name); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:180:17 [INFO] [stdout] | [INFO] [stdout] 180 | debug!("Registered new player: {}", name); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:180:17 [INFO] [stdout] | [INFO] [stdout] 180 | debug!("Registered new player: {}", name); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:210:9 [INFO] [stdout] | [INFO] [stdout] 210 | debug!("Ready to play!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:210:9 [INFO] [stdout] | [INFO] [stdout] 210 | debug!("Ready to play!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:210:9 [INFO] [stdout] | [INFO] [stdout] 210 | debug!("Ready to play!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:210:9 [INFO] [stdout] | [INFO] [stdout] 210 | debug!("Ready to play!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:210:9 [INFO] [stdout] | [INFO] [stdout] 210 | debug!("Ready to play!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:230:9 [INFO] [stdout] | [INFO] [stdout] 230 | debug!("Key pressed"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:230:9 [INFO] [stdout] | [INFO] [stdout] 230 | debug!("Key pressed"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:230:9 [INFO] [stdout] | [INFO] [stdout] 230 | debug!("Key pressed"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:230:9 [INFO] [stdout] | [INFO] [stdout] 230 | debug!("Key pressed"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:230:9 [INFO] [stdout] | [INFO] [stdout] 230 | debug!("Key pressed"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:232:13 [INFO] [stdout] | [INFO] [stdout] 232 | debug!("It was space, checking available moves"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:232:13 [INFO] [stdout] | [INFO] [stdout] 232 | debug!("It was space, checking available moves"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:232:13 [INFO] [stdout] | [INFO] [stdout] 232 | debug!("It was space, checking available moves"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:232:13 [INFO] [stdout] | [INFO] [stdout] 232 | debug!("It was space, checking available moves"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:232:13 [INFO] [stdout] | [INFO] [stdout] 232 | debug!("It was space, checking available moves"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:234:17 [INFO] [stdout] | [INFO] [stdout] 234 | debug!("Checking player {}", i); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:234:17 [INFO] [stdout] | [INFO] [stdout] 234 | debug!("Checking player {}", i); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:234:17 [INFO] [stdout] | [INFO] [stdout] 234 | debug!("Checking player {}", i); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:234:17 [INFO] [stdout] | [INFO] [stdout] 234 | debug!("Checking player {}", i); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:234:17 [INFO] [stdout] | [INFO] [stdout] 234 | debug!("Checking player {}", i); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:236:21 [INFO] [stdout] | [INFO] [stdout] 236 | debug!("They are waiting on a move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:236:21 [INFO] [stdout] | [INFO] [stdout] 236 | debug!("They are waiting on a move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:236:21 [INFO] [stdout] | [INFO] [stdout] 236 | debug!("They are waiting on a move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:236:21 [INFO] [stdout] | [INFO] [stdout] 236 | debug!("They are waiting on a move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:236:21 [INFO] [stdout] | [INFO] [stdout] 236 | debug!("They are waiting on a move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:238:25 [INFO] [stdout] | [INFO] [stdout] 238 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:238:25 [INFO] [stdout] | [INFO] [stdout] 238 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:238:25 [INFO] [stdout] | [INFO] [stdout] 238 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:238:25 [INFO] [stdout] | [INFO] [stdout] 238 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:238:25 [INFO] [stdout] | [INFO] [stdout] 238 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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: variable does not need to be mutable [INFO] [stdout] --> src/main.rs:42:13 [INFO] [stdout] | [INFO] [stdout] 42 | let mut window = match RenderWindow::new(VideoMode::new_init(SCREEN_SIZE, SCREEN_SIZE, 32), [INFO] [stdout] | ----^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | help: remove this `mut` [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_mut)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: variable does not need to be mutable [INFO] [stdout] --> src/main.rs:50:13 [INFO] [stdout] | [INFO] [stdout] 50 | let mut board = Board::new(); [INFO] [stdout] | ----^^^^^ [INFO] [stdout] | | [INFO] [stdout] | help: remove this `mut` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: variable does not need to be mutable [INFO] [stdout] --> src/main.rs:51:13 [INFO] [stdout] | [INFO] [stdout] 51 | let mut players = BTreeMap::new(); [INFO] [stdout] | ----^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | help: remove this `mut` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused variable: `id` [INFO] [stdout] --> src/main.rs:87:46 [INFO] [stdout] | [INFO] [stdout] 87 | CommandData::Message(id,msg) => [INFO] [stdout] | ^^ help: if this is intentional, prefix it with an underscore: `_id` [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_variables)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused variable: `id` [INFO] [stdout] --> src/main.rs:204:14 [INFO] [stdout] | [INFO] [stdout] 204 | for (id, p) in &self.players { [INFO] [stdout] | ^^ help: if this is intentional, prefix it with an underscore: `_id` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: fields `turn` and `game_started` are never read [INFO] [stdout] --> src/main.rs:26:5 [INFO] [stdout] | [INFO] [stdout] 21 | struct Engine { [INFO] [stdout] | ------ fields in this struct [INFO] [stdout] ... [INFO] [stdout] 26 | turn: Colour, [INFO] [stdout] | ^^^^ [INFO] [stdout] 27 | game_started: bool, [INFO] [stdout] | ^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(dead_code)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/main.rs:95:59 [INFO] [stdout] | [INFO] [stdout] 95 | Err(GetCommandErr::Failed(why)) => panic!(why), [INFO] [stdout] | ^^^ [INFO] [stdout] | [INFO] [stdout] = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: `#[warn(non_fmt_panics)]` on by default [INFO] [stdout] help: add a "{}" format string to `Display` the message [INFO] [stdout] | [INFO] [stdout] 95 | Err(GetCommandErr::Failed(why)) => panic!("{}", why), [INFO] [stdout] | +++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/main.rs:104:34 [INFO] [stdout] | [INFO] [stdout] 104 | Err(s) => panic!(s), [INFO] [stdout] | ^ [INFO] [stdout] | [INFO] [stdout] = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] help: add a "{}" format string to `Display` the message [INFO] [stdout] | [INFO] [stdout] 104 | Err(s) => panic!("{}", s), [INFO] [stdout] | +++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/main.rs:141:9 [INFO] [stdout] | [INFO] [stdout] 141 | / reply.send(match self.board.move_piece(&mov,&player_colour) { [INFO] [stdout] 142 | | Ok(()) => { [INFO] [stdout] 143 | | Ok(CommandOk::None) [INFO] [stdout] 144 | | }, [INFO] [stdout] 145 | | Err(MoveErr::NoPiece) => Err(CommandErr::NoPiece), [INFO] [stdout] 146 | | Err(MoveErr::WrongPiece) => Err(CommandErr::WrongPiece), [INFO] [stdout] 147 | | }); [INFO] [stdout] | |__________^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] = note: `#[warn(unused_must_use)]` on by default [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 141 | let _ = reply.send(match self.board.move_piece(&mov,&player_colour) { [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/main.rs:156:21 [INFO] [stdout] | [INFO] [stdout] 156 | other.reply.clone().unwrap().send(Ok(CommandOk::Move(mov.clone()))); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 156 | let _ = other.reply.clone().unwrap().send(Ok(CommandOk::Move(mov.clone()))); [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/main.rs:173:13 [INFO] [stdout] | [INFO] [stdout] 173 | reply.send(Err(CommandErr::AlreadyRegistered)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 173 | let _ = reply.send(Err(CommandErr::AlreadyRegistered)); [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/main.rs:177:9 [INFO] [stdout] | [INFO] [stdout] 177 | / reply.send( [INFO] [stdout] 178 | | if self.players.len() < 2 { [INFO] [stdout] 179 | | self.players.insert(id,(Player::new(name.to_string()))); [INFO] [stdout] 180 | | debug!("Registered new player: {}", name); [INFO] [stdout] ... | [INFO] [stdout] 183 | | Err(CommandErr::GameFull) [INFO] [stdout] 184 | | }); [INFO] [stdout] | |______________^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 177 | let _ = reply.send( [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/main.rs:189:9 [INFO] [stdout] | [INFO] [stdout] 189 | reply.send(Ok(CommandOk::None)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 189 | let _ = reply.send(Ok(CommandOk::None)); [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/main.rs:195:23 [INFO] [stdout] | [INFO] [stdout] 195 | None => { reply.send(Err(CommandErr::NotRegistered)); return; }, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 195 | None => { let _ = reply.send(Err(CommandErr::NotRegistered)); return; }, [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/main.rs:218:13 [INFO] [stdout] | [INFO] [stdout] 218 | p1.reply.clone().unwrap().send(Ok(CommandOk::Ready(p2_name, p1.colour.clone()))); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 218 | let _ = p1.reply.clone().unwrap().send(Ok(CommandOk::Ready(p2_name, p1.colour.clone()))); [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/main.rs:225:13 [INFO] [stdout] | [INFO] [stdout] 225 | p2.reply.clone().unwrap().send(Ok(CommandOk::Ready(p1_name, p2.colour))); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 225 | let _ = p2.reply.clone().unwrap().send(Ok(CommandOk::Ready(p1_name, p2.colour))); [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/main.rs:239:25 [INFO] [stdout] | [INFO] [stdout] 239 | self.players.get(&i).unwrap().reply.clone().unwrap().send(Ok(CommandOk::Move(mov.clone()))); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 239 | let _ = self.players.get(&i).unwrap().reply.clone().unwrap().send(Ok(CommandOk::Move(mov.clone()))); [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 2.69s [INFO] running `Command { std: "docker" "inspect" "a64b0fe0be68d359c58ac98ae6f157b3980342613b0b3b0958b4b6e241f7d87f", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "a64b0fe0be68d359c58ac98ae6f157b3980342613b0b3b0958b4b6e241f7d87f", kill_on_drop: false }` [INFO] [stdout] a64b0fe0be68d359c58ac98ae6f157b3980342613b0b3b0958b4b6e241f7d87f [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=forbid -Dtail-expr-drop-order" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:f3a9d4ad9d972b27faf3965f35b62e55ba32bbce8f20bc8fe909558a86702fde" "/opt/rustwide/cargo-home/bin/cargo" "+11663cd3bfefef7d34e8f0892c250bf698049392" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 8a01bb68367559c4f8f403afe79345ba64a1aed119185832d2ac7102e21ddf7e [INFO] running `Command { std: "docker" "start" "-a" "8a01bb68367559c4f8f403afe79345ba64a1aed119185832d2ac7102e21ddf7e", kill_on_drop: false }` [INFO] [stderr] warning: no edition set: defaulting to the 2015 edition while the latest is 2024 [INFO] [stdout] warning: unused imports: `Display`, `Error`, and `Formatter` [INFO] [stdout] --> src/board.rs:2:16 [INFO] [stdout] | [INFO] [stdout] 2 | use std::fmt::{Formatter,Error,Display}; [INFO] [stdout] | ^^^^^^^^^ ^^^^^ ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_imports)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused import: `SocketAddr` [INFO] [stdout] --> src/server.rs:44:40 [INFO] [stdout] | [INFO] [stdout] 44 | use std::net::{TcpListener, TcpStream, SocketAddr}; [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused import: `Captures` [INFO] [stdout] --> src/server.rs:47:25 [INFO] [stdout] | [INFO] [stdout] 47 | use self::regex::{Regex,Captures}; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/server.rs:161:5 [INFO] [stdout] | [INFO] [stdout] 161 | debug!("Accepted"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `fmt_debug`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, and `windows` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see 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 `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/server.rs:161:5 [INFO] [stdout] | [INFO] [stdout] 161 | debug!("Accepted"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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/server.rs:161:5 [INFO] [stdout] | [INFO] [stdout] 161 | debug!("Accepted"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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/server.rs:161:5 [INFO] [stdout] | [INFO] [stdout] 161 | debug!("Accepted"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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/server.rs:161:5 [INFO] [stdout] | [INFO] [stdout] 161 | debug!("Accepted"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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: `Captures` [INFO] [stdout] --> src/api.rs:3:25 [INFO] [stdout] | [INFO] [stdout] 3 | use self::regex::{Regex,Captures}; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused import: `SocketAddr` [INFO] [stdout] --> src/api.rs:4:27 [INFO] [stdout] | [INFO] [stdout] 4 | use std::net::{TcpStream, SocketAddr, ToSocketAddrs}; [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `handle` is never read [INFO] [stdout] --> src/server.rs:180:5 [INFO] [stdout] | [INFO] [stdout] 178 | pub struct GameServer { [INFO] [stdout] | ---------- field in this struct [INFO] [stdout] 179 | command_receiver: Receiver, [INFO] [stdout] 180 | handle: thread::JoinHandle<()>, [INFO] [stdout] | ^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(dead_code)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/server.rs:82:15 [INFO] [stdout] | [INFO] [stdout] 82 | { stream.write(b"Move successful;\n"); }, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] = note: `#[warn(unused_must_use)]` on by default [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 82 | { let _ = stream.write(b"Move successful;\n"); }, [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/server.rs:84:15 [INFO] [stdout] | [INFO] [stdout] 84 | { stream.write(b"You can't move air, ya numpty;\n"); }, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 84 | { let _ = stream.write(b"You can't move air, ya numpty;\n"); }, [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/server.rs:86:15 [INFO] [stdout] | [INFO] [stdout] 86 | { stream.write(b"Stick to your own pieces!;\n"); }, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 86 | { let _ = stream.write(b"Stick to your own pieces!;\n"); }, [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/server.rs:101:15 [INFO] [stdout] | [INFO] [stdout] 101 | { stream.write(format!("Oh, hai {}!;\n",name).as_bytes()); }, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 101 | { let _ = stream.write(format!("Oh, hai {}!;\n",name).as_bytes()); }, [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/server.rs:103:15 [INFO] [stdout] | [INFO] [stdout] 103 | { stream.write(b"You've already registered, you asshat;\n"); }, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 103 | { let _ = stream.write(b"You've already registered, you asshat;\n"); }, [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/server.rs:105:15 [INFO] [stdout] | [INFO] [stdout] 105 | { stream.write(b"The game is full, get tae;\n"); }, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 105 | { let _ = stream.write(b"The game is full, get tae;\n"); }, [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/server.rs:106:49 [INFO] [stdout] | [INFO] [stdout] 106 | Err(CommandErr::Other(s)) => panic!(s), [INFO] [stdout] | ^ [INFO] [stdout] | [INFO] [stdout] = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: `#[warn(non_fmt_panics)]` on by default [INFO] [stdout] help: add a "{}" format string to `Display` the message [INFO] [stdout] | [INFO] [stdout] 106 | Err(CommandErr::Other(s)) => panic!("{}", s), [INFO] [stdout] | +++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/server.rs:146:15 [INFO] [stdout] | [INFO] [stdout] 146 | { stream.write(format!("You are {:?} and {} wants to batter you;\n",col,opponent).as_bytes()); }, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 146 | { let _ = stream.write(format!("You are {:?} and {} wants to batter you;\n",col,opponent).as_bytes()); }, [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/server.rs:148:15 [INFO] [stdout] | [INFO] [stdout] 148 | { stream.write(b"Who even are you?;\n"); }, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 148 | { let _ = stream.write(b"Who even are you?;\n"); }, [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/server.rs:156:9 [INFO] [stdout] | [INFO] [stdout] 156 | stream.write(b"You wot m8?;\n"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 156 | let _ = stream.write(b"You wot m8?;\n"); [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/server.rs:173:30 [INFO] [stdout] | [INFO] [stdout] 173 | Err(e) => panic!(e), [INFO] [stdout] | ^ [INFO] [stdout] | [INFO] [stdout] = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] help: add a "{}" format string to `Display` the message [INFO] [stdout] | [INFO] [stdout] 173 | Err(e) => panic!("{}", e), [INFO] [stdout] | +++++ [INFO] [stdout] help: or use std::panic::panic_any instead [INFO] [stdout] | [INFO] [stdout] 173 | Err(e) => std::panic::panic_any(e), [INFO] [stdout] | ~~~~~~~~~~~~~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/server.rs:201:40 [INFO] [stdout] | [INFO] [stdout] 201 | Err(e) => { panic!(e); } [INFO] [stdout] | ^ [INFO] [stdout] | [INFO] [stdout] = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] help: add a "{}" format string to `Display` the message [INFO] [stdout] | [INFO] [stdout] 201 | Err(e) => { panic!("{}", e); } [INFO] [stdout] | +++++ [INFO] [stdout] help: or use std::panic::panic_any instead [INFO] [stdout] | [INFO] [stdout] 201 | Err(e) => { std::panic::panic_any(e); } [INFO] [stdout] | ~~~~~~~~~~~~~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/api.rs:23:9 [INFO] [stdout] | [INFO] [stdout] 23 | stream.read(&mut c); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 23 | let _ = stream.read(&mut c); [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/api.rs:26:13 [INFO] [stdout] | [INFO] [stdout] 26 | stream.read(&mut c); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 26 | let _ = stream.read(&mut c); [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/api.rs:29:9 [INFO] [stdout] | [INFO] [stdout] 29 | stream.read(&mut c); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 29 | let _ = stream.read(&mut c); [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling lines-of-action v0.1.0 (/opt/rustwide/workdir) [INFO] [stdout] warning: unused imports: `Display`, `Error`, and `Formatter` [INFO] [stdout] --> src/board.rs:2:16 [INFO] [stdout] | [INFO] [stdout] 2 | use std::fmt::{Formatter,Error,Display}; [INFO] [stdout] | ^^^^^^^^^ ^^^^^ ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_imports)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused import: `SocketAddr` [INFO] [stdout] --> src/server.rs:44:40 [INFO] [stdout] | [INFO] [stdout] 44 | use std::net::{TcpListener, TcpStream, SocketAddr}; [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused import: `Captures` [INFO] [stdout] --> src/server.rs:47:25 [INFO] [stdout] | [INFO] [stdout] 47 | use self::regex::{Regex,Captures}; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/server.rs:161:5 [INFO] [stdout] | [INFO] [stdout] 161 | debug!("Accepted"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `fmt_debug`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, and `windows` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see 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 `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/server.rs:161:5 [INFO] [stdout] | [INFO] [stdout] 161 | debug!("Accepted"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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/server.rs:161:5 [INFO] [stdout] | [INFO] [stdout] 161 | debug!("Accepted"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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/server.rs:161:5 [INFO] [stdout] | [INFO] [stdout] 161 | debug!("Accepted"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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/server.rs:161:5 [INFO] [stdout] | [INFO] [stdout] 161 | debug!("Accepted"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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: `Captures` [INFO] [stdout] --> src/api.rs:3:25 [INFO] [stdout] | [INFO] [stdout] 3 | use self::regex::{Regex,Captures}; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused import: `SocketAddr` [INFO] [stdout] --> src/api.rs:4:27 [INFO] [stdout] | [INFO] [stdout] 4 | use std::net::{TcpStream, SocketAddr, ToSocketAddrs}; [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:116:9 [INFO] [stdout] | [INFO] [stdout] 116 | debug!("{} requested a move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `clippy`, `debug_assertions`, `doc`, `docsrs`, `doctest`, `feature`, `fmt_debug`, `miri`, `overflow_checks`, `panic`, `proc_macro`, `relocation_model`, `rustfmt`, `sanitize`, `sanitizer_cfi_generalize_pointers`, `sanitizer_cfi_normalize_integers`, `target_abi`, `target_arch`, `target_endian`, `target_env`, `target_family`, `target_feature`, `target_has_atomic`, `target_has_atomic_equal_alignment`, `target_has_atomic_load_store`, `target_os`, `target_pointer_width`, `target_thread_local`, `target_vendor`, `test`, `ub_checks`, `unix`, and `windows` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see 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 `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:116:9 [INFO] [stdout] | [INFO] [stdout] 116 | debug!("{} requested a move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:116:9 [INFO] [stdout] | [INFO] [stdout] 116 | debug!("{} requested a move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:116:9 [INFO] [stdout] | [INFO] [stdout] 116 | debug!("{} requested a move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:116:9 [INFO] [stdout] | [INFO] [stdout] 116 | debug!("{} requested a move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:119:13 [INFO] [stdout] | [INFO] [stdout] 119 | debug!("{} already has a move waiting.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:119:13 [INFO] [stdout] | [INFO] [stdout] 119 | debug!("{} already has a move waiting.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:119:13 [INFO] [stdout] | [INFO] [stdout] 119 | debug!("{} already has a move waiting.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:119:13 [INFO] [stdout] | [INFO] [stdout] 119 | debug!("{} already has a move waiting.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:119:13 [INFO] [stdout] | [INFO] [stdout] 119 | debug!("{} already has a move waiting.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:121:17 [INFO] [stdout] | [INFO] [stdout] 121 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:121:17 [INFO] [stdout] | [INFO] [stdout] 121 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:121:17 [INFO] [stdout] | [INFO] [stdout] 121 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:121:17 [INFO] [stdout] | [INFO] [stdout] 121 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:121:17 [INFO] [stdout] | [INFO] [stdout] 121 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:126:17 [INFO] [stdout] | [INFO] [stdout] 126 | debug!("{} waiting on move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:126:17 [INFO] [stdout] | [INFO] [stdout] 126 | debug!("{} waiting on move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:126:17 [INFO] [stdout] | [INFO] [stdout] 126 | debug!("{} waiting on move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:126:17 [INFO] [stdout] | [INFO] [stdout] 126 | debug!("{} waiting on move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:126:17 [INFO] [stdout] | [INFO] [stdout] 126 | debug!("{} waiting on move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:131:13 [INFO] [stdout] | [INFO] [stdout] 131 | debug!("{} waiting on move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:131:13 [INFO] [stdout] | [INFO] [stdout] 131 | debug!("{} waiting on move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:131:13 [INFO] [stdout] | [INFO] [stdout] 131 | debug!("{} waiting on move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:131:13 [INFO] [stdout] | [INFO] [stdout] 131 | debug!("{} waiting on move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:131:13 [INFO] [stdout] | [INFO] [stdout] 131 | debug!("{} waiting on move.", player.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:138:9 [INFO] [stdout] | [INFO] [stdout] 138 | debug!("{} sent a move.", self.players.get(&id).unwrap().name); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:138:9 [INFO] [stdout] | [INFO] [stdout] 138 | debug!("{} sent a move.", self.players.get(&id).unwrap().name); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:138:9 [INFO] [stdout] | [INFO] [stdout] 138 | debug!("{} sent a move.", self.players.get(&id).unwrap().name); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:138:9 [INFO] [stdout] | [INFO] [stdout] 138 | debug!("{} sent a move.", self.players.get(&id).unwrap().name); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:138:9 [INFO] [stdout] | [INFO] [stdout] 138 | debug!("{} sent a move.", self.players.get(&id).unwrap().name); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:154:21 [INFO] [stdout] | [INFO] [stdout] 154 | debug!("{} is waiting on move.", other.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:154:21 [INFO] [stdout] | [INFO] [stdout] 154 | debug!("{} is waiting on move.", other.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:154:21 [INFO] [stdout] | [INFO] [stdout] 154 | debug!("{} is waiting on move.", other.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:154:21 [INFO] [stdout] | [INFO] [stdout] 154 | debug!("{} is waiting on move.", other.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:154:21 [INFO] [stdout] | [INFO] [stdout] 154 | debug!("{} is waiting on move.", other.name.clone()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:155:21 [INFO] [stdout] | [INFO] [stdout] 155 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:155:21 [INFO] [stdout] | [INFO] [stdout] 155 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:155:21 [INFO] [stdout] | [INFO] [stdout] 155 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:155:21 [INFO] [stdout] | [INFO] [stdout] 155 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:155:21 [INFO] [stdout] | [INFO] [stdout] 155 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:160:21 [INFO] [stdout] | [INFO] [stdout] 160 | debug!("Caching move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:160:21 [INFO] [stdout] | [INFO] [stdout] 160 | debug!("Caching move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:160:21 [INFO] [stdout] | [INFO] [stdout] 160 | debug!("Caching move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:160:21 [INFO] [stdout] | [INFO] [stdout] 160 | debug!("Caching move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:160:21 [INFO] [stdout] | [INFO] [stdout] 160 | debug!("Caching move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:164:17 [INFO] [stdout] | [INFO] [stdout] 164 | debug!("Caching move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:164:17 [INFO] [stdout] | [INFO] [stdout] 164 | debug!("Caching move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:164:17 [INFO] [stdout] | [INFO] [stdout] 164 | debug!("Caching move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:164:17 [INFO] [stdout] | [INFO] [stdout] 164 | debug!("Caching move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:164:17 [INFO] [stdout] | [INFO] [stdout] 164 | debug!("Caching move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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: unnecessary parentheses around method argument [INFO] [stdout] --> src/main.rs:179:40 [INFO] [stdout] | [INFO] [stdout] 179 | self.players.insert(id,(Player::new(name.to_string()))); [INFO] [stdout] | ^ ^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_parens)]` on by default [INFO] [stdout] help: remove these parentheses [INFO] [stdout] | [INFO] [stdout] 179 - self.players.insert(id,(Player::new(name.to_string()))); [INFO] [stdout] 179 + self.players.insert(id,Player::new(name.to_string())); [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:180:17 [INFO] [stdout] | [INFO] [stdout] 180 | debug!("Registered new player: {}", name); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:180:17 [INFO] [stdout] | [INFO] [stdout] 180 | debug!("Registered new player: {}", name); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:180:17 [INFO] [stdout] | [INFO] [stdout] 180 | debug!("Registered new player: {}", name); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:180:17 [INFO] [stdout] | [INFO] [stdout] 180 | debug!("Registered new player: {}", name); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:180:17 [INFO] [stdout] | [INFO] [stdout] 180 | debug!("Registered new player: {}", name); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:210:9 [INFO] [stdout] | [INFO] [stdout] 210 | debug!("Ready to play!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:210:9 [INFO] [stdout] | [INFO] [stdout] 210 | debug!("Ready to play!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:210:9 [INFO] [stdout] | [INFO] [stdout] 210 | debug!("Ready to play!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:210:9 [INFO] [stdout] | [INFO] [stdout] 210 | debug!("Ready to play!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:210:9 [INFO] [stdout] | [INFO] [stdout] 210 | debug!("Ready to play!"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:230:9 [INFO] [stdout] | [INFO] [stdout] 230 | debug!("Key pressed"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:230:9 [INFO] [stdout] | [INFO] [stdout] 230 | debug!("Key pressed"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:230:9 [INFO] [stdout] | [INFO] [stdout] 230 | debug!("Key pressed"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:230:9 [INFO] [stdout] | [INFO] [stdout] 230 | debug!("Key pressed"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:230:9 [INFO] [stdout] | [INFO] [stdout] 230 | debug!("Key pressed"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:232:13 [INFO] [stdout] | [INFO] [stdout] 232 | debug!("It was space, checking available moves"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:232:13 [INFO] [stdout] | [INFO] [stdout] 232 | debug!("It was space, checking available moves"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:232:13 [INFO] [stdout] | [INFO] [stdout] 232 | debug!("It was space, checking available moves"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:232:13 [INFO] [stdout] | [INFO] [stdout] 232 | debug!("It was space, checking available moves"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:232:13 [INFO] [stdout] | [INFO] [stdout] 232 | debug!("It was space, checking available moves"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:234:17 [INFO] [stdout] | [INFO] [stdout] 234 | debug!("Checking player {}", i); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:234:17 [INFO] [stdout] | [INFO] [stdout] 234 | debug!("Checking player {}", i); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:234:17 [INFO] [stdout] | [INFO] [stdout] 234 | debug!("Checking player {}", i); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:234:17 [INFO] [stdout] | [INFO] [stdout] 234 | debug!("Checking player {}", i); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:234:17 [INFO] [stdout] | [INFO] [stdout] 234 | debug!("Checking player {}", i); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:236:21 [INFO] [stdout] | [INFO] [stdout] 236 | debug!("They are waiting on a move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:236:21 [INFO] [stdout] | [INFO] [stdout] 236 | debug!("They are waiting on a move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:236:21 [INFO] [stdout] | [INFO] [stdout] 236 | debug!("They are waiting on a move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:236:21 [INFO] [stdout] | [INFO] [stdout] 236 | debug!("They are waiting on a move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:236:21 [INFO] [stdout] | [INFO] [stdout] 236 | debug!("They are waiting on a move"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:238:25 [INFO] [stdout] | [INFO] [stdout] 238 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:238:25 [INFO] [stdout] | [INFO] [stdout] 238 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:238:25 [INFO] [stdout] | [INFO] [stdout] 238 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:238:25 [INFO] [stdout] | [INFO] [stdout] 238 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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:238:25 [INFO] [stdout] | [INFO] [stdout] 238 | debug!("Sending move."); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for 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: field `handle` is never read [INFO] [stdout] --> src/server.rs:180:5 [INFO] [stdout] | [INFO] [stdout] 178 | pub struct GameServer { [INFO] [stdout] | ---------- field in this struct [INFO] [stdout] 179 | command_receiver: Receiver, [INFO] [stdout] 180 | handle: thread::JoinHandle<()>, [INFO] [stdout] | ^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(dead_code)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/server.rs:82:15 [INFO] [stdout] | [INFO] [stdout] 82 | { stream.write(b"Move successful;\n"); }, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] = note: `#[warn(unused_must_use)]` on by default [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 82 | { let _ = stream.write(b"Move successful;\n"); }, [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/server.rs:84:15 [INFO] [stdout] | [INFO] [stdout] 84 | { stream.write(b"You can't move air, ya numpty;\n"); }, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 84 | { let _ = stream.write(b"You can't move air, ya numpty;\n"); }, [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/server.rs:86:15 [INFO] [stdout] | [INFO] [stdout] 86 | { stream.write(b"Stick to your own pieces!;\n"); }, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 86 | { let _ = stream.write(b"Stick to your own pieces!;\n"); }, [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/server.rs:101:15 [INFO] [stdout] | [INFO] [stdout] 101 | { stream.write(format!("Oh, hai {}!;\n",name).as_bytes()); }, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 101 | { let _ = stream.write(format!("Oh, hai {}!;\n",name).as_bytes()); }, [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/server.rs:103:15 [INFO] [stdout] | [INFO] [stdout] 103 | { stream.write(b"You've already registered, you asshat;\n"); }, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 103 | { let _ = stream.write(b"You've already registered, you asshat;\n"); }, [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/server.rs:105:15 [INFO] [stdout] | [INFO] [stdout] 105 | { stream.write(b"The game is full, get tae;\n"); }, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 105 | { let _ = stream.write(b"The game is full, get tae;\n"); }, [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/server.rs:106:49 [INFO] [stdout] | [INFO] [stdout] 106 | Err(CommandErr::Other(s)) => panic!(s), [INFO] [stdout] | ^ [INFO] [stdout] | [INFO] [stdout] = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: `#[warn(non_fmt_panics)]` on by default [INFO] [stdout] help: add a "{}" format string to `Display` the message [INFO] [stdout] | [INFO] [stdout] 106 | Err(CommandErr::Other(s)) => panic!("{}", s), [INFO] [stdout] | +++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/server.rs:146:15 [INFO] [stdout] | [INFO] [stdout] 146 | { stream.write(format!("You are {:?} and {} wants to batter you;\n",col,opponent).as_bytes()); }, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 146 | { let _ = stream.write(format!("You are {:?} and {} wants to batter you;\n",col,opponent).as_bytes()); }, [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/server.rs:148:15 [INFO] [stdout] | [INFO] [stdout] 148 | { stream.write(b"Who even are you?;\n"); }, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 148 | { let _ = stream.write(b"Who even are you?;\n"); }, [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/server.rs:156:9 [INFO] [stdout] | [INFO] [stdout] 156 | stream.write(b"You wot m8?;\n"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 156 | let _ = stream.write(b"You wot m8?;\n"); [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/server.rs:173:30 [INFO] [stdout] | [INFO] [stdout] 173 | Err(e) => panic!(e), [INFO] [stdout] | ^ [INFO] [stdout] | [INFO] [stdout] = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] help: add a "{}" format string to `Display` the message [INFO] [stdout] | [INFO] [stdout] 173 | Err(e) => panic!("{}", e), [INFO] [stdout] | +++++ [INFO] [stdout] help: or use std::panic::panic_any instead [INFO] [stdout] | [INFO] [stdout] 173 | Err(e) => std::panic::panic_any(e), [INFO] [stdout] | ~~~~~~~~~~~~~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/server.rs:201:40 [INFO] [stdout] | [INFO] [stdout] 201 | Err(e) => { panic!(e); } [INFO] [stdout] | ^ [INFO] [stdout] | [INFO] [stdout] = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] help: add a "{}" format string to `Display` the message [INFO] [stdout] | [INFO] [stdout] 201 | Err(e) => { panic!("{}", e); } [INFO] [stdout] | +++++ [INFO] [stdout] help: or use std::panic::panic_any instead [INFO] [stdout] | [INFO] [stdout] 201 | Err(e) => { std::panic::panic_any(e); } [INFO] [stdout] | ~~~~~~~~~~~~~~~~~~~~~ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/api.rs:23:9 [INFO] [stdout] | [INFO] [stdout] 23 | stream.read(&mut c); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 23 | let _ = stream.read(&mut c); [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/api.rs:26:13 [INFO] [stdout] | [INFO] [stdout] 26 | stream.read(&mut c); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 26 | let _ = stream.read(&mut c); [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/api.rs:29:9 [INFO] [stdout] | [INFO] [stdout] 29 | stream.read(&mut c); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 29 | let _ = stream.read(&mut c); [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: variable does not need to be mutable [INFO] [stdout] --> src/main.rs:42:13 [INFO] [stdout] | [INFO] [stdout] 42 | let mut window = match RenderWindow::new(VideoMode::new_init(SCREEN_SIZE, SCREEN_SIZE, 32), [INFO] [stdout] | ----^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | help: remove this `mut` [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_mut)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: variable does not need to be mutable [INFO] [stdout] --> src/main.rs:50:13 [INFO] [stdout] | [INFO] [stdout] 50 | let mut board = Board::new(); [INFO] [stdout] | ----^^^^^ [INFO] [stdout] | | [INFO] [stdout] | help: remove this `mut` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: variable does not need to be mutable [INFO] [stdout] --> src/main.rs:51:13 [INFO] [stdout] | [INFO] [stdout] 51 | let mut players = BTreeMap::new(); [INFO] [stdout] | ----^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | help: remove this `mut` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused variable: `id` [INFO] [stdout] --> src/main.rs:87:46 [INFO] [stdout] | [INFO] [stdout] 87 | CommandData::Message(id,msg) => [INFO] [stdout] | ^^ help: if this is intentional, prefix it with an underscore: `_id` [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_variables)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused variable: `id` [INFO] [stdout] --> src/main.rs:204:14 [INFO] [stdout] | [INFO] [stdout] 204 | for (id, p) in &self.players { [INFO] [stdout] | ^^ help: if this is intentional, prefix it with an underscore: `_id` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: fields `turn` and `game_started` are never read [INFO] [stdout] --> src/main.rs:26:5 [INFO] [stdout] | [INFO] [stdout] 21 | struct Engine { [INFO] [stdout] | ------ fields in this struct [INFO] [stdout] ... [INFO] [stdout] 26 | turn: Colour, [INFO] [stdout] | ^^^^ [INFO] [stdout] 27 | game_started: bool, [INFO] [stdout] | ^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(dead_code)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/main.rs:95:59 [INFO] [stdout] | [INFO] [stdout] 95 | Err(GetCommandErr::Failed(why)) => panic!(why), [INFO] [stdout] | ^^^ [INFO] [stdout] | [INFO] [stdout] = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] = note: `#[warn(non_fmt_panics)]` on by default [INFO] [stdout] help: add a "{}" format string to `Display` the message [INFO] [stdout] | [INFO] [stdout] 95 | Err(GetCommandErr::Failed(why)) => panic!("{}", why), [INFO] [stdout] | +++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: panic message is not a string literal [INFO] [stdout] --> src/main.rs:104:34 [INFO] [stdout] | [INFO] [stdout] 104 | Err(s) => panic!(s), [INFO] [stdout] | ^ [INFO] [stdout] | [INFO] [stdout] = note: this usage of `panic!()` is deprecated; it will be a hard error in Rust 2021 [INFO] [stdout] = note: for more information, see [INFO] [stdout] help: add a "{}" format string to `Display` the message [INFO] [stdout] | [INFO] [stdout] 104 | Err(s) => panic!("{}", s), [INFO] [stdout] | +++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/main.rs:141:9 [INFO] [stdout] | [INFO] [stdout] 141 | / reply.send(match self.board.move_piece(&mov,&player_colour) { [INFO] [stdout] 142 | | Ok(()) => { [INFO] [stdout] 143 | | Ok(CommandOk::None) [INFO] [stdout] 144 | | }, [INFO] [stdout] 145 | | Err(MoveErr::NoPiece) => Err(CommandErr::NoPiece), [INFO] [stdout] 146 | | Err(MoveErr::WrongPiece) => Err(CommandErr::WrongPiece), [INFO] [stdout] 147 | | }); [INFO] [stdout] | |__________^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] = note: `#[warn(unused_must_use)]` on by default [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 141 | let _ = reply.send(match self.board.move_piece(&mov,&player_colour) { [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/main.rs:156:21 [INFO] [stdout] | [INFO] [stdout] 156 | other.reply.clone().unwrap().send(Ok(CommandOk::Move(mov.clone()))); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 156 | let _ = other.reply.clone().unwrap().send(Ok(CommandOk::Move(mov.clone()))); [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/main.rs:173:13 [INFO] [stdout] | [INFO] [stdout] 173 | reply.send(Err(CommandErr::AlreadyRegistered)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 173 | let _ = reply.send(Err(CommandErr::AlreadyRegistered)); [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/main.rs:177:9 [INFO] [stdout] | [INFO] [stdout] 177 | / reply.send( [INFO] [stdout] 178 | | if self.players.len() < 2 { [INFO] [stdout] 179 | | self.players.insert(id,(Player::new(name.to_string()))); [INFO] [stdout] 180 | | debug!("Registered new player: {}", name); [INFO] [stdout] ... | [INFO] [stdout] 183 | | Err(CommandErr::GameFull) [INFO] [stdout] 184 | | }); [INFO] [stdout] | |______________^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 177 | let _ = reply.send( [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/main.rs:189:9 [INFO] [stdout] | [INFO] [stdout] 189 | reply.send(Ok(CommandOk::None)); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 189 | let _ = reply.send(Ok(CommandOk::None)); [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/main.rs:195:23 [INFO] [stdout] | [INFO] [stdout] 195 | None => { reply.send(Err(CommandErr::NotRegistered)); return; }, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 195 | None => { let _ = reply.send(Err(CommandErr::NotRegistered)); return; }, [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/main.rs:218:13 [INFO] [stdout] | [INFO] [stdout] 218 | p1.reply.clone().unwrap().send(Ok(CommandOk::Ready(p2_name, p1.colour.clone()))); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 218 | let _ = p1.reply.clone().unwrap().send(Ok(CommandOk::Ready(p2_name, p1.colour.clone()))); [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/main.rs:225:13 [INFO] [stdout] | [INFO] [stdout] 225 | p2.reply.clone().unwrap().send(Ok(CommandOk::Ready(p1_name, p2.colour))); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 225 | let _ = p2.reply.clone().unwrap().send(Ok(CommandOk::Ready(p1_name, p2.colour))); [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `Result` that must be used [INFO] [stdout] --> src/main.rs:239:25 [INFO] [stdout] | [INFO] [stdout] 239 | self.players.get(&i).unwrap().reply.clone().unwrap().send(Ok(CommandOk::Move(mov.clone()))); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 239 | let _ = self.players.get(&i).unwrap().reply.clone().unwrap().send(Ok(CommandOk::Move(mov.clone()))); [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 0.38s [INFO] running `Command { std: "docker" "inspect" "8a01bb68367559c4f8f403afe79345ba64a1aed119185832d2ac7102e21ddf7e", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "8a01bb68367559c4f8f403afe79345ba64a1aed119185832d2ac7102e21ddf7e", kill_on_drop: false }` [INFO] [stdout] 8a01bb68367559c4f8f403afe79345ba64a1aed119185832d2ac7102e21ddf7e