Repository navigation
Sort GPUs newest first across leaderboard pages - #270
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
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.
GPU sections and selectors currently follow database or alphabetical order, so A100 can appear before B200. Apply one shared order—B200, H100, MI300, A100, L4, T4—across leaderboard pages, homepage tiles, live rankings, submission/editor selectors, and trend GPU menus. Unknown GPU types follow alphabetically; ranking entries and scores are preserved.
Validation: production build and ESLint pass. Fetch-level checks verified ordering, unknown types, empty results, and unchanged ranking/input data. The frontend suite reports 95 passed and six failures; the exact same six failures reproduce on clean main (login, news, and profile tests).