Spaces:
Running
Running
Commit History
-
Apply adversarial-review fixes to the merged page and API route
- Source narrower: 'All sources (merged)' now clears the ?source pre-highlight instead of being a dead option. - eval-summary route: merged lookup failures degrade to the per-source lookup/404 instead of a 500 (connection-reset race on the optional merged table). - hasMergedEvalsView: only cache the positive probe, so a transient init failure of the optional parquet can't pin merged pages to 'absent' for the process lifetime. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>10276e4 -
Add merged-benchmark accessor + API routing (spec F1)
getMergedBenchmarkSummary reads the new merged_evals_view row and the observation-grain leaderboard live from eval_results_view on metric_id_effective, sorted by score_canonical in the metric's direction. Echo rows are kept — the accessor never calls dedupeLeaderboardRowsByModelIdentity (design pt 3/Q3) — and eval-matrices.json is not consulted. Slice-grain pages (design pt 7b) query the slice's own benchmark_id with is_slice. merged_evals_view loads best-effort at connection init so pre-merged snapshots keep working; the accessor probes the catalog and returns null when the artifact is absent. /api/eval-summary resolves single-segment ids (no %2F after routeIdFromSegments normalization — the new isMergedEvalId helper) through the merged accessor with ?metric=/?slice= params, returning a { merged: true } discriminated payload; two-segment ids keep the existing path byte-identical. fetchEvalSummary adapts merged payloads to the BenchmarkEvalSummary shape so the eval embeds render merg…0fd9809
-
Add DuckDB shadow-read backend with source-metadata fix
Jenny Chim +1: Claude Opus 4.7 (1M context)Two-part change behind a feature flag. Backend dispatcher (lib/data-backend.ts) routes 11 API routes + app/page.tsx to either lib/model-data.ts (default JSON path) or the new lib/duckdb-data.ts based on DATA_BACKEND=duckdb. The DuckDB path reads payload_json from local Parquet via @duckdb/node-api; pipeline-side export is gated by EXPORT_EXPERIMENTAL_PARQUET=1 (lives in eval_cards_backend_pipeline). For parity testing, lib/hf-data.ts gains HF_DATA_LOCAL_DIR (override the default .cache/hf-data path) and HF_DATA_OFFLINE=1 (refuse remote fetches so background refreshes can't poison parity tests). scripts/compare-data-backends.mjs diffs the two backends endpoint-by-endpoint. Source-metadata fallback (item #4 in notes/ts-to-pipeline-migration.md) deleted: pipeline now carries source_metadata on every model_result row (verified 86,183/86,183 production hierarchy + 43,859/43,859 eval-detail). Removed getCanonicalSourceMetadata, buildSourceMetadataIndex, and three inline duplicates in lib/…2fcae3f
-
redesigned
3a12290
