Allow contests and analyses to continue indefinitely
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1k
- Forks
- 412
- Avg merge
- 6d 10h
- Merged PRs (30d)
- 3
Description
The outline of the proposal:
- we retain the current fields: contest_{start,stop}, analysis_{enabled,start,stop}
- all timestamps are nullable meaning "extending indefinitely in that direction"
- contest_stop = null => analysis_enabled = False
- analysis_enabled = False => analysis_start = null and analysis_stop = null
- analysis_enabled = True => analysis_start != null
- whenever non-null, contest_start <= contest_stop <= analysis_start <= analysis_stop
(probably the conditions can be simplified a bit, this is just for illustrative purposes)
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
The issue names no files or tests. Start by locating the contest_start, contest_stop, analysis_enabled, analysis_start, and analysis_stop fields, then trace their validation and scheduling behavior; done means nullable timestamps support indefinite ends while the listed implications and ordering constraints hold.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100