Spaces:
Running
Running
Commit History
28 days ago
-
Sync from evaleval/eval-cards via hub-sync
Verified signaturea3005bd
-
Update to uniform US spelling
2fd6a71
-
Use slash-form path for in-page model navigation (drop %2F from URL)
The two router.replace calls on the model detail page navigated to the raw %2F-encoded route_id, leaking `/models/openai%2Fgpt-4o` into the address bar on variant/query changes. Wrap in routeIdToPath so they match the slash-form links the rest of the app already emits. Verified: /models/openai/gpt-4o resolves 200 (catch-all + routeIdFromSegments round-trip) — no backend change.73cce97 -
Add per-model + per-eval OpenGraph thumbnails; replace "EE/EC" mark with logo image
Social/chat unfurls now identify the specific model or benchmark being shared instead of showing the generic homepage card. - /api/og/models/[...id] and /api/og/evals/[...id] render dynamic 1200x630 PNGs via next/og's ImageResponse, pulling display name / developer / category / models-evaluated / top-model from the existing DuckDB-backed summary getters. Cards include the EvalEval brand logo (logo-square.png) in place of the previous text mark. The handlers live under /api/og/ rather than as `opengraph-image.tsx` siblings because Next.js 15 rejects metadata files inside catch-all (`[...id]`) folders. - app/models/[...id]/layout.tsx and app/evals/[...id]/layout.tsx own the `generateMetadata` for those routes (the page components are client-side, so they can't export metadata directly). The layouts also seed the per-entity `title`/`description`/`og:image`/`twitter:image` so non-image unfurls also identify the entity. - app/opengraph-image.tsx swaps the inline "EE" te…c315a26 -
Untrack accidentally-committed noise files; gitignore the patterns
The previous commit (b6dab21) pulled in several files that should not be tracked: - "(1).tsx" — Finder duplicates of route files - output/hierarchy_explorer.html — local probe output - public/peer-ranks.json — local-generated cache (~370k lines) - app/embed/eval/distribution/[...id]/page.tsx — orphan route Remove from the index and extend .gitignore so they can't sneak back through a `git add -A` or accidental wildcard. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>445ce35 -
view-data: paranoid CAST every output column to a primitive type
The previous patch left simple scalars (VARCHAR / BOOLEAN / DOUBLE / INTEGER) untouched, on the assumption the binding handles those natively. The deployed log still surfaces "Invalid Error: don't know what type:" on the new explicit-column SELECT, which means whatever the binding is choking on is reachable even without r.* expansion and even with every nested type wrapped. The only thing left to vary is whether the binding ever sees the parquet's native logical types at all. Force every output column through `CAST(... AS <primitive>)`. The binding now only ever sees VARCHAR / BOOLEAN / INTEGER / DOUBLE in the result schema regardless of what type the underlying parquet column declared. Local prod build keeps returning 200 on /api/model-summary with model_info correctly nested. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>b6dab21
-
Cross-source dedup, plotbox polish, pretty URLs, eval page fallbacks
Model page (benchmark-detail.tsx) — cross-source grouping rework: - Category-mode tiles dedupe per benchmark canonical (8x MMLU-Pro across helm/vals-ai/openeval/… → 1 tile + cross-family whisker overlay), with an "N sources" badge. - Fixed benchmarkIndexLookup to prefer benchmark canonicals over umbrella entries (suite/aggregator) when building eval_summary_id → canonical_key. Without that, ids like artificial-analysis-llms/mmlu-pro mapped to "artificial analysis" instead of "mmlu-pro" and dedup leaked. - Aggregator-only score dedup: byte-equal scores from llm-stats are dropped (republished canonical numbers) but two independent evaluators arriving at the same number both stay — confirming signal, not duplicate data. Plus an eval_summary_id dedup before score dedup so the same observation listed under two family_keys in benchmark_index doesn't double-count. - Multi-category bucketing: a benchmark with curated tags ["general", "re…0b45710