zhiminy/EvalEng huggingface dataset:
Repository: Cloud-CV/EvalAI
Issue: Unable to configure project to work properly on virtualenv with Python-3 default. 
Root cause: Documentation Deficiency

- ## Observed Behaviour

While installing the project on a `virtualenv`, if the `virtualenv` was installed through Python-3 then the environment's default will be Python-3 if not specified otherwise. The problem is that if the project is installed on a `virtualenv` with default Python 3 it will lead to very unexpected errors, which are very hard to solve and the submission and challenge system won't run properly. 

- ## How to solve it?
In the long term, the project should be updated to work in Python 3 but now we should clearly specify in the installation instructions that the `virtualenv`'s default python version is supposed to be Python2.7, and also add the commands to help with the installation. 



@isht3 Please check `Readme.md`, the python version with commands for installation are already mentioned there.

@RishabhJain2018 `virtualenv --python=/usr/bin/python2.7 venv` Adding this command will make the `virtualenv` be installed with Python2.7 default otherwise in the new versions it'll be Python3.


@isht3: instead of changing the command, can we just add in the README somewhere which says that EvalAI supports Python2.x for now? 

@deshraj Yes, that would be nice. :+1:
Repository: Cloud-CV/EvalAI
Issue: Typo Fix in Documentation
GitHub labels: bug

enhancement

easy_to_fix

docs

good first issue

**Current Documentation** : In `Architecture Decision` the operations are described as `CURD`.
**Related Links** : https://github.com/Cloud-CV/EvalAI/blob/master/docs/source/architecture_decisions.md#url-patterns
**Solution** : The operations must be described as `CRUD` according to the convention.

Hey, I can pick this one up for you if you like.

@jakecarr Yes sure. Go ahead!
Repository: Cloud-CV/EvalAI
Issue: Navigation menu is not coming on mobile after login.
GitHub labels: bug

easy_to_fix

frontend

good first issue

Navigation menu icon is not coming up on mobile for logged in user.

I would like to work on this.

Hi, can I work on this?

@AmosHason assigning this to you.

@rohitnaik246 please pick any other issue as @AmosHason already asked for it.

Yes, you can work on this. @Obtin 

@aka-jain  is this issue still open? I'd like to work on it.

@Obtin Are you working on this ?
Repository: Cloud-CV/EvalAI
Issue: Setup "Deploy to Heroku" option for EvalAI
Root cause: Unimplemented Feature Gap

Follow the instructions given here: https://devcenter.heroku.com/articles/heroku-button

@deshraj I'm quite familiar with heroku, I've deployed a few apps onto it. Can I try solving this?

@isht3 Please take up one issue at a time so that it won't be a bottleneck for the overall development of the project. I think you are solving #1342 . Please complete that first then you can take this up, till then it is open to all :)

@RishabhJain2018 Okay, cool!

Can I work on this? 


@anweshknayak Sure. go ahead :)

This wouldn't work as there's two servers, one is the backend and the other is frontend. if they're served together, I can work this out.

#1449 Will do after this.

Not required now. We will get back to it once we have ported the frontend to angular 5.
Repository: Cloud-CV/EvalAI
Issue: Down Chevron button not working on Mobile Phones
GitHub labels: bug

enhancement

frontend

good first issue

