Skip to content

fix: remove leftover debugging code and improve error handling in yolo_mapping.py #1317

@Dotify71

Description

@Dotify71

Describe the bug or improvement
The database module backend/app/database/yolo_mapping.py contains leftover debugging code (import os and print(os.getcwd())) that clutters the console output every time the YOLO classes table is created.

Additionally, the database execution block lacks proper except sqlite3.Error handling and logging, which is inconsistent with the rest of the database modules.

Proposed Solution

  1. Remove the leftover import os and print(os.getcwd()) from db_create_YOLO_classes_table.
  2. Wrap the cursor.execute calls in an except sqlite3.Error block to catch and log database failures properly using the project's standard logger (logger.error()), matching the recent cleanup done in faces.py, metadata.py, etc.

This is a good first issue for anyone looking to contribute!

Metadata

Metadata

Assignees

No one assigned

    Labels

    possible-duplicatePotential semantic duplicate (upstream comparison)

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions