Replace print() debug statements with logger calls in db_engine.py #22

New Issue

cal · 2026-02-20T06:49:48Z

cal commented

2026-02-20 06:49:48 +00:00

app/db_engine.py:462, 523, 584, 890 — Multiple print() calls in core model methods bypass the rotating file logger. Examples: print(f'I could not drop {move.player.name}'), print(f'**Error** (db_engine player): {e}').

Priority: low | Labels: tech-debt

`app/db_engine.py:462, 523, 584, 890` — Multiple `print()` calls in core model methods bypass the rotating file logger. Examples: `print(f'I could not drop {move.player.name}')`, `print(f'**Error** (db_engine player): {e}')`. **Priority**: low | **Labels**: tech-debt

cal added the

ai-working

label 2026-03-06 00:31:04 +00:00

cal referenced this issue from a commit

2026-03-06 00:34:05 +00:00

fix: replace print() debug statements with logger calls in db_engine.py (#22)

cal referenced this issue

2026-03-06 00:34:18 +00:00

fix: replace print() debug statements with logger calls in db_engine.py (#22) #53

cal added

ai-pr-opened

and removed

ai-working

labels 2026-03-06 00:34:28 +00:00

cal commented

2026-03-06 00:34:30 +00:00

Fixed in PR #53.

Replaced all 4 print() calls in app/db_engine.py with logger.error() calls using the existing module-level logger = logging.getLogger('discord_app'). The messages now route through the rotating file handler at /tmp/sba-database.log instead of being silently dropped in the container.

Fixed in PR #53. Replaced all 4 `print()` calls in `app/db_engine.py` with `logger.error()` calls using the existing module-level `logger = logging.getLogger('discord_app')`. The messages now route through the rotating file handler at `/tmp/sba-database.log` instead of being silently dropped in the container.

Sign in to join this conversation.