[INFO] fetching crate modbus-rs 0.16.0...
[INFO] testing modbus-rs-0.16.0 against 1.100.0-beta.1+cargoflags=--release for beta-release-1.100-2
[INFO] extracting crate modbus-rs 0.16.0 into /workspace/builds/worker-2-tc2/source
[INFO] started tweaking crates.io crate modbus-rs 0.16.0
[INFO] removed 0 missing examples
[INFO] finished tweaking crates.io crate modbus-rs 0.16.0
[INFO] tweaked toml for crates.io crate modbus-rs 0.16.0 written to /workspace/builds/worker-2-tc2/source/Cargo.toml
[INFO] validating manifest of crates.io crate modbus-rs 0.16.0 on toolchain 1.100.0-beta.1
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+1.100.0-beta.1" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] crate crates.io crate modbus-rs 0.16.0 already has a lockfile, it will not be regenerated
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+1.100.0-beta.1" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr] warning: `package.homepage` is redundant with `package.repository`
[INFO] [stderr]    --> Cargo.toml:227:12
[INFO] [stderr]     |
[INFO] [stderr] 227 | homepage = "https://github.com/Raghava-Ch/modbus-rs"
[INFO] [stderr]     |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 232 | repository = "https://github.com/Raghava-Ch/modbus-rs"
[INFO] [stderr]     |              -----------------------------------------
[INFO] [stderr]     |
[INFO] [stderr]     = note: `cargo::redundant_homepage` is set to `warn` by default
[INFO] [stderr] help: consider removing `package.homepage`
[INFO] [stderr] warning: `modbus-rs` (manifest) generated 1 warning
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,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" "-m" "1610612736" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:77db811e55d90add9212f6832c23229e3de5f1c1f9905e8cb07319ea15df73ac" "sleep" "infinity", kill_on_drop: false }`
[INFO] [stdout] aad9ece8f5c826e1a98bbf953b32c224c70278ffed597ee0624e7d4a2c2351db
[INFO] running `Command { std: "docker" "start" "aad9ece8f5c826e1a98bbf953b32c224c70278ffed597ee0624e7d4a2c2351db", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "aad9ece8f5c826e1a98bbf953b32c224c70278ffed597ee0624e7d4a2c2351db", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-w" "/opt/rustwide/workdir" "--user" "0:0" "aad9ece8f5c826e1a98bbf953b32c224c70278ffed597ee0624e7d4a2c2351db" "/opt/rustwide/cargo-home/bin/cargo" "+1.100.0-beta.1" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "aad9ece8f5c826e1a98bbf953b32c224c70278ffed597ee0624e7d4a2c2351db", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-w" "/opt/rustwide/workdir" "--user" "0:0" "aad9ece8f5c826e1a98bbf953b32c224c70278ffed597ee0624e7d4a2c2351db" "/opt/rustwide/cargo-home/bin/cargo" "+1.100.0-beta.1" "build" "--frozen" "--message-format=json" "--release", kill_on_drop: false }`
[INFO] [stderr] warning: `package.homepage` is redundant with `package.repository`
[INFO] [stderr]    --> Cargo.toml:227:12
[INFO] [stderr]     |
[INFO] [stderr] 227 | homepage = "https://github.com/Raghava-Ch/modbus-rs"
[INFO] [stderr]     |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 232 | repository = "https://github.com/Raghava-Ch/modbus-rs"
[INFO] [stderr]     |              -----------------------------------------
[INFO] [stderr]     |
[INFO] [stderr]     = note: `cargo::redundant_homepage` is set to `warn` by default
[INFO] [stderr] help: consider removing `package.homepage`
[INFO] [stderr] warning: `modbus-rs` (manifest) generated 1 warning
[INFO] [stderr]    Compiling syn v2.0.118
[INFO] [stderr]    Compiling libc v0.2.186
[INFO] [stderr]    Compiling zerocopy v0.8.52
[INFO] [stderr]    Compiling byteorder v1.5.0
[INFO] [stderr]    Compiling bytes v1.12.0
[INFO] [stderr]    Compiling heapless v0.9.3
[INFO] [stderr]    Compiling cfg_aliases v0.2.1
[INFO] [stderr]    Compiling futures-sink v0.3.32
[INFO] [stderr]    Compiling scopeguard v1.2.0
[INFO] [stderr]    Compiling winnow v0.7.15
[INFO] [stderr]    Compiling indexmap v2.14.0
[INFO] [stderr]    Compiling toml_write v0.1.2
[INFO] [stderr]    Compiling sha1 v0.10.6
[INFO] [stderr]    Compiling nix v0.31.3
[INFO] [stderr]    Compiling hash32 v0.3.1
[INFO] [stderr]    Compiling http v1.4.2
[INFO] [stderr]    Compiling mbus-core v0.16.0
[INFO] [stderr]    Compiling mbus-client v0.16.0
[INFO] [stderr]    Compiling mio v1.2.1
[INFO] [stderr]    Compiling getrandom v0.3.4
[INFO] [stderr]    Compiling socket2 v0.6.4
[INFO] [stderr]    Compiling nix v0.26.4
[INFO] [stderr]    Compiling rand_core v0.9.5
[INFO] [stderr]    Compiling thiserror-impl v2.0.18
[INFO] [stderr]    Compiling tokio-macros v2.7.0
[INFO] [stderr]    Compiling serde_derive v1.0.228
[INFO] [stderr]    Compiling futures-macro v0.3.32
[INFO] [stderr]    Compiling mbus-macros v0.16.0
[INFO] [stderr]    Compiling ppv-lite86 v0.2.21
[INFO] [stderr]    Compiling futures-util v0.3.32
[INFO] [stderr]    Compiling tokio v1.52.3
[INFO] [stderr]    Compiling rand_chacha v0.9.0
[INFO] [stderr]    Compiling rand v0.9.4
[INFO] [stderr]    Compiling thiserror v2.0.18
[INFO] [stderr]    Compiling unescaper v0.1.10
[INFO] [stderr]    Compiling serialport v4.9.0
[INFO] [stderr]    Compiling tungstenite v0.29.0
[INFO] [stderr]    Compiling mio-serial v5.0.7
[INFO] [stderr]    Compiling serde v1.0.228
[INFO] [stderr]    Compiling serde_spanned v0.6.9
[INFO] [stderr]    Compiling toml_datetime v0.6.11
[INFO] [stderr]    Compiling toml_edit v0.22.27
[INFO] [stderr]    Compiling tokio-serial v5.5.0
[INFO] [stderr]    Compiling tokio-tungstenite v0.29.0
[INFO] [stderr]    Compiling mbus-serial v0.16.0
[INFO] [stderr]    Compiling mbus-network v0.16.0
[INFO] [stderr]    Compiling mbus-async v0.16.0
[INFO] [stderr]    Compiling mbus-gateway v0.16.0
[INFO] [stderr]    Compiling toml v0.8.23
[INFO] [stderr]    Compiling mbus-client-async v0.16.0
[INFO] [stderr]    Compiling mbus-server-async v0.16.0
[INFO] [stderr]    Compiling mbus-server v0.16.0
[INFO] [stderr]    Compiling modbus-rs v0.16.0 (/opt/rustwide/workdir)
[INFO] [stderr]     Finished `release` profile [optimized] target(s) in 30.96s
[INFO] [stderr] warning: the following packages contain code that will be rejected by a future version of Rust: nix v0.31.3
[INFO] [stderr] note: to see what the problems were, use the option `--future-incompat-report`, or run `cargo report future-incompatibilities --id 1`
[INFO] running `Command { std: "docker" "inspect" "aad9ece8f5c826e1a98bbf953b32c224c70278ffed597ee0624e7d4a2c2351db", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-w" "/opt/rustwide/workdir" "--user" "0:0" "aad9ece8f5c826e1a98bbf953b32c224c70278ffed597ee0624e7d4a2c2351db" "/opt/rustwide/cargo-home/bin/cargo" "+1.100.0-beta.1" "test" "--frozen" "--no-run" "--message-format=json" "--release", kill_on_drop: false }`
[INFO] [stderr] warning: `package.homepage` is redundant with `package.repository`
[INFO] [stderr]    --> Cargo.toml:227:12
[INFO] [stderr]     |
[INFO] [stderr] 227 | homepage = "https://github.com/Raghava-Ch/modbus-rs"
[INFO] [stderr]     |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 232 | repository = "https://github.com/Raghava-Ch/modbus-rs"
[INFO] [stderr]     |              -----------------------------------------
[INFO] [stderr]     |
[INFO] [stderr]     = note: `cargo::redundant_homepage` is set to `warn` by default
[INFO] [stderr] help: consider removing `package.homepage`
[INFO] [stderr] warning: `modbus-rs` (manifest) generated 1 warning
[INFO] [stderr]    Compiling log v0.4.33
[INFO] [stderr]    Compiling memchr v2.8.2
[INFO] [stderr]    Compiling regex-syntax v0.8.11
[INFO] [stderr]    Compiling anyhow v1.0.103
[INFO] [stderr]    Compiling jiff v0.2.31
[INFO] [stderr]    Compiling anstream v1.0.0
[INFO] [stderr]    Compiling mbus-server v0.16.0
[INFO] [stderr]    Compiling mio v1.2.1
[INFO] [stderr]    Compiling tungstenite v0.29.0
[INFO] [stderr]    Compiling tokio v1.52.3
[INFO] [stderr]    Compiling mio-serial v5.0.7
[INFO] [stderr]    Compiling aho-corasick v1.1.4
[INFO] [stderr]    Compiling regex-automata v0.4.14
[INFO] [stderr]    Compiling regex v1.12.4
[INFO] [stderr]    Compiling env_filter v2.0.0
[INFO] [stderr]    Compiling env_logger v0.11.11
[INFO] [stderr]    Compiling tokio-serial v5.5.0
[INFO] [stderr]    Compiling tokio-tungstenite v0.29.0
[INFO] [stderr]    Compiling mbus-serial v0.16.0
[INFO] [stderr]    Compiling mbus-network v0.16.0
[INFO] [stderr]    Compiling mbus-async v0.16.0
[INFO] [stderr]    Compiling mbus-gateway v0.16.0
[INFO] [stderr]    Compiling mbus-client-async v0.16.0
[INFO] [stderr]    Compiling mbus-server-async v0.16.0
[INFO] [stderr]    Compiling modbus-rs v0.16.0 (/opt/rustwide/workdir)
[INFO] [stdout] error[E0277]: `?` couldn't convert the error: `MbusError: std::error::Error` is not satisfied
[INFO] [stdout]   --> examples/client/serial-rtu/sync/backoff_jitter.rs:85:52
[INFO] [stdout]    |
[INFO] [stdout] 72 | fn main() -> Result<()> {
[INFO] [stdout]    |              ---------- required `MbusError: std::error::Error` because of this
[INFO] [stdout] ...
[INFO] [stdout] 84 |         port_path: heapless::String::<64>::from_str(port_path)
[INFO] [stdout]    |                    ------------------------------------------- this has type `Result<_, CapacityError>`
[INFO] [stdout] 85 |             .map_err(|_| MbusError::BufferTooSmall)?,
[INFO] [stdout]    |              --------------------------------------^ the trait `std::error::Error` is not implemented for `MbusError`
[INFO] [stdout]    |              |
[INFO] [stdout]    |              this has type `Result<_, MbusError>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = note: required for `anyhow::Error` to implement `From<MbusError>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `CoilState` doesn't implement `std::fmt::Display`
[INFO] [stdout]   --> examples/client/network-tcp/async/tcp.rs:44:44
[INFO] [stdout]    |
[INFO] [stdout] 44 |         println!("  input[{}] = {}", addr, discrete.value(addr).unwrap());
[INFO] [stdout]    |                                 --         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `CoilState` cannot be formatted with the default formatter
[INFO] [stdout]    |                                 |
[INFO] [stdout]    |                                 required by this formatting parameter
[INFO] [stdout]    |
[INFO] [stdout]    = help: the trait `std::fmt::Display` is not implemented for `CoilState`
[INFO] [stdout]    = note: in format strings you may be able to use `{:?}` (or `{:#?}` for pretty-print) instead
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error: `MbusError: std::error::Error` is not satisfied
[INFO] [stdout]   --> examples/client/serial-rtu/sync/backoff_jitter.rs:99:92
[INFO] [stdout]    |
[INFO] [stdout] 72 | fn main() -> Result<()> {
[INFO] [stdout]    |              ---------- required `MbusError: std::error::Error` because of this
[INFO] [stdout] ...
[INFO] [stdout] 99 |         ClientServices::<_, _, 1>::new(transport, app, ModbusConfig::Serial(serial_config))?;
[INFO] [stdout]    |         -----------------------------------------------------------------------------------^ the trait `std::error::Error` is not implemented for `MbusError`
[INFO] [stdout]    |         |
[INFO] [stdout]    |         this has type `Result<_, MbusError>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = note: required for `anyhow::Error` to implement `From<MbusError>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error: `MbusError: std::error::Error` is not satisfied
[INFO] [stdout]    --> examples/client/serial-rtu/sync/backoff_jitter.rs:100:21
[INFO] [stdout]     |
[INFO] [stdout]  72 | fn main() -> Result<()> {
[INFO] [stdout]     |              ---------- required `MbusError: std::error::Error` because of this
[INFO] [stdout] ...
[INFO] [stdout] 100 |     client.connect()?;
[INFO] [stdout]     |            ---------^ the trait `std::error::Error` is not implemented for `MbusError`
[INFO] [stdout]     |            |
[INFO] [stdout]     |            this has type `Result<_, MbusError>`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]     = note: required for `anyhow::Error` to implement `From<MbusError>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error: `MbusError: std::error::Error` is not satisfied
[INFO] [stdout]    --> examples/client/serial-rtu/sync/backoff_jitter.rs:102:47
[INFO] [stdout]     |
[INFO] [stdout]  72 | fn main() -> Result<()> {
[INFO] [stdout]     |              ---------- required `MbusError: std::error::Error` because of this
[INFO] [stdout] ...
[INFO] [stdout] 102 |     let unit = UnitIdOrSlaveAddr::new(unit_id)?;
[INFO] [stdout]     |                -------------------------------^ the trait `std::error::Error` is not implemented for `MbusError`
[INFO] [stdout]     |                |
[INFO] [stdout]     |                this has type `Result<_, MbusError>`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]     = note: required for `anyhow::Error` to implement `From<MbusError>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `ObjectId` doesn't implement `std::fmt::Display`
[INFO] [stdout]   --> examples/client/network-tcp/sync/device_id.rs:33:42
[INFO] [stdout]    |
[INFO] [stdout] 33 |         println!("  Next Object ID: {}", response.next_object_id);
[INFO] [stdout]    |                                     --   ^^^^^^^^^^^^^^^^^^^^^^^ `ObjectId` cannot be formatted with the default formatter
[INFO] [stdout]    |                                     |
[INFO] [stdout]    |                                     required by this formatting parameter
[INFO] [stdout]    |
[INFO] [stdout]    = help: the trait `std::fmt::Display` is not implemented for `ObjectId`
[INFO] [stdout]    = note: in format strings you may be able to use `{:?}` (or `{:#?}` for pretty-print) instead
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `ObjectId` doesn't implement `std::fmt::Display`
[INFO] [stdout]   --> examples/client/network-tcp/sync/device_id.rs:45:46
[INFO] [stdout]    |
[INFO] [stdout] 45 |                     println!("    - {}: {}", obj.object_id, value_str);
[INFO] [stdout]    |                                     --       ^^^^^^^^^^^^^ `ObjectId` cannot be formatted with the default formatter
[INFO] [stdout]    |                                     |
[INFO] [stdout]    |                                     required by this formatting parameter
[INFO] [stdout]    |
[INFO] [stdout]    = help: the trait `std::fmt::Display` is not implemented for `ObjectId`
[INFO] [stdout]    = note: in format strings you may be able to use `{:?}` (or `{:#?}` for pretty-print) instead
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0432]: unresolved import `modbus_rs::StdAsciiTransport`
[INFO] [stdout]   --> examples/client/serial-ascii/sync/coils.rs:7:5
[INFO] [stdout]    |
[INFO] [stdout]  7 |     StdAsciiTransport, TimeKeeper, UnitIdOrSlaveAddr,
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^^ no `StdAsciiTransport` in the root
[INFO] [stdout]    |
[INFO] [stdout] note: found an item that was configured out
[INFO] [stdout]   --> src/lib.rs:27:22
[INFO] [stdout]    |
[INFO] [stdout] 26 | #[cfg(feature = "serial-ascii")]
[INFO] [stdout]    |       ------------------------ the item is gated behind the `serial-ascii` feature
[INFO] [stdout] 27 | pub use mbus_serial::StdAsciiTransport;
[INFO] [stdout]    |                      ^^^^^^^^^^^^^^^^^
[INFO] [stdout] help: a similar name exists in the module
[INFO] [stdout]    |
[INFO] [stdout]  7 -     StdAsciiTransport, TimeKeeper, UnitIdOrSlaveAddr,
[INFO] [stdout]  7 +     StdTcpTransport, TimeKeeper, UnitIdOrSlaveAddr,
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error: `MbusError: std::error::Error` is not satisfied
[INFO] [stdout]    --> examples/client/serial-rtu/sync/backoff_jitter.rs:103:54
[INFO] [stdout]     |
[INFO] [stdout]  72 | fn main() -> Result<()> {
[INFO] [stdout]     |              ---------- required `MbusError: std::error::Error` because of this
[INFO] [stdout] ...
[INFO] [stdout] 103 |     client.coils().read_multiple_coils(1, unit, 0, 8)?;
[INFO] [stdout]     |                    ----------------------------------^ the trait `std::error::Error` is not implemented for `MbusError`
[INFO] [stdout]     |                    |
[INFO] [stdout]     |                    this has type `Result<_, MbusError>`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]     = note: required for `anyhow::Error` to implement `From<MbusError>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `ObjectId` doesn't implement `std::fmt::Display`
[INFO] [stdout]   --> examples/client/serial-rtu/sync/device_id.rs:32:42
[INFO] [stdout]    |
[INFO] [stdout] 32 |         println!("  Next Object ID: {}", response.next_object_id);
[INFO] [stdout]    |                                     --   ^^^^^^^^^^^^^^^^^^^^^^^ `ObjectId` cannot be formatted with the default formatter
[INFO] [stdout]    |                                     |
[INFO] [stdout]    |                                     required by this formatting parameter
[INFO] [stdout]    |
[INFO] [stdout]    = help: the trait `std::fmt::Display` is not implemented for `ObjectId`
[INFO] [stdout]    = note: in format strings you may be able to use `{:?}` (or `{:#?}` for pretty-print) instead
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `CoilState` doesn't implement `std::fmt::Display`
[INFO] [stdout]   --> examples/client/serial-rtu/async/rtu.rs:48:43
[INFO] [stdout]    |
[INFO] [stdout] 48 |         println!("  coil[{}] = {}", addr, coils.value(addr)?);
[INFO] [stdout]    |                                --         ^^^^^^^^^^^^^^^^^^ `CoilState` cannot be formatted with the default formatter
[INFO] [stdout]    |                                |
[INFO] [stdout]    |                                required by this formatting parameter
[INFO] [stdout]    |
[INFO] [stdout]    = help: the trait `std::fmt::Display` is not implemented for `CoilState`
[INFO] [stdout]    = note: in format strings you may be able to use `{:?}` (or `{:#?}` for pretty-print) instead
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `CoilState` doesn't implement `std::fmt::Display`
[INFO] [stdout]   --> examples/client/serial-rtu/sync/coils.rs:31:60
[INFO] [stdout]    |
[INFO] [stdout] 31 |                 Ok(val) => println!("  Coil {}: {}", addr, val),
[INFO] [stdout]    |                                                 --         ^^^ `CoilState` cannot be formatted with the default formatter
[INFO] [stdout]    |                                                 |
[INFO] [stdout]    |                                                 required by this formatting parameter
[INFO] [stdout]    |
[INFO] [stdout]    = help: the trait `std::fmt::Display` is not implemented for `CoilState`
[INFO] [stdout]    = note: in format strings you may be able to use `{:?}` (or `{:#?}` for pretty-print) instead
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `CoilState` doesn't implement `std::fmt::Display`
[INFO] [stdout]   --> examples/client/serial-rtu/sync/coils.rs:63:13
[INFO] [stdout]    |
[INFO] [stdout] 59 |             "Response [Txn: {}, Unit: {}]: Write Single Coil (Addr: {}, Value: {}) Success",
[INFO] [stdout]    |                                                                                -- required by this formatting parameter
[INFO] [stdout] ...
[INFO] [stdout] 63 |             value
[INFO] [stdout]    |             ^^^^^ `CoilState` cannot be formatted with the default formatter
[INFO] [stdout]    |
[INFO] [stdout]    = help: the trait `std::fmt::Display` is not implemented for `CoilState`
[INFO] [stdout]    = note: in format strings you may be able to use `{:?}` (or `{:#?}` for pretty-print) instead
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `ObjectId` doesn't implement `std::fmt::Display`
[INFO] [stdout]   --> examples/client/serial-rtu/sync/device_id.rs:41:46
[INFO] [stdout]    |
[INFO] [stdout] 41 |                     println!("    - {}: {}", obj.object_id, value_str);
[INFO] [stdout]    |                                     --       ^^^^^^^^^^^^^ `ObjectId` cannot be formatted with the default formatter
[INFO] [stdout]    |                                     |
[INFO] [stdout]    |                                     required by this formatting parameter
[INFO] [stdout]    |
[INFO] [stdout]    = help: the trait `std::fmt::Display` is not implemented for `ObjectId`
[INFO] [stdout]    = note: in format strings you may be able to use `{:?}` (or `{:#?}` for pretty-print) instead
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error: `MbusError: std::error::Error` is not satisfied
[INFO] [stdout]   --> examples/client/serial-rtu/async/rtu.rs:48:60
[INFO] [stdout]    |
[INFO] [stdout] 48 |         println!("  coil[{}] = {}", addr, coils.value(addr)?);
[INFO] [stdout]    |                                                 -----------^ the trait `std::error::Error` is not implemented for `MbusError`
[INFO] [stdout]    |                                                 |
[INFO] [stdout]    |                                                 this has type `Result<_, MbusError>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = note: required for `anyhow::Error` to implement `From<MbusError>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error: `MbusError: std::error::Error` is not satisfied
[INFO] [stdout]   --> examples/client/network-tcp/sync/logging.rs:15:83
[INFO] [stdout]    |
[INFO] [stdout]  4 | fn main() -> Result<()> {
[INFO] [stdout]    |              ---------- required `MbusError: std::error::Error` because of this
[INFO] [stdout] ...
[INFO] [stdout] 15 |     let config = ModbusConfig::Tcp(ModbusTcpConfig::new("invalid-host.local", 502)?);
[INFO] [stdout]    |                                    -----------------------------------------------^ the trait `std::error::Error` is not implemented for `MbusError`
[INFO] [stdout]    |                                    |
[INFO] [stdout]    |                                    this has type `Result<_, MbusError>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = note: required for `anyhow::Error` to implement `From<MbusError>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0277`.
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `TransportError` doesn't implement `std::fmt::Display`
[INFO] [stdout]   --> examples/client/network-tcp/sync/logging.rs:23:61
[INFO] [stdout]    |
[INFO] [stdout] 23 |             println!("Connection failed (expected in demo): {err}");
[INFO] [stdout]    |                                                             ^^^^^ `TransportError` cannot be formatted with the default formatter
[INFO] [stdout]    |
[INFO] [stdout]    = help: the trait `std::fmt::Display` is not implemented for `TransportError`
[INFO] [stdout]    = note: in format strings you may be able to use `{:?}` (or `{:#?}` for pretty-print) instead
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `CoilState` doesn't implement `std::fmt::Display`
[INFO] [stdout]   --> examples/client/serial-ascii/sync/coils.rs:30:60
[INFO] [stdout]    |
[INFO] [stdout] 30 |                 Ok(val) => println!("  Coil {}: {}", addr, val),
[INFO] [stdout]    |                                                 --         ^^^ `CoilState` cannot be formatted with the default formatter
[INFO] [stdout]    |                                                 |
[INFO] [stdout]    |                                                 required by this formatting parameter
[INFO] [stdout]    |
[INFO] [stdout]    = help: the trait `std::fmt::Display` is not implemented for `CoilState`
[INFO] [stdout]    = note: in format strings you may be able to use `{:?}` (or `{:#?}` for pretty-print) instead
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error: `MbusError: std::error::Error` is not satisfied
[INFO] [stdout]   --> examples/client/network-tcp/sync/backoff_jitter.rs:83:58
[INFO] [stdout]    |
[INFO] [stdout] 71 | fn main() -> Result<()> {
[INFO] [stdout]    |              ---------- required `MbusError: std::error::Error` because of this
[INFO] [stdout] ...
[INFO] [stdout] 83 |     let mut tcp_config = ModbusTcpConfig::new(host, port)?;
[INFO] [stdout]    |                          --------------------------------^ the trait `std::error::Error` is not implemented for `MbusError`
[INFO] [stdout]    |                          |
[INFO] [stdout]    |                          this has type `Result<_, MbusError>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = note: required for `anyhow::Error` to implement `From<MbusError>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `modbus-rs` (example "modbus_rs_client_async_serial_rtu") due to 2 previous errors
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stdout] For more information about this error, try `rustc --explain E0277`.
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0277`.
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error: `MbusError: std::error::Error` is not satisfied
[INFO] [stdout]   --> examples/client/network-tcp/sync/backoff_jitter.rs:94:99
[INFO] [stdout]    |
[INFO] [stdout] 71 | fn main() -> Result<()> {
[INFO] [stdout]    |              ---------- required `MbusError: std::error::Error` because of this
[INFO] [stdout] ...
[INFO] [stdout] 94 |     let mut client = ClientServices::<_, _, 8>::new(transport, app, ModbusConfig::Tcp(tcp_config))?;
[INFO] [stdout]    |                      -----------------------------------------------------------------------------^ the trait `std::error::Error` is not implemented for `MbusError`
[INFO] [stdout]    |                      |
[INFO] [stdout]    |                      this has type `Result<_, MbusError>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = note: required for `anyhow::Error` to implement `From<MbusError>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error: `MbusError: std::error::Error` is not satisfied
[INFO] [stdout]   --> examples/client/network-tcp/async/tcp.rs:78:30
[INFO] [stdout]    |
[INFO] [stdout] 78 |         verify_coils.value(0)?,
[INFO] [stdout]    |                      --------^ the trait `std::error::Error` is not implemented for `MbusError`
[INFO] [stdout]    |                      |
[INFO] [stdout]    |                      this has type `Result<_, MbusError>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = note: required for `anyhow::Error` to implement `From<MbusError>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error: `MbusError: std::error::Error` is not satisfied
[INFO] [stdout]   --> examples/client/network-tcp/sync/backoff_jitter.rs:95:21
[INFO] [stdout]    |
[INFO] [stdout] 71 | fn main() -> Result<()> {
[INFO] [stdout]    |              ---------- required `MbusError: std::error::Error` because of this
[INFO] [stdout] ...
[INFO] [stdout] 95 |     client.connect()?;
[INFO] [stdout]    |            ---------^ the trait `std::error::Error` is not implemented for `MbusError`
[INFO] [stdout]    |            |
[INFO] [stdout]    |            this has type `Result<_, MbusError>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = note: required for `anyhow::Error` to implement `From<MbusError>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error: `MbusError: std::error::Error` is not satisfied
[INFO] [stdout]   --> examples/client/network-tcp/sync/backoff_jitter.rs:97:47
[INFO] [stdout]    |
[INFO] [stdout] 71 | fn main() -> Result<()> {
[INFO] [stdout]    |              ---------- required `MbusError: std::error::Error` because of this
[INFO] [stdout] ...
[INFO] [stdout] 97 |     let unit = UnitIdOrSlaveAddr::new(unit_id)?;
[INFO] [stdout]    |                -------------------------------^ the trait `std::error::Error` is not implemented for `MbusError`
[INFO] [stdout]    |                |
[INFO] [stdout]    |                this has type `Result<_, MbusError>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = note: required for `anyhow::Error` to implement `From<MbusError>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `modbus-rs` (example "modbus_rs_client_tcp_logging") due to 2 previous errors
[INFO] [stderr] error: could not compile `modbus-rs` (example "modbus_rs_client_serial_rtu_backoff_jitter") due to 5 previous errors
[INFO] [stdout] error[E0277]: `?` couldn't convert the error: `MbusError: std::error::Error` is not satisfied
[INFO] [stdout]   --> examples/client/network-tcp/sync/backoff_jitter.rs:98:54
[INFO] [stdout]    |
[INFO] [stdout] 71 | fn main() -> Result<()> {
[INFO] [stdout]    |              ---------- required `MbusError: std::error::Error` because of this
[INFO] [stdout] ...
[INFO] [stdout] 98 |     client.coils().read_multiple_coils(1, unit, 0, 8)?;
[INFO] [stdout]    |                    ----------------------------------^ the trait `std::error::Error` is not implemented for `MbusError`
[INFO] [stdout]    |                    |
[INFO] [stdout]    |                    this has type `Result<_, MbusError>`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]    = note: required for `anyhow::Error` to implement `From<MbusError>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0277`.
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: the method `anyhow_kind` exists for reference `&MbusError`, but its trait bounds were not satisfied
[INFO] [stdout]    --> examples/client/network-tcp/sync/device_id.rs:153:71
[INFO] [stdout]     |
[INFO] [stdout] 153 |     let mut tcp_config = ModbusTcpConfig::new(host, port).map_err(|e| anyhow::anyhow!(e))?;
[INFO] [stdout]     |                                                                       ^^^^^^^^^^^^^^^^^^ method cannot be called on `&MbusError` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/mbus-core-0.16.0/src/errors/mod.rs:45:1
[INFO] [stdout]     |
[INFO] [stdout]  45 | pub enum MbusError {
[INFO] [stdout]     | ------------------ doesn't satisfy `MbusError: Into<anyhow::Error>`, `MbusError: anyhow::__private::kind::TraitKind` or `MbusError: std::fmt::Display`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]             `MbusError: std::fmt::Display`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::AdhocKind`
[INFO] [stdout]             `&MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]     = note: this error originates in the macro `anyhow::anyhow` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0277`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `modbus-rs` (example "modbus_rs_client_async_tcp") due to 2 previous errors
[INFO] [stdout] error[E0599]: the method `anyhow_kind` exists for reference `&MbusError`, but its trait bounds were not satisfied
[INFO] [stdout]    --> examples/client/serial-rtu/sync/device_id.rs:136:76
[INFO] [stdout]     |
[INFO] [stdout] 136 |         ClientServices::<_, _, 1>::new(transport, app, config).map_err(|e| anyhow::anyhow!(e))?;
[INFO] [stdout]     |                                                                            ^^^^^^^^^^^^^^^^^^ method cannot be called on `&MbusError` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/mbus-core-0.16.0/src/errors/mod.rs:45:1
[INFO] [stdout]     |
[INFO] [stdout]  45 | pub enum MbusError {
[INFO] [stdout]     | ------------------ doesn't satisfy `MbusError: Into<anyhow::Error>`, `MbusError: anyhow::__private::kind::TraitKind` or `MbusError: std::fmt::Display`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]             `MbusError: std::fmt::Display`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::AdhocKind`
[INFO] [stdout]             `&MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]     = note: this error originates in the macro `anyhow::anyhow` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: the method `anyhow_kind` exists for reference `&MbusError`, but its trait bounds were not satisfied
[INFO] [stdout]    --> examples/client/network-tcp/sync/device_id.rs:160:77
[INFO] [stdout]     |
[INFO] [stdout] 160 |         ClientServices::<_, _, 10>::new(transport, app, config).map_err(|e| anyhow::anyhow!(e))?;
[INFO] [stdout]     |                                                                             ^^^^^^^^^^^^^^^^^^ method cannot be called on `&MbusError` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/mbus-core-0.16.0/src/errors/mod.rs:45:1
[INFO] [stdout]     |
[INFO] [stdout]  45 | pub enum MbusError {
[INFO] [stdout]     | ------------------ doesn't satisfy `MbusError: Into<anyhow::Error>`, `MbusError: anyhow::__private::kind::TraitKind` or `MbusError: std::fmt::Display`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]             `MbusError: std::fmt::Display`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::AdhocKind`
[INFO] [stdout]             `&MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]     = note: this error originates in the macro `anyhow::anyhow` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: the method `anyhow_kind` exists for reference `&MbusError`, but its trait bounds were not satisfied
[INFO] [stdout]    --> examples/client/serial-rtu/sync/coils.rs:140:76
[INFO] [stdout]     |
[INFO] [stdout] 140 |         ClientServices::<_, _, 1>::new(transport, app, config).map_err(|e| anyhow::anyhow!(e))?;
[INFO] [stdout]     |                                                                            ^^^^^^^^^^^^^^^^^^ method cannot be called on `&MbusError` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/mbus-core-0.16.0/src/errors/mod.rs:45:1
[INFO] [stdout]     |
[INFO] [stdout]  45 | pub enum MbusError {
[INFO] [stdout]     | ------------------ doesn't satisfy `MbusError: Into<anyhow::Error>`, `MbusError: anyhow::__private::kind::TraitKind` or `MbusError: std::fmt::Display`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]             `MbusError: std::fmt::Display`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::AdhocKind`
[INFO] [stdout]             `&MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]     = note: this error originates in the macro `anyhow::anyhow` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: the method `anyhow_kind` exists for reference `&MbusError`, but its trait bounds were not satisfied
[INFO] [stdout]    --> examples/client/serial-rtu/sync/device_id.rs:137:34
[INFO] [stdout]     |
[INFO] [stdout] 137 |     client.connect().map_err(|e| anyhow::anyhow!(e))?;
[INFO] [stdout]     |                                  ^^^^^^^^^^^^^^^^^^ method cannot be called on `&MbusError` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/mbus-core-0.16.0/src/errors/mod.rs:45:1
[INFO] [stdout]     |
[INFO] [stdout]  45 | pub enum MbusError {
[INFO] [stdout]     | ------------------ doesn't satisfy `MbusError: Into<anyhow::Error>`, `MbusError: anyhow::__private::kind::TraitKind` or `MbusError: std::fmt::Display`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]             `MbusError: std::fmt::Display`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::AdhocKind`
[INFO] [stdout]             `&MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]     = note: this error originates in the macro `anyhow::anyhow` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: the method `anyhow_kind` exists for reference `&MbusError`, but its trait bounds were not satisfied
[INFO] [stdout]    --> examples/client/network-tcp/sync/device_id.rs:161:34
[INFO] [stdout]     |
[INFO] [stdout] 161 |     client.connect().map_err(|e| anyhow::anyhow!(e))?;
[INFO] [stdout]     |                                  ^^^^^^^^^^^^^^^^^^ method cannot be called on `&MbusError` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/mbus-core-0.16.0/src/errors/mod.rs:45:1
[INFO] [stdout]     |
[INFO] [stdout]  45 | pub enum MbusError {
[INFO] [stdout]     | ------------------ doesn't satisfy `MbusError: Into<anyhow::Error>`, `MbusError: anyhow::__private::kind::TraitKind` or `MbusError: std::fmt::Display`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]             `MbusError: std::fmt::Display`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::AdhocKind`
[INFO] [stdout]             `&MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]     = note: this error originates in the macro `anyhow::anyhow` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `modbus-rs` (example "modbus_rs_client_tcp_backoff_jitter") due to 5 previous errors
[INFO] [stdout] error[E0599]: the method `anyhow_kind` exists for reference `&MbusError`, but its trait bounds were not satisfied
[INFO] [stdout]    --> examples/client/serial-rtu/sync/device_id.rs:151:22
[INFO] [stdout]     |
[INFO] [stdout] 151 |         .map_err(|e| anyhow::anyhow!(e))?;
[INFO] [stdout]     |                      ^^^^^^^^^^^^^^^^^^ method cannot be called on `&MbusError` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/mbus-core-0.16.0/src/errors/mod.rs:45:1
[INFO] [stdout]     |
[INFO] [stdout]  45 | pub enum MbusError {
[INFO] [stdout]     | ------------------ doesn't satisfy `MbusError: Into<anyhow::Error>`, `MbusError: anyhow::__private::kind::TraitKind` or `MbusError: std::fmt::Display`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]             `MbusError: std::fmt::Display`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::AdhocKind`
[INFO] [stdout]             `&MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]     = note: this error originates in the macro `anyhow::anyhow` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: the method `anyhow_kind` exists for reference `&MbusError`, but its trait bounds were not satisfied
[INFO] [stdout]    --> examples/client/serial-rtu/sync/coils.rs:141:34
[INFO] [stdout]     |
[INFO] [stdout] 141 |     client.connect().map_err(|e| anyhow::anyhow!(e))?;
[INFO] [stdout]     |                                  ^^^^^^^^^^^^^^^^^^ method cannot be called on `&MbusError` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/mbus-core-0.16.0/src/errors/mod.rs:45:1
[INFO] [stdout]     |
[INFO] [stdout]  45 | pub enum MbusError {
[INFO] [stdout]     | ------------------ doesn't satisfy `MbusError: Into<anyhow::Error>`, `MbusError: anyhow::__private::kind::TraitKind` or `MbusError: std::fmt::Display`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]             `MbusError: std::fmt::Display`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::AdhocKind`
[INFO] [stdout]             `&MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]     = note: this error originates in the macro `anyhow::anyhow` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: the method `anyhow_kind` exists for reference `&MbusError`, but its trait bounds were not satisfied
[INFO] [stdout]    --> examples/client/serial-rtu/sync/discrete_inputs.rs:115:76
[INFO] [stdout]     |
[INFO] [stdout] 115 |         ClientServices::<_, _, 1>::new(transport, app, config).map_err(|e| anyhow::anyhow!(e))?;
[INFO] [stdout]     |                                                                            ^^^^^^^^^^^^^^^^^^ method cannot be called on `&MbusError` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/mbus-core-0.16.0/src/errors/mod.rs:45:1
[INFO] [stdout]     |
[INFO] [stdout]  45 | pub enum MbusError {
[INFO] [stdout]     | ------------------ doesn't satisfy `MbusError: Into<anyhow::Error>`, `MbusError: anyhow::__private::kind::TraitKind` or `MbusError: std::fmt::Display`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]             `MbusError: std::fmt::Display`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::AdhocKind`
[INFO] [stdout]             `&MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]     = note: this error originates in the macro `anyhow::anyhow` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: the method `anyhow_kind` exists for reference `&MbusError`, but its trait bounds were not satisfied
[INFO] [stdout]    --> examples/client/network-tcp/sync/device_id.rs:171:22
[INFO] [stdout]     |
[INFO] [stdout] 171 |         .map_err(|e| anyhow::anyhow!(e))?;
[INFO] [stdout]     |                      ^^^^^^^^^^^^^^^^^^ method cannot be called on `&MbusError` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/mbus-core-0.16.0/src/errors/mod.rs:45:1
[INFO] [stdout]     |
[INFO] [stdout]  45 | pub enum MbusError {
[INFO] [stdout]     | ------------------ doesn't satisfy `MbusError: Into<anyhow::Error>`, `MbusError: anyhow::__private::kind::TraitKind` or `MbusError: std::fmt::Display`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]             `MbusError: std::fmt::Display`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::AdhocKind`
[INFO] [stdout]             `&MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]     = note: this error originates in the macro `anyhow::anyhow` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0277, E0432.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0277`.
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0277, E0599.
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: the method `anyhow_kind` exists for reference `&MbusError`, but its trait bounds were not satisfied
[INFO] [stdout]    --> examples/client/network-tcp/sync/device_id.rs:182:22
[INFO] [stdout]     |
[INFO] [stdout] 182 |         .map_err(|e| anyhow::anyhow!(e))?;
[INFO] [stdout]     |                      ^^^^^^^^^^^^^^^^^^ method cannot be called on `&MbusError` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/mbus-core-0.16.0/src/errors/mod.rs:45:1
[INFO] [stdout]     |
[INFO] [stdout]  45 | pub enum MbusError {
[INFO] [stdout]     | ------------------ doesn't satisfy `MbusError: Into<anyhow::Error>`, `MbusError: anyhow::__private::kind::TraitKind` or `MbusError: std::fmt::Display`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]             `MbusError: std::fmt::Display`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::AdhocKind`
[INFO] [stdout]             `&MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]     = note: this error originates in the macro `anyhow::anyhow` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0277`.
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: the method `anyhow_kind` exists for reference `&MbusError`, but its trait bounds were not satisfied
[INFO] [stdout]    --> examples/client/serial-rtu/sync/discrete_inputs.rs:116:34
[INFO] [stdout]     |
[INFO] [stdout] 116 |     client.connect().map_err(|e| anyhow::anyhow!(e))?;
[INFO] [stdout]     |                                  ^^^^^^^^^^^^^^^^^^ method cannot be called on `&MbusError` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/mbus-core-0.16.0/src/errors/mod.rs:45:1
[INFO] [stdout]     |
[INFO] [stdout]  45 | pub enum MbusError {
[INFO] [stdout]     | ------------------ doesn't satisfy `MbusError: Into<anyhow::Error>`, `MbusError: anyhow::__private::kind::TraitKind` or `MbusError: std::fmt::Display`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]             `MbusError: std::fmt::Display`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::AdhocKind`
[INFO] [stdout]             `&MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]     = note: this error originates in the macro `anyhow::anyhow` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `modbus-rs` (example "modbus_rs_client_serial_ascii_coils") due to 2 previous errors
[INFO] [stdout] error[E0599]: the method `anyhow_kind` exists for reference `&MbusError`, but its trait bounds were not satisfied
[INFO] [stdout]    --> examples/client/serial-rtu/sync/coils.rs:155:22
[INFO] [stdout]     |
[INFO] [stdout] 155 |         .map_err(|e| anyhow::anyhow!(e))?;
[INFO] [stdout]     |                      ^^^^^^^^^^^^^^^^^^ method cannot be called on `&MbusError` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/mbus-core-0.16.0/src/errors/mod.rs:45:1
[INFO] [stdout]     |
[INFO] [stdout]  45 | pub enum MbusError {
[INFO] [stdout]     | ------------------ doesn't satisfy `MbusError: Into<anyhow::Error>`, `MbusError: anyhow::__private::kind::TraitKind` or `MbusError: std::fmt::Display`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]             `MbusError: std::fmt::Display`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::AdhocKind`
[INFO] [stdout]             `&MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]     = note: this error originates in the macro `anyhow::anyhow` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: the method `anyhow_kind` exists for reference `&MbusError`, but its trait bounds were not satisfied
[INFO] [stdout]    --> examples/client/network-tcp/sync/device_id.rs:193:22
[INFO] [stdout]     |
[INFO] [stdout] 193 |         .map_err(|e| anyhow::anyhow!(e))?;
[INFO] [stdout]     |                      ^^^^^^^^^^^^^^^^^^ method cannot be called on `&MbusError` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/mbus-core-0.16.0/src/errors/mod.rs:45:1
[INFO] [stdout]     |
[INFO] [stdout]  45 | pub enum MbusError {
[INFO] [stdout]     | ------------------ doesn't satisfy `MbusError: Into<anyhow::Error>`, `MbusError: anyhow::__private::kind::TraitKind` or `MbusError: std::fmt::Display`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]             `MbusError: std::fmt::Display`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::AdhocKind`
[INFO] [stdout]             `&MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]     = note: this error originates in the macro `anyhow::anyhow` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: the method `anyhow_kind` exists for reference `&MbusError`, but its trait bounds were not satisfied
[INFO] [stdout]   --> examples/client/network-tcp/sync/discrete_inputs.rs:97:71
[INFO] [stdout]    |
[INFO] [stdout] 97 |     let mut tcp_config = ModbusTcpConfig::new(host, port).map_err(|e| anyhow::anyhow!(e))?;
[INFO] [stdout]    |                                                                       ^^^^^^^^^^^^^^^^^^ method cannot be called on `&MbusError` due to unsatisfied trait bounds
[INFO] [stdout]    |
[INFO] [stdout]   ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/mbus-core-0.16.0/src/errors/mod.rs:45:1
[INFO] [stdout]    |
[INFO] [stdout] 45 | pub enum MbusError {
[INFO] [stdout]    | ------------------ doesn't satisfy `MbusError: Into<anyhow::Error>`, `MbusError: anyhow::__private::kind::TraitKind` or `MbusError: std::fmt::Display`
[INFO] [stdout]    |
[INFO] [stdout]    = note: the following trait bounds were not satisfied:
[INFO] [stdout]            `MbusError: Into<anyhow::Error>`
[INFO] [stdout]            which is required by `MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]            `MbusError: std::fmt::Display`
[INFO] [stdout]            which is required by `&MbusError: anyhow::__private::kind::AdhocKind`
[INFO] [stdout]            `&MbusError: Into<anyhow::Error>`
[INFO] [stdout]            which is required by `&MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]    = note: this error originates in the macro `anyhow::anyhow` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `modbus-rs` (example "modbus_rs_client_serial_rtu_device_id") due to 5 previous errors
[INFO] [stdout] error[E0599]: the method `anyhow_kind` exists for reference `&MbusError`, but its trait bounds were not satisfied
[INFO] [stdout]    --> examples/client/serial-rtu/sync/coils.rs:165:22
[INFO] [stdout]     |
[INFO] [stdout] 165 |         .map_err(|e| anyhow::anyhow!(e))?;
[INFO] [stdout]     |                      ^^^^^^^^^^^^^^^^^^ method cannot be called on `&MbusError` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/mbus-core-0.16.0/src/errors/mod.rs:45:1
[INFO] [stdout]     |
[INFO] [stdout]  45 | pub enum MbusError {
[INFO] [stdout]     | ------------------ doesn't satisfy `MbusError: Into<anyhow::Error>`, `MbusError: anyhow::__private::kind::TraitKind` or `MbusError: std::fmt::Display`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]             `MbusError: std::fmt::Display`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::AdhocKind`
[INFO] [stdout]             `&MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]     = note: this error originates in the macro `anyhow::anyhow` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: the method `anyhow_kind` exists for reference `&MbusError`, but its trait bounds were not satisfied
[INFO] [stdout]    --> examples/client/network-tcp/sync/device_id.rs:204:22
[INFO] [stdout]     |
[INFO] [stdout] 204 |         .map_err(|e| anyhow::anyhow!(e))?;
[INFO] [stdout]     |                      ^^^^^^^^^^^^^^^^^^ method cannot be called on `&MbusError` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/mbus-core-0.16.0/src/errors/mod.rs:45:1
[INFO] [stdout]     |
[INFO] [stdout]  45 | pub enum MbusError {
[INFO] [stdout]     | ------------------ doesn't satisfy `MbusError: Into<anyhow::Error>`, `MbusError: anyhow::__private::kind::TraitKind` or `MbusError: std::fmt::Display`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]             `MbusError: std::fmt::Display`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::AdhocKind`
[INFO] [stdout]             `&MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]     = note: this error originates in the macro `anyhow::anyhow` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: the method `anyhow_kind` exists for reference `&MbusError`, but its trait bounds were not satisfied
[INFO] [stdout]    --> examples/client/serial-rtu/sync/discrete_inputs.rs:125:22
[INFO] [stdout]     |
[INFO] [stdout] 125 |         .map_err(|e| anyhow::anyhow!(e))?;
[INFO] [stdout]     |                      ^^^^^^^^^^^^^^^^^^ method cannot be called on `&MbusError` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/mbus-core-0.16.0/src/errors/mod.rs:45:1
[INFO] [stdout]     |
[INFO] [stdout]  45 | pub enum MbusError {
[INFO] [stdout]     | ------------------ doesn't satisfy `MbusError: Into<anyhow::Error>`, `MbusError: anyhow::__private::kind::TraitKind` or `MbusError: std::fmt::Display`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]             `MbusError: std::fmt::Display`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::AdhocKind`
[INFO] [stdout]             `&MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]     = note: this error originates in the macro `anyhow::anyhow` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: the method `anyhow_kind` exists for reference `&MbusError`, but its trait bounds were not satisfied
[INFO] [stdout]    --> examples/client/serial-rtu/sync/coils.rs:187:22
[INFO] [stdout]     |
[INFO] [stdout] 187 |         .map_err(|e| anyhow::anyhow!(e))?;
[INFO] [stdout]     |                      ^^^^^^^^^^^^^^^^^^ method cannot be called on `&MbusError` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/mbus-core-0.16.0/src/errors/mod.rs:45:1
[INFO] [stdout]     |
[INFO] [stdout]  45 | pub enum MbusError {
[INFO] [stdout]     | ------------------ doesn't satisfy `MbusError: Into<anyhow::Error>`, `MbusError: anyhow::__private::kind::TraitKind` or `MbusError: std::fmt::Display`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]             `MbusError: std::fmt::Display`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::AdhocKind`
[INFO] [stdout]             `&MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]     = note: this error originates in the macro `anyhow::anyhow` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: the method `anyhow_kind` exists for reference `&MbusError`, but its trait bounds were not satisfied
[INFO] [stdout]    --> examples/client/network-tcp/sync/discrete_inputs.rs:103:77
[INFO] [stdout]     |
[INFO] [stdout] 103 |         ClientServices::<_, _, 10>::new(transport, app, config).map_err(|e| anyhow::anyhow!(e))?;
[INFO] [stdout]     |                                                                             ^^^^^^^^^^^^^^^^^^ method cannot be called on `&MbusError` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/mbus-core-0.16.0/src/errors/mod.rs:45:1
[INFO] [stdout]     |
[INFO] [stdout]  45 | pub enum MbusError {
[INFO] [stdout]     | ------------------ doesn't satisfy `MbusError: Into<anyhow::Error>`, `MbusError: anyhow::__private::kind::TraitKind` or `MbusError: std::fmt::Display`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]             `MbusError: std::fmt::Display`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::AdhocKind`
[INFO] [stdout]             `&MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]     = note: this error originates in the macro `anyhow::anyhow` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `MbusError` doesn't implement `std::fmt::Display`
[INFO] [stdout]   --> examples/client/network-tcp/sync/coils.rs:79:13
[INFO] [stdout]    |
[INFO] [stdout] 76 |             "Client: Request failed - txn_id: {}, unit_id: {}, error: {}",
[INFO] [stdout]    |                                                                       -- required by this formatting parameter
[INFO] [stdout] ...
[INFO] [stdout] 79 |             error
[INFO] [stdout]    |             ^^^^^ `MbusError` cannot be formatted with the default formatter
[INFO] [stdout]    |
[INFO] [stdout]    = help: the trait `std::fmt::Display` is not implemented for `MbusError`
[INFO] [stdout]    = note: in format strings you may be able to use `{:?}` (or `{:#?}` for pretty-print) instead
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0277, E0599.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0277`.
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0599`.
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: the method `anyhow_kind` exists for reference `&MbusError`, but its trait bounds were not satisfied
[INFO] [stdout]    --> examples/client/network-tcp/sync/discrete_inputs.rs:104:34
[INFO] [stdout]     |
[INFO] [stdout] 104 |     client.connect().map_err(|e| anyhow::anyhow!(e))?;
[INFO] [stdout]     |                                  ^^^^^^^^^^^^^^^^^^ method cannot be called on `&MbusError` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/mbus-core-0.16.0/src/errors/mod.rs:45:1
[INFO] [stdout]     |
[INFO] [stdout]  45 | pub enum MbusError {
[INFO] [stdout]     | ------------------ doesn't satisfy `MbusError: Into<anyhow::Error>`, `MbusError: anyhow::__private::kind::TraitKind` or `MbusError: std::fmt::Display`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]             `MbusError: std::fmt::Display`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::AdhocKind`
[INFO] [stdout]             `&MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]     = note: this error originates in the macro `anyhow::anyhow` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0277, E0599.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0277`.
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: the method `anyhow_kind` exists for reference `&MbusError`, but its trait bounds were not satisfied
[INFO] [stdout]    --> examples/client/network-tcp/sync/discrete_inputs.rs:113:22
[INFO] [stdout]     |
[INFO] [stdout] 113 |         .map_err(|e| anyhow::anyhow!(e))?;
[INFO] [stdout]     |                      ^^^^^^^^^^^^^^^^^^ method cannot be called on `&MbusError` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/mbus-core-0.16.0/src/errors/mod.rs:45:1
[INFO] [stdout]     |
[INFO] [stdout]  45 | pub enum MbusError {
[INFO] [stdout]     | ------------------ doesn't satisfy `MbusError: Into<anyhow::Error>`, `MbusError: anyhow::__private::kind::TraitKind` or `MbusError: std::fmt::Display`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]             `MbusError: std::fmt::Display`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::AdhocKind`
[INFO] [stdout]             `&MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]     = note: this error originates in the macro `anyhow::anyhow` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `modbus-rs` (example "modbus_rs_client_serial_rtu_discrete_inputs") due to 3 previous errors
[INFO] [stderr] error: could not compile `modbus-rs` (example "modbus_rs_client_tcp_device_id") due to 9 previous errors
[INFO] [stdout] error[E0599]: the method `anyhow_kind` exists for reference `&MbusError`, but its trait bounds were not satisfied
[INFO] [stdout]    --> examples/client/network-tcp/sync/discrete_inputs.rs:123:22
[INFO] [stdout]     |
[INFO] [stdout] 123 |         .map_err(|e| anyhow::anyhow!(e))?;
[INFO] [stdout]     |                      ^^^^^^^^^^^^^^^^^^ method cannot be called on `&MbusError` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/mbus-core-0.16.0/src/errors/mod.rs:45:1
[INFO] [stdout]     |
[INFO] [stdout]  45 | pub enum MbusError {
[INFO] [stdout]     | ------------------ doesn't satisfy `MbusError: Into<anyhow::Error>`, `MbusError: anyhow::__private::kind::TraitKind` or `MbusError: std::fmt::Display`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]             `MbusError: std::fmt::Display`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::AdhocKind`
[INFO] [stdout]             `&MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]     = note: this error originates in the macro `anyhow::anyhow` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `modbus-rs` (example "modbus_rs_client_serial_rtu_coils") due to 7 previous errors
[INFO] [stdout] error[E0599]: the method `anyhow_kind` exists for reference `&MbusError`, but its trait bounds were not satisfied
[INFO] [stdout]    --> examples/client/network-tcp/sync/coils.rs:101:65
[INFO] [stdout]     |
[INFO] [stdout] 101 |         ModbusTcpConfig::new("192.168.55.200", 502).map_err(|e| anyhow::anyhow!(e))?;
[INFO] [stdout]     |                                                                 ^^^^^^^^^^^^^^^^^^ method cannot be called on `&MbusError` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/mbus-core-0.16.0/src/errors/mod.rs:45:1
[INFO] [stdout]     |
[INFO] [stdout]  45 | pub enum MbusError {
[INFO] [stdout]     | ------------------ doesn't satisfy `MbusError: Into<anyhow::Error>`, `MbusError: anyhow::__private::kind::TraitKind` or `MbusError: std::fmt::Display`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]             `MbusError: std::fmt::Display`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::AdhocKind`
[INFO] [stdout]             `&MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]     = note: this error originates in the macro `anyhow::anyhow` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0599`.
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: the method `anyhow_kind` exists for reference `&MbusError`, but its trait bounds were not satisfied
[INFO] [stdout]    --> examples/client/network-tcp/sync/coils.rs:106:77
[INFO] [stdout]     |
[INFO] [stdout] 106 |         ClientServices::<_, _, 10>::new(transport, app, config).map_err(|e| anyhow::anyhow!(e))?;
[INFO] [stdout]     |                                                                             ^^^^^^^^^^^^^^^^^^ method cannot be called on `&MbusError` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/mbus-core-0.16.0/src/errors/mod.rs:45:1
[INFO] [stdout]     |
[INFO] [stdout]  45 | pub enum MbusError {
[INFO] [stdout]     | ------------------ doesn't satisfy `MbusError: Into<anyhow::Error>`, `MbusError: anyhow::__private::kind::TraitKind` or `MbusError: std::fmt::Display`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]             `MbusError: std::fmt::Display`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::AdhocKind`
[INFO] [stdout]             `&MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]     = note: this error originates in the macro `anyhow::anyhow` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0599]: the method `anyhow_kind` exists for reference `&MbusError`, but its trait bounds were not satisfied
[INFO] [stdout]    --> examples/client/network-tcp/sync/coils.rs:107:34
[INFO] [stdout]     |
[INFO] [stdout] 107 |     client.connect().map_err(|e| anyhow::anyhow!(e))?;
[INFO] [stdout]     |                                  ^^^^^^^^^^^^^^^^^^ method cannot be called on `&MbusError` due to unsatisfied trait bounds
[INFO] [stdout]     |
[INFO] [stdout]    ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/mbus-core-0.16.0/src/errors/mod.rs:45:1
[INFO] [stdout]     |
[INFO] [stdout]  45 | pub enum MbusError {
[INFO] [stdout]     | ------------------ doesn't satisfy `MbusError: Into<anyhow::Error>`, `MbusError: anyhow::__private::kind::TraitKind` or `MbusError: std::fmt::Display`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the following trait bounds were not satisfied:
[INFO] [stdout]             `MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]             `MbusError: std::fmt::Display`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::AdhocKind`
[INFO] [stdout]             `&MbusError: Into<anyhow::Error>`
[INFO] [stdout]             which is required by `&MbusError: anyhow::__private::kind::TraitKind`
[INFO] [stdout]     = note: this error originates in the macro `anyhow::anyhow` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `modbus-rs` (example "modbus_rs_client_tcp_discrete_inputs") due to 5 previous errors
[INFO] [stdout] error[E0277]: `?` couldn't convert the error: `MbusError: std::error::Error` is not satisfied
[INFO] [stdout]    --> examples/client/network-tcp/sync/coils.rs:132:45
[INFO] [stdout]     |
[INFO] [stdout]  96 | fn main() -> Result<()> {
[INFO] [stdout]     |              ---------- required `MbusError: std::error::Error` because of this
[INFO] [stdout] ...
[INFO] [stdout] 132 |             coils.value(read_single_address)?
[INFO] [stdout]     |                   --------------------------^ the trait `std::error::Error` is not implemented for `MbusError`
[INFO] [stdout]     |                   |
[INFO] [stdout]     |                   this has type `Result<_, MbusError>`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]     = note: required for `anyhow::Error` to implement `From<MbusError>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error: `MbusError: std::error::Error` is not satisfied
[INFO] [stdout]    --> examples/client/network-tcp/sync/coils.rs:134:52
[INFO] [stdout]     |
[INFO] [stdout]  96 | fn main() -> Result<()> {
[INFO] [stdout]     |              ---------- required `MbusError: std::error::Error` because of this
[INFO] [stdout] ...
[INFO] [stdout] 134 |         assert_eq!(coils.value(read_single_address)?, CoilState::On); // Initialized to true
[INFO] [stdout]     |                          --------------------------^ the trait `std::error::Error` is not implemented for `MbusError`
[INFO] [stdout]     |                          |
[INFO] [stdout]     |                          this has type `Result<_, MbusError>`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]     = note: required for `anyhow::Error` to implement `From<MbusError>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error: `MbusError: std::error::Error` is not satisfied
[INFO] [stdout]    --> examples/client/network-tcp/sync/coils.rs:180:56
[INFO] [stdout]     |
[INFO] [stdout]  96 | fn main() -> Result<()> {
[INFO] [stdout]     |              ---------- required `MbusError: std::error::Error` because of this
[INFO] [stdout] ...
[INFO] [stdout] 180 |             coils_read_back.value(write_single_address)?
[INFO] [stdout]     |                             ---------------------------^ the trait `std::error::Error` is not implemented for `MbusError`
[INFO] [stdout]     |                             |
[INFO] [stdout]     |                             this has type `Result<_, MbusError>`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]     = note: required for `anyhow::Error` to implement `From<MbusError>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `CoilState` doesn't implement `std::fmt::Display`
[INFO] [stdout]    --> examples/client/network-tcp/sync/coils.rs:180:13
[INFO] [stdout]     |
[INFO] [stdout] 178 |             "Client: Read back coil at address {}: {}",
[INFO] [stdout]     |                                                    -- required by this formatting parameter
[INFO] [stdout] 179 |             write_single_address,
[INFO] [stdout] 180 |             coils_read_back.value(write_single_address)?
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ `CoilState` cannot be formatted with the default formatter
[INFO] [stdout]     |
[INFO] [stdout]     = help: the trait `std::fmt::Display` is not implemented for `CoilState`
[INFO] [stdout]     = note: in format strings you may be able to use `{:?}` (or `{:#?}` for pretty-print) instead
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error: `MbusError: std::error::Error` is not satisfied
[INFO] [stdout]    --> examples/client/network-tcp/sync/coils.rs:183:56
[INFO] [stdout]     |
[INFO] [stdout]  96 | fn main() -> Result<()> {
[INFO] [stdout]     |              ---------- required `MbusError: std::error::Error` because of this
[INFO] [stdout] ...
[INFO] [stdout] 183 |             coils_read_back.value(write_single_address)?,
[INFO] [stdout]     |                             ---------------------------^ the trait `std::error::Error` is not implemented for `MbusError`
[INFO] [stdout]     |                             |
[INFO] [stdout]     |                             this has type `Result<_, MbusError>`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]     = note: required for `anyhow::Error` to implement `From<MbusError>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error: `MbusError: std::error::Error` is not satisfied
[INFO] [stdout]    --> examples/client/network-tcp/sync/coils.rs:219:51
[INFO] [stdout]     |
[INFO] [stdout]  96 | fn main() -> Result<()> {
[INFO] [stdout]     |              ---------- required `MbusError: std::error::Error` because of this
[INFO] [stdout] ...
[INFO] [stdout] 219 |                 coils_multi.value(current_address)?
[INFO] [stdout]     |                             ----------------------^ the trait `std::error::Error` is not implemented for `MbusError`
[INFO] [stdout]     |                             |
[INFO] [stdout]     |                             this has type `Result<_, MbusError>`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]     = note: required for `anyhow::Error` to implement `From<MbusError>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error: `MbusError: std::error::Error` is not satisfied
[INFO] [stdout]    --> examples/client/network-tcp/sync/coils.rs:222:41
[INFO] [stdout]     |
[INFO] [stdout]  96 | fn main() -> Result<()> {
[INFO] [stdout]     |              ---------- required `MbusError: std::error::Error` because of this
[INFO] [stdout] ...
[INFO] [stdout] 222 |         assert_eq!(coils_multi.value(10)?, CoilState::On);
[INFO] [stdout]     |                                ---------^ the trait `std::error::Error` is not implemented for `MbusError`
[INFO] [stdout]     |                                |
[INFO] [stdout]     |                                this has type `Result<_, MbusError>`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]     = note: required for `anyhow::Error` to implement `From<MbusError>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error: `MbusError: std::error::Error` is not satisfied
[INFO] [stdout]    --> examples/client/network-tcp/sync/coils.rs:223:41
[INFO] [stdout]     |
[INFO] [stdout]  96 | fn main() -> Result<()> {
[INFO] [stdout]     |              ---------- required `MbusError: std::error::Error` because of this
[INFO] [stdout] ...
[INFO] [stdout] 223 |         assert_eq!(coils_multi.value(11)?, CoilState::Off);
[INFO] [stdout]     |                                ---------^ the trait `std::error::Error` is not implemented for `MbusError`
[INFO] [stdout]     |                                |
[INFO] [stdout]     |                                this has type `Result<_, MbusError>`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]     = note: required for `anyhow::Error` to implement `From<MbusError>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error: `MbusError: std::error::Error` is not satisfied
[INFO] [stdout]    --> examples/client/network-tcp/sync/coils.rs:224:41
[INFO] [stdout]     |
[INFO] [stdout]  96 | fn main() -> Result<()> {
[INFO] [stdout]     |              ---------- required `MbusError: std::error::Error` because of this
[INFO] [stdout] ...
[INFO] [stdout] 224 |         assert_eq!(coils_multi.value(12)?, CoilState::On);
[INFO] [stdout]     |                                ---------^ the trait `std::error::Error` is not implemented for `MbusError`
[INFO] [stdout]     |                                |
[INFO] [stdout]     |                                this has type `Result<_, MbusError>`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]     = note: required for `anyhow::Error` to implement `From<MbusError>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error: `MbusError: std::error::Error` is not satisfied
[INFO] [stdout]    --> examples/client/network-tcp/sync/coils.rs:302:61
[INFO] [stdout]     |
[INFO] [stdout]  96 | fn main() -> Result<()> {
[INFO] [stdout]     |              ---------- required `MbusError: std::error::Error` because of this
[INFO] [stdout] ...
[INFO] [stdout] 302 |                 coils_read_back_multi.value(current_address)?
[INFO] [stdout]     |                                       ----------------------^ the trait `std::error::Error` is not implemented for `MbusError`
[INFO] [stdout]     |                                       |
[INFO] [stdout]     |                                       this has type `Result<_, MbusError>`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]     = note: required for `anyhow::Error` to implement `From<MbusError>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error: `MbusError: std::error::Error` is not satisfied
[INFO] [stdout]    --> examples/client/network-tcp/sync/coils.rs:305:61
[INFO] [stdout]     |
[INFO] [stdout]  96 | fn main() -> Result<()> {
[INFO] [stdout]     |              ---------- required `MbusError: std::error::Error` because of this
[INFO] [stdout] ...
[INFO] [stdout] 305 |                 coils_read_back_multi.value(current_address)?,
[INFO] [stdout]     |                                       ----------------------^ the trait `std::error::Error` is not implemented for `MbusError`
[INFO] [stdout]     |                                       |
[INFO] [stdout]     |                                       this has type `Result<_, MbusError>`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]     = note: required for `anyhow::Error` to implement `From<MbusError>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error: `MbusError: std::error::Error` is not satisfied
[INFO] [stdout]    --> examples/client/network-tcp/sync/coils.rs:345:39
[INFO] [stdout]     |
[INFO] [stdout]  96 | fn main() -> Result<()> {
[INFO] [stdout]     |              ---------- required `MbusError: std::error::Error` because of this
[INFO] [stdout] ...
[INFO] [stdout] 345 |             batch_read_coils.value(12)?
[INFO] [stdout]     |                              ---------^ the trait `std::error::Error` is not implemented for `MbusError`
[INFO] [stdout]     |                              |
[INFO] [stdout]     |                              this has type `Result<_, MbusError>`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]     = note: required for `anyhow::Error` to implement `From<MbusError>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: `?` couldn't convert the error: `MbusError: std::error::Error` is not satisfied
[INFO] [stdout]    --> examples/client/network-tcp/sync/coils.rs:347:46
[INFO] [stdout]     |
[INFO] [stdout]  96 | fn main() -> Result<()> {
[INFO] [stdout]     |              ---------- required `MbusError: std::error::Error` because of this
[INFO] [stdout] ...
[INFO] [stdout] 347 |         assert_eq!(batch_read_coils.value(12)?, CoilState::Off);
[INFO] [stdout]     |                                     ---------^ the trait `std::error::Error` is not implemented for `MbusError`
[INFO] [stdout]     |                                     |
[INFO] [stdout]     |                                     this has type `Result<_, MbusError>`
[INFO] [stdout]     |
[INFO] [stdout]     = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
[INFO] [stdout]     = note: required for `anyhow::Error` to implement `From<MbusError>`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0277, E0599.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0277`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `modbus-rs` (example "modbus_rs_client_tcp_coils") due to 17 previous errors
[INFO] running `Command { std: "docker" "inspect" "aad9ece8f5c826e1a98bbf953b32c224c70278ffed597ee0624e7d4a2c2351db", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "aad9ece8f5c826e1a98bbf953b32c224c70278ffed597ee0624e7d4a2c2351db", kill_on_drop: false }`
[INFO] [stdout] aad9ece8f5c826e1a98bbf953b32c224c70278ffed597ee0624e7d4a2c2351db
