forked from 0xWheatyz/SPARC
Fix get_db_client() in auth.py to reuse a shared pooled DatabaseClient #134
Reference in New Issue
Block a user
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?
Context
get_db_client()inauth.pyinstantiates a newDatabaseClienton every invocation, bypassing the connection pool. Under concurrent load this exhausts database connections.Work
get_db_client()to return a module-level singleton or dependency-injected pooled client, consistent with howDatabaseClientis used elsewhere.DatabaseClientinstances outside the pool.Acceptance Criteria
get_db_client()returns the same pooled client instance on repeated calls.DatabaseClient()is constructed per request inauth.py.References
Roadmap: P1 — Error handling and resilience — get_db_client() creates new DatabaseClient on every call.
Closing: get_db_client() in auth.py uses a module-level singleton DatabaseClient with connection pooling. Resolved.