fix: Remove invalid evaluation sets#424
Merged
Merged
Conversation
…T_SET_ID_WITH_GOOD_DATA constant
ibraheem-abe
approved these changes
Jul 17, 2026
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
2 participants
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.
Summary
This PR updates the
/evaluation-setsendpoints to only look at the evaluation sets that have "good data". This was already done by theGET /problem-statisticsendpoint using a constantEARLIEST_SET_ID_WITH_GOOD_DATAdefined at the top of the fileapi/endpoints/statistics.py.This constant is now a config variable, this way it is defined in one place and it can be updated without needing to re-deploy the application.