cms-dev / cms-dev/cms

rerun and archive changes submission results

Open
#1,707 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1k
Forks
412
Avg merge
6d 10h
Merged PRs (30d)
3

Description

Issue template

Currently, when clicking on Rerun and Archive button in AWS, a re-evaluation is done on the submission and the result replaces the previous one. Therefore the contestant's score can simply change (e.g. in case of a randomized solution). This is undesirable as this button is used for debugging during which we usually are not sure if we want to do any intervention.

Optimally, we want this button to do the re-evaluation without changing the current SubmissionResult.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the Rerun and Archive button flow in AWS and how it re-evaluates a submission and updates SubmissionResult. Done means debugging re-evaluation still occurs, while the contestant's current SubmissionResult remains unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, python
Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.