Commit 06280fb
authored
fix: soft-fail MCP server connection errors instead of throwing (#485)
When both transports (streamable HTTP + SSE) fail to connect to an
external MCP server, the error was thrown and double-logged via
logHttpError (which emits log.exception for 500s), causing noisy
alerts in Mezmo during bug duty.
Now connectMCPClient returns null on all connection failures (matching
the existing timeout behavior) and logs via log.softFail instead.
This eliminates double-logging since all callers already handle null
returns gracefully.1 parent 136d2d8 commit 06280fb
1 file changed
Lines changed: 12 additions & 8 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
5 | 5 | | |
6 | 6 | | |
7 | 7 | | |
8 | | - | |
| 8 | + | |
9 | 9 | | |
10 | 10 | | |
11 | 11 | | |
| |||
16 | 16 | | |
17 | 17 | | |
18 | 18 | | |
19 | | - | |
20 | 19 | | |
21 | | - | |
22 | | - | |
| 20 | + | |
23 | 21 | | |
24 | 22 | | |
25 | 23 | | |
| |||
34 | 32 | | |
35 | 33 | | |
36 | 34 | | |
37 | | - | |
38 | | - | |
| 35 | + | |
39 | 36 | | |
40 | 37 | | |
41 | 38 | | |
42 | 39 | | |
43 | 40 | | |
44 | | - | |
45 | | - | |
| 41 | + | |
| 42 | + | |
| 43 | + | |
| 44 | + | |
| 45 | + | |
| 46 | + | |
| 47 | + | |
| 48 | + | |
| 49 | + | |
46 | 50 | | |
47 | 51 | | |
48 | 52 | | |
| |||
0 commit comments