Commit 16b80f1
authored
feat: capture and log container stderr when MCP connection fails (#615)
When a container/process fails to launch, the stderr output is now
captured and logged to help diagnose issues. This is particularly useful
for debugging container startup failures where the error message is
written to stderr.
The SDK's CommandTransport only uses stdin/stdout for the MCP protocol,
so we can safely capture stderr separately for debugging purposes.1 file changed
Lines changed: 16 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
190 | 190 | | |
191 | 191 | | |
192 | 192 | | |
| 193 | + | |
| 194 | + | |
| 195 | + | |
| 196 | + | |
| 197 | + | |
| 198 | + | |
193 | 199 | | |
194 | 200 | | |
195 | 201 | | |
| |||
208 | 214 | | |
209 | 215 | | |
210 | 216 | | |
| 217 | + | |
| 218 | + | |
| 219 | + | |
| 220 | + | |
| 221 | + | |
| 222 | + | |
| 223 | + | |
| 224 | + | |
| 225 | + | |
| 226 | + | |
211 | 227 | | |
212 | 228 | | |
213 | 229 | | |
| |||
0 commit comments