You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add regression tests for tool-call timeout handling
Extract the shared "race work against a timeout" logic used by
DebuggingExecutor.dapRequest and DebugMCPServer.runTool into a tested
withTimeout() utility (behavior preserved), and add regression coverage
for the "server stuck when a tool call hangs" fix:
- withTimeout.test.ts: resolves fast work, propagates work rejections,
rejects with the caller's error when work hangs, and clears the timer
so a late-but-eventual result still wins.
- routing.test.ts: a control server that accepts but never responds must
cause handleStartDebugging to reject with the actionable "did not
respond within ... unresponsive" message. RoutingDebuggingHandler now
accepts an optional forwardTimeoutMs override so the test runs fast.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 6ea24b92-40ad-4539-aa13-61aa6ff8751f
0 commit comments