Skip to content

feat: retry redis connection #199

feat: retry redis connection

feat: retry redis connection #199

Triggered via pull request March 11, 2026 13:31
Status Success
Total duration 2m 52s
Artifacts 1

check-and-lint.yaml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

17 warnings
Rustfmt
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions-rs/cargo@v1, actions-rs/toolchain@v1, actions/checkout@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Rustfmt
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/
Rustfmt
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/
Rustfmt
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/
Rustfmt
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/
Check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions-rs/cargo@v1, actions-rs/toolchain@v1, actions/checkout@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Check
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/
Check
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/
Check
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/
Check
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/
Clippy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, auguwu/clippy-action@1.4.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
name `ERROR` contains a capitalized acronym: src/main.rs#L242
warning: name `ERROR` contains a capitalized acronym --> src/status_message.rs:242:5 | 242 | ERROR = -1, | ^^^^^ help: consider making the acronym lowercase, except the initial letter: `Error` | = help: for further information visit https://rust-lang.github.io/rust-clippy/rust-1.94.0/index.html#upper_case_acronyms
name `IDLE` contains a capitalized acronym: src/main.rs#L241
warning: name `IDLE` contains a capitalized acronym --> src/status_message.rs:241:5 | 241 | IDLE = 0, | ^^^^ help: consider making the acronym lowercase, except the initial letter: `Idle` | = help: for further information visit https://rust-lang.github.io/rust-clippy/rust-1.94.0/index.html#upper_case_acronyms
name `BUSY` contains a capitalized acronym: src/main.rs#L240
warning: name `BUSY` contains a capitalized acronym --> src/status_message.rs:240:5 | 240 | BUSY = 1, | ^^^^ help: consider making the acronym lowercase, except the initial letter (notice the capitalization): `Busy` | = help: for further information visit https://rust-lang.github.io/rust-clippy/rust-1.94.0/index.html#upper_case_acronyms
name `RUNNING` contains a capitalized acronym: src/main.rs#L239
warning: name `RUNNING` contains a capitalized acronym --> src/status_message.rs:239:5 | 239 | RUNNING = 2, | ^^^^^^^ help: consider making the acronym lowercase, except the initial letter: `Running` | = help: for further information visit https://rust-lang.github.io/rust-clippy/rust-1.94.0/index.html#upper_case_acronyms = note: `#[warn(clippy::upper_case_acronyms)]` on by default
large size difference between variants: src/main.rs#L109
warning: large size difference between variants --> src/status_message.rs:109:1 | 109 | / pub enum Info { 110 | | ServiceInfo(ServiceInfoMessagePack), | | ----------------------------------- the largest variant contains at least 232 bytes 111 | | Object(::serde_json::Map<::std::string::String, ::serde_json::Value>), | | --------------------------------------------------------------------- the second-largest variant contains at least 24 bytes 112 | | } | |_^ the entire enum is at least 232 bytes | = help: for further information visit https://rust-lang.github.io/rust-clippy/rust-1.94.0/index.html#large_enum_variant = note: `#[warn(clippy::large_enum_variant)]` on by default help: consider boxing the large fields or introducing indirection in some other way to reduce the total size of the enum | 110 - ServiceInfo(ServiceInfoMessagePack), 110 + ServiceInfo(Box<ServiceInfoMessagePack>), |
Test cross compilation and RPM build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, Swatinem/rust-cache@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
Test binary artifact and RPM
6.44 MB
sha256:5d322b6d362bdc1270706bddfdefd3d73125176124e7db710ef077d3dd796f08