zhiminy/EvalEng huggingface dataset:
Repository: Cloud-CV/EvalAI
Issue: Header Buttons Not behaving as expected on Mobile view
GitHub labels: frontend

good first issue

- the expected behaviour:-

The 3 Buttons Challenge,Docs & Forum should have either collapse with header or align in more proper way so user dont have problem viewing and the log out button should stick to the header 
- the observed behaviour:-

All 4 Buttons mentioned above follow the view if user scroll down it would have been correct if aligned properly . But they will interrupt when user might try to click something else 
- steps to reproduce the problem:-

Login and go to any page like dashboard in smartphone 
- which operating system and/or browser you're using, if relevant
Android 8.0, Chrome

![Screenshot_20191229-051254_Chrome](https://user-images.githubusercontent.com/34577232/71550575-f14a5f00-29f9-11ea-9353-923399e01ab4.jpg)



@Suryansh5545 As you have reported this issue, would you like to work on it?

@Sanji515 Yes i will work on it

Hey @RishabhJain2018 @Suryansh5545  this issue has been solved both for EvalAI ang ngx so i think we can close this one. Attaching the screenshot for confirming the same. 
![Screenshot_2020-06-09-22-49-20-064_com android chrome](https://user-images.githubusercontent.com/44888949/84179527-bb7acd80-aaa3-11ea-960a-6e4cc03f6eee.jpg)
![Screenshot_2020-06-09-22-49-33-216_com android chrome](https://user-images.githubusercontent.com/44888949/84179540-c03f8180-aaa3-11ea-85e0-ffb486d978ff.jpg)


@RishabhJain2018 I also agree with @Kajol-Kumari the recent UI fix have addressed this issue and the UI is functioning well. So this issue can be closed.
Repository: Cloud-CV/EvalAI
Issue: Add tests for new RL Worker files
Root cause: Validation Gap

#### Scenario:
Recently, new files for RL workers have been added:
1. [rl_submission_worker.py](https://github.com/Cloud-CV/EvalAI/blob/master/scripts/workers/rl_submission_worker.py)
2. [worker_util.py](https://github.com/Cloud-CV/EvalAI/blob/master/scripts/workers/worker_util.py)

#### Solution
We will need new tests for these.

> warning note: the concerned part is still under development. Therefore, tests should be added for utility functions first (which are guaranteed to be used), and then those for the newer part.

Thanks, @nikochiko for adding this and I'd suggest you to work on the utils first as `rl_submission_worker.py` might change since it is still under development.
Moreover, @vkartik97 will be there to help you since he has written this code during his GSoC 2019. 
(I'm also available for help.)

@RishabhJain2018 Thanks for updating me with the development status. I will start work on the utils part then. And, I am already in touch with @vkartik97 over this issue 😄.

Perfect!

I think this is probably an error in the code: https://github.com/Cloud-CV/EvalAI/blob/master/scripts/workers/worker_util.py#L58 
The returned response will be `dict` object (see [`make_request`](https://github.com/Cloud-CV/EvalAI/blob/master/scripts/workers/worker_util.py#L40)) and reference to `response.status_code` should raise an `AttributeError`.
Am I missing something?

For the fix, I was thinking we could add an extra argument:
```python
def make_request(self, return_status_code=False):
    .
    .
    .
    if return_status_code:
        return response.status_code  # instead of response.json()

    return response.json()
```

> For the fix, I was thinking we could add an extra argument:

No, avoid using flags in open source codebases. Why? Maintaining code that makes use of flags is that the number of states grows quickly, and there are almost always unhandled states.

Thank you for sharing that. I will keep that in mind. 
Then how about this:
We leave the `make_request` method untouched and make changes in the `delete_message_from_sqs_queue` function, 
According to the views.py, the returned response contains this [message](https://github.com/Cloud-CV/EvalAI/blob/master/apps/jobs/views.py#L1209).

As this message can clarify if the deleting was successful, we can return the response dict as it is or return "success" or "error" depending on the keys of the response dict.
What do you think?

Edit:
@RishabhJain2018 Thanks for the fixing PR: https://github.com/Cloud-CV/EvalAI/pull/2575

Closing this since it is a very old issue.
Repository: Cloud-CV/EvalAI
Issue: Remove the common errors
GitHub labels: bug

easy_to_fix

docs

good first issue

GSOC-2025

Remove the common errors which are not used from the [docs page](https://evalai.readthedocs.io/en/latest/faq(developers).html#common-errors-during-installation) now since we have shifted the setup from virtualvenv to docker.

Hey @gautamjajoo can I take up this issue?

@gautamjajoo Please take a look

@keskarshreesh are you still on the issue?


@adrijshikhar there is already a pr for this mentioned above

hello, Is it possible being assigned to this issue?


Hello is the issue still open I would like to work on it.


Hello @RishabhJain2018 @gautamjajoo I’d like to work on this issue. Could you please assign it to me?

@RishabhJain2018 @gautamjajoo please assign me.
Repository: Cloud-CV/EvalAI
Issue: Update the Contribution Guidelines on EvalAI-Docs 
GitHub labels: docs

good first issue

Update the Contribution Guidelines on [EvalAI-Docs](https://evalai.readthedocs.io/en/latest/contribution.html) with the one present on Github.

@gautamjajoo Can i work on it

#2561 

@Suryansh5545 are you still on the issue?

@adrijshikhar  There is already a pr open to close this issue

I want to work on it


hello, Is it possible being assigned to this issue?

can  work on this?


Hello @RishabhJain2018 , I’m interested in tackling this issue. Is it available to pick up? Please assign it to me if it’s free; otherwise, could you point me to other good starter issues? Thank you!
Repository: Cloud-CV/EvalAI
Issue: Duplication of Code


A lot of files have duplicated code.
Files and counts are as follows.
Count | Path 
      1   | evalai/utils/challenges.pyDuplication 
      1   | evalai/utils/teams.pyDuplication
    11   | tests/test_challenges.pyDuplication
     2    | tests/test_requests.pyDuplication
     2    | tests/test_teams.pyDuplication 

Removing these duplicate codes and taking a look at them might help lessening the code and the unnecessary complexity.
Repository: Cloud-CV/EvalAI
Issue: Remove duplicated code

A lot of files have duplicated code.
Files and counts are as follows.

Count | Path

1 | apps/base/utils.py
1)https://github.com/Cloud-CV/EvalAI/blob/master/apps/base/utils.py#L16
   https://github.com/Cloud-CV/EvalAI/blob/master/apps/base/utils.py#L157
1 | apps/challenges/views.py
1)https://github.com/Cloud-CV/EvalAI/blob/master/apps/challenges/views.py#L277
   https://github.com/Cloud-CV/EvalAI/blob/master/apps/participants/views.py#L230

Removing these duplicate codes and taking a look at them might help lessening the code and the unnecessary complexity.

@amanex007 please point the links too.


sure


done


@amanex007 is this issue still open?
i would like to work on this.

Hi @amanex007 . I have removed the duplicate strings 'domains' in the views.py of both participants and challenges folders. But, the base/utils.py duplicates mentioned in the issue can not be removed. Since, the code you mentioned is a library which is used to import PageNumberPagination module which is used in multiple places in the code. Also, in the #L157, do you want me to get rid of the entire method 'get_or_create_sqs_queue_object'. Please let me know. Thanks!

Ask @pushkalkatara  to review it, he has opened this issue and has more knowleadge and understanding about the issue.

Sure @amanex007 . Thanks!!

@pushkalkatara Hi, could you please guide me through this?
Repository: Cloud-CV/EvalAI
Issue: Increase the z-index of Profile Page sidebar
GitHub labels: bug

GSOC-2019

easy_to_fix

frontend


Increase how much ? @aka-jain 

Can you set it by yourself, so that everything will work fine?

@anweshknayak : Are you still working on this? We need to solve this issue as soon as possible.
Let me know if you are busy, I can handle it.

@aka-jain sure you can take it. I will be engaged for 2-3 days or more. 

@aka-jain can I work on it or it is solved ?


@anweshknayak : Sorry to not update it, this issue has been solved with PR #279.
@deshraj : Closing it.
Repository: Cloud-CV/EvalAI
Issue: Use a single library for HTTP requests in jobs/utils

#### Current behavior:
In jobs/utils.py, two libraries (urllib and requests) are being used for the same purpose

#### Expected behavior:
Only one library (preferably `requests`) should be used.

@nikochiko is this issue still open? i would like to work on this.

There's a PR for it already. Please find another issue! :)

On Wed, Jan 22, 2020, 23:36 Adrij Shikhar <notifications@github.com> wrote:

> is this issue still open? i would like to work on this.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/Cloud-CV/EvalAI/issues/2570?email_source=notifications&email_token=AI7MKYI2QVOA6KSRSMRT7E3Q7CDI3A5CNFSM4KCFG7MKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJURNXY#issuecomment-577312479>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AI7MKYI7E5ARVYQDLSWQ7UDQ7CDI3ANCNFSM4KCFG7MA>
> .
>
Repository: Cloud-CV/EvalAI
Issue: Improper error message
GitHub labels: priority-low

frontend_v2

**The observed behavior**:
When I input Japanese words into team name, the error message "This field is required" is shown.
![Screenshot from 2020-01-04 02-06-17](https://user-images.githubusercontent.com/57856193/71737568-5e953e80-2e97-11ea-87f9-22d276e3d0f1.png)

**The expected behavior**:
When unexpected letter (not limited to Japanese letter) is in input, the error message should be something like "Invalid letter is contained".



Can you try this out in EvalAI-ngx too?


Sure :smile_cat: 

@takitsuse Are you solving this or can I?

@Tanuj22 I'm not working on this, so please go ahead :+1: 

I was looking into this issue. Does creating a regex to allow only english letter sound good?


Sounds good to me. What do you say @Sanji515?

We are only planning to support only alphanumeric characters for the team name going forward. 

Here are the updated rules:
- Team name can be contain alphanumeric characters with spaces, `-`, and `_`
- Show proper error message if not correct team name is entered

\cc @Kajol-Kumari 

Closing this as we already have this.
Repository: Cloud-CV/EvalAI
Issue: Improve documentation structure

#### The current picture:
The structure for the readthedocs documentation for EvalAI (https://evalai.readthedocs.io/en/latest/) is a bit hard to follow, The titles of different section as seen in the panel on the left look like random topics where two unrelated or two similarly titled topics are placed next to each other.

#### The improvement:
As the documentation covers a wide variety of topics, we should organize the topics into further sections with friendly names such as: **What is EvalAI?**, **How do I use it?** and **How to contribute?**. This is just one way, we can be more creative here.

For a visual idea of the sections, here is a snip from [Scrapy's documentation](https://scrapy.readthedocs.io/en/latest/), the sections and topics are excellently titled, and finding the required information is really easy:
![scrapy-rtd-left-panel](https://user-images.githubusercontent.com/37668193/71767273-871d4700-2f30-11ea-836d-039027248095.PNG)


I have recently work on a .rst files and it is quite hard in it to organize it to look good . 

@nikochiko Can i work on it?

@Suryansh5545 Sure! But make sure you also talk to a maintainer so that they verify that this change is needed and that your PR can be merged. I'll ping them in cc here.
cc: @RishabhJain2018 @Ram81 @vkartik97 

is this issue still open?

@adrijshikhar the issue is open but as no maintainer have given any though about it. it might not be good to proceed 

Hey! I want to work on it
Repository: Cloud-CV/EvalAI
Issue: Add footer to all inside pages (dashboard view)
GitHub labels: enhancement

GSOC-2019

easy_to_fix

frontend


@aka-jain I want to take this one! 
Can you guide me through this one coz I am new to django!


Sure @ram81 go ahead


@aka-jain  as you said to include the footer template I've done that,but because of sidebar footer needs to be adjusted so can I go for that?

close this ?

Thanks @anweshknayak .
Closing issue with reference PR at #315
Repository: Cloud-CV/EvalAI
Issue: [docs] 2 partially inconsistent instances of contributing guidelines

#### The issue:
* There are two different instances of contributing guidelines: https://github.com/Cloud-CV/EvalAI/blob/master/.github/CONTRIBUTING.md and https://github.com/Cloud-CV/EvalAI/blob/master/docs/source/contribution.rst
* It is confusing as it is hard to understand which is the more up-to-date one (from the commit history, both have been updated separately before the last commit).
* As we make more updates, the guidelines will have to be updated in two places, which is an overhead and can be easily forgotten.

#### The solution:
* There should be only one up-to-date file for contributing guidelines.

@nikochiko There are two contribution guidelines because one is for github which support .md file only and other for readthedocs site which support .rst files only . So we can't have one. For both 

I think this issue can now be closed 

@Suryansh5545 We have support for markdown files in Sphinx (see https://github.com/Cloud-CV/EvalAI/blob/master/docs/source/conf.py#L37) through CommonMarkParser, which is why all the other documents in docs/source directory are in markdown format. 
(Sphinx is the one building the documentation, not readthedocs).
Moreover, simply that two services we use do not support similar filetype is not a reason to compromise on the quality of the project. In that case, we could have an in-between script or some other arrangement to convert md to rst or vice versa so that both remain in sync. 

Markdown doesn’t support a lot of the features of Sphinx, like inline markup and directives. However, it works for basic prose content. reStructuredText is the preferred format for technical documentation

I think this answers it

And making sync will be for now more difficult than perhaps updating both


@Suryansh5545 Yes, I agree with that, but I think markdown is still very usable. Almost all of our documentation is in markdown. So I think we can go with Markdown for consistency purposes. And I don't think the contributing file would need to contain any technical information. 
So I think this is still a critical issue as both of the guidelines differ (I think one is even outdated and shows incorrect information). 
The threat of this is twofold:
* Overhead of maintaining an extra file for same purpose
* Could cause confusion among new developers.

We can give it a try

Similar to #2578 and keeping one issue open for all documentation related issues.
Repository: Cloud-CV/EvalAI
Issue: [Frontend V2] Only one footer component
GitHub labels: frontend_v2

**Current Scenario** 
Currently We have two footer component one for Authenticated users and other for none authenticated . But both are almost identical. With very little different. 
**Expected Scenario**
We can have the functionality of both in just one footer component this will reduce the work of editing both footer . if we have to change it .

Can i work on it?

Hey @RishabhJain2018  @deshraj we have a single footer component for both verified and non-verified users in `frontend_v2`.

Closing this as it is fixed.
Repository: Cloud-CV/EvalAI
Issue: Scroll up Button not showing up 

- **The expected behaviour**
In the challenge list the scroll up button should show up after going down a bit the page.  
- **The observed behaviour**
The scroll up button doesn't show up at all even after reaching at the bottom 
- steps to reproduce the problem
1.go to evalai.cloudcv.org/web/challenges/list
2. Scroll down 



Can i work on it?

@Kajol-Kumari Can you please check if this is fixed in frontend v2.

> @Kajol-Kumari Can you please check if this is fixed in frontend v2.

Yes @RishabhJain2018 It's working perfectly fine for frontend_v2.

Though the scroll up button is visible in the page but it's width is quite less and a lot of space is getting wasted in left and the right side, so we can increase the width of scroll bar a little to make it user friendly.
Should I do this?

i would like to work on this issue
Repository: Cloud-CV/EvalAI
Issue: Add Collapsible to Challenge list

Currently When user visits the evalai challenge list page . He is bombarded with all the challenges the on going, up coming and past ones . This make it hard for user to navigate and search. Currently there are 48! challenges on evalai challenge list .

Expected Solution:
Add a Collapsible so the user can open and close the list he wants . like if he want to look for current challenge then we will open on going tab .etc

Can i work on this

This is fixed in frontend v2 and we added multiple tabs instead or collapsible.
Repository: Cloud-CV/EvalAI
Issue: Add a Search Bar In Challenge-List

Currently the evalai challenge list have 48 challenges Which make it hard for user to search. While We can add a Collapsible to increase the navigability . We need to have a search bar so if user knows the name of challenge then he can search it and wouldn't require to search though all the challenges.


Can i Work on this? 

Hi @Suryansh5545, Thanks for opening this. I've added this as an issue and noticed it later. I'm closing it.
Repository: Cloud-CV/EvalAI
Issue: UI-issues in Mobile.
Root cause: Validation Gap

The Topbar options and and Logout botton are not showing as expected in Mobile View.

![Screenshot from 2020-01-08 23-38-38](https://user-images.githubusercontent.com/42486853/72004285-15ffcb80-3271-11ea-9536-54de3915f4a1.png)


Can i work on this?


@Tanuj22 This is the duplicate of #2553 and there is a PR to close this #2563
Repository: Cloud-CV/EvalAI
Issue: Fix toggle problem between login and signup tabs on UI
Root cause: Validation Gap

Here is the way to replicate the bug: 

1. Go to the login page 
2. Enter some details
3. Click on the signup button above the form
4. Enter details on the signup page
5. Switch back to the login page by clicking the login button above the form

You will get to see that the password field's label should go up as I switch but it does not behave like that. So, we need to fix this. 

Let me know if this is not clear or you need help with this.

So one thing. as you see the input email field in sign up page gets cleared when you switch back and forth.Rest the issue persists as said.  So can we just not store the field input variables when we switch ? 

Yeah, we need to store all the fields including the email field. 

@anweshknayak : You have to add material script for this. Please make a directive and add $.material.options.autofill = true in directive and add it to login and signup page.
Let if know it you need more help.

@anweshknayak : I hope you haven't solved this issue, actually I've solved it because we have an urgent requirements of this. Please work on other issues :)
@deshraj :  Closing this issue, fixed with PR #268 .
Repository: Cloud-CV/EvalAI
Issue: Dark Theme Option

These days many big sites and app have dark theme and it is also good for eye in dark(i open evalai at night in dark and it is not eye friendly )
I have created a prototype with black and dark grey of homepage here are  images of it.
**Black in background  and dark grey in the rest**
![Selection_015](https://user-images.githubusercontent.com/34577232/72087341-4f4a4100-332e-11ea-8dae-44e74375b9e4.png)
![Selection_016](https://user-images.githubusercontent.com/34577232/72087343-4f4a4100-332e-11ea-885f-07d033a593a8.png)
![Selection_017](https://user-images.githubusercontent.com/34577232/72087344-4fe2d780-332e-11ea-9cc4-cd3417bfc3c9.png)
![Selection_018](https://user-images.githubusercontent.com/34577232/72087345-4fe2d780-332e-11ea-92a8-bcd270346061.png)
**dark grey in background and black in rest**
![Selection_020](https://user-images.githubusercontent.com/34577232/72087466-802a7600-332e-11ea-8546-484c0df9ad2b.png)

I have changed most images for dark theme . but they are not present in this prototype.

 

@Suryansh5545 Just throwing a personal opinion: the screenshots look really cool! :D 

@RishabhJain2018 @Sanji515 @Ram81 @KhalidRmb 
Should i continue working on this if it looks good??

Closing This as the feature is currently not required but can be revisited later
Repository: Cloud-CV/EvalAI
Issue: Add integration tests for remote_submission_worker
Root cause: Unimplemented Feature Gap

Currently, only integration tests for submission_worker are present (reference: https://github.com/Cloud-CV/EvalAI/tree/master/tests/integration/worker). So I think integration tests for remote_submission_worker would be required as well. 
Please let me know if the work on that is already underway or if we have planned to only have unit tests for that.
Repository: Cloud-CV/EvalAI
Issue: Unused argument in update_submission_data

**Current**:
`update_submission_data` function is implemented in [here](https://github.com/Cloud-CV/EvalAI/blob/master/scripts/workers/worker_util.py#L88) and [there](https://github.com/Cloud-CV/EvalAI/blob/master/scripts/workers/remote_submission_worker.py#L447), but none of them use `submission_pk` argument in their codes.

**Proposal**:
I think we should remove the unused argument.

P.S: I'd like to work on this if we get a consensus on removing it.

I noticed it too while writing tests for worker_util.py (https://github.com/Cloud-CV/EvalAI/pull/2576). I applied the fix in worker_util.py there but I think having a separate PR for this will be better as it has two occurences. :+1:

I agree. I'll create a new PR for this.
Repository: Cloud-CV/EvalAI
Issue: Analyze why maintainability estimate is low (D)
GitHub labels: priority-low

As per `codeclimate.com` (which has been integrated with EvalAI and creates a maintainability sticker on the README), the maintainability of the code in EvalAI is `D`. This is a rough estimate of the maintainability (for example, the simplicity and cleanliness of the code). This can be improved by refactoring some parts of the code. 
The codeclimate report is a bit stricter and some issues from that can be ignored. The first part should be to figure out the pieces of code that actually need to be cleaned. Suggestions to improve the code should also be included. 
I think we can maximize time efficiency by diving the research part into python issues / javascript issues.  

Refer this report: https://codeclimate.com/github/Cloud-CV/EvalAI/issues

P.S. I would like to dig into the python code and suggest improvements, but the javascript side is still up for grabs. 

This is my report for the python side: https://github.com/nikochiko/EvalAI/blob/ImproveMaintainability/improve_maintainability.md

Please let me know if anything can be added. Work can be started one-by-one on each.
Repository: Cloud-CV/EvalAI
Issue: Website crumbles if cookies are blocked 
Root cause: Validation Gap

**The expected Behaviour:-**
The Website should be accessible to the user even if he is blocking the cookies.
**The Observed Behaviour:-**  
Everything in the header except the image disappear, buttons in footer stop working and year is not shown. The login is also not working. animations disappears and  the evalai image is no longer take back to homepage if clicked . the contact page if reached is not working. Blocking cookies literally makes the whole site paralyzed. 
**Steps to reproduce:-** 
Just block the cookies

In privacy policy we state that some features of website won't work.  But instead the whole site falls.