P5.1: Eval harness — scripted, repeatable local check
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- testing
Research direction
The payload names only the agent/evals/ directory, with its golden-question runs and the eval set from #587 as dependencies. Read the existing eval set and any runner already there, then agree with maintainers on the single local command. Done means one command produces a pass/fail report per question, with diffs against the known-good answers, across the full team.
Written by the indexing model from the issue text.
Description
Part of #545 (Phase 5). Depends on P2.5 (#587 — eval set exists).
Scope
- Script the
agent/evals/golden-question runs as a repeatable local check (script-first; CI is a thin wrapper per repo workflow philosophy) - Output: pass/fail per question with diffs against known-good answers
Done when a maintainer can run one command locally and get an eval report for the full team.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 4
- Avg merge
- 1d 58m
- Merged PRs (30d)
- 65
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mieweb/ui
-
src/tailwind-preset.cjs drifted from tailwind-preset.ts — missing `info` and `chart` color scalesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
MIEUI R&D TicketOpen
Difficulty 1/5 Under an hour Newbie friendliness 8/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 22/100
Maintainers usually reply within 1 day
Similar issues
-
Unsampled pageload span is profiled when profileLifecycle is 'trace' (browser UI profiling)Possibly taken @Jxxunnn claimed this today. OpenBrowser Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
getsentry/sentry-javascript#25497 · 1 comment ·
Maintainers usually reply within 1 day
-
e2e-failure ready-to-code
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
redhat-developer/rhdh-plugin-export-overlays#4438 · 1 comment ·
Maintainers usually reply within 1 day
-
resource: destroying a resource calls AbortController.abort() without a reason, creating an AbortError with a stack trace each timePossibly taken A pull request linked to this issue is open or already merged. Openarea: core
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
angular/angular#71422 · 1 comment ·
Maintainers usually reply within 1 day
-
bug status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
facebook/docusaurus#12739 · 1 comment ·
Maintainers usually reply within 1 day
-
factory-active task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day