Cloud-CV / Cloud-CV/EvalAI

[Backend] Add start evaluation worker function call in challenge creation using github API

Open
#3,313 9 comments 0 reactions 0 assignees View on GitHub
backend easy_to_fix GSOC-2021
Dominant language
Python
Stars
2k
Forks
984
Avg merge
2h 54m
Merged PRs (30d)
14

Description

### Description

When a challenge is created using github based challenge creation pipeline, follow the steps mentioned [here](https://github.com/Cloud-CV/EvalAI-starters#create-challenge-using-github) to use the set up, we don't automatically start evaluation workers for the challenge. We should make a `start_worker` celery task call when a new challenge is created using github based set up. [Here's](https://github.com/Cloud-CV/EvalAI/blob/master/apps/challenges/views.py#L1472) the reference to how we are doing it for challenge creation using zip file.

### Deliverable

- [x] Backend API changes to trigger `start_workers` celery task when challenge is created using github based setup.

Contributor guide

Open the contributing guide

Research direction

Start in apps/challenges/views.py around line 1472 and compare the existing zip-based challenge creation flow with the GitHub-based setup described in EvalAI-starters. Verify where challenge creation completes and confirm that the start_workers Celery task is triggered for GitHub-created challenges.

Written by the indexing model from the issue text.

Assessment

Tech stack
django, github, python
Domain
api, backend
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.