[INFO] fetching crate eat-nom 0.1.5...
[INFO] checking eat-nom-0.1.5 against master#f609b7e0586f81fefb3523e3e17adf779ac416be for pr-129466-2
[INFO] extracting crate eat-nom 0.1.5 into /workspace/builds/worker-7-tc1/source
[INFO] validating manifest of crates.io crate eat-nom 0.1.5 on toolchain f609b7e0586f81fefb3523e3e17adf779ac416be
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+f609b7e0586f81fefb3523e3e17adf779ac416be" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] started tweaking crates.io crate eat-nom 0.1.5
[INFO] finished tweaking crates.io crate eat-nom 0.1.5
[INFO] tweaked toml for crates.io crate eat-nom 0.1.5 written to /workspace/builds/worker-7-tc1/source/Cargo.toml
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+f609b7e0586f81fefb3523e3e17adf779ac416be" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]      Locking 14 packages to latest compatible versions
[INFO] [stderr]       Adding arrayvec v0.5.2 (available: v0.7.6)
[INFO] [stderr]       Adding bitflags v1.3.2 (available: v2.6.0)
[INFO] [stderr]       Adding bitvec v0.19.6 (available: v1.0.1)
[INFO] [stderr]       Adding funty v1.1.0 (available: v2.0.0)
[INFO] [stderr]       Adding lexical-core v0.7.6 (available: v1.0.2)
[INFO] [stderr]       Adding memchr v2.3.4 (available: v2.7.4)
[INFO] [stderr]       Adding nom v6.2.2 (available: v7.1.3)
[INFO] [stderr]       Adding radium v0.5.3 (available: v1.1.0)
[INFO] [stderr]       Adding wyz v0.2.0 (available: v0.6.1)
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+f609b7e0586f81fefb3523e3e17adf779ac416be" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded radium v0.5.3
[INFO] [stderr]   Downloaded bitvec v0.19.6
[INFO] [stderr]   Downloaded nom v6.2.2
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-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:ceb6ea022f8a89cebbe621bb4987e73a935bd40dfbb726f832cfff4742a5b95a" "/opt/rustwide/cargo-home/bin/cargo" "+f609b7e0586f81fefb3523e3e17adf779ac416be" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 4a1109db03346c65750e7e41c09b827cb01ecf0908c7cf74a5dafbb6cc129bc6
[INFO] running `Command { std: "docker" "start" "-a" "4a1109db03346c65750e7e41c09b827cb01ecf0908c7cf74a5dafbb6cc129bc6", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "4a1109db03346c65750e7e41c09b827cb01ecf0908c7cf74a5dafbb6cc129bc6", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "4a1109db03346c65750e7e41c09b827cb01ecf0908c7cf74a5dafbb6cc129bc6", kill_on_drop: false }`
[INFO] [stdout] 4a1109db03346c65750e7e41c09b827cb01ecf0908c7cf74a5dafbb6cc129bc6
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:ceb6ea022f8a89cebbe621bb4987e73a935bd40dfbb726f832cfff4742a5b95a" "/opt/rustwide/cargo-home/bin/cargo" "+f609b7e0586f81fefb3523e3e17adf779ac416be" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 560c790566fb55a19e5b9d76e990179eb6798d9b5b9e90e3f4b174e08271747e
[INFO] running `Command { std: "docker" "start" "-a" "560c790566fb55a19e5b9d76e990179eb6798d9b5b9e90e3f4b174e08271747e", kill_on_drop: false }`
[INFO] [stderr]    Compiling radium v0.5.3
[INFO] [stderr]    Compiling memchr v2.3.4
[INFO] [stderr]    Compiling lexical-core v0.7.6
[INFO] [stderr]    Compiling version_check v0.9.5
[INFO] [stderr]     Checking arrayvec v0.5.2
[INFO] [stderr]     Checking tap v1.0.1
[INFO] [stderr]     Checking bitflags v1.3.2
[INFO] [stderr]     Checking funty v1.1.0
[INFO] [stderr]     Checking wyz v0.2.0
[INFO] [stderr]    Compiling nom v6.2.2
[INFO] [stderr]     Checking bitvec v0.19.6
[INFO] [stderr]     Checking eat-nom v0.1.5 (/opt/rustwide/workdir)
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin`
[INFO] [stdout]   --> src/error.rs:13:16
[INFO] [stdout]    |
[INFO] [stdout] 13 |     #[cfg_attr(tarpaulin, skip)]
[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]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin`
[INFO] [stdout]   --> src/error.rs:24:16
[INFO] [stdout]    |
[INFO] [stdout] 24 |     #[cfg_attr(tarpaulin, skip)]
[INFO] [stdout]    |                ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin`
[INFO] [stdout]   --> src/error.rs:35:16
[INFO] [stdout]    |
[INFO] [stdout] 35 |     #[cfg_attr(tarpaulin, skip)]
[INFO] [stdout]    |                ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin`
[INFO] [stdout]   --> src/error.rs:42:16
[INFO] [stdout]    |
[INFO] [stdout] 42 |     #[cfg_attr(tarpaulin, skip)]
[INFO] [stdout]    |                ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin`
[INFO] [stdout]   --> src/error.rs:49:16
[INFO] [stdout]    |
[INFO] [stdout] 49 |     #[cfg_attr(tarpaulin, skip)]
[INFO] [stdout]    |                ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin`
[INFO] [stdout]   --> src/error.rs:54:16
[INFO] [stdout]    |
[INFO] [stdout] 54 |     #[cfg_attr(tarpaulin, skip)]
[INFO] [stdout]    |                ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin`
[INFO] [stdout]   --> src/error.rs:61:16
[INFO] [stdout]    |
[INFO] [stdout] 61 |     #[cfg_attr(tarpaulin, skip)]
[INFO] [stdout]    |                ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin`
[INFO] [stdout]   --> src/error.rs:13:16
[INFO] [stdout]    |
[INFO] [stdout] 13 |     #[cfg_attr(tarpaulin, skip)]
[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]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin`
[INFO] [stdout]   --> src/error.rs:24:16
[INFO] [stdout]    |
[INFO] [stdout] 24 |     #[cfg_attr(tarpaulin, skip)]
[INFO] [stdout]    |                ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin`
[INFO] [stdout]   --> src/error.rs:35:16
[INFO] [stdout]    |
[INFO] [stdout] 35 |     #[cfg_attr(tarpaulin, skip)]
[INFO] [stdout]    |                ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin`
[INFO] [stdout]   --> src/error.rs:42:16
[INFO] [stdout]    |
[INFO] [stdout] 42 |     #[cfg_attr(tarpaulin, skip)]
[INFO] [stdout]    |                ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin`
[INFO] [stdout]   --> src/error.rs:49:16
[INFO] [stdout]    |
[INFO] [stdout] 49 |     #[cfg_attr(tarpaulin, skip)]
[INFO] [stdout]    |                ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin`
[INFO] [stdout]   --> src/error.rs:54:16
[INFO] [stdout]    |
[INFO] [stdout] 54 |     #[cfg_attr(tarpaulin, skip)]
[INFO] [stdout]    |                ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin`
[INFO] [stdout]   --> src/error.rs:61:16
[INFO] [stdout]    |
[INFO] [stdout] 61 |     #[cfg_attr(tarpaulin, skip)]
[INFO] [stdout]    |                ^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:26:29
[INFO] [stdout]    |
[INFO] [stdout] 25 | pub fn parse_ip(input: &str) -> EatResult<IpAddr> {
[INFO] [stdout]    |                                 ----------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 26 |     let (_, out) = ip(input)?;
[INFO] [stdout]    |                    ---------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<IpAddr, error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |                    |
[INFO] [stdout]    |                    this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              `error::ErrorKind` implements `From<AddrParseError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<ParseIntError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<nom::Err<(&str, nom::error::ErrorKind)>>`
[INFO] [stdout]    = note: required for `Result<IpAddr, error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/error.rs:85:50
[INFO] [stdout]    |
[INFO] [stdout] 80 |     fn test_until_eof_ok() -> EatResult<()> {
[INFO] [stdout]    |                               ------------- expected `error::ErrorKind` because of this
[INFO] [stdout] ...
[INFO] [stdout] 85 |         let (x, y) = until_eof("hello, worldeof")?;
[INFO] [stdout]    |                      ----------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<(), error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |                      |
[INFO] [stdout]    |                      this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              `error::ErrorKind` implements `From<AddrParseError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<ParseIntError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<nom::Err<(&str, nom::error::ErrorKind)>>`
[INFO] [stdout]    = note: required for `Result<(), error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:45:67
[INFO] [stdout]    |
[INFO] [stdout] 44 | pub fn parse_ip_mask<'a>(input: &'a str, concat: &'a str) -> EatResult<(IpAddr, IpAddr)> {
[INFO] [stdout]    |                                                              --------------------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 45 |     let (_, (ip, _, mask)) = tuple((ip, tag(concat), mask))(input)?;
[INFO] [stdout]    |                              -------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<(IpAddr, IpAddr), error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |                              |
[INFO] [stdout]    |                              this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              `error::ErrorKind` implements `From<AddrParseError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<ParseIntError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<nom::Err<(&str, nom::error::ErrorKind)>>`
[INFO] [stdout]    = note: required for `Result<(IpAddr, IpAddr), error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:53:81
[INFO] [stdout]    |
[INFO] [stdout] 51 | pub fn parse_ip_mask_opt(input: &str) -> EatResult<(IpAddr, IpAddr)> {
[INFO] [stdout]    |                                          --------------------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 52 |     let (_, (ip, _, mask)) =
[INFO] [stdout] 53 |         tuple((ip, alt((tag("/"), tag("-"), tag(" "), tag("\\"))), mask))(input)?;
[INFO] [stdout]    |         ------------------------------------------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<(IpAddr, IpAddr), error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |         |
[INFO] [stdout]    |         this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              `error::ErrorKind` implements `From<AddrParseError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<ParseIntError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<nom::Err<(&str, nom::error::ErrorKind)>>`
[INFO] [stdout]    = note: required for `Result<(IpAddr, IpAddr), error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:26:29
[INFO] [stdout]    |
[INFO] [stdout] 25 | pub fn parse_ip(input: &str) -> EatResult<IpAddr> {
[INFO] [stdout]    |                                 ----------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 26 |     let (_, out) = ip(input)?;
[INFO] [stdout]    |                    ---------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<IpAddr, error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |                    |
[INFO] [stdout]    |                    this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              `error::ErrorKind` implements `From<AddrParseError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<ParseIntError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<nom::Err<(&str, nom::error::ErrorKind)>>`
[INFO] [stdout]    = note: required for `Result<IpAddr, error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:60:67
[INFO] [stdout]    |
[INFO] [stdout] 59 | pub fn parse_ip_range<'a>(input: &'a str, concat: &'a str) -> EatResult<Range<IpAddr>> {
[INFO] [stdout]    |                                                               ------------------------ expected `error::ErrorKind` because of this
[INFO] [stdout] 60 |     let (_, (start, _, end)) = tuple((ip, tag(concat), ip))(input)?;
[INFO] [stdout]    |                                -----------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<std::ops::Range<IpAddr>, error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |                                |
[INFO] [stdout]    |                                this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              `error::ErrorKind` implements `From<AddrParseError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<ParseIntError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<nom::Err<(&str, nom::error::ErrorKind)>>`
[INFO] [stdout]    = note: required for `Result<std::ops::Range<IpAddr>, error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:68:79
[INFO] [stdout]    |
[INFO] [stdout] 66 | pub fn parse_ip_range_opt(input: &str) -> EatResult<Range<IpAddr>> {
[INFO] [stdout]    |                                           ------------------------ expected `error::ErrorKind` because of this
[INFO] [stdout] 67 |     let (_, (start, _, end)) =
[INFO] [stdout] 68 |         tuple((ip, alt((tag("/"), tag("-"), tag(" "), tag("\\"))), ip))(input)?;
[INFO] [stdout]    |         ----------------------------------------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<std::ops::Range<IpAddr>, error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |         |
[INFO] [stdout]    |         this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              `error::ErrorKind` implements `From<AddrParseError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<ParseIntError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<nom::Err<(&str, nom::error::ErrorKind)>>`
[INFO] [stdout]    = note: required for `Result<std::ops::Range<IpAddr>, error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:45:67
[INFO] [stdout]    |
[INFO] [stdout] 44 | pub fn parse_ip_mask<'a>(input: &'a str, concat: &'a str) -> EatResult<(IpAddr, IpAddr)> {
[INFO] [stdout]    |                                                              --------------------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 45 |     let (_, (ip, _, mask)) = tuple((ip, tag(concat), mask))(input)?;
[INFO] [stdout]    |                              -------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<(IpAddr, IpAddr), error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |                              |
[INFO] [stdout]    |                              this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              `error::ErrorKind` implements `From<AddrParseError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<ParseIntError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<nom::Err<(&str, nom::error::ErrorKind)>>`
[INFO] [stdout]    = note: required for `Result<(IpAddr, IpAddr), error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:75:69
[INFO] [stdout]    |
[INFO] [stdout] 74 | pub fn parse_ip_cidr<'a>(input: &'a str, concat: &'a str) -> EatResult<(IpAddr, usize)> {
[INFO] [stdout]    |                                                              -------------------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 75 |     let (_, (ip, _, cidr)) = tuple((ip, tag(concat), digit1))(input)?;
[INFO] [stdout]    |                              ---------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<(IpAddr, usize), error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |                              |
[INFO] [stdout]    |                              this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              `error::ErrorKind` implements `From<AddrParseError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<ParseIntError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<nom::Err<(&str, nom::error::ErrorKind)>>`
[INFO] [stdout]    = note: required for `Result<(IpAddr, usize), error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:83:83
[INFO] [stdout]    |
[INFO] [stdout] 81 | pub fn parse_ip_cidr_opt(input: &str) -> EatResult<(IpAddr, usize)> {
[INFO] [stdout]    |                                          -------------------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 82 |     let (_, (ip, _, cidr)) =
[INFO] [stdout] 83 |         tuple((ip, alt((tag("/"), tag("-"), tag(" "), tag("\\"))), digit1))(input)?;
[INFO] [stdout]    |         --------------------------------------------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<(IpAddr, usize), error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |         |
[INFO] [stdout]    |         this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              `error::ErrorKind` implements `From<AddrParseError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<ParseIntError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<nom::Err<(&str, nom::error::ErrorKind)>>`
[INFO] [stdout]    = note: required for `Result<(IpAddr, usize), error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:53:81
[INFO] [stdout]    |
[INFO] [stdout] 51 | pub fn parse_ip_mask_opt(input: &str) -> EatResult<(IpAddr, IpAddr)> {
[INFO] [stdout]    |                                          --------------------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 52 |     let (_, (ip, _, mask)) =
[INFO] [stdout] 53 |         tuple((ip, alt((tag("/"), tag("-"), tag(" "), tag("\\"))), mask))(input)?;
[INFO] [stdout]    |         ------------------------------------------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<(IpAddr, IpAddr), error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |         |
[INFO] [stdout]    |         this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              `error::ErrorKind` implements `From<AddrParseError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<ParseIntError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<nom::Err<(&str, nom::error::ErrorKind)>>`
[INFO] [stdout]    = note: required for `Result<(IpAddr, IpAddr), error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:60:67
[INFO] [stdout]    |
[INFO] [stdout] 59 | pub fn parse_ip_range<'a>(input: &'a str, concat: &'a str) -> EatResult<Range<IpAddr>> {
[INFO] [stdout]    |                                                               ------------------------ expected `error::ErrorKind` because of this
[INFO] [stdout] 60 |     let (_, (start, _, end)) = tuple((ip, tag(concat), ip))(input)?;
[INFO] [stdout]    |                                -----------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<std::ops::Range<IpAddr>, error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |                                |
[INFO] [stdout]    |                                this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              `error::ErrorKind` implements `From<AddrParseError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<ParseIntError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<nom::Err<(&str, nom::error::ErrorKind)>>`
[INFO] [stdout]    = note: required for `Result<std::ops::Range<IpAddr>, error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:68:79
[INFO] [stdout]    |
[INFO] [stdout] 66 | pub fn parse_ip_range_opt(input: &str) -> EatResult<Range<IpAddr>> {
[INFO] [stdout]    |                                           ------------------------ expected `error::ErrorKind` because of this
[INFO] [stdout] 67 |     let (_, (start, _, end)) =
[INFO] [stdout] 68 |         tuple((ip, alt((tag("/"), tag("-"), tag(" "), tag("\\"))), ip))(input)?;
[INFO] [stdout]    |         ----------------------------------------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<std::ops::Range<IpAddr>, error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |         |
[INFO] [stdout]    |         this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              `error::ErrorKind` implements `From<AddrParseError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<ParseIntError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<nom::Err<(&str, nom::error::ErrorKind)>>`
[INFO] [stdout]    = note: required for `Result<std::ops::Range<IpAddr>, error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:75:69
[INFO] [stdout]    |
[INFO] [stdout] 74 | pub fn parse_ip_cidr<'a>(input: &'a str, concat: &'a str) -> EatResult<(IpAddr, usize)> {
[INFO] [stdout]    |                                                              -------------------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 75 |     let (_, (ip, _, cidr)) = tuple((ip, tag(concat), digit1))(input)?;
[INFO] [stdout]    |                              ---------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<(IpAddr, usize), error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |                              |
[INFO] [stdout]    |                              this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              `error::ErrorKind` implements `From<AddrParseError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<ParseIntError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<nom::Err<(&str, nom::error::ErrorKind)>>`
[INFO] [stdout]    = note: required for `Result<(IpAddr, usize), error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error to `error::ErrorKind`
[INFO] [stdout]   --> src/ip.rs:83:83
[INFO] [stdout]    |
[INFO] [stdout] 81 | pub fn parse_ip_cidr_opt(input: &str) -> EatResult<(IpAddr, usize)> {
[INFO] [stdout]    |                                          -------------------------- expected `error::ErrorKind` because of this
[INFO] [stdout] 82 |     let (_, (ip, _, cidr)) =
[INFO] [stdout] 83 |         tuple((ip, alt((tag("/"), tag("-"), tag(" "), tag("\\"))), digit1))(input)?;
[INFO] [stdout]    |         --------------------------------------------------------------------------^ the trait `From<nom::Err<nom::error::Error<&str>>>` is not implemented for `error::ErrorKind`, which is required by `Result<(IpAddr, usize), error::ErrorKind>: FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout]    |         |
[INFO] [stdout]    |         this can't be annotated with `?` because it has type `Result<_, nom::Err<nom::error::Error<&str>>>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = help: the following other types implement trait `From<T>`:
[INFO] [stdout]              `error::ErrorKind` implements `From<AddrParseError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<ParseIntError>`
[INFO] [stdout]              `error::ErrorKind` implements `From<nom::Err<(&str, nom::error::ErrorKind)>>`
[INFO] [stdout]    = note: required for `Result<(IpAddr, usize), error::ErrorKind>` to implement `FromResidual<Result<Infallible, nom::Err<nom::error::Error<&str>>>>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: aborting due to 7 previous errors; 7 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0277`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `eat-nom` (lib) due to 8 previous errors; 7 warnings emitted
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stdout] error: aborting due to 8 previous errors; 7 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0277`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `eat-nom` (lib test) due to 9 previous errors; 7 warnings emitted
[INFO] running `Command { std: "docker" "inspect" "560c790566fb55a19e5b9d76e990179eb6798d9b5b9e90e3f4b174e08271747e", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "560c790566fb55a19e5b9d76e990179eb6798d9b5b9e90e3f4b174e08271747e", kill_on_drop: false }`
[INFO] [stdout] 560c790566fb55a19e5b9d76e990179eb6798d9b5b9e90e3f4b174e08271747e