Use timezone-aware datetime.now(UTC) in TransactionFreezeTask.weekly_loop #38

New Issue

cal · 2026-02-20T06:50:53Z

cal commented

2026-02-20 06:50:53 +00:00

Description

tasks/transaction_freeze.py:300 — Uses datetime.now() (timezone-naive, local server time) for freeze/thaw timing. If server timezone differs from league's expected timezone, freezes fire at wrong time. Rest of file uses datetime.now(UTC). Same issue in models/custom_command.py:102, models/help_command.py:121,126, services/draft_service.py, services/custom_commands_service.py.

File Locations

tasks/transaction_freeze.py:300
models/custom_command.py:102
models/help_command.py:121
models/help_command.py:126
services/draft_service.py
services/custom_commands_service.py

Labels

bug

Priority

medium

## Description `tasks/transaction_freeze.py:300` — Uses `datetime.now()` (timezone-naive, local server time) for freeze/thaw timing. If server timezone differs from league's expected timezone, freezes fire at wrong time. Rest of file uses `datetime.now(UTC)`. Same issue in `models/custom_command.py:102`, `models/help_command.py:121,126`, `services/draft_service.py`, `services/custom_commands_service.py`. ## File Locations - `tasks/transaction_freeze.py:300` - `models/custom_command.py:102` - `models/help_command.py:121` - `models/help_command.py:126` - `services/draft_service.py` - `services/custom_commands_service.py` ## Labels bug ## Priority medium

cal referenced this issue from a commit

2026-02-20 20:17:40 +00:00

fix: batch quick-wins — 4 issues resolved (closes #37, #27, #25, #38)

cal closed this issue

2026-02-20 20:29:08 +00:00

Sign in to join this conversation.