EvalAI Invalid Challenge creation using space

Invalid Challenge creation using space

Open viditjain08 opened this issue 6 years ago • 13 comments

Issues to be fixed

[ ] When a user tries to create a challenge, if he uploads an invalid file ( zip without YAML) or any other format, the user gets an error but the files are stored in challenge configurations.
[ ] This can result in large consumption of disk space and can be exploited by the users.

Jan 22 '18 05:01 viditjain08

@viditjain08: Thanks for the catch. This is in our todo list for the next quarter. Please feel free to work on this issue.

Jan 23 '18 22:01 deshraj

Also just to let you know about another issue related to the challenge creation process. Currently the challenge creation happens in this process:

Step 1: User uploads the zip file Step 2: All the fields get populated in the database Step 3: EvalAI Admin tests the challenge on test server Step 4: Admin approves the challenge is everything looks ok. Step 5: Challenge becomes public.

We actually want to change the process to something like this:

Step 1: User uploads the zip file Step 2: EvalAI Admin tests the challenge on test server Step 3: Admin approves the challenge is everything looks ok. Step 4: All the fields get populated in the database Step 5: Challenge becomes public.

Let me know if you want to work on this issue. You can start working on this after you are done with the current issue.

Jan 23 '18 22:01 deshraj

Yes, sure, I will, after this

Jan 24 '18 03:01 viditjain08

This issue is still open. If someone is interested, please feel free to take this issue.

Sep 12 '18 00:09 deshraj

@Abhi-1198 Sure, go ahead. Please do let us know if you face any issues.

Jan 10 '19 08:01 deshraj

Sure!, I'll keep you posted!