[PR #18] [MERGED] Frontend tab: show the custom-node packs that run on GPU #17

Closed
opened 2026-10-31 22:06:03 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/Comfy-Org/comfyci-dashboard/pull/18
Author: @marawan206
Created: 10/20/2026
Status: ✅ Merged
Merged: 10/20/2026
Merged by: @marawan206

Base: main ← Head: frontend-packs-on-gpu


📝 Commits (1)

  • bf92654 Frontend tab: show the custom-node packs that run on GPU

📊 Changes

8 files changed (+700 additions, -11 deletions)

View changed files

📝 README.md (+1 -1)
📝 components/frontend/FrontendKpis.tsx (+50 -4)
➕ components/frontend/PacksOnGpu.tsx (+333 -0)
📝 pages/frontend/index.tsx (+9 -4)
📝 src/frontend/client.ts (+81 -2)
➕ src/frontend/packs.ts (+211 -0)
📝 src/regression/client.ts (+8 -0)
📝 src/regression/types.ts (+7 -0)

📄 Description

What

The core GPU regression runs KJNodes, VideoHelperSuite, Impact-Pack and Manager on every core commit (comfyci-runpod-worker#13), but the results only showed on the Regression tab's cu130 lane. The Frontend tab is where the frontend team looks, so it now shows them too:

  • A fourth KPI card, Packs on GPU: pack workflows passing in the newest run of the lane, with the core commit and the run age. Green when all pass, amber for drift, infra or missing baselines, red when a workflow fails or a pack does not import.
  • A Custom-node packs on GPU section right under the CPU gate: one row per pack workflow with its latest verdict badge, the last runs as dots (oldest to newest, each linking to its commit page), exec time, golden tag, and each pack's import status plus its pinned commit (label and short sha linking to GitHub, read from the worker's manifest/custom_nodes.json).
  • Lanes and workflows are discovered from the published index (any lane whose newest entry carries pack status), nothing is hardcoded; the registry is fetched from a fixed URL and every repo and sha is validated before it becomes a link.

Verification

npx tsc --noEmit, pnpm lint, pnpm build pass. Rendered with live data: 4 of 4 pack workflows green, five packs ok with their pin links; phone width keeps the table inside its scroll container; dark and light mode checked.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/Comfy-Org/comfyci-dashboard/pull/18 **Author:** [@marawan206](https://github.com/marawan206) **Created:** 10/20/2026 **Status:** ✅ Merged **Merged:** 10/20/2026 **Merged by:** [@marawan206](https://github.com/marawan206) **Base:** `main` ← **Head:** `frontend-packs-on-gpu` --- ### 📝 Commits (1) - [`bf92654`](https://github.com/Comfy-Org/comfyci-dashboard/commit/bf92654c6a6936bae96dcab796f0418b743ffebe) Frontend tab: show the custom-node packs that run on GPU ### 📊 Changes **8 files changed** (+700 additions, -11 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -1) 📝 `components/frontend/FrontendKpis.tsx` (+50 -4) ➕ `components/frontend/PacksOnGpu.tsx` (+333 -0) 📝 `pages/frontend/index.tsx` (+9 -4) 📝 `src/frontend/client.ts` (+81 -2) ➕ `src/frontend/packs.ts` (+211 -0) 📝 `src/regression/client.ts` (+8 -0) 📝 `src/regression/types.ts` (+7 -0) </details> ### 📄 Description ## What The core GPU regression runs KJNodes, VideoHelperSuite, Impact-Pack and Manager on every core commit (comfyci-runpod-worker#13), but the results only showed on the Regression tab's cu130 lane. The Frontend tab is where the frontend team looks, so it now shows them too: - A fourth KPI card, **Packs on GPU**: pack workflows passing in the newest run of the lane, with the core commit and the run age. Green when all pass, amber for drift, infra or missing baselines, red when a workflow fails or a pack does not import. - A **Custom-node packs on GPU** section right under the CPU gate: one row per pack workflow with its latest verdict badge, the last runs as dots (oldest to newest, each linking to its commit page), exec time, golden tag, and each pack's import status plus its pinned commit (label and short sha linking to GitHub, read from the worker's `manifest/custom_nodes.json`). - Lanes and workflows are discovered from the published index (any lane whose newest entry carries pack status), nothing is hardcoded; the registry is fetched from a fixed URL and every repo and sha is validated before it becomes a link. ## Verification `npx tsc --noEmit`, `pnpm lint`, `pnpm build` pass. Rendered with live data: 4 of 4 pack workflows green, five packs ok with their pin links; phone width keeps the table inside its scroll container; dark and light mode checked. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 22:06:03 +00:00
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Comfy-Org/comfyci-dashboard#17
No description provided.