zhiminy/EvalEng huggingface dataset:
Repository: Cloud-CV/EvalAI
Issue: Incorrect Fields in Jobs serializer
Root cause: Validation Gap

*Observed code:* [here](https://github.com/Cloud-CV/EvalAI/blob/master/apps/jobs/serializers.py/#L54)
```
class Meta:
        model = LeaderboardData
        fields = "__all__"
        fields = ('id', 'participant_team_name', 'challenge_phase_split', 'leaderboard_schema', 'result')
```
*Expected Code:*
```
class Meta:
        model = LeaderboardData
        fields = ('id', 'participant_team_name', 'challenge_phase_split', 'leaderboard_schema', 'result')
```

@Ayukha thanks for reporting this issue. Can you please create a PR for the same? 

sure !
Repository: Cloud-CV/EvalAI
Issue: Update seed script to add broker url in challenge
Root cause: Unimplemented Feature Gap

## Current Behaviour:

Currently, when the challenge is created using the seed script, the `queue` field is not populated.

## Expected Behaviour:
When the seed script is run, the `queue` field must be populated with the random string of 75 characters in length.

I'd like to take this up @RishabhJain2018 

Sure! You can work on it.

Can I work on this? @RishabhJain2018
Repository: Cloud-CV/EvalAI
Issue: Editing team name input feild reflects the input feild of new participant team name 
GitHub labels: inactivity

**Bug**
We we edit a team name in participant team name then the text in the input feild of team starts appearing in the input feild of create participant team name.
![screenshot from 2019-01-17 20-35-23](https://user-images.githubusercontent.com/19318218/51430030-27546000-1c3b-11e9-8300-c5de18316b9c.png)

On the right hand side where create participant team is located you can see the same text is appearing on the change participant team name.

**Expected Behaviour**
There should be no text in the create participant team name when we are editing a team name.

I want to work on this


@RishabhJain2018 I'm working on this issue.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.


This issue has been automatically closed as there is no further activity. Thank you for your contributions.
Repository: Cloud-CV/EvalAI
Issue: Change the submission visibility to public by default
Root cause: Unimplemented Feature Gap

## Current Behaviour

Currently, when a submission is made then it is always private by default. A participant has to explicitly make it public to be visible on the leaderboard even if the leaderboard is public.

## Expected Behavior

The submission made should have the default visibility as public.

## Deliverables

- [ ] Change the `is_public` flag default value in Submissions model to `True`.
- [ ] Create the migrations for the same with name `Change_submission_visibility_default_to_public`


Can I take this issue?

Sure!
Repository: Cloud-CV/EvalAI
Issue: Add a http response interceptor to catch all responses with status code 401
Root cause: Unimplemented Feature Gap

## Current Behaviour

Currently, all the 401 responses are handled separately in different controllers which increases redundancy in the code.

## Expected Behaviour

A single function which will handle all the requests.

## Deliverables

- [ ] Create an interceptor service in `services.js` in order to catch all the response and check for 401 status code and return the response if there is 401 code in the response.
The below code can be utilized to create an interceptor service.

```
    angular
        .module('evalai')
        .service('utilities', utilities)
        .factory('authHttpResponseInterceptor',['$q','$location',function($q, $location){
            return {
                responseError: function(rejection) {
                    if (rejection.status === 401) {
                        localStorage.clear();
                        $location.path('/auth/login');
                    }
                    return $q.reject(rejection);
                }
            };
        }])
        .config(['$httpProvider',function($httpProvider) {
            //Http Intercpetor to check auth failures for xhr requests
            $httpProvider.interceptors.push('authHttpResponseInterceptor');
        }]);
```

- [ ] Remove all the 401 response codes from different controllers.

- [ ] Test the system end to end after removing the code.

I'd like to take this up

Sure! go ahead.

@RishabhJain2018 what did you mean by step 3 ? We currently do not have end to end tests for EvalAI, right ? I saw only unit tests in the tests section

Yeah, currently we don't have unit tests written for the frontend. I meant to test it manually if it is working or not. Can you please do that too?

@RishabhJain2018 Could you help me out producing 401 errors ? Most of the 401 errors are due to login timeouts and I'm not sure how to produce them on my build manually 

You can change the token expiration time to something like 30 seconds or 1 minute and then you will be able to reproduce this error. Change has to be made in this line: https://github.com/Cloud-CV/EvalAI/blob/master/settings/common.py#L194

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.


This issue has been automatically closed as there is no further activity. Thank you for your contributions.
Repository: Cloud-CV/EvalAI
Issue: Add feature to toggle leaderboard visibility by challenge host
Root cause: Unimplemented Feature Gap

## Current Behaviour

The challenge host can view the challenge leaderboard but can't make it public/private after the challenge is completed.

## Expected Behaviour

A challenge host will be able to make the leaderboard public/private using the UI.

## Deliverables

### Backend
- [ ] Add a check in `get_or_update_challenge_phase_split` API for PATCH requests that the requesting user should a challenge host or a member of challenge host team.
- [ ] Add two tests one when the requesting user is a member of host team and one if the user isn't the member of host team.

### Frontend
- [ ] Add a toggle button in the leaderboard tab of the challenge host which will appear when the leaderboard is selected.
- [ ] Add a function in the challenge controller to which will be bind to the above toggle button to change the visibility.

Please feel free to ask if you have some doubts!

I'm just getting started with the project and I'd like to work on this.

yeah, you can work on it. Please feel free to ask if you have any doubts.

Hi @RishabhJain2018 , I'd like to clarify two things..

1. > The challenge can view the challenge leaderboard but can't make it public/private after the challenge is completed.

Should challenge host be allowed to change visibility only after challenge completes or anytime?
`visibility` of `challenge_phase_split` model needs to be set to 1 for it to be private?
`leaderboard_public` status of challenge_phase table is not to be affected right?


2. If we have to use `get_or_update_challenge_phase_split`, should toggle button be presented to host only after he chooses challenge phase in leaderboard tab?

@RishabhJain2018 , When you have some time, can you clarify the above doubts. I'll submit the PR soon.

Ohh..I missed this,

> Should challenge host be allowed to change visibility only after challenge completes or anytime?

Anytime the challenge host wants to toggle the visibility.

> visibility of challenge_phase_split model needs to be set to 1 for it to be private?

yeah.

> leaderboard_public status of challenge_phase table is not to be affected right?

right.

> If we have to use get_or_update_challenge_phase_split, should toggle button be presented to host only after he chooses challenge phase in leaderboard tab?

yeah, the toggle button should appear only after the challenge host chooses challenge phase and split in the leaderboard tab.

Please feel free to ask if you have some other questions too!



This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.


This issue has been automatically closed as there is no further activity. Thank you for your contributions.
Repository: Cloud-CV/EvalAI
Issue: Center align the leaderboard
Root cause: Documentation Deficiency

## Current Behaviour

The leaderboard table metrics are not properly aligned with their header.

## Expected Behaviour

The header and values must be properly aligned.

## Deliverables

- [ ] Remove all the align classes like `align-right, align-left etc.` in the leaderboard.html
- [ ] Add a class `align-center` to `table` attribute in the same file.

## For Testing
- [ ] Create at least 5 entries on the leaderboard with different team names.
- [ ] Paste the screenshot with the entries along with the PR.

Please feel free to ask if there are any doubts.

Can I work on this?

Sure!

@RishabhJain2018 I think you wrote the wrong class name here. The table should have a `centered` class instead of `align-center` so that it gets centered through materializecss. For reference, please see this https://materializecss.com/table.html. @gautamjajoo: please make sure that you don't miss this comment. :) 

@deshraj @RishabhJain2018 This is screenshot when I use `centered` in `table` and `center-align` in `<tr>` tag. I have to use `center-align` in `<tr>` tag because without that the upper tab is not being center aligned. While I researched on it and saw that it is not being aligned because of the icons on the upper tab. Isthis okay? 

![](https://files.gitter.im/gautamjajoo/oUzK/Screenshot-from-2019-01-21-19-50-31.png)


@gautamjajoo This looks good. Can you please open a PR for the same?

Can I take this issue ?

Sorry, but this has already been taken.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.


This issue has been automatically closed as there is no further activity. Thank you for your contributions.
Repository: Cloud-CV/EvalAI
Issue: Editing hosted challenges directly doesn't work
Root cause: Architectural Constraint

- The expected behaviour : 
     Editing any hosted challenge properties should go smoothly
- The observed behaviour :
     Editing gives off an error
- Reason : localStorage which should contain the current challenge is not updated when we directly go through the 'Hosted Challenges' section. Only the 'All Challenges' section updates the localStorage
- Steps to reproduce the problem :
     1. Create a challenge (don't go to the 'All Challenges' section)
     2. Go to Hosted Challenges page and select your hosted challenge
     3. Edit the properties

![screenshot_20190121_203454](https://user-images.githubusercontent.com/19976688/51482372-49292080-1dbc-11e9-9f02-305e080bde09.png)
![screenshot-0 0 0 0-8888-2019 01 21-20-36-11](https://user-images.githubusercontent.com/19976688/51482403-5b0ac380-1dbc-11e9-86c8-681fe09030f2.png)




Would I like to take this up ? 
Yes.
Thanks!


I think this issue is already opened. Please check https://github.com/Cloud-CV/EvalAI/issues/1802

@sachinmukherjee this one is different. 

@yashdusing I am not sure if this is a bug. It seems more like someone is tampering with the local storage related to a particular hostname on the browser. It will cause the same issue for every website (which uses local storage) if you just go ahead and delete the contents of the local storage. 

Please let me know if I am missing something here. 

@deshraj Actually, I'm not altering the localStorage in any way. The condition for localStorage to be empty is not exactly true. I forgot to change the description but even an empty localStorage works.
Anyways, the bug is actually caused because of a user directly trying to edit the hosted challenge through the 'Hosted-Challenges' site without going through 'All Challenges' site. Only the 'All Challenges' section contains the logic to update the localStorage so if the user tried to go through the other way (i.e. through hosted challenges site) he'd encounter this issue

I should have used the term 'empty localStorage' carefully. What I meant was a localStorage that doesn't yet contain the newly created challenge 

Thanks for the clarification. This makes sense. It's a valid issue. Can you please update your issue description so that it is clear for anyone who reads it for the first time? :) 

@deshraj Sure !

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.


This issue has been automatically closed as there is no further activity. Thank you for your contributions.
Repository: Cloud-CV/EvalAI
Issue: Determine why code coverage is low
GitHub labels: enhancement

GSOC-2019

easy_to_fix

critical

good first issue

## Current Behaviour
The code coverage is 72% which is quite low.

## Expected Behaviour
The code coverage should be > 90%.

## Deliverable
- [ ] Figure out the pieces of code for which the test cases are missing.
(A link to google doc highlighting those sections in the comments would suffice for it.)

I would like to work on this one. @RishabhJain2018 

Sure! You can take this up.

@RishabhJain2018 @KhalidRmb #1997 is related to this issue.

Thanks, @vkartik97 for mentioning it.
@KhalidRmb Please do take a note of it in the doc you are preparing.

@RishabhJain2018 Link to Google doc with a checklist of all the relevant unit tests to be written: https://docs.google.com/document/d/1IF3APjd93hUeov4KKRGDupMlcjpLO-MYo3_lEP8e42k/edit?usp=sharing

@RishabhJain2018 ..any comments/changes required to the doc?

@KhalidRmb @RishabhJain2018 I will create an issue and write unit tests for /apps/base/utils.py because #2054 couldn't pass the coverage tests.

@KhalidRmb Added unit tests for both functions `decode_data` and `encode_data` in /apps/base/utils.py #2107 

`scripts/workers/submission_worker.py`  is a major area where Test coverage can be improved @KhalidRmb . I guess python unit tests can do the job for submission worker. Yet we also need to think where Integration tests are missing in apps to increase coverage

i would like to work on this @RishabhJain2018 

i would like to work on this @RishabhJain2018
Repository: Cloud-CV/EvalAI
Issue: Display the participant team name by which a participant participates in a challenge
Root cause: Unimplemented Feature Gap

## Current Behaviour
In the current setup, a participant doesn't know the participant team by which they have participated until they select the submissions under `My Submissions` Tab.


## Expected Behaviour

The participant team should be constantly visible under the `My Submissions` Tab.

## Deliverables
- [x] Add an API to fetch the participant team of the user corresponding the challenge.
- [ ] Write tests for the API
- [ ] Add frontend code in `My Submissions` Tab to display the participant team of the user for the corresponding challenge.
- [ ] Paste a screenshot of the UI with the PR

Please feel free to ask if you have any doubts!

Can i take this up?

Sure! But you are already working on a feature. You can take it up after finishing that. Till then, it is open to everyone.

May I take this up, as I'm not working on any feature currently?

Sure! You can work on it.

@deshraj @RishabhJain2018 Can I take this up if I've finished all of my other tasks and are waiting for review ?

@yashdusing  I've actually started on this one, and will make a PR for my other task soon. So, please be free to take up other issues :)

@RishabhJain2018 Sorry for the delay, been busy lately :). However, here's a screenshot. Will this do?
![screenshot from 2019-03-04 16-03-32](https://user-images.githubusercontent.com/31621523/53727835-3b74b980-3e97-11e9-8c34-40d229775560.png)


This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.


This issue has been automatically closed as there is no further activity. Thank you for your contributions.
Repository: Cloud-CV/EvalAI
Issue: Typos
GitHub labels: GSOC-2019

easy_to_fix

frontend

priority-high

good first issue

https://github.com/Cloud-CV/EvalAI/blob/fa2756c6e6c2c049f8fdf1649c05e1d0d1bf7ae1/frontend/src/views/web/challenge/participate.html#L90

https://github.com/Cloud-CV/EvalAI/blob/98065e3257db0cd629bc64b959a29bae519b0bfe/frontend/src/views/web/challenge/submission.html#L186

"Sorry, The Challenge is not active!" —> "Sorry, the challenge is not active."

Can I work on this issue?

Sure! go ahead.

https://github.com/Cloud-CV/EvalAI/blob/b9246417c50d4a7308a1ae05457e1be10bcf292d/frontend/src/views/web/featured-challenge/participate.html#L11

"Proceed to challenge page to participate in this Challenge!" —> "Proceed to challenge page to participate."

https://github.com/Cloud-CV/EvalAI/blob/b9246417c50d4a7308a1ae05457e1be10bcf292d/frontend/src/views/web/featured-challenge/participate.html#L12

https://github.com/Cloud-CV/EvalAI/blob/fa2756c6e6c2c049f8fdf1649c05e1d0d1bf7ae1/frontend/src/views/web/challenge/participate.html#L96

"Please Log In to participate in this Challenge!" —> "Please log in to participate in this challenge."
Repository: Cloud-CV/EvalAI
Issue: Update Django version in docs
GitHub labels: enhancement

GSOC-2019

easy_to_fix

docs

good first issue

Django version was updated to `1.11.18`. It should be updated in [Docs](https://evalai.readthedocs.io/en/latest/architecture.html#django
) also
@deshraj @RishabhJain2018 

Can I work on this issue @gautamjajoo ?

Sure! @kurianbenoy .
Repository: Cloud-CV/EvalAI
Issue: Add feature for slack notification
GitHub labels: enhancement

GSOC-2019

medium-difficulty

backend

new-feature

inactivity

## Current Behaviour

Currently, when a challenge is created, submission is made or a contact message is received, EvalAI Admin doesn't get any notification.

## Expected Behaviour

A slack notification should be added for all the three events.

## Deliverables
- [ ] Create a common function in `base/utils` which will take input a slack webhook URL and a message to be sent to the slack.
- [ ] Add the notification for following events:
	- [ ] When a challenge zip is uploaded
	- [ ] When a contact message is received
	- [ ] When a submission is made
- [ ] Write test cases.

## Starter Code
```
def send_slack_notification(webhook=settings.SLACK_WEBHOOKS['default'], message=""):
    '''Send slack notification to any workspace
    
    Keyword Arguments:
        webhook {string} -- slack webhook URL (default: {settings.SLACK_WEBHOOKS['default']})
        message {str} -- JSON/Text message to be sent to slack (default: {""})
    '''

    try:
        response = requests.post(
            webhook,
            data=json.dumps({'text': str(message)}),
            headers={'Content-Type': 'application/json'}
        )
    except Exception as e:
        logger.info('Exception raised while sending slack notification. \n Exception message: {}'.format(e))
```

Please feel free to ask if you have any doubts!


I'd like to take this up

Sure! go ahead.

@RishabhJain2018 What all information should be posted to the slack channel when any of these are created ? Just a notification or some other related info as well ? 

@RishabhJain2018 what all test cases need to be written ? All I've done is include the send slack notification function, so should I write a test case for that ?

Hi @yashdusing 
1. It should be just a message like `A challenge is created` or `A contact message is received`, we can iterate over it once you open a PR.

2. Yeah, the test cases for that function.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.


This issue has been automatically closed as there is no further activity. Thank you for your contributions.
Repository: Cloud-CV/EvalAI
Issue: Bug while editing Participating Team name

### Observed Behaviour
When a user edits his team name he could see the previous name on the right side of the page. (See attached screenshot)

### Expected Behaviour
The team name on the right side should not be visible.

### Steps to Reproduce
 Make a Team and try to edit the team name/ you could cancel the change as well.

@deshraj @RishabhJain2018 

![2019-01-26](https://user-images.githubusercontent.com/24366008/51787380-19e92980-2197-11e9-9a6f-4fcfbc2ce531.png)

![2019-01-26 1 _li](https://user-images.githubusercontent.com/24366008/51787381-1c4b8380-2197-11e9-8b7d-fab0e982e729.jpg)



@gautamjajoo  This issue has already been reported. Please see #2017  if its same.
Repository: Cloud-CV/EvalAI
Issue: Center align the footer of dashboard when viewed below medium screen
Root cause: Unimplemented Feature Gap

The dashboard footer be aligned properly as in the homepage when viewed below medium screen size.
@deshraj @RishabhJain2018 

<table border="0">
<tr>
<td width="300">
<p align="center"><b> Observed </b></p>
<img src="https://user-images.githubusercontent.com/24366008/51787549-78afa280-2199-11e9-9a75-fa3835da104e.png" width="300" />
</td>
<td width="300">
<p align="center"><b> Expected </b></p>
<img src="https://user-images.githubusercontent.com/24366008/51787545-72b9c180-2199-11e9-8db6-c3f3a736d385.png" width="300" />
</td>
</tr>
</table>



@RishabhJain2018 Can I work on this issue??

Sure! You can work on this issue.

@RishabhJain2018 Can i still work on this or has it been resolved?
Repository: Cloud-CV/EvalAI
Issue: Display success and error message notification
Root cause: Unimplemented Feature Gap

## Current Behaviour
We don't show a notification for success and error messages when a participant toggles the submission visibility.

## Expected Behaviour & Deliverable
Display a notification for both cases on Success and on Error.

Can I take this?

Sure! You can work on this.

is this issue still workable on ?

@indranilbiswas7 I have already opened a PR for this, please take up another issue.
Repository: Cloud-CV/EvalAI
Issue: Add leaderboard description field
Root cause: Unimplemented Feature Gap

## Current Behaviour
Currently, we don't display leaderboard description under the leaderboard tab.

## Expected Behaviour
A text field which will display the description about the leaderboard.

## Deliverables
- [ ] Add a blank and nullable text field in the Challenge model with the name `leaderboard_description`.
- [ ] Name the migrations as `Add_leaderboard_description_field_in_challenge`
- [ ] Add a card on the frontend above the card for selecting phases to display the leaderboard with the heading `Description`
- [ ] Paste the screenshot of the leaderboard with some sample data in the `Description` card.


Can I work on this issue?

Sure! you can work on this issue.

is this issue still workable on ?


@indranilbiswas7 
I am working on this feature, only the tests are remaining and about to make a PR for this.

Is this issue still open?
Can i work on this issue?

Hi @iamjayantk 
I have opened a PR for this #2056
Repository: Cloud-CV/EvalAI
Issue: Use of 2 docs in the requirements
Root cause: Architectural Constraint

If you'd like to report a bug, please include the following information:
- We should have only one documentation in the requirements
- We have both drfdocs and drf-yasg
Thanks!


This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.


This issue has been automatically closed as there is no further activity. Thank you for your contributions.