githubnext / githubnext/gh-aw-cao

Dashboard view assessment

Closed
#12,218 0 comments 0 reactions 0 assignees View on GitHub
self-care
Dominant language
JavaScript
Stars
3
Forks
1
Avg merge
49m
Merged PRs (30d)
837

Description

### Dashboard view assessment
**0/2** views passed the informational assessment. The DOM budget is **6000** nodes per loaded view.
Assessment blocker: browser.newPage: Target page, context or browser has been closed
| View | Result | DOM nodes | Findings |
|---|---:|---:|---|
| operations | failed | unknown | 1 browser error(s); 174 failed request(s) |
| readiness | failed | unknown | 1 browser error(s); 152 failed request(s) |
[View the workflow run](https://github.com/githubnext/gh-aw-cao/actions/runs/35124826329).

**Action:** Assign this issue to Copilot using the agent prompt below; accept the fix when the affected views pass the assessment.

Agent prompt

Investigate and fix the dashboard view assessment findings reported in this issue.

1. Download the `dashboard-views` artifact from https://github.com/githubnext/gh-aw-cao/actions/runs/35124826329 and inspect `summary.json` for the affected page IDs, browser errors, failed requests, missing views or data sources, and DOM-budget violations.
2. Reproduce the findings from the repository root with `DASHBOARD_DATA_URL=https://githubnext.github.io/gh-aw-cao/cao/payload-hashes.json npm run test:e2e:dashboard-views`; use `DASHBOARD_PAGE_IDS` to narrow the run when appropriate.
3. Trace each failure through the declarative view, canonical data adapter and normalization, query worker, and view payload stages. Do not add a JavaScript-based dashboard view or treat browser IndexedDB as an authority.
4. Make the smallest root-cause fix and add or update focused regression coverage.
5. Validate the affected assessment plus `npm test`, `npm run lint`, and `npm run typecheck` from `dashboard/site/`.

Contributor guide

Open the contributing guide

Research direction

Download the dashboard-views artifact and inspect summary.json, then reproduce with DASHBOARD_DATA_URL and the dashboard-views end-to-end command from the repository root. Trace failures through the declarative view, canonical data adapter and normalization, query worker, and view payload stages. Done means the affected views pass, focused regression coverage is updated, and npm test, npm run lint, and npm run typecheck pass from dashboard/site/.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.