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

Can not push leaderboard test docker to EvalAI platform #359

Open
rb93dett opened this issue Jan 25, 2024 · 1 comment
Open

Can not push leaderboard test docker to EvalAI platform #359

rb93dett opened this issue Jan 25, 2024 · 1 comment

Comments

@rb93dett
Copy link

Hi, I‘m trying to test my CARLA agent on the CARLA leaderboard 1.0 (CARLA Autonomous Driving Challenge 2.0), for which I have obtained permission from the organizers to compete. I have installed the latest version of the EvalAI package (1.3.16) and completed the "set token" operation.

However, when attempting to use the "evalai push" command to submit the required Docker image to the leaderboard, I encountered an error message "Error: None". Additionally, I tried other commands such as "evalai challenges," but received a "404 Client Error: Not Found for url: https://eval.ai/api/challenges/challenge/all" error.

I have attempted these operations on both a Linux machine and my personal Mac, and encountered the same issues on both platforms. Upon searching the EvalAI forum, I discovered that other users have also encountered similar problems, which can be found here: https://evalai-forum.cloudcv.org/t/evalai-push-error-or-am-i-just-a-noob-with-docker/1773

I tried to send an email to the EvalAI team but got no response, so I wonder if you could give me any advice, I would be very appreciate!

My commands for push the docker to the platform:

pip install evalai
evalai set_token {MY_EVALAI_TOKEN}
evalai push {MY_DOCKER_IMAGE} --phase carla-leaderboard-10-sensors-2098

image
@joel99
Copy link

joel99 commented Mar 28, 2024

Commenting here to let you know -- I got around this by making a brand new account with a brand new email.
The CLI worked with the new token. Maybe old tokens lurking around the system are incompatible

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

No branches or pull requests

2 participants