Speed up evaluation history and add successful-run table - #70
Merged
Merged
Conversation
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
1 participant
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.
Evaluation history issued three separate metadata queries per run, causing the 13-run production history to take 75 seconds for metadata alone and exceed the browser timeout. Batch allocation, publication, and summary metadata into one query for user/admin/public lists, while retaining ownership filtering and output semantics.
Add a separate styled successful-runs table with results/transcript links above the full run history.
Validation: 101 backend tests passed (5 skipped), including a one-query history regression and owner isolation. Frontend production build and TypeScript passed.