![screenshot_20171027-011942](https://user-images.githubusercontent.com/22341493/32104752-6620aee2-bb43-11e7-9b97-3ca989ddd5b5.png)


The Down Chevron button linked with "See More" is not working on mobile phones. 
Browser: Chrome

@HargovindArora can you please tell for which screen size it is not working ? 

@RishabhJain2018 It's 5.5-inch screen and 720 x 1280 pixels.

@HargovindArora are you on this ?

It is working fine for 720 x 1280 pixels  I just checked. 

@anweshknayak I tested this on my device, it wasn't working. If you want to work on this feel free to make a PR. I just reported the issue here :smile: 

It's working now, so closing this issue. @HargovindArora @anweshknayak
Repository: Cloud-CV/EvalAI
Issue: Increase the width of edit details dialog box
GitHub labels: enhancement

easy_to_fix

frontend

good first issue

**Observed Behaviour :**
![dialog_box](https://user-images.githubusercontent.com/12206047/32119513-22efbffc-bb73-11e7-8e69-4f9ba7e78a34.jpg)
The dialog box looks small in the screenshot.

**Expected Behaviour:** Increase the width of the dialog box suitably and paste the screenshot in the PR.


Hi , i would like to take this up.

@vikneshwar Go ahead!

@RishabhJain2018  Can i take this up if @vikneshwar  is not working on it ?

@vikneshwar Any update on this ?
@Ayukha Let's wait for him, if he is not working on it then you can take this up :-)

Hi, I had difficult time setting up the dependencies for this project, so couldn't continue. @Ayukha you can take this up. I will try meanwhile if I get time. Thanks 


@vikneshwar If you need some help in setting up the project, I will be glad to help you. You can also join the gitter channel https://gitter.im/Cloud-CV/EvalAI for your queries.

Hi @RishabhJain2018 got this error, when i started the server https://gist.github.com/vikneshwar/adbeb25e96a077c33d23ad77d9cd3063

@vikneshwar It looks like the SSL package you have installed isn't new enough for Twisted. I suggest you to upgrade it. Moreover, can you tell me which OS are you using ?

@RishabhJain2018  i would like to work on this.

@kunalvishnoi Sure, go ahead. :) 

Is somebody working on this?? Can i claim it?? 

@16116073 Please take up any other issue as @S2606 had asked for it earlier than you. :smile: 

@RishabhJain2018 I think nobody is working on it, can I take this issue?

@anuj-rathore i am working on this..

@Obtin Yes sure!

@Obtin  Are you still working on this or I can take this up ? Please let me know :+1:
Repository: Cloud-CV/EvalAI
Issue: Write documentation for preparing evaluation script
Root cause: Documentation Deficiency

## Deliverables

We already have the documentation for creating a challenge. We still don't have the documentation which tells the challenge hosts "How to prepare the evaluation script?" for their challenge. 

This issue requires proper understanding of how the evaluation script is executed when a submission is made. You should also know how the submission worker is evaluating the submissions at the backend ( a good thing here is that if you know this, then you know most important part of EvalAI).

See https://github.com/Cloud-CV/EvalAI-Examples to find an example of challenge evaluation script. 

Fixed in #1526 

@deshraj Since, it is fixed in #1526 , can we close this issue and #1114 this also?

Thanks @gautamjajoo for pointing out. Closing this now.
Repository: Cloud-CV/EvalAI
Issue: Add feature to invite users to participant team using URL
GitHub labels: enhancement

GSOC-2019

medium-difficulty

backend

priority-high

## Deliverables

Add a feature to invite new team member to a participant team using a Unique URL. Also, don't forget to write unit tests. :) 

## Steps

1. **user1** enters the email of his teammate (let's say **user2**)
2. Send an email to **user2** (if he/she is registered on EvalAI) with a unique URL
3. **user2** clicks on the URL to accept the invitation to the team.
4. *user1* gets an email saying that "**user2** has accepted your invite to team <blah>" (we can iterate over the email message later) 

### Some important points to note

- [ ] Checks performed before inviting to the team should be similar to current invitation logic  

@deshraj Can I take this up?

@isht3 Yes sure ! Go ahead

@RishabhJain2018 Cool! On it.

@deshraj From what I understood, this issue is to replace the current method of adding members directly into a team without the user's consent and switch to an Email invite so that the user can choose whether to be added onto the team, yes?

@deshraj Could you provide some insight? :smile: 

You got it right. :) 

@deshraj @RishabhJain2018  For sending Email invites, can I use the inbuilt `django.core.mail` or should I use something else?

Yep. 

Hi, @deshraj @RishabhJain2018 https://stackoverflow.com/a/6367458/6439372 This answer suggests using an external SMTP like sendgrid for sending E-mails, I was wondering what we were using for sending E-mail's right now. Should I look into the Sendgrid option? 

@deshraj Should I do the PR with frontend and backend as one commit?

@isht3 No, please open different pull requests for frontend and backend.

@RishabhJain2018 Okay, cool. But how do I test if it works while hosting?

Since @isht3 isn't active these days to update the PRs. Hence this issue is still open :)

@RishabhJain2018 Can I work on this after the completion of my previous issue?

Even I'd like to work on a medium level difficulty issue but I'm already assigned to a problem. So, it's better that once we complete the assigned problems we work on this

Hi, @Sanji515 @yashdusing You guys can take this issue only when you've completed the previous ones. Till then it is open for everyone.

@RishabhJain2018 @deshraj I've completed my previous issue, Can I work on this?

Sure. you can start with this one now!

@RishabhJain2018 can I take this issue.?


@deshraj @RishabhJain2018  @Ram81 As the issue is still open, can I work on it ?
Repository: Cloud-CV/EvalAI
Issue: Add feature to invite users to host team using URL
GitHub labels: medium-difficulty

backend

new-feature

priority-high

GSOC-2025

Very similar to #1346. 

## Deliverables

Add a feature to invite new team member to a host team using a unique URL. Also, don't forget to write unit tests. :) 

## Steps

1. **user1** enters the email of his teammate (let's say **user2**)
2. Send an email to **user2** (if he/she is registered on EvalAI) with a unique URL
3. **user2** clicks on the URL to accept the invitation to the team.
4. *user1* gets an email saying that "**user2** has accepted your invite to team <blah>" (we can iterate over the email message later) 

### Some important points to note

- [ ] Checks performed before inviting to the team should be similar to current invitation logic  

@deshraj can I take this one ?

@deshraj @Ram81 @RishabhJain2018  If currently no one is working on it.
Can I work on it ?

@aka-jain @RishabhJain2018 @deshraj I completed the other similar issue, can I work on this?

@sudhanshuchopra please let us know if you can work on this? If we don't hear back from @sudhanshuchopra, then @isht3 you can work on it. :) 

Yes @deshraj you can assign it to @isht3

Only tests for this are pending, I'll do the PR tomorrow. 

@isht3: any update? 


@deshraj Done!

This issue is still open to work :).

@deshraj @RishabhJain2018 What's the difference between this and #1346 ?

@yashdusing This issue is for inviting members for host team. And the other one is for inviting members to join participant team.

@RishabhJain2018 @deshraj @gautamjajoo I'd like to take this up. I haven't been assigned any issues yet and have finished all my previous work

@Ram81 @RishabhJain2018 Can I work on this issue? 

Sure, you can work on this issue.

Taking this up!

@RishabhJain2018   is This issue is still open to work? If yes can i work on this issue?

@deshraj  @RishabhJain2018 @Ram81  As the issue is still open, can I work on it ?

 can i work in this too :)

