fix: replace broad Exception and print() with proper error handling in faces.py

[ajithhraj]

db_update_face_cluster_ids_batch in faces.py has two problems:

• Uses broad except Exception instead of sqlite3.Error
• Uses print("Error updating face cluster IDs in batch.") instead of proper logging

Proposed fix

• Replace except Exception with except sqlite3.Error
• Replace print() with logger.error()
• Add import logging and logger = logging.getLogger(__name__)

I'd like to fix this if maintainers agree.

[github-actions]

👋 Thanks for opening this issue! The maintainers will review it shortly. Till then, do not open any PR. This is a strict rule we like to follow around here :)

[Riddhi8077]

Hi! @rahulharpal1603 I looked at the db_update_face_cluster_ids_batch function in faces.py.

Currently the exception handling uses a broad except Exception block and prints the error using print():
except Exception:
if own_connection:
conn.rollback()
print("Error updating face cluster IDs in batch.")
raise

Since this function interacts with SQLite through executemany, it would be safer to catch sqlite3.Error specifically instead of a general exception. Also, replacing print() with the project logger would make error reporting consistent with the rest of the backend.

Something along the lines of:
except sqlite3.Error as e:
if own_connection:
conn.rollback()
logger.error(f"Error updating face cluster IDs in batch: {e}")
raise

This would improve error handling and logging consistency.
If this approach looks good, I’d be happy to submit a small PR implementing the change.

[ajithhraj]

"Hi @rahulharpal1603 , I have already implemented this fix and the branch is ready to push as a PR. Could you please assign this issue to me? Branch: fix/faces-error-handling"

[JITENDRAGAHERWAR03]

Hello 👋
I am interested in working on this issue. I have basic knowledge of Python and I’m eager to learn and contribute. I will try to provide a clean and well-documented solution.
Please assign this issue to me if possible.
Thank you 😊