error: non-local `impl` definition, they should be avoided as they go against expectation --> src/protocol.rs:46:45 | 46 | #[derive(Clone, Copy, Debug, FromPrimitive, ToPrimitive)] | ^^^^^^^^^^^ | = help: move this `impl` block outside the of the current constant `_IMPL_NUM_ToPrimitive_FOR_RequestType` = note: an `impl` definition is non-local if it is nested inside an item and neither the type nor the trait are at the same nesting level as the `impl` block = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363> = note: the derive macro `ToPrimitive` may come from an old version of the `num_derive` crate, try updating your dependency with `cargo update -p num_derive` = note: this error originates in the derive macro `ToPrimitive` (in Nightly builds, run with -Z macro-backtrace for more info)

error: non-local `impl` definition, they should be avoided as they go against expectation --> src/protocol.rs:46:30 | 46 | #[derive(Clone, Copy, Debug, FromPrimitive, ToPrimitive)] | ^^^^^^^^^^^^^ | = help: move this `impl` block outside the of the current constant `_IMPL_NUM_FromPrimitive_FOR_RequestType` = note: an `impl` definition is non-local if it is nested inside an item and neither the type nor the trait are at the same nesting level as the `impl` block = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363> = note: the derive macro `FromPrimitive` may come from an old version of the `num_derive` crate, try updating your dependency with `cargo update -p num_derive` = note: `-D non-local-definitions` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(non_local_definitions)]` = note: this error originates in the derive macro `FromPrimitive` (in Nightly builds, run with -Z macro-backtrace for more info)

error: non-local `impl` definition, they should be avoided as they go against expectation --> src/protocol.rs:46:45 | 46 | #[derive(Clone, Copy, Debug, FromPrimitive, ToPrimitive)] | ^^^^^^^^^^^ | = help: move this `impl` block outside the of the current constant `_IMPL_NUM_ToPrimitive_FOR_RequestType` = note: an `impl` definition is non-local if it is nested inside an item and neither the type nor the trait are at the same nesting level as the `impl` block = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363> = note: the derive macro `ToPrimitive` may come from an old version of the `num_derive` crate, try updating your dependency with `cargo update -p num_derive` = note: this error originates in the derive macro `ToPrimitive` (in Nightly builds, run with -Z macro-backtrace for more info)

error: non-local `impl` definition, they should be avoided as they go against expectation --> src/protocol.rs:46:30 | 46 | #[derive(Clone, Copy, Debug, FromPrimitive, ToPrimitive)] | ^^^^^^^^^^^^^ | = help: move this `impl` block outside the of the current constant `_IMPL_NUM_FromPrimitive_FOR_RequestType` = note: an `impl` definition is non-local if it is nested inside an item and neither the type nor the trait are at the same nesting level as the `impl` block = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363> = note: the derive macro `FromPrimitive` may come from an old version of the `num_derive` crate, try updating your dependency with `cargo update -p num_derive` = note: `-D non-local-definitions` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(non_local_definitions)]` = note: this error originates in the derive macro `FromPrimitive` (in Nightly builds, run with -Z macro-backtrace for more info)

error: field `addr_type` is never read --> src/ffi.rs:101:9 | 98 | pub struct Hostent { | ------- field in this struct ... 101 | pub addr_type: i32, | ^^^^^^^^^ | = note: `Hostent` has derived impls for the traits `Debug` and `Clone`, but these are intentionally ignored during dead code analysis = note: `-D dead-code` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(dead_code)]`

error: field `addr_type` is never read --> src/ffi.rs:101:9 | 98 | pub struct Hostent { | ------- field in this struct ... 101 | pub addr_type: i32, | ^^^^^^^^^ | = note: `Hostent` has derived impls for the traits `Debug` and `Clone`, but these are intentionally ignored during dead code analysis = note: `-D dead-code` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(dead_code)]`

error: field `addr_type` is never read --> src/ffi.rs:101:9 | 98 | pub struct Hostent { | ------- field in this struct ... 101 | pub addr_type: i32, | ^^^^^^^^^ | = note: `Hostent` has derived impls for the traits `Debug` and `Clone`, but these are intentionally ignored during dead code analysis = note: `-D dead-code` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(dead_code)]`

error: field `addr_type` is never read --> src/ffi.rs:101:9 | 98 | pub struct Hostent { | ------- field in this struct ... 101 | pub addr_type: i32, | ^^^^^^^^^ | = note: `Hostent` has derived impls for the traits `Debug` and `Clone`, but these are intentionally ignored during dead code analysis = note: `-D dead-code` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(dead_code)]`

error: field `addr_type` is never read --> src/ffi.rs:101:9 | 98 | pub struct Hostent { | ------- field in this struct ... 101 | pub addr_type: i32, | ^^^^^^^^^ | = note: `Hostent` has derived impls for the traits `Debug` and `Clone`, but these are intentionally ignored during dead code analysis = note: `-D dead-code` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(dead_code)]`

error: field `addr_type` is never read --> src/ffi.rs:101:9 | 98 | pub struct Hostent { | ------- field in this struct ... 101 | pub addr_type: i32, | ^^^^^^^^^ | = note: `Hostent` has derived impls for the traits `Debug` and `Clone`, but these are intentionally ignored during dead code analysis = note: `-D dead-code` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(dead_code)]`

error: field `addr_type` is never read --> src/ffi.rs:101:9 | 98 | pub struct Hostent { | ------- field in this struct ... 101 | pub addr_type: i32, | ^^^^^^^^^ | = note: `Hostent` has derived impls for the traits `Debug` and `Clone`, but these are intentionally ignored during dead code analysis = note: `-D dead-code` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(dead_code)]`

error: field `addr_type` is never read --> src/ffi.rs:101:9 | 98 | pub struct Hostent { | ------- field in this struct ... 101 | pub addr_type: i32, | ^^^^^^^^^ | = note: `Hostent` has derived impls for the traits `Debug` and `Clone`, but these are intentionally ignored during dead code analysis = note: `-D dead-code` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(dead_code)]`

error: field `addr_type` is never read --> src/ffi.rs:101:9 | 98 | pub struct Hostent { | ------- field in this struct ... 101 | pub addr_type: i32, | ^^^^^^^^^ | = note: `Hostent` has derived impls for the traits `Debug` and `Clone`, but these are intentionally ignored during dead code analysis = note: `-D dead-code` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(dead_code)]`

error: field `addr_type` is never read --> src/ffi.rs:101:9 | 98 | pub struct Hostent { | ------- field in this struct ... 101 | pub addr_type: i32, | ^^^^^^^^^ | = note: `Hostent` has derived impls for the traits `Debug` and `Clone`, but these are intentionally ignored during dead code analysis = note: `-D dead-code` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(dead_code)]`

error: field `addr_type` is never read --> src/ffi.rs:101:9 | 98 | pub struct Hostent { | ------- field in this struct ... 101 | pub addr_type: i32, | ^^^^^^^^^ | = note: `Hostent` has derived impls for the traits `Debug` and `Clone`, but these are intentionally ignored during dead code analysis = note: `-D dead-code` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(dead_code)]`

error: field `addr_type` is never read --> src/ffi.rs:101:9 | 98 | pub struct Hostent { | ------- field in this struct ... 101 | pub addr_type: i32, | ^^^^^^^^^ | = note: `Hostent` has derived impls for the traits `Debug` and `Clone`, but these are intentionally ignored during dead code analysis = note: `-D dead-code` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(dead_code)]`

error: field `addr_type` is never read --> src/ffi.rs:101:9 | 98 | pub struct Hostent { | ------- field in this struct ... 101 | pub addr_type: i32, | ^^^^^^^^^ | = note: `Hostent` has derived impls for the traits `Debug` and `Clone`, but these are intentionally ignored during dead code analysis = note: `-D dead-code` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(dead_code)]`

error: non-local `impl` definition, they should be avoided as they go against expectation --> src/protocol.rs:46:45 | 46 | #[derive(Clone, Copy, Debug, FromPrimitive, ToPrimitive)] | ^^^^^^^^^^^ | = help: move this `impl` block outside the of the current constant `_IMPL_NUM_ToPrimitive_FOR_RequestType` = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl` = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363> = note: the derive macro `ToPrimitive` may come from an old version of the `num_derive` crate, try updating your dependency with `cargo update -p num_derive` = note: this error originates in the derive macro `ToPrimitive` (in Nightly builds, run with -Z macro-backtrace for more info)

error: non-local `impl` definition, they should be avoided as they go against expectation --> src/protocol.rs:46:30 | 46 | #[derive(Clone, Copy, Debug, FromPrimitive, ToPrimitive)] | ^^^^^^^^^^^^^ | = help: move this `impl` block outside the of the current constant `_IMPL_NUM_FromPrimitive_FOR_RequestType` = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl` = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363> = note: the derive macro `FromPrimitive` may come from an old version of the `num_derive` crate, try updating your dependency with `cargo update -p num_derive` = note: `-D non-local-definitions` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(non_local_definitions)]` = note: this error originates in the derive macro `FromPrimitive` (in Nightly builds, run with -Z macro-backtrace for more info)

error: field `addr_type` is never read --> src/ffi.rs:101:9 | 98 | pub struct Hostent { | ------- field in this struct ... 101 | pub addr_type: i32, | ^^^^^^^^^ | = note: `Hostent` has derived impls for the traits `Debug` and `Clone`, but these are intentionally ignored during dead code analysis = note: `-D dead-code` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(dead_code)]`

error: non-local `impl` definition, they should be avoided as they go against expectation --> src/protocol.rs:46:45 | 46 | #[derive(Clone, Copy, Debug, FromPrimitive, ToPrimitive)] | ^^^^^^^^^^^ | = help: move this `impl` block outside the of the current constant `_IMPL_NUM_ToPrimitive_FOR_RequestType` = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl` = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363> = note: the derive macro `ToPrimitive` may come from an old version of the `num_derive` crate, try updating your dependency with `cargo update -p num_derive` = note: this error originates in the derive macro `ToPrimitive` (in Nightly builds, run with -Z macro-backtrace for more info)

error: non-local `impl` definition, they should be avoided as they go against expectation --> src/protocol.rs:46:30 | 46 | #[derive(Clone, Copy, Debug, FromPrimitive, ToPrimitive)] | ^^^^^^^^^^^^^ | = help: move this `impl` block outside the of the current constant `_IMPL_NUM_FromPrimitive_FOR_RequestType` = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl` = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363> = note: the derive macro `FromPrimitive` may come from an old version of the `num_derive` crate, try updating your dependency with `cargo update -p num_derive` = note: `-D non-local-definitions` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(non_local_definitions)]` = note: this error originates in the derive macro `FromPrimitive` (in Nightly builds, run with -Z macro-backtrace for more info)

error: field `addr_type` is never read --> src/ffi.rs:101:9 | 98 | pub struct Hostent { | ------- field in this struct ... 101 | pub addr_type: i32, | ^^^^^^^^^ | = note: `Hostent` has derived impls for the traits `Debug` and `Clone`, but these are intentionally ignored during dead code analysis = note: `-D dead-code` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(dead_code)]`

error: non-local `impl` definition, they should be avoided as they go against expectation --> src/protocol.rs:46:45 | 46 | #[derive(Clone, Copy, Debug, FromPrimitive, ToPrimitive)] | ^^^^^^^^^^^ | = help: move this `impl` block outside the of the current constant `_IMPL_NUM_ToPrimitive_FOR_RequestType` = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl` = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363> = note: the derive macro `ToPrimitive` may come from an old version of the `num_derive` crate, try updating your dependency with `cargo update -p num_derive` = note: this error originates in the derive macro `ToPrimitive` (in Nightly builds, run with -Z macro-backtrace for more info)

error: non-local `impl` definition, they should be avoided as they go against expectation --> src/protocol.rs:46:30 | 46 | #[derive(Clone, Copy, Debug, FromPrimitive, ToPrimitive)] | ^^^^^^^^^^^^^ | = help: move this `impl` block outside the of the current constant `_IMPL_NUM_FromPrimitive_FOR_RequestType` = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl` = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363> = note: the derive macro `FromPrimitive` may come from an old version of the `num_derive` crate, try updating your dependency with `cargo update -p num_derive` = note: `-D non-local-definitions` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(non_local_definitions)]` = note: this error originates in the derive macro `FromPrimitive` (in Nightly builds, run with -Z macro-backtrace for more info)

error: field `addr_type` is never read --> src/ffi.rs:101:9 | 98 | pub struct Hostent { | ------- field in this struct ... 101 | pub addr_type: i32, | ^^^^^^^^^ | = note: `Hostent` has derived impls for the traits `Debug` and `Clone`, but these are intentionally ignored during dead code analysis = note: `-D dead-code` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(dead_code)]`

error: non-local `impl` definition, they should be avoided as they go against expectation --> src/protocol.rs:46:45 | 46 | #[derive(Clone, Copy, Debug, FromPrimitive, ToPrimitive)] | ^^^^^^^^^^^ | = help: move this `impl` block outside the of the current constant `_IMPL_NUM_ToPrimitive_FOR_RequestType` = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl` = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363> = note: the derive macro `ToPrimitive` may come from an old version of the `num_derive` crate, try updating your dependency with `cargo update -p num_derive` = note: this error originates in the derive macro `ToPrimitive` (in Nightly builds, run with -Z macro-backtrace for more info)

error: non-local `impl` definition, they should be avoided as they go against expectation --> src/protocol.rs:46:30 | 46 | #[derive(Clone, Copy, Debug, FromPrimitive, ToPrimitive)] | ^^^^^^^^^^^^^ | = help: move this `impl` block outside the of the current constant `_IMPL_NUM_FromPrimitive_FOR_RequestType` = note: an `impl` definition is non-local if it is nested inside an item and may impact type checking outside of that item. This can be the case if neither the trait or the self type are at the same nesting level as the `impl` = note: one exception to the rule are anon-const (`const _: () = { ... }`) at top-level module and anon-const at the same nesting as the trait or type = note: this lint may become deny-by-default in the edition 2024 and higher, see the tracking issue <https://github.com/rust-lang/rust/issues/120363> = note: the derive macro `FromPrimitive` may come from an old version of the `num_derive` crate, try updating your dependency with `cargo update -p num_derive` = note: `-D non-local-definitions` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(non_local_definitions)]` = note: this error originates in the derive macro `FromPrimitive` (in Nightly builds, run with -Z macro-backtrace for more info)

error: field `addr_type` is never read --> src/ffi.rs:101:9 | 98 | pub struct Hostent { | ------- field in this struct ... 101 | pub addr_type: i32, | ^^^^^^^^^ | = note: `Hostent` has derived impls for the traits `Debug` and `Clone`, but these are intentionally ignored during dead code analysis = note: `-D dead-code` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(dead_code)]`

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions-rs/clippy-check@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/clippy-check@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: codecov/codecov-action@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/download-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.