Hi @RishabhJain2018 if this issue is free to be worked on, can you please assign it to me?

Sure @Zahed-Riyaz !
Repository: Cloud-CV/EvalAI
Issue: Broken link in readme.md

There is a link in [readme.md](https://github.com/Cloud-CV/EvalAI/blob/master/README.md)  line 84 to https://github.com/Cloud-CV/EvalAI/blob/development/CONTRIBUTING.md 

Thanks @neeraj12121 for reporting this. Actually, the correct link is https://github.com/Cloud-CV/EvalAI/blob/master/CONTRIBUTING.md

If you want to fix it, then go ahead. :-)

@deshraj yeah sure
Repository: Cloud-CV/EvalAI
Issue: Remove unused code from ChallengeCreate Controller.
GitHub labels: enhancement

easy_to_fix

frontend

priority-low

good first issue

**Expected Behaviour:** Remove the commented code after line `84` from controller `ChallengeCreate.js`.
**Hint:** https://github.com/Cloud-CV/EvalAI/blob/master/frontend/src/js/controllers/challengeCreate.js#L84

Can i take this up?

Sure go ahead!

I would like to try this. This would be my very first contribution. Please allow me to

@prajwalgatti Go Ahead !

I made a pull request. Please review
Repository: Cloud-CV/EvalAI
Issue: Add comments in the codebase for analytics controller.
GitHub labels: easy_to_fix

docs

good first issue


@RishabhJain2018 I would like to work on this. Would you guide me how to proceed? :)


@HargovindArora The issues labelled with `dev-sprint` are for developers participating in Pycon India 2017 dev-sprints. I will open it to everyone once it gets over.
Till then please take up any other issue from the list. :-)

@RishabhJain2018 Sure :)


@RishabhJain2018  I want to work on this issue, May I?

Fixed to some extent. Hence closing it.
Repository: Cloud-CV/EvalAI
Issue: Add comments in the codebase for auth controller
GitHub labels: easy_to_fix

docs

good first issue


@RishabhJain2018 Since this is similar to #1357 . Can I take this up?


@HargovindArora The issues labelled with `dev-sprint` are for developers participating in Pycon India 2017 dev-sprints. I will open it to everyone once it gets over.
Till then please take up any other issue from the list. :-)

