fix(DATAGO-133559): Context usage indicator inflates after tasks with peer delegation #5419
ci.yaml
on: pull_request
Detect Context
3s
Test and SonarQube
/
Build and Verify Packages
6m 53s
Matrix: Test and SonarQube / test-python-matrix
Test and SonarQube
/
Validate Dependencies
11s
Test and SonarQube
/
Test UI (Storybook + Unit)
5m 45s
Matrix: Build and Push Image / build-platform
Build and Push Image
/
Create Multi-Platform Manifest
0s
Release Readiness
/
...
/
SCA Scan
Release Readiness
/
Prisma Scan
CI Status
2s
Annotations
8 errors and 26 warnings
|
FOSSA Scan / SCA Scan
Process completed with exit code 1.
|
|
Build and Push Image / Build linux/arm64
Process completed with exit code 1.
|
|
Build and Push Image / Build linux/amd64
Process completed with exit code 1.
|
|
Test and SonarQube / Test Python 3.10
⚠️ Failed to parse file (/home/runner/work/solace-agent-mesh/solace-agent-mesh/junit-3.10.xml) with error Error: Text data outside of root node.
Line: 0
Column: 1101824
Char: n
|
|
Test and SonarQube / Test Python 3.13
⚠️ Failed to parse file (/home/runner/work/solace-agent-mesh/solace-agent-mesh/junit-3.13.xml) with error Error: Text data outside of root node.
Line: 0
Column: 1101826
Char: n
|
|
Test and SonarQube / SonarQube Analysis
Process completed with exit code 1.
|
|
CI Status
Process completed with exit code 1.
|
|
CI Status
Test and SonarQube is 'failure' (expected: success)
|
|
PR Size Check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. 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/
|
|
Validate Conventional Commit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: amannn/action-semantic-pull-request@e32d7e603df1aa1ba07e981f2a23455dee596825. 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 and Push Image / Prepare Build Metadata
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, astral-sh/setup-uv@38f3f104447c67c051c4a08e39b64a148898af3a. 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 and Push Image / Prepare Build Metadata
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0ou7raQAAAAC2sfmOMN/sQJm9AScQj/DnUEhMMzBFREdFMDQwOQBFZGdl
|
|
Build and Push Image / Prepare Build Metadata
Failed to restore: Cache service responded with 400
|
|
Test and SonarQube / Validate Dependencies
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
|
|
FOSSA Scan / SCA Scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5. 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 and SonarQube / Test UI (Storybook + Unit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/save@0057852bfaa89a56745cba8c7296529d2fc39830, actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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 and SonarQube / Test UI (Storybook + Unit):
client/webui/frontend/src/lib/components/pages/TaskExecutionHistoryPage.tsx#L51
The 'executions' logical expression could make the dependencies of useEffect Hook (at line 66) change on every render. To fix this, wrap the initialization of 'executions' in its own useMemo() Hook
|
|
Test and SonarQube / Test UI (Storybook + Unit):
client/webui/frontend/src/lib/components/pages/ArtifactsPage.tsx#L374
React Hook useEffect has a missing dependency: 'artifact'. Either include it or remove the dependency array
|
|
Test and SonarQube / Test UI (Storybook + Unit):
client/webui/frontend/src/lib/components/models/ModelEditPage.tsx#L58
React Hook useCallback has a missing dependency: 'agentsRefetch'. Either include it or remove the dependency array
|
|
Test and SonarQube / Test UI (Storybook + Unit):
client/webui/frontend/src/lib/components/chat/file/FileMessage.tsx#L29
The 'artifacts' conditional could make the dependencies of useMemo Hook (at line 33) change on every render. Move it inside the useMemo callback. Alternatively, wrap the initialization of 'artifacts' in its own useMemo() Hook
|
|
Test and SonarQube / Test UI (Storybook + Unit):
client/webui/frontend/src/lib/components/chat/file/FileIcon.tsx#L180
Fast refresh only works when a file only exports components. Use a new file to share constants or functions between components
|
|
Test and SonarQube / Test UI (Storybook + Unit):
client/webui/frontend/src/lib/components/chat/file/FileIcon.tsx#L46
Fast refresh only works when a file only exports components. Use a new file to share constants or functions between components
|
|
Test and SonarQube / Test UI (Storybook + Unit):
client/webui/frontend/src/lib/components/chat/file/FileIcon.tsx#L23
Fast refresh only works when a file only exports components. Use a new file to share constants or functions between components
|
|
Test and SonarQube / Test UI (Storybook + Unit):
client/webui/frontend/src/lib/components/chat/file/DocumentThumbnail.tsx#L91
Fast refresh only works when a file only exports components. Use a new file to share constants or functions between components
|
|
Test and SonarQube / Test UI (Storybook + Unit):
client/webui/frontend/src/lib/components/chat/file/ArtifactMessage.tsx#L175
React Hook useCallback has a missing dependency: 'props'. Either include it or remove the dependency array. However, 'props' will change when *any* prop changes, so the preferred fix is to destructure the 'props' object outside of the useCallback call and refer to those specific props inside useCallback
|
|
Test and SonarQube / Test UI (Storybook + Unit):
client/webui/frontend/src/lib/components/chat/UserAvatar.tsx#L14
Fast refresh only works when a file only exports components. Use a new file to share constants or functions between components
|
|
Build and Push Image / Build linux/arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, aws-actions/amazon-ecr-login@062b18b96a7aff071d4dc91bc00c4c1a7945b076, aws-actions/configure-aws-credentials@7474bc4690e29a8392af63c5b98e7449536d5c3a, docker/build-push-action@14487ce63c7a62a4a324b0bfb37086795e31c6c1, docker/setup-buildx-action@b5ca514318bd6ebac0fb2aedd5d36ec1b5c232a2. 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/
|
|
Sensitive data should not be used in the ARG or ENV commands:
Dockerfile#L232
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "SESSION_SECRET_KEY")
More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
|
|
Build and Push Image / Build linux/amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, aws-actions/amazon-ecr-login@062b18b96a7aff071d4dc91bc00c4c1a7945b076, aws-actions/configure-aws-credentials@7474bc4690e29a8392af63c5b98e7449536d5c3a, docker/build-push-action@14487ce63c7a62a4a324b0bfb37086795e31c6c1, docker/setup-buildx-action@b5ca514318bd6ebac0fb2aedd5d36ec1b5c232a2. 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/
|
|
Sensitive data should not be used in the ARG or ENV commands:
Dockerfile#L232
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "SESSION_SECRET_KEY")
More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
|
|
Test and SonarQube / Build and Verify Packages
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, actions/setup-python@8d9ed9ac5c53483de85588cdf95a591a75ab9f55, astral-sh/setup-uv@38f3f104447c67c051c4a08e39b64a148898af3a. 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 and SonarQube / Test Python 3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, actions/setup-python@8d9ed9ac5c53483de85588cdf95a591a75ab9f55, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, mikepenz/action-junit-report@3585e9575db828022551b4231f165eb59a0e74e3. 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 and SonarQube / Test Python 3.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, actions/setup-python@8d9ed9ac5c53483de85588cdf95a591a75ab9f55, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02, mikepenz/action-junit-report@3585e9575db828022551b4231f165eb59a0e74e3. 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 and SonarQube / SonarQube Analysis
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093, sonarsource/sonarqube-scan-action@fd88b7d7ccbaefd23d8f36f73b59db7a3d246602. 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 | |
|---|---|---|---|
|
SolaceLabs~solace-agent-mesh~HUMQ7N.dockerbuild
|
121 KB |
sha256:fce550fa4c744f1c58d2a7bda5f0140ee9e55bf6d3606a352e2ab106db710c22
|
|
|
SolaceLabs~solace-agent-mesh~XCHEKO.dockerbuild
|
120 KB |
sha256:b0bc0187de8e26f205e19eaf1b4f52b2c7bec4a224b506f0e2ed67cd507220f7
|
|
|
dependency-conflict-report
|
1.02 KB |
sha256:7696518b9dad3ed0e18096fdacae86484a94440a425658da8145f410661e1668
|
|
|
prisma-cloud-scan-results-Linux-ARM64-1.20.0-c9fcc851d5-arm64
|
41.5 KB |
sha256:574dbae6e1a1db698277d6be8593f09448ba34c2305fb52014abc011c56bcfc6
|
|
|
prisma-cloud-scan-results-Linux-X64-1.20.0-c9fcc851d5-amd64
|
41.6 KB |
sha256:c35bc756fcbf3ea68b5af21d9300c8d8a3fb6c4a690f53ac0075df09a1e1dc0e
|
|
|
python-coverage-3.10
Expired
|
355 KB |
sha256:eacfa8fac2858883b5856345ba4d59b1a455bdf52bdc7201f4479920281aeca1
|
|
|
python-coverage-3.13
Expired
|
355 KB |
sha256:041edbe6cbac4f6e169283240a22328133c6ebaf57a3e6b9c852896f2d8fa7be
|
|
|
ui-coverage
Expired
|
3.25 MB |
sha256:7df3a724964f6194c1a7995bcdbf4fa2d77d665fb7419f488d3480b4134875ed
|
|