Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix error on get all challenges #342

Closed
gchhablani opened this issue Mar 13, 2023 · 2 comments · Fixed by #344
Closed

Fix error on get all challenges #342

gchhablani opened this issue Mar 13, 2023 · 2 comments · Fixed by #344

Comments

@gchhablani
Copy link
Collaborator

gchhablani commented Mar 13, 2023

Description

Currently, evalai challenges is failing on both staging and production. On calling evalai challenges, we get the following error:

Error: None

Note that other usual commands are working.

The task is to figure out the issue why this is happening and fix it.

Pre-requisites/Benefits

This issue essentially requires background on a few things:

Approach

  • Set up evalai-cli using the installation described here.
  • Reproduce the issue for both production and staging. This will require you to go over the repository to understand how to use EvalAI CLI for production and staging.
    Steps for staging:
(habitat) lawn-128-61-54-75:habitat-challenge gunjanchhablani$ export EVALAI_CLI_ENVIRONMENT="PRODUCTION"
(habitat) lawn-128-61-54-75:habitat-challenge gunjanchhablani$ export EVALAI_API_URL=https://staging.eval.ai/
(habitat) lawn-128-61-54-75:habitat-challenge gunjanchhablani$ evalai push rearrange_submission:latest --phase march-dev-748
  • Find the problem area in the code and open a draft PR with descriptive comments and appropriate fix.

Please reach out to us in case you face any issues.

@erudin
Copy link

erudin commented Mar 29, 2023

Hey I came here from GSoC and was checking this issue and playing around with EvalAI web service and evalai-cli. I noticed that there is this PR #341 that seems related to this, the fix I wrote is similar to that. I was thinking on doing a PR for it, but wanted to be sure because of the other PR that is created.

@priyanshmathur
Copy link

hey @gchhablani
The second link of this message is 404 this one
Kindly provide an alternate link
Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants