Process completed with exit code 1.

Process completed with exit code 100.

Process completed with exit code 1.

Process completed with exit code 100.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 100.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

This is only informational and not a blocker.

this `if` can be collapsed into the outer `match`

this `if` can be collapsed into the outer `match`

this `if` can be collapsed into the outer `match`

this function has too many arguments (10/7)

this function has too many arguments (8/7)

this `if` can be collapsed into the outer `match`

explicit call to `.into_iter()` in function argument accepting `IntoIterator`

explicit call to `.into_iter()` in function argument accepting `IntoIterator`

very complex type used. Consider factoring parts into `type` definitions

consider using `sort_by_key`

artifacts/Test Results (macos-latest-stable)/junit.xml artifacts/Test Results (ubuntu-latest-nightly)/junit.xml artifacts/Test Results (ubuntu-latest-stable)/junit.xml

artifacts/Test Results (macos-latest-stable)/junit.xml artifacts/Test Results (ubuntu-latest-nightly)/junit.xml artifacts/Test Results (ubuntu-latest-stable)/junit.xml

artifacts/Test Results (macos-latest-stable)/junit.xml artifacts/Test Results (ubuntu-latest-nightly)/junit.xml artifacts/Test Results (ubuntu-latest-stable)/junit.xml

artifacts/Test Results (windows-latest-stable)/junit.xml

artifacts/Test Results (windows-latest-stable)/junit.xml

artifacts/Test Results (windows-latest-stable)/junit.xml

artifacts/Test Results (windows-latest-stable)/junit.xml

artifacts/Test Results (windows-latest-stable)/junit.xml

artifacts/Test Results (windows-latest-stable)/junit.xml

artifacts/Test Results (windows-latest-stable)/junit.xml

artifacts/Test Results (windows-latest-stable)/junit.xml

artifacts/Test Results (windows-latest-stable)/junit.xml

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/