-
Notifications
You must be signed in to change notification settings - Fork 785
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Prize Money to Challenges #3893
Comments
Hi @gchhablani |
@gchhablani What's difference between 'prize_amount' and 'amount' in model? |
@b9aurav My bad, they are the same thing. |
@gchhablani hey i would also like to work on this issue? can i start working on this as you have assigned this one already ? |
@ADITYA97-CODER Can you please take up one of the other issues? |
@gchhablani sure . Can you assign me "contacting host using a form issue" |
@gchhablani I've done my coding part, Now I am struggling in hosting a challenge locally to test it. Workflow error log for Workflow error log for '127.0.0.1:8888' I am guessing, there's another way to host challenge locally (For testing purpose). |
@b9aurav I had the same problem and I fixed by creating a script to test the challenges locally you can refer to my pull request here It include script along with the documentation. It will solve your issue |
@AyushR1 Thanks, I'll definitely give it try |
@gchhablani It seems like my pull request #3906 build failed due to test case failure, Do I need to add test cases along with my other commits? |
Description
Currently it is difficult to find know which challenges have prizes, and if yes, what are the first/second/thrid prizes, etc. This feature will help us understand which challenges on EvalAI have prizes. The idea is to add a new prize money section here:
There are several components to be designed here:
ChallengePrizes
with the following details:has_prizes
in the Challenge model.create_or_update_github_challenge
function to update the challenge and the entries.Pre-requisites/Learnings
This issue essentially requires background on a few things:
How to Approach
The text was updated successfully, but these errors were encountered: