Cloud-CV / Cloud-CV/EvalAI

Add constraints for setting challenge phase start and end date

Open
#1,558 16 comments 0 reactions 0 assignees View on GitHub
backend easy_to_fix enhancement good first issue GSOC-2025 priority-high
Dominant language
Python
Stars
2k
Forks
984
Avg merge
2h 54m
Merged PRs (30d)
14

Description

## Current Observation

Challenge hosts can set the challenge phase start and end date to anything irrespective of the challenge start and end date.

## Deliverables

Add the following checks in proper places in the codebase (i.e some/all of these things would go in the ChallengePhase `save()` method)
- [ ] Challenge phase start datetime >= Challenge start datetime
- [ ] Challenge phase start datetime < Challenge end datetime
- [ ] Challenge phase end datetime > Challenge start datetime
- [ ] Challenge phase end datetime <= Challenge end datetime
- [ ] Challenge phase start datetime < Challenge phase end datetime
- [ ] Add check if Challenge start datetime < Challenge end datetime

## Goal
- [ ] Can you open a new PR using this PR (https://github.com/Cloud-CV/EvalAI/pull/2020) and verify that it behaves as expected in all relevant scenarios before we proceed with merging?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.