exadel-inc / exadel-inc/compreface-python-sdk

Multiple face add

Open
#10 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
167
Forks
55
PR merge metrics
No merged PRs in 30d

Description

Try add face in loop for files in my folder(6000 faces)
i got error **FATAL: sorry, too many clients already**
but api response is ok
`compreface-core | {"severity": "DEBUG", "message": "Found: BoundingBoxDTO(x_min=30, y_min=46, x_max=122, y_max=152, probability=0.9968504309654236, _np_landmarks=array([[ 59, 91],\n [ 91, 90],\n [ 75, 112],\n [ 63, 125],\n [ 89, 124]]))", "request": {"method": "POST", "path": "/find_faces", "filename": "6af6425dafe57fd88148a0b7d6f14d5c19771001.jpg", "api_key": "", "remote_addr": "172.25.0.4"}, "logger": "src.services.facescan.plugins.facenet.facenet", "module": "facenet", "traceback": null, "build_version": "dev"}
compreface-core | {"severity": "INFO", "message": "200 OK", "request": {"method": "POST", "path": "/find_faces", "filename": "6af6425dafe57fd88148a0b7d6f14d5c19771001.jpg", "api_key": "", "remote_addr": "172.25.0.4"}, "logger": "src.services.flask_.log_response", "module": "log_response", "traceback": null, "build_version": "dev"}
compreface-postgres-db | 2021-09-15 05:47:10.758 UTC [145] FATAL: sorry, too many clients already
compreface-api | 2021-09-15 05:47:10.758 ERROR 7 --- [nio-8080-exec-7] c.e.f.c.t.s.NotificationSenderService : Connection Error: sorry, too many clients already
compreface-ui | 192.168.101.111 - - [15/Sep/2021:05:47:10 +0000] "POST /api/v1/recognition/faces?subject=makarskayato%20%D0%9F%D1%80%D0%B8%D0%B5%D0%BC%D1%89%D0%B8%D0%BA%20%D0%B7%D0%B0%D0%BA%D0%B0%D0%B7%D0%BE%D0%B2 HTTP`

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the reported loop that adds faces through POST /api/v1/recognition/faces and inspect the accompanying compreface-postgres-db and NotificationSenderService errors. Trace how repeated requests use database connections; done means bulk face addition no longer exhausts PostgreSQL clients and failures are reported consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
postgresql, python
Domain
api, backend, database
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.