Identify old submission results
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1k
- Forks
- 412
- Avg merge
- 6d 10h
- Merged PRs (30d)
- 3
Description
If an admin changes something in a task (read: dataset after they are merged), there is no way to discern the submission results that were computed with the new task/dataset data and those computed after. Proposal: add an "up_to_date" field in the submission results table to be flipped when something changes in the task/dataset, and allow admins to re-evaluate only those submission.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how submission results are stored and how task or dataset changes are handled, then inspect the admin re-evaluation flow. Done means administrators can distinguish results computed with outdated task or dataset data and selectively re-evaluate those submissions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100