never ending phase has null status

[lbeziaud]

Hi,

Phases without without end date have "status": null (example). Apparently this sometimes breaks submission, with the submission form not being available to users. I have not experienced that (I'm an admin on tested competitions) but it was reported by two participants here. This was "solved" on this particular challenge by setting an end date. Participant were not able to submit before, except on some unknown occasion (ending date was added on June 8, some submissions could be made on June 7, but reports were made after and before those submissions…).

The issue might be related to this line:

codabench/src/static/riot/competitions/detail/submission_upload.tag

Line 3 in b43105a

show="{_.get(selected_phase, 'status') === 'Current' || opts.is_admin}">

but a better fix would be to have "status": "Current" for phases without an end date. This could also be the result of an issue with the phase indexing.

Thank you @BrunetNathan for the initial report

[ihsaan-ullah]

Trying to reproduce this issue. Here are some more details

Competition with NO end date.

Situation 1: I am the admin of the competition:

Previous Phase

• Phase status: NULL
• End date : OK
• Can submit: NO(Phase ended, warning message: YES)

Current Phase

• Phase status: NULL
• End date : NULL
• Can submit: YES

Situation 2: I am a participant of the competition:

Previous Phase

• Phase status: NULL
• End date : OK
• Can submit: NO(Phase ended, warning message: NO)

Current Phase

• Phase status: NULL
• End date : NULL
• Can submit: NO

What should we see

1. Actual phase status (Previous, Current, Next)
2. Warning message for ended phases or not started phases
3. participant should be able to submit to current phase