yujonglee 2d79d5dba7 refactor(proxy): give database shutdown one lifespan owner (#48506) ... * refactor(proxy): give database shutdown one lifespan owner Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(proxy): log database cleanup errors and bound shutdown waits Database.aclose now logs a failure in either cleanup step instead of raising out of the lifespan exit, which matches how main handled stop errors and keeps setup_prisma_client from raising out of cleanup after a failed connect Shutdown waits for an in-flight reconnect for a fixed five seconds instead of the reconnect timeout plus grace, and joins engine wait threads with a fixed limit instead of indefinitely. The threads are daemon threads, so a thread still alive after the limit cannot keep the process from exiting Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>		2026-10-30 22:57:53 +00:00
..
helpers	fix(responses): run the guardrails a Responses WebSocket frame selects (#48725)	2026-10-30 14:12:51 -07:00
prisma_and_spend	refactor(proxy): give database shutdown one lifespan owner (#48506)	2026-10-30 22:57:53 +00:00
proxy_logging	fix(proxy)!: log and bill Responses-style bodies sent to /cursor/chat/completions (#30277)	2026-10-30 00:18:15 -07:00
__init__.py	test(proxy): move utils, agent_endpoints and endpoint tests into tests/unit/proxy (#44006)	2026-10-01 11:06:42 -07:00