[FIXED] DateTime timezone handling causing Internal Server Errors #20

New Issue

chihlasm · 2026-02-03T04:41:53Z

chihlasm commented

2026-02-03 04:41:53 +00:00

(Migrated from github.com)

Problem: Mixing timezone-aware and timezone-naive datetime objects caused errors in session completion.

Solution:

Updated all SQLAlchemy models to use DateTime(timezone=True)
Changed all default datetime factories to lambda: datetime.now(timezone.utc)

Files affected: All models with timestamp fields

Fixed: January 28, 2026

**Problem:** Mixing timezone-aware and timezone-naive datetime objects caused errors in session completion. **Solution:** - Updated all SQLAlchemy models to use `DateTime(timezone=True)` - Changed all default datetime factories to `lambda: datetime.now(timezone.utc)` **Files affected:** All models with timestamp fields Fixed: January 28, 2026

chihlasm referenced this issue from a commit

2026-05-13 21:58:51 +00:00

feat(api): add POST /accounts/me/security/revoke-sessions

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: chihlasm/resolutionflow#20