zhiminy/EvalEng huggingface dataset:
Repository: Cloud-CV/EvalAI
Issue: Add a Cookie Consent 
GitHub labels: enhancement

easy_to_fix

GSoC-2020

frontend_v2

Currently we don't show the user the cookies consent which might make us non compiling to the international regularities . We should have a cookies consent display below for new users

Can i work on this?

Hi @Suryansh5545 @Sanji515 . This can be fixed by adding ngCookies module in the app.js. I would like to take up this issue. Please, let me know if the addition of cookie consent is needed. Thanks!

Hi @Abhi58 , Sure, you can work on this issue.

@Abhi58 are you working on this issue?

I created a new user and still don't get any cookie consent message , @RishabhJain2018  can i take up this issue.
I was thinking of using the ngx-cookieconsent library for this what are your views regarding this.

Is Anyone currently working on this issue. I want to work on this issue. It will be grateful if someone can guide me I want to contribute to this issue
Repository: Cloud-CV/EvalAI
Issue: EvalAI nav is not responsive

# Current Behavior
The EvalAI mobile view looks like this now
![Screenshot_20200116-121134](https://user-images.githubusercontent.com/35180217/72520470-d3825400-3859-11ea-8f9f-8b21c3b0f665.png)

# Expected behavior
It should be responsive on mobile view


@nsjcorps Are you talking about those forum, docs and log out button?

Yes @Suryansh5545 and also "all-challenges"

@nsjcorps Actually there is a issue #2553 about it and a pr to close it #2563 .
I think this issue can be closed now.

O alright. Thanks for the info @Suryansh5545
Repository: Cloud-CV/EvalAI
Issue: Editing team name adds data to other fields

- the expected behaviour:-
The data should not be automatically entered into the field creating a participant new team
- the observed behaviour:-
the data of user is automatically added to the field of creating a participant new team
![ezgif com-video-to-gif](https://user-images.githubusercontent.com/34577232/72522034-af873880-3882-11ea-8ae3-19cc558f719a.gif)

- steps to reproduce the problem:-
1.Try to edit the participant team name

Can i work on it?



@Suryansh5545 Can i work on this,please?

@Kajol-Kumari yea sure go for it:+1:
Repository: Cloud-CV/EvalAI
Issue: Update paper link on landing page and README

Currently the paper link in README and the landing page points to the arxiv version. Recently, the paper was accepted at AI Systems Workshop at SOSP 2019. We want to update the link and bibtext to that. 

Here is the updated link: http://learningsys.org/sosp19/assets/papers/23_CameraReadySubmission_EvalAI_SOSP_2019%20(8)%20(1).pdf

I'd like to work on this! @deshraj 

Sure @bosecodes
Repository: Cloud-CV/EvalAI
Issue: Remove tests.py from all the django apps
GitHub labels: enhancement

GSOC-2019

easy_to_fix

backend

We have all the unit and integration tests in `tests/` directory. Hence, don't need the `tests.py` file in all django apps. 

@deshraj I would like to take a stab at the issue.

Sure, go ahead. :-)

@souravsingh : it will be great if you remove `tests/test_dummy.py` :)
Repository: Cloud-CV/EvalAI
Issue: Admin Dashboard don't give correct count of host and participant teams
Root cause: Algorithmic Error


After adding 3 host teams and two participant teams:
- the expected behaviour:
The count should have been 3 for host team and 2 for participant team
- the observed behaviour: The count showed 2 for both of them

Screen record link:
https://drive.google.com/file/d/1mwk7XcQ8xQm6pwsx5uwBrVpWVtyTxGUh/view?usp=sharing


Thank you @Kajol-Kumari for reporting this issue and as you have reported this would you like to work on it?

I would love to work on it @Suryansh5545 

Nice catch @Kajol-Kumari Thanks for reporting this issue and opening PR.
Repository: Cloud-CV/EvalAI
Issue: Participant and Host can't remove their member
GitHub labels: enhancement

easy_to_fix

frontend

GSOC-2025

Current Behaviour:
For Participant:
If a participant add a member in his/her team by mistake,he/she will have to create a new team from scratch in  order to remove that particular member. 

For host:
If a Host Team add a member in his/her team by mistake,he/she will have to create a new host team from scratch in order to remove that particular member.

Screenshot
![Screenshot from 2020-02-08 02-25-27](https://user-images.githubusercontent.com/44888949/74065562-33b08400-4a1b-11ea-960b-9fb859d737f9.png)


Feature Requested:
There should be a delete option(in the form of icon will be more suitable) after the name of each member and host of the participant team and host team respectively. It will make it easier for them to remove any of his/her member if needed.

can i work on this?


Thanks @Kajol-Kumari for opening the issue. @Sanji515 will be reviewing your PR soon :)

