Open ncsibra opened 2 years ago
Looks like this is a critical bug. I checked the code and this logic was removed during refactoring that was in 0.6.0 version. If you need this functionality, please use 0.5.1 version. I will add this bug as critical to 1.0.0 release that we plan to release soon. I'll update the documentation as well to warn other users.
@pospielov Do you have any ETA for 1.0.0?
I think we will release this or the next week.
Hello All how could I see data stored by CompreFace at my server as files or DB etc?
Thanks
All files are stored in compreface-postgres-db
container in the PostgreSQL database.
You can expose the port in docker-compose.jml
file, you can see how it's done in dev docker-compose.jml
:
https://github.com/exadel-inc/CompreFace/blob/master/dev/docker-compose.yml
Then connect to DB using pgadmin or another tool and see all information.
Describe the bug I'm testing CompreFace with the provided Docker Compose distribution in the root directory and looks like the
save_images_to_db=false
option does not work.The trained faces are still saved to Postgres
img
table. Tested withv0.6.1
tag and the latest master.Based on docker inspect the related configuration option passed correctly to
compreface-api
.Here's the original implementation: https://github.com/exadel-inc/CompreFace/pull/163/files#diff-d829967df73c63987fa6772e8f2e0e9b9374ad3df661a20e3931094b1726253fR80 Quickly searching through the code, I can't see the relevant logic in the current codebase, but I'm not a big Java guy. :)
To Reproduce Steps to reproduce the behavior:
.env
file setsave_images_to_db=false
img
table, a new entry will be added and the size of the data in thecontent
column is the same as the uploaded image sizeExpected behavior Do not save the image to the database when
save_images_to_db=false