Repository navigation
Show build compute and self-reported production costs on problem pages - #105
Merged
Merged
Conversation
Collaborator
Author
|
Prerequisites: merge/deploy https://github.com/leanprover/lean-eval-state/pull/51 and leanprover/lean-eval-submissions#2163 before this consumer. The Worker also depends on https://github.com/leanprover/lean-eval-state-staging/pull/25. This PR targets main. Production now requests projection v7 and links to the new owner editor, so deploy the producers first. PR builds continue to use public base Results without private State credentials. |
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.
Problem pages omit acceptance-build compute costs and useful submitter production details. Add separate Measured by LeanEval and Production information — self-reported displays, plus sortable per-problem comparisons. Wall times are labeled very noisy, unavailable counters have explicit reasons, and zero remains distinct from missing data. Existing standings and ranking rules are unchanged.
The consumer reads public State v7, prefers an available acceptance measurement (otherwise the latest successful replay), and links owners to the authenticated metadata editor. Current fields retain the date they actually changed; removed and superseded metadata text is not republished. Optional stray, malformed, duplicate or mismatched receipts are skipped with a diagnostic, preserving accepted-result publication. The site keeps its output schema checks without another copy of the producer's hash validator or canonical contract tests. Earlier public projection schemas remain unchanged.
Prerequisites: https://github.com/leanprover/lean-eval-state/pull/51 and leanprover/lean-eval-submissions#2163. Merge/deploy those producers before this consumer. See
docs/compute-reporting.md. Historical replay remains separate operator work.Validation: 89 Python tests, four Node behavior tests, workflow actionlint, and complete real Results/current-State-v7 generation and output validation. Regression tests cover field-level dates and accepted results surviving optional-statistics errors. Pages CI performs the full build; no production deployment is performed by this PR.