Skip to content

feat(medium): Optimize Spotify Track Selection UI for High Density #8239

feat(medium): Optimize Spotify Track Selection UI for High Density

feat(medium): Optimize Spotify Track Selection UI for High Density #8239

Triggered via issue March 26, 2026 03:43
@ariiarii
commented on #9547 4090c4b
Status Failure
Total duration 1m 14s
Artifacts

comment-ops.yml

on: issue_comment
🔍 Route Comment
3s
🔍 Route Comment
execute-review  /  Analyze Changes for Review
5s
execute-review / Analyze Changes for Review
execute-review  /  disabled-guidance
0s
execute-review / disabled-guidance
prepare-coder
0s
prepare-coder
prepare-review-issues-manual
0s
prepare-review-issues-manual
prepare-resolve
0s
prepare-resolve
execute-squash  /  squash-and-rebase
execute-squash / squash-and-rebase
init-status
6s
init-status
execute-help
0s
execute-help
execute-triage  /  disabled-guidance
execute-triage / disabled-guidance
execute-triage  /  maintenance
execute-triage / maintenance
execute-triage  /  triage
execute-triage / triage
execute-enrich  /  Enrich PR Title and Description
execute-enrich / Enrich PR Title and Description
execute-review  /  Post Skip Check
0s
execute-review / Post Skip Check
execute-review  /  Execute Gemini Review
39s
execute-review / Execute Gemini Review
execute-coder  /  ai-developer
execute-coder / ai-developer
execute-coder  /  disabled-guidance
execute-coder / disabled-guidance
execute-create-review-issues  /  Create Issues from Gemini Review
execute-create-review-issues / Create Issues from Gemini Review
execute-create-review-issues  /  disabled-guidance
execute-create-review-issues / disabled-guidance
execute-resolve  /  merge_and_resolve
execute-resolve / merge_and_resolve
execute-squash  /  check-for-changes-after-squash
execute-squash / check-for-changes-after-squash
execute-squash  /  trigger-ci-workflow
execute-squash / trigger-ci-workflow
execute-review  /  Manage PR Labels
6s
execute-review / Manage PR Labels
📝 Prepare Issue Context
0s
📝 Prepare Issue Context
finalize-status
3s
finalize-status
🚀 Create Review Issues  /  Create Issues from Gemini Review
🚀 Create Review Issues / Create Issues from Gemini Review
🚀 Create Review Issues  /  disabled-guidance
🚀 Create Review Issues / disabled-guidance
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 6 warnings
execute-review / Execute Gemini Review
Process completed with exit code 1.
execute-review / Manage PR Labels
Process completed with exit code 1.
execute-review / Manage PR Labels
Unable to download artifact(s): Artifact not found for name: review-result Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact. For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
execute-review / Analyze Changes for Review
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 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/
execute-review / Analyze Changes for Review
Could not resolve SHAs for PR #9547; SHAs will be empty
init-status
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: peter-evans/create-or-update-comment@v4. 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/
execute-review / Execute Gemini Review
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 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/
execute-review / Manage PR Labels
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 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/
finalize-status
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: peter-evans/create-or-update-comment@v4. 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/