Skip to content

fix: execute-block handle no explicit --at #232

fix: execute-block handle no explicit --at

fix: execute-block handle no explicit --at #232

Triggered via pull request April 29, 2024 08:24
Status Failure
Total duration 53m 17s
Artifacts

rust-checks.yaml

on: pull_request
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 2 warnings
redundant pattern matching, consider using `is_some()`: core/src/commands/execute_block.rs#L103
error: redundant pattern matching, consider using `is_some()` --> core/src/commands/execute_block.rs:103:20 | 103 | if let Some(_) = live_state.at { | -------^^^^^^^---------------- help: try: `if live_state.at.is_some()` | = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#redundant_pattern_matching = note: `-D clippy::redundant-pattern-matching` implied by `-D warnings` = help: to override `-D warnings` add `#[allow(clippy::redundant_pattern_matching)]`
lint
Clippy had exited with the 101 exit code
doc
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: arduino/setup-protoc@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
test (ubuntu-latest, stable)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: arduino/setup-protoc@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.