@RishabhJain2018 Sure. Got it :)


@RishabhJain2018  Is this issue open? Can I start working on it?

  

@DhruvThakker Yes sure. This is open you can take this up.

@RishabhJain2018 anyone working on this issue?

This is a very vague issue. Also, we don't need it now since we are moving towards Cloud-CV/EvalAI-ngx (new frontend of EvalAI). Hence, closing it.
Repository: Cloud-CV/EvalAI
Issue: Research and suggest Frequently Asked Questions.
GitHub labels: easy_to_fix

docs


Hi, I'm new here and would like to contribute to this project. Can I start with this issue?

Hello @nitinprakash96 yes you can start with the issue. 

@RishabhJain2018 Here's some of the Frequently Asked Questions 
[Frequently Asked Questions.docx](https://github.com/Cloud-CV/EvalAI/files/1576129/Frequently.Asked.Questions.docx)


@gautamjajoo The doc looks ok to me but you can add certain questions the common problems in setting up the project with solutions (Check EvalAI channel for the problems and solutions).

Sorry but I think @RishabhJain2018 and @gautamjajoo misunderstood the requirement. The FAQ here is for the end users and not for EvalAI developers. So, there have to be questions such as:

1. What is EvalAI?
2. What kind of challenges does EvalAI support?
3. Can I run EvalAI on my private server?
4. How to host a challenge on EvalAI?
5. How to participate in a challenge in EvalAI?
6. What is the best way to contact EvalAI team?
7. I am interested in contributing. Where should I start from?

There are a lot more FAQs that we can think of. 

Sorry @gautamjajoo, it looks like you did a lot of work for this Pull Request but I am afraid that you would have to modify the questions and answers. We will make sure that this doesn't happen in future. 

@deshraj Can we add this file as "Common Error during installation"??

As I mentioned that the FAQ that we want is for the end users and not the EvalAI Developers, so I don't think we can include it. Please feel free to suggest some other questions that you have in mind. 

Closing this issue since we are going to release the new frontend of EvalAI soon. (Cloud-CV/EvalAI-ngx)
Repository: Cloud-CV/EvalAI
Issue: Tutorial to participate in a challenge.
Root cause: Documentation Deficiency

**Description:** Write a tutorial showing how to participate in a challenge on EvalAI. Stepwise instructions are expected.

**Hint:** Go to [https://evalai.cloudcv.org](https://evalai.cloudcv.org) and participate in a challenge.

@RishabhJain2018 Can I take this up? :)

@HargovindArora The issues labelled with `dev-sprint` are for developers participating in Pycon India 2017 dev-sprints. I will open it to everyone once it gets over.
Till then please take up any other issue from the list. :-)

@RishabhJain2018 Sure. :)

@RishabhJain2018 Hi, Can I start with it?

