devin-ai-integration[bot] 25ebb9458c fix(proxy): surface a database outage from the user read as 503 no_db_connection (#42399) ... get_user_object wrapped every failed read, a refused connection included, in ValueError("User doesn't exist in db ..."), so JWT callers got a 401 naming a missing user while Postgres was down and virtual-key callers got 503 no_db_connection for the same outage. A connection or transport error now propagates as-is and the auth exception mapper answers 503 no_db_connection; a genuinely missing row and query-level errors still answer 401. The MCP auth and token-exchange docstrings and the exception-chain helper's docstring described the old wrap and are updated to the new contract. Co-authored-by: mateo-berri <277851410+mateo-berri@users.noreply.github.com>		2026-09-21 20:52:41 -07:00
..
mcp_server	fix(proxy): surface a database outage from the user read as 503 no_db_connection (#42399)	2026-09-21 20:52:41 -07:00