-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Could not get models from the server #2541
Comments
@beep-love Hi, please attach logs from cvat container: |
PFA |
GET http://localhost:8080/api/v1/lambda/functions 500 (Internal xhr.js:184 GET http://localhost:8080/api/v1/lambda/functions 500 (Internal Server Error) Your error happens within the function. |
|
@jahaniam Thanks for the help. It worked after deleting the functions from nuclio dashboard before rebuilding the function. I was able to load models and auto annotate with faster RCNN function. Regards |
@beep-love can you please tell me how you rebuilt the function? I am facing a same issue of "Could not get models from the server" |
Use this
|
Also, delete the nuclio error function from nuclio dashboard! |
My actions before raising this issue
Hi, I was following the instructions as per https://github.com/openvinotoolkit/cvat/blob/develop/cvat/apps/documentation/installation.md .
As per the document I was able to compose docker for CVAT and the tool was successfully hosted at http://localhost:8080/
After the deployment, i was also able to compose a serverless component from docker using
The above steps recreated cvat and nuclio. The log is provided below
Current Behaviour
After above-mentioned steps, when I went to http://localhost:8080/models, the browser was not able to load the models and displayed the error at the web console:
Context
I was trying to run auto annotation using available models. But the problem in my view seems to be API error. Also, i have skipped the advanced topic: Deploying CVAT behind the proxy. Does that make any issues related to my problem??
Environment
Next steps
You may join our Gitter channel for community support.
The text was updated successfully, but these errors were encountered: