-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
fbrs semi automatic annotation nuclio function starts unhealhy #4736
Comments
Same thing,
the logs of the container are:
|
I ran into this error a few months ago and forgot to make a PR for it. Google Drive changed and so the previous method to download the model weights no longer works. I tested with my fix today and FBRS worked, however I could not get the Docker image for IOG (which has the same problem) to build properly. I may try to solve the problem and make a PR next week, but if you want to try the changes on your own you can see my branch here |
* Update curl command for Google Drive weights and adjust yaml files (#4736) * update changelog Co-authored-by: Boris Sekachev <boris.sekachev@yandex.ru>
My actions before raising this issue
fbrs network for semi automatic annotations does not start with the current nuclio function code.
Am i doing something wrong? (please check steps to repeat)
Expected Behaviour
fbrs network for semi automatic annotation works after running
deploy_cpu.sh
Current Behaviour
fbrs network for semi automatic annotation just says
unhealthy
when runningnuctl get functions
when trying to access in cvat it returns error code 500.
Possible Solution
it says something with `pickle key´ not found in docker logs.
Did something change with the download url for the checkpoint?
Steps to Reproduce (for bugs)
docker-compose -f docker-compose.yml -f components/serverless/docker-compose.serverless.yml up -d
cd serverless
deploy_cpu.sh
(or only start fbrs network)nuctl get functions
pth-saic-vul-fbrs
, it says unhealthyContext
cant do semi automatic annotation
Your Environment
ubuntu 22.04
Next steps
You may join our Gitter channel for community support.
The text was updated successfully, but these errors were encountered: