Repository navigation
Runs and details on results (#130 step 4, light version) - #144
Merged
Merged
Conversation
No second table: a run is results sharing a run_id. - Migration 20261118120000: model_repo, model_file, model_sha256, decode_tps_min, decode_tps_max (browser-writable, reset verification) and run_id (set only by PR ingestion and the API batch route). - Result files may hold a points list: one result per point, sharing the file's other fields and a run id. The parser reads each point as a full result and names shared problems once. - POST /results/batch takes sameRun to put its items in one run. - Submit form, result card, schema, README, agent docs and prompt.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
✅ The catalog validates: 85 hardware, 54 models, 29 quants, 13 runtimes. Once merged, the entry is synced to the database automatically and shows up on the site with the next deploy. Format notes are in frontend/src/catalog/README.md. |
No submission files to import. |
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Step 4 of #130, the light version agreed on: runs go on top of the results table instead of a second table. Stacked on #143 (the protocol), so merge that one first. Until then, its commit also shows here.
What changes
Database (migration `20261118120000_result_runs`)
Result files
API: `POST /results/batch` accepts `sameRun: true`. Results carry `runId`, and the five detail fields round-trip.
UI: the submit form has slowest/fastest run fields and model repository/file/SHA-256 fields. The result card shows the range under the headline number and the model file under Model. The legacy PR preview prefills from the first point and says how many points the file holds.
Docs: README (field table, One run, several points, and the protocol now uses the fields instead of `notes`), schema.json, agent API intro and agent prompt.
Tests
Rollout
After merge: `supabase db push` for `20261118120000`. No backfill is needed; existing rows keep null. The rig-page curve that uses `run_id` and `inputTokens` comes in a follow-up PR.