Skip to content
CI

docs(#48): finalize phase 1 UX layout and interaction proposal #27

Sign in to view logs

docs(#48): finalize phase 1 UX layout and interaction proposal

docs(#48): finalize phase 1 UX layout and interaction proposal #27

Triggered via pull request April 20, 2026 15:45
@OmarEhab007OmarEhab007
opened #46
feature/GH-40-ux-layout-and-interaction-proposal-for-d
Status Failure
Total duration 4m 11s
Artifacts 1

ci.yml

on: pull_request
lint-go
1m 41s
lint-go
lint-frontend
37s
lint-frontend
test-go
1m 55s
test-go
build-scan
4m 7s
build-scan
helm-lint
10s
helm-lint
Fit to window
Zoom out
Zoom in

Annotations

1 error and 17 warnings
build-scan
ERROR: Unexpected exit code [1]
helm-lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, azure/setup-helm@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/
lint-frontend
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/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/
lint-frontend: frontend/src/components/trace/span-list.test.tsx#L224
'user' is assigned a value but never used
lint-frontend: frontend/src/components/explorer/search-bar.tsx#L69
The 'suggestions' logical expression could make the dependencies of useCallback Hook (at line 147) change on every render. To fix this, wrap the initialization of 'suggestions' in its own useMemo() Hook
lint-frontend: frontend/src/components/explorer/search-bar.test.tsx#L9
'fireEvent' is defined but never used
lint-frontend: frontend/src/components/explorer/log-table.test.tsx#L9
'within' is defined but never used
lint-frontend: frontend/src/components/explorer/filter-panel.test.tsx#L18
'defaultProps' is assigned a value but never used
lint-frontend: frontend/src/components/dashboard/time-series-chart.tsx#L26
'LOG_TYPE_COLORS' is defined but never used
lint-frontend: frontend/src/components/ai/message-view.test.tsx#L11
'userEvent' is defined but never used
lint-frontend: frontend/src/components/ai/chat-input.test.tsx#L93
'user' is assigned a value but never used
lint-frontend: frontend/src/app/(dashboard)/analysis/page.tsx#L366
The 'jobs' logical expression could make the dependencies of useMemo Hook (at line 384) change on every render. To fix this, wrap the initialization of 'jobs' in its own useMemo() Hook
lint-frontend: frontend/src/app/(dashboard)/analysis/page.tsx#L366
The 'jobs' logical expression could make the dependencies of useMemo Hook (at line 375) change on every render. To fix this, wrap the initialization of 'jobs' in its own useMemo() Hook
lint-go
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/setup-go@v5. 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/
lint-go
Restore cache failed: Dependencies file is not found in /home/runner/work/RemedyIQ/RemedyIQ. Supported file pattern: go.sum
test-go
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/setup-go@v5. 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-go
Restore cache failed: Dependencies file is not found in /home/runner/work/RemedyIQ/RemedyIQ. Supported file pattern: go.sum
build-scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, gitleaks/gitleaks-action@v2. 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
gitleaks-results.sarif
6.61 KB
sha256:f5f79cb430fa0db53163b9fc4c869aab02c0bc30405b6cfba4f94d062a0be1c7