Fix 14 deep-review findings across security, concurrency, and API #32
Triggered via pull request
May 19, 2026 10:59
Status
Failure
Total duration
1d 0h 3m 15s
Artifacts
6
CI.yml
on: pull_request
Matrix: build-linux
Build – macOS (arm64 + x64)
1m 37s
Integration Test – Harper UDS proxy
45s
Matrix: test
Annotations
12 errors and 9 warnings
|
Test – ubuntu-latest Node 22
Process completed with exit code 1.
|
|
Integration Test – Harper UDS proxy
Cannot find module '../core/config/configUtils.js' or its corresponding type declarations.
|
|
Integration Test – Harper UDS proxy
Cannot find module '../core/utility/installation.js' or its corresponding type declarations.
|
|
Integration Test – Harper UDS proxy
Cannot find module '../core/utility/logging/harper_logger.js' or its corresponding type declarations.
|
|
Integration Test – Harper UDS proxy
Cannot find module '../core/utility/environment/environmentManager.js' or its corresponding type declarations.
|
|
Integration Test – Harper UDS proxy
Cannot find module '../core/components/Scope.ts' or its corresponding type declarations.
|
|
Integration Test – Harper UDS proxy
Cannot find module '../core/utility/logging/harper_logger.js' or its corresponding type declarations.
|
|
Integration Test – Harper UDS proxy
Cannot find module '../core/server/threads/manageThreads.js' or its corresponding type declarations.
|
|
Integration Test – Harper UDS proxy
Cannot find module '../core/utility/packageUtils.js' or its corresponding type declarations.
|
|
Integration Test – Harper UDS proxy
Cannot find module '../core/utility/environment/environmentManager.js' or its corresponding type declarations.
|
|
Integration Test – Harper UDS proxy
Cannot find module '../core/resources/analytics/write.ts' or its corresponding type declarations.
|
|
Test – macos-13 Node 20
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
|
|
Build – macOS (arm64 + x64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@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/
|
|
Build – aarch64-unknown-linux-gnu
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/
|
|
Build – x86_64-unknown-linux-gnu
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/
|
|
Build – aarch64-unknown-linux-musl
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/
|
|
Build – x86_64-unknown-linux-musl
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/
|
|
Test – ubuntu-latest Node 22
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/download-artifact@v4, actions/setup-node@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/
|
|
Test – macos-14 Node 20
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/download-artifact@v4, actions/setup-node@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/
|
|
Test – ubuntu-latest Node 20
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/download-artifact@v4, actions/setup-node@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/
|
|
Integration Test – Harper UDS proxy
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/download-artifact@v4, actions/setup-node@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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
symphony.darwin-arm64.node
|
1.25 MB |
sha256:2178cf5c56fc418db54f3b8d030668ee477f292c6b0e2e8bb67c42fb8c0ffc49
|
|
|
symphony.darwin-x64.node
|
1.33 MB |
sha256:b376aeb76e00d561a4f453ec7ac5915a0203435fcb0725ff9a5140ab464a480f
|
|
|
symphony.linux-arm64-gnu.node
|
1.29 MB |
sha256:e2cf0aad897cd0bed46e99c9b65ca5d94cd33bb6d1ec8b2790bb849a79e5623a
|
|
|
symphony.linux-arm64-musl.node
|
1.32 MB |
sha256:33fbc62873582883c0373f8db450bb16125e2e29f820356d28cd2d52236b9138
|
|
|
symphony.linux-x64-gnu.node
|
1.38 MB |
sha256:8333a39ed75f976c617fc5d8283f522cad1a0d8296e0b590ee0f838eeaf1835c
|
|
|
symphony.linux-x64-musl.node
|
1.38 MB |
sha256:1e6476fd1b01bcf00834012c5cc9e6ade9630b093baf5eecc4ef9befd6f603bf
|
|