Skip to content

Open views on the window that has data; group duplicate issues; mark unchecked runs - #76

Merged
architsharm merged 1 commit into
mainfrom
claude/empty-states
Oct 9, 2026
Merged

architsharm merged 1 commit into
mainfrom
claude/empty-states

Conversation

@architsharm

Copy link
Copy Markdown
Owner

Found by testing the deployed dashboard: the workspace's last traffic was 18 days ago, so every view (which opened on 7 days) showed "No requests".

  • Views open where the data is. New GET /api/metrics/activity returns the last request and the smallest range (7d/30d/90d) that holds it. Pages with no range in the URL redirect to it; Home and Agents use it and label the window ("Requests · 30 days").
  • Issues: identical rows grouped with a count (legacy findings without fingerprints never merged: ~30 copies of "unpinned server" in production).
  • Packs with 0 rules no longer listed as "watching" on Policies and Home.
  • Runs with no checks read "Not checked" instead of "Allowed" (checks added to the traces API).

Tests: gateway + platform suites (571), repo checks (141), dashboard vitest (67), typecheck, ruff, import-linter. Wheels rebuilt.

🤖 Generated with Claude Code

…unchecked runs

Found testing the deployed dashboard: a workspace whose last traffic was
three weeks ago showed "No requests" on Home, Observe, Runs, Policies and
every agent, because every view opened on the last 7 days.

- GET /api/metrics/activity: the latest request and the smallest range
  (7d, 30d, 90d) that holds it. Views with no range in the URL redirect to
  it; Home and the Agents list use it directly and say which window.
- Filter links keep the range explicit, so choosing 7d sticks.
- Issues: identical issues are one row with a count (findings raised before
  fingerprints existed were never merged; ~30 duplicate rows in production).
- Policies and Home: packs with no rules are not listed as "watching".
- Runs: a run with no checks (telemetry only) reads "Not checked", not
  "Allowed"; the traces API returns `checks` per run.

Co-Authored-By: Claude <noreply@anthropic.com>
@vercel

vercel Bot commented Oct 9, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
guardrails-api Ready Ready Preview Oct 9, 2026 1:01am UTC
guardrails-dashboard Ready Ready Preview Oct 9, 2026 1:01am UTC
guardrails-redteam-lang Ready Ready Preview Oct 9, 2026 1:01am UTC

This branch was successfully deployed

3 active deployments
Preview – guardrails-redteam-lang — 0237fc3f Deployed Oct 9, 2026 by vercel[bot]
Preview – guardrails-api — 0237fc3f Deployed Oct 9, 2026 by vercel[bot]
Preview – guardrails-dashboard — 0237fc3f Deployed Oct 9, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant