The process '/home/ubuntu/.cargo/bin/cargo' failed with exit code 1

error: very complex type used. Consider factoring parts into `type` definitions --> farmer/src/lib.rs:683:9 | 683 | Option<mpsc::Receiver<anyhow::Result<TaskOutput<Option<SingleDiskFarmId>, String>>>>, | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#type_complexity = note: `-D clippy::type-complexity` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(clippy::type_complexity)]`

error: this `MutexGuard` is held across an `await` point --> farmer/src/lib.rs:567:9 | 567 | readers_and_pieces.lock().replace(create_readers_and_pieces(&single_disk_farms).await?); | ^^^^^^^^^^^^^^^^^^^^^^^^^ | = help: consider using an async-aware `Mutex` type or ensuring the `MutexGuard` is dropped before calling await note: these are all the `await` points this lock is held through --> farmer/src/lib.rs:567:89 | 567 | readers_and_pieces.lock().replace(create_readers_and_pieces(&single_disk_farms).await?); | ^^^^^ = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#await_holding_lock = note: `-D clippy::await-holding-lock` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(clippy::await_holding_lock)]`

error: unused import: `FullSelectChain` --> node/src/domains/builder.rs:25:51 | 25 | use subspace_service::{FullClient as CFullClient, FullSelectChain}; | ^^^^^^^^^^^^^^^ | = note: `-D unused-imports` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(unused_imports)]`

Clippy had exited with the 101 exit code

Process completed with exit code 1.

Clippy had exited with the 101 exit code

error: very complex type used. Consider factoring parts into `type` definitions --> farmer/src/lib.rs:683:9 | 683 | Option<mpsc::Receiver<anyhow::Result<TaskOutput<Option<SingleDiskFarmId>, String>>>>, | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#type_complexity = note: `-D clippy::type-complexity` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(clippy::type_complexity)]`

error: this `MutexGuard` is held across an `await` point --> farmer/src/lib.rs:567:9 | 567 | readers_and_pieces.lock().replace(create_readers_and_pieces(&single_disk_farms).await?); | ^^^^^^^^^^^^^^^^^^^^^^^^^ | = help: consider using an async-aware `Mutex` type or ensuring the `MutexGuard` is dropped before calling await note: these are all the `await` points this lock is held through --> farmer/src/lib.rs:567:89 | 567 | readers_and_pieces.lock().replace(create_readers_and_pieces(&single_disk_farms).await?); | ^^^^^ = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#await_holding_lock = note: `-D clippy::await-holding-lock` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(clippy::await_holding_lock)]`

Clippy had exited with the 101 exit code

Process completed with exit code 101.

The job was canceled because "self-hosted_macos-12-arm6" failed.

Process completed with exit code 1.

The operation was canceled.

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

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

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