Last 12 weeks · 40 commits
2 of 6 standards met
What Changed The dashboard chart now renders a placeholder while is being fetched, and surfaces the fetch error if the request fails. Previously it rendered in both cases, making the page look broken on slow networks and on real failures. The chart's empty-state text is unchanged. It still appears once the fetch completes successfully with zero records. Why initializes with and falls back to an empty array until the fetch resolves (). That empty array was passed straight to , which has no way to distinguish "still fetching" from "fetched, no data" and so always renders . Gating the chart on at the call site mirrors the existing pattern used by for its loading and error branches. UI Changes Before: chart area shows for the entire fetch window. After: chart area shows during fetch (and the error message on failure). Checklist [x] This PR is small and focused [x] I explained what changed and why [x] I included before/after screenshots for any UI changes The PR was formatted this way because I just used the same template as T3code for clarity (since you already review PRs there). Hope you don't mind! :)
Summary Added custom date-range filtering controls to the benchmark chart view. Updated the client to filter charted benchmark runs dynamically based on the selected range. Simplified the benchmark data payload by removing an embedded historical snapshot no longer needed by the app. Testing Not run (not requested). Reviewed the diff to confirm the chart range state flows through the UI and server data handling. Confirmed the change is limited to the chart view and benchmark data source cleanup.
Repository: t3dotgg/azure-bench. Description: Showing azure foundry's awful perf on openai models Stars: 31, Forks: 2. Primary language: TypeScript. Languages: TypeScript (98.9%), CSS (0.7%), HTML (0.4%). License: MIT. Open PRs: 1, open issues: 0. Last activity: 2mo ago. Community health: 42%. Top contributors: t3dotgg.