can I take this issue ?

can I take this issue ?
Repository: Cloud-CV/EvalAI
Issue: Hardware configuration

Hi,

This question is related to hardware configuration. We would like to host a "Host Prediction upload based challenge" based internal challenge.  What kind of server capacity and HW configuration needed to host this challenge with 1000 team participants.

Thanks,
Mahesh




Hi @msubglb ,

Thanks for reaching out to us. For hosting, you can use `m4.2xlarge`  but it will again depend upon the size of your annotation files as they are loaded in the RAM.
Please feel free to ask if you've more questions.
Repository: Cloud-CV/EvalAI
Issue: Host team can't remove member 

Current Behaviour:
If a Host Team add a member in his/her team by mistake,he/she will have to create a new host team from scratch in order to remove that particular member.

Feature Requested:
There should be a delete option(in the form of icon will be more suitable) after the name of each member of the team. It will make it easier for the host to remove any of his/her member if needed.

Screenshot
![Screenshot from 2020-02-08 02-25-27](https://user-images.githubusercontent.com/44888949/74065562-33b08400-4a1b-11ea-960b-9fb859d737f9.png)


@Kajol-Kumari As this is similar to other issue can we just change the name of your other issue and include both of these and merge this delete member change in single pr.

> @Kajol-Kumari As this is similar to other issue can we just change the name of your other issue and include both of these and merge this delete member change in single pr.

I was thinking of the same @Suryansh5545 but was not sure.Thanks for suggestion, i am adding it in the other issue and removing this one.
Repository: Cloud-CV/EvalAI
Issue: Squash all commits into single commit in pull request


Current Behaviour:
Each pull request contains many commits that makes it difficult for the reader.

Feature Requested:
Add squash feature in the Contribution guideline (https://github.com/Cloud-CV/EvalAI/blob/master/.github/CONTRIBUTING.md). This will help the contributors to squash all the commits in a single commit making the pull request much cleaner than now.

Steps to squash:
1. git rebase -i HEAD~N(N is the number of commits you want to squash into 1).
2. Then a screen will appear with all N commits having "pick" written in front of every commit.
3. change pick to s for the last N-1 commits and let it be pick for the first one and save it.
4. Then it will ask to change commit message change it accordingly and save it and then force push

For further info, please visit:
https://www.internalpointers.com/post/squash-commits-into-one-git



@Kajol-Kumari The suggestion is quite good . But we should also see the pros and cons http://www.davidchudzicki.com/posts/first-parent and after this if community finds it ok then we can add this as a mandatory or suggested way to keep pr nice and organized 

> @Kajol-Kumari The suggestion is quite good . But we should also see the pros and cons http://www.davidchudzicki.com/posts/first-parent and after this if community finds it ok then we can add this as a mandatory or suggested way to keep pr nice and organized

@Suryansh5545 Most of the against points can be tackled by adding a note in the guideline i.e "Please squash only if you are done with all the work to done with that pr and has been reviewed by one of the mentor." And rest as the community decides after looking at the suggestions and docs.

@Kajol-Kumari Yea this can be done.

Thanks, @Kajol-Kumari for the issue and @Suryansh5545 for the suggestion. Can anyone of you please add this and open up a PR?

@RishabhJain2018 I would like to work on it.

This is fixed.
Repository: Cloud-CV/EvalAI
Issue: Host Deletion function performs no check for the type of Host
Root cause: Validation Gap

#Bug

Expected behaviour:
- Participants should not be allowed to remove the admin of the host team.
- Admin should be provided proper warning when he/she tries to remove himself/herself from the team.

Observed behaviour:
- When Admin tries to remove himself, the whole team along with his members get removed.
- The participant of the host team is able to remove it's admin.
 
Steps to reproduce the problem:
After writing controller function for deleting host.
Go to Host Team -> Create a new host team -> Add members to it -> Try deleting Admin 

Operating System:
Ubuntu 18.04

Browser:
Google Chrome

![ezgif com-video-to-gif (9)](https://user-images.githubusercontent.com/44888949/74377869-cdf13d00-4e0a-11ea-80f2-e3d5f8ea06b6.gif)



Reference: https://github.com/Cloud-CV/EvalAI/blob/master/apps/hosts/views.py#L204-L206

@Kajol-Kumari As you have added this new feature and you know what possibly went wrong would to like to fix it?

@Kajol-Kumari The feature isn't merged yet so you can fix this bug in that and close this issue.

> @Kajol-Kumari The feature isn't merged yet so you can fix this bug in that and close this issue.

@Suryansh5545  The part of code i have given in reference is already merged. While working on adding deletion feature for host, i found that the codes for deletion is already written but it is not performing any check on the type of  user trying to delete a particular host.

> @Kajol-Kumari As you have added this new feature and you know what possibly went wrong would to like to fix it?

I am working on it @Suryansh5545 

@Kajol-Kumari we have an updated plan for this.

- Only person who created the team should be able to delete members from the team and invited members should not have the rights to delete other users in the team. This applies to both participants and hosts team. 

> @Kajol-Kumari we have an updated plan for this.
> 
> * Only person who created the team should be able to delete members from the team and invited members should not have the rights to delete other users in the team. This applies to both participants and hosts team.

Yes @deshraj . This is what i have implemented [here](https://github.com/Cloud-CV/EvalAI/pull/2781/files#diff-936afd091c6c99c1a02293abc3be8653R201). Invited members won't have the privilege to delete any of the members and also the `delete` icon would not be visible to him/her. Please see the 3rd GIF [here](https://github.com/Cloud-CV/EvalAI/pull/2781)
Repository: Cloud-CV/EvalAI
Issue: Unclear Naming to variables

Current Behaviour:
Many Variable names are unclear and creates confusion regarding their purpose.

Expected Behaviour:
Variable names should clearly describe its purpose.

References:
1. https://github.com/Cloud-CV/EvalAI/blob/master/frontend/tests/controllers-test/challengeHostTeamsCtrl.test.js#L418
Here, the test is written for delete function for hostTeam where Variable name "ParticipantId" is not appropriate and hence leading to the confusion.

2. https://github.com/Cloud-CV/EvalAI/blob/master/frontend/tests/controllers-test/challengeHostTeamsCtrl.test.js#L441
Here, the controller function is written for delete function for hostTeam where Variable name "ParticipantId" is not appropriate and hence leading to the confusion.

3. https://github.com/Cloud-CV/EvalAI/blob/master/apps/hosts/urls.py#L27
According to the name the url has got, it should have been for getting details of the hostTeam but instead it's doing all of the get,post,patch and delete operations on the challenge_host_team


Hi @Kajol-Kumari,
Thanks for opening the issue and the corresponding PR. We would be happy to incorporate the suggestion. Can you please write in the description here why the variable names are incorrect and are creating confusion?
Repository: Cloud-CV/EvalAI
Issue: Tests for 'encode_data' and 'decode_data' in apps/base/utils.py

This is with reference to https://github.com/Cloud-CV/EvalAI/issues/2107 . Someone created this issue but it wasn't completed. 
Secondly, I could not fine where these functions are being used. Still, I wrote unit tests for them to increase the coverage.
Repository: Cloud-CV/EvalAI
Issue: Create an API for getting submission counts based upon different statuses
GitHub labels: medium-difficulty

priority-high

GSoC-2020

**Description:**
Currently, we have the APIs for fetching & deleting the messages from SQS Queue but the challenge host doesn't know the pending messages in the AWS SQS queue.

**Deliverables**:
- [x] Add an API for returning the count of the pending messages in SQS Queue.
- [x] Add relevant tests for the API.

**References:**
- https://forums.aws.amazon.com/thread.jspa?threadID=93105


Can I take this up ?

Sure @yashdusing.

@RishabhJain2018 I have a doubt.
As far as I've understood from the reference link, you mean to get the ApproximateReceiveCount (number of times the message has been read up till now) for a particular message. Problem is the fetch messages API in jobs app fetches a bulk of message at once (queue.receive_messages()) and returns only one of the messages which leads to false counting. We can limit this by setting maximum number of messages field for receive messages call. Is this correct or am I missing something ? 

Sorry, I added the wrong reference link there. What we need is an API that will return the number of messages in the SQS queue at any time.

Can I work on this if this is still available?

Hi @abhishekcrdsa7, No, this is done, please take up any other from the list.
Repository: Cloud-CV/EvalAI
Issue: Fix potential vulnerabilities due to outdated requirements
Root cause: External Dependency Breakage

There are some outdated requirements that can open potential security threats. Hence we should update the vulnerable package versions as suggested by Github. Here is the list of upgrades to be done (as suggested by Github):

Django>=1.11.28

There is a PR for it #2663 but please test and make sure to verify the validity and compatibility of suggestions with EvalAI current master branch.

@RishabhJain2018 Sir , django 1.11 is going out of extended maintenance after April so shouldn't we move to 2.2 Lts version instead of 1.11.28?

Yes, the plan is to move towards Django 2 but that will require a significant amount of work in the codebase. Can you please try installing Django 2 and check what all changes we will need for it in the existing codebase.

Similar issue: https://github.com/Cloud-CV/EvalAI/issues/2564

Thanks for mentioning @nikochiko. I'm closing this one.
Repository: Cloud-CV/EvalAI
Issue: Redundant worker dependencies
Root cause: Configuration Error

2 different versions of numpy have been installed in the Worker dockerfile
https://github.com/Cloud-CV/EvalAI/blob/810322c6adb01d42d318105bfc7981dfc8c3e06b/requirements/worker.txt#L3
https://github.com/Cloud-CV/EvalAI/blob/810322c6adb01d42d318105bfc7981dfc8c3e06b/docker/dev/worker/Dockerfile#L14

Also, all the requirements could be specified in worker.txt file, which would reduce a layer on docker image hence the size.

@RishabhJain2018 

Thanks @Ayukha for catching it. Would you like to work on this issue?

Sure!

@Ayukha Are you still working on this issue ? If not, can i work on this one?

@Ayukha , @spectre1811 are you guys taking this issue up?

@Ayukha and @RishabhJain2018  I have made the required changes. Please kindly check and merge.

can i work in this

Hey @devjayswal , Sure!

Thanks Sir I will raise PR soon
Repository: Cloud-CV/EvalAI
Issue: Remote worker tests missing.
GitHub labels: enhancement

medium-difficulty

GSoC-2020

Hi,

There are several tests missing for `remote_worker.py`.

Codebase - https://github.com/Cloud-CV/EvalAI/blob/master/scripts/workers/remote_submission_worker.py

Testfile - https://github.com/Cloud-CV/EvalAI/blob/master/tests/unit/remoteworker/test_remote_worker.py

Coverage report: https://codecov.io/gh/Cloud-CV/EvalAI/src/master/scripts/workers/remote_submission_worker.py

@RishabhJain2018 @vkartik97 Can I work on this issue?

Missing Tests:
`remote_submission_worker.py`

- [x] download_and_extract_zip_file (https://github.com/Cloud-CV/EvalAI/pull/2690)
- [x] load_challenge (https://github.com/Cloud-CV/EvalAI/pull/2527)
- [x] process_submission_message (https://github.com/Cloud-CV/EvalAI/pull/2551)
- [x] extract_challenge_data (https://github.com/Cloud-CV/EvalAI/pull/2690)
- [x] extract_submission_data (https://github.com/Cloud-CV/EvalAI/pull/2690)
- [x] process_submission_callback (https://github.com/Cloud-CV/EvalAI/pull/2690)

Yes, definitely.

Noticed two open PR for the issue - 

1. https://github.com/Cloud-CV/EvalAI/pull/2551
2. https://github.com/Cloud-CV/EvalAI/pull/2527

I would like to add that apart from the unit tests, the integration tests for remote submission worker are also missing (ref: https://github.com/Cloud-CV/EvalAI/issues/2607).
I am not sure how it is supposed to be, but consistency-wise it makes sense to have both.
cc: @RishabhJain2018 

@nikochiko Thanks for pointing out. I have added a list above of missing tests, also referenced open PRs for the same. Do add to the list if you find something missing.

Similar to #2607, hence closing it.
Repository: Cloud-CV/EvalAI
Issue: Test and Verify django, worker container with python 3.7.5
Root cause: Environment Incompatibility

**Description:**

We would like to update the python dependency from 3.6.5  to 3.7.5 and it requires testing of django and worker development container with python3.7.5

**Deliverables:**
- [ ] Test the Django docker container and if it works fine, then update the dev Dockerfile with python3.7.5 as the base image.
- [ ] Test the worker docker container and if it works fine, then update the dev Dockerfile with python3.7.5 as the base image.

Can I take this up?

Sure @Ayukha 

@RishabhJain2018  `Python:3.7.5` is built upon `Debian 10 Buster`and `Python:3.6.5` was on `Debian 9 stretch`, it has dropped support for `openjdk-8-jdk` because of security issues, I have updated to `jdk 11` which is the latest LTS and it works fine. Should i open a PR for same?
https://github.com/Cloud-CV/EvalAI/blob/36f7c2696c1b3a096917c405a2ce640bbea4efe1/docker/dev/worker/Dockerfile#L7

sounds good, please open the PR.
Repository: Cloud-CV/EvalAI
Issue: Update Python version to latest across all environments
Root cause: Configuration Error

As we have updated the python version in the dev environment to 3.7.5, I think we should also update the python version used by Travis for CI, currently, it uses python 3.6
https://github.com/Cloud-CV/EvalAI/blob/1b1318d458c9dff4d2a0d936015e57215989ca21/.travis.yml#L6

@RishabhJain2018 

Yes, please update it.

@RishabhJain2018 I had few doubts related to the Dockerfile. Could you please resolve them. 

Can I work this issue?

Can I work for and contribute in this issue? @RishabhJain2018 

I think the required changes have not been done. So if I am right can I work on this issue @RishabhJain2018 .

Hi, @GauravSarkar ! I made a PR already, when I actually started with this issue, I think there was a build problem with `docker-compose` and forgot about this issue afterwards. Thanks though! :D

@RishabhJain2018, please check

is the issue open?


Hi @RishabhJain2018 ,
Is the issue still open, I would Like to work on it??

This issue has been inactive for a while, so we're closing it for now. If this is still relevant, please feel free to reopen or create a new issue with updated details. Thanks!
Repository: Cloud-CV/EvalAI
Issue: Irrelevant dependencies installed in docker images
Root cause: Architectural Constraint

The docker files contain dependencies related to Django which are not used by the Workers and Celery. The current size of the docker images can be reduced to a large amount if we remove the irrelevant requirements.

- [ ] Separate requirement files for worker and remote worker

- [ ]  Seperate dockerfile for remote worker

- [ ] remove irrelevant dependencies from dockerfile

@RishabhJain2018 


Thanks @Ayukha for pointing it out. Please feel free to work on it.

This issue is still open :)

@RishabhJain2018  I would like to work on it

Sure @pystar-oss you can take this up.

@pystar-oss if you are still working on this issue? if not, @RishabhJain2018 can I take this up?

This is fixed, hence closing it.
Repository: Cloud-CV/EvalAI
Issue: django-import-export is not able to export the files
Root cause: Validation Gap

**Description:**
Django import-export isn't able to export the files. The list for the type of file to be exported doesn't open. Please see the screenshot for more reference.
<img width="1390" alt="Screenshot 2020-03-01 at 2 22 28 PM" src="https://user-images.githubusercontent.com/12206047/75632267-66880b00-5bc8-11ea-84e7-d90ee695f848.png">


can i take this up?

Sure @Ayukha .

@Ayukha aren't you working on #2693 ?
I'd like to also work on this issue

I think @Ayukha didn't ask to work on #2693. I simply asked him to work. My bad. Since @Ayukha is working on this one, @yashdusing would you like to pick up #2693?

@RishabhJain2018 Yes, for sure 

Perfect!
Repository: Cloud-CV/EvalAI
Issue: Display stats on homepage dynamically
Root cause: Unimplemented Feature Gap

**Description**
The count for hosted AI challenges, users, submissions on homepage is hardcoded in the codebase and we want to update it dynamically.

**Deliverables:**
- [ ] Add API to fetch the total count of ongoing and past challenges, users and submissions.
- [ ] Update the homepage code fetch using the above API.
- [ ] Add unit tests for the backend and frontend.

cc: @Ram81 @Sanji515 @vkartik97  

Can I work on this instead of #2693 ?

Sure.

@RishabhJain2018 do we need real time updates ? Or updates on load only ?

Hi.. Is this issue still open to claim? Are you finished working on this @yashdusing ?

@srichakradhar I already have made a PR for it. It’s still underway. Could you please take up some other issue?

Thank you for your interest everyone. We have decided to punt this feature for a future release, hence closing this issue for now.
Repository: Cloud-CV/EvalAI
Issue: Add models for storing organization information
GitHub labels: enhancement

medium-difficulty

backend

new-feature

GSoC-2020

**Description:**
The information for the organization name, logo are hardcoded in the homepage. We would like to update this information dynamically from the backend.

 **Deliverables:**
- [ ] Add models for storing the information of the organizations in the `web` app.
- [ ] The table name should be - Organization
- [ ] The model fields should be - name, logo, is_active (boolean flag to decide if we want to show it on the homepage or not, defaults to True)
- [ ] Register the models in the Django admin.
- [ ] Name the migration file to -`add_models_to_store_partner_organizations`


Hi @RishabhJain2018 Would it be fine if I take this up with #2678 in review?

Sure.

@abbasidaniyal Please claim the issue before making a PR to avoid conflicts. I already claimed the issue with the https://github.com/Cloud-CV/EvalAI/issues/2696#issuecomment-593231047 and recently made a PR for the same. I noticed you worked on the same issue with the PR #2705 and now we two same PR for the issue. 

@pushkalkatara My apologies. I'll take care from now onwards!

We have decided to punt this feature to a later release and work on other important stuff we have on plate.