stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Keep authentication database writes off the event loop #311

New Issue
Closed
opened 2026-08-08 14:50:42 +00:00 by timmy · 0 comments
timmy commented 2026-08-08 14:50:42 +00:00
Owner
Copy Link

Problem

The async sign-in and single-device sign-out routes perform synchronous SQLite operations for throttling, session activation, and revocation. Under lock contention, these waits can stall unrelated live-dashboard requests. Session validation and all-device revocation already use worker threads, but the remaining authentication write path does not.

Acceptance criteria

  • Slow login-attempt lookup, failure recording, and clearing do not block an event-loop heartbeat.
  • Slow session activation and single-session revocation do not block unrelated async work.
  • Existing 401/429 behavior, secure cookie timing, and privacy-safe 503 failure responses remain unchanged.
  • Focused authentication tests and the full suite pass.

Non-duplication evidence

#275 covered session validation reads only; #270 introduced throttling. Current src/main.py still calls these SQLite-backed operations synchronously. No open issue covers the remaining authentication write path.

## Problem The async sign-in and single-device sign-out routes perform synchronous SQLite operations for throttling, session activation, and revocation. Under lock contention, these waits can stall unrelated live-dashboard requests. Session validation and all-device revocation already use worker threads, but the remaining authentication write path does not. ## Acceptance criteria - Slow login-attempt lookup, failure recording, and clearing do not block an event-loop heartbeat. - Slow session activation and single-session revocation do not block unrelated async work. - Existing 401/429 behavior, secure cookie timing, and privacy-safe 503 failure responses remain unchanged. - Focused authentication tests and the full suite pass. ## Non-duplication evidence #275 covered session validation reads only; #270 introduced throttling. Current `src/main.py` still calls these SQLite-backed operations synchronously. No open issue covers the remaining authentication write path.
timmy self-assigned this 2026-08-08 14:50:42 +00:00
timmy closed this issue 2026-08-08 14:58:00 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
timmy
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#311
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?