@RishabhJain2018 Here's the document.
[Tutorial to participate in a challenge in.docx](https://github.com/Cloud-CV/EvalAI/files/1579239/Tutorial.to.participate.in.a.challenge.in.docx)


@gautamjajoo this looks great. Can you please add this to the docs and create a pull request for this? There might be really minor changes that I can suggest once you have the pull request ready.
Repository: Cloud-CV/EvalAI
Issue: Try and suggest different color schemes for pop up info notifications
GitHub labels: enhancement

easy_to_fix

good first issue

**Description:** The color scheme must be in accordance with our new UI. Student should try different colours with notification toast so as to match the UI.

Is der any one work on it

or should I take this up ?

@HimanshuAwasthi95 Yes sure . You can take it up. Feel free to ask if you face any difficulty.

I would like to work on this issue.
Repository: Cloud-CV/EvalAI
Issue: TypeError: Related Field got invalid lookup: icontains
GitHub labels: bug

easy_to_fix

backend

priority-high

good first issue

While trying to search for a team name in submissions model from djago admin using the search feature, one encounters the following error:

```
TypeError: Related Field got invalid lookup: icontains
  File "django/core/handlers/exception.py", line 39, in inner
    response = get_response(request)
  File "django/core/handlers/base.py", line 187, in _get_response
    response = self.process_exception_by_middleware(e, request)
  File "django/core/handlers/base.py", line 185, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "django/contrib/admin/options.py", line 544, in wrapper
    return self.admin_site.admin_view(view)(*args, **kwargs)
  File "django/utils/decorators.py", line 149, in _wrapped_view
    response = view_func(request, *args, **kwargs)
  File "django/views/decorators/cache.py", line 57, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
  File "django/contrib/admin/sites.py", line 211, in inner
    return view(request, *args, **kwargs)
  File "django/utils/decorators.py", line 67, in _wrapper
    return bound_func(*args, **kwargs)
  File "django/utils/decorators.py", line 149, in _wrapped_view
    response = view_func(request, *args, **kwargs)
  File "django/utils/decorators.py", line 63, in bound_func
    return func.__get__(self, type(self))(*args2, **kwargs2)
  File "django/contrib/admin/options.py", line 1543, in changelist_view
    self.list_max_show_all, self.list_editable, self,
  File "django/contrib/admin/views/main.py", line 78, in __init__
    self.queryset = self.get_queryset(request)
  File "django/contrib/admin/views/main.py", line 346, in get_queryset
    qs, search_use_distinct = self.model_admin.get_search_results(request, qs, self.query)
  File "django/contrib/admin/options.py", line 905, in get_search_results
    queryset = queryset.filter(reduce(operator.or_, or_queries))
  File "django/db/models/query.py", line 796, in filter
    return self._filter_or_exclude(False, *args, **kwargs)
  File "django/db/models/query.py", line 814, in _filter_or_exclude
    clone.query.add_q(Q(*args, **kwargs))
  File "django/db/models/sql/query.py", line 1227, in add_q
    clause, _ = self._add_q(q_object, self.used_aliases)
  File "django/db/models/sql/query.py", line 1247, in _add_q
    current_negated, allow_joins, split_subq)
  File "django/db/models/sql/query.py", line 1253, in _add_q
    allow_joins=allow_joins, split_subq=split_subq,
  File "django/db/models/sql/query.py", line 1178, in build_filter
    lookup_class = field.get_lookup(lookups[0])
  File "django/db/models/fields/related.py", line 694, in get_lookup
    raise TypeError('Related Field got invalid lookup: %s' % lookup_name)
```

@deshraj May I work on this? :)

@HargovindArora sure, go ahead. :) 

@deshraj Ohkay. On it :+1: 

Is this issue still open?


The pull request is under review and soon this will be closed. :)
Repository: Cloud-CV/EvalAI
Issue: 403 Forbidden response from Github API
Root cause: Architectural Constraint

See the screenshot below for more details about the error:

<img width="1918" alt="screen shot 2017-11-18 at 6 16 41 am" src="https://user-images.githubusercontent.com/2945708/32979687-3248de50-cc28-11e7-8eb6-1a2ea3ed5325.png">


Hi, to fix these we need an authentication token from github, so i'd request the team leaders to create a client id with a secret and then we can request the api url which will look like: 
`https://api.github.com/users/whatever?client_id=xxxx&client_secret=yyyy`

Thanks @DakshMiglani for the suggestion.
@deshraj, @RishabhJain2018  any action on this?
  

Hi @DakshMiglani, thanks for the suggestion. We would like to leave it as it is for now. We cannot expose the `client_id` and `client_secret` since we are requesting from the client side. We would love to have suggestions from the contributors for various workarounds for this problem.  

@deshraj Currently unauthorized users (user is determined by his IP) can make up to 60 requests per hour so for normal usage this won't be a problem.
Another option is to create a view in backend to access the API with the token. The limit would be 5000 per hour but for all users. We would need to limit the refresh-rate of these stats then.

@Obtin please feel free to take this issue. :) 

@Obtin: I just thought about a new way of doing this. Can you integrate the https://buttons.github.io/ for showing the fork and star button? It will help us to remove the dependency of Github API and just use this service.
Repository: Cloud-CV/EvalAI
Issue: Cannot read property 'hulk' of undefined
Root cause: Validation Gap

See the screenshot below for more context related to this error:

<img width="1920" alt="screen shot 2017-11-18 at 6 46 04 am" src="https://user-images.githubusercontent.com/2945708/32979945-30c6c52a-cc2c-11e7-8f3c-31a73746cc42.png">
Repository: Cloud-CV/EvalAI
Issue: Typo in README
GitHub labels: bug

GSOC-2019

easy_to_fix

The line `That's it, Now to connect to dev server at http://127.0.0.1:8000` needs to be replaced with `That's it, Now to connect to dev server at http://127.0.0.1:8888`

a new pr is made #154 

close this ? 

Sure. Thanks @gauthamzz :-)