error[E0277]: the trait bound `logging::ErrorContext: defmt::Format` is not satisfied --> libraries/messages/src/logging/macros.rs:19:47 | 19 | Event::$e($($p),*) => defmt::write!(f, $s, $($p),*), | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `defmt::Format` is not implemented for `logging::ErrorContext` | ::: libraries/messages/src/logging/mod.rs:28:1 | 28 | / display_event!( 29 | | [Initialized, "Initialized"], 30 | | [Error, "Encountered error: {}", e], 31 | | [MainDeploy, "Main parachute deployed"] 32 | | ); | |_- in this macro invocation | = help: the following other types implement trait `defmt::Format`: bool char isize i8 i16 i32 i64 i128 and 154 others = note: required for `&logging::ErrorContext` to implement `defmt::Format` note: required by a bound in `defmt::export::fmt` --> /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/defmt-0.3.5/src/export/mod.rs:137:15 | 137 | pub fn fmt<T: Format + ?Sized>(f: &T) { | ^^^^^^ required by this bound in `fmt` = note: this error originates in the macro `defmt::write` which comes from the expansion of the macro `display_event` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0277]: `logging::ErrorContext` doesn't implement `core::fmt::Display` --> libraries/messages/src/logging/macros.rs:9:63 | 9 | Event::$e($($p),*) => write!(f, $s, $($p),*), | ^^ `logging::ErrorContext` cannot be formatted with the default formatter | ::: libraries/messages/src/logging/mod.rs:28:1 | 28 | / display_event!( 29 | | [Initialized, "Initialized"], 30 | | [Error, "Encountered error: {}", e], 31 | | [MainDeploy, "Main parachute deployed"] 32 | | ); | |_- in this macro invocation | = help: the trait `core::fmt::Display` is not implemented for `logging::ErrorContext` = note: in format strings you may be able to use `{:?}` (or {:#?} for pretty-print) instead = note: this error originates in the macro `$crate::format_args` which comes from the expansion of the macro `display_event` (in Nightly builds, run with -Z macro-backtrace for more info)

Clippy had exited with the 101 exit code

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions-rs/toolchain@v1, actions/cache@v3, 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/toolchain@v1, 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/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/