AssertionError: expected true to be false // Object.is equality - Expected + Received - false + true ❯ src/paths-exdev.test.ts:72:39

Error: kill ESRCH ❯ process.kill node:internal/process/per_thread:281:13 ❯ Timeout._onTimeout src/agent/tools/handlers/bash.ts:255:17 ❯ listOnTimeout node:internal/timers:585:17 ❯ processTimers node:internal/timers:521:7 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { errno: -4040, code: 'ESRCH', syscall: 'kill' } This error originated in "src/agent/tools/handlers/overflow-telemetry.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "does NOT include the bash command string in the telemetry payload". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: kill ESRCH ❯ process.kill node:internal/process/per_thread:281:13 ❯ Timeout._onTimeout src/agent/tools/handlers/bash.ts:255:17 ❯ listOnTimeout node:internal/timers:585:17 ❯ processTimers node:internal/timers:521:7 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { errno: -4040, code: 'ESRCH', syscall: 'kill' } This error originated in "src/agent/tools/handlers/overflow-telemetry.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "emits tool.overflow_kill with operational fields when bash crosses the hard cap". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: kill ESRCH ❯ process.kill node:internal/process/per_thread:281:13 ❯ Timeout._onTimeout src/agent/tools/handlers/bash.ts:255:17 ❯ listOnTimeout node:internal/timers:585:17 ❯ processTimers node:internal/timers:521:7 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { errno: -4040, code: 'ESRCH', syscall: 'kill' } This error originated in "src/agent/tools/handlers/bash.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "[process-group kill] reaps descendant processes, not just the direct child". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: kill ESRCH ❯ process.kill node:internal/process/per_thread:281:13 ❯ Timeout._onTimeout src/agent/tools/handlers/bash.ts:255:17 ❯ listOnTimeout node:internal/timers:585:17 ❯ processTimers node:internal/timers:521:7 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { errno: -4040, code: 'ESRCH', syscall: 'kill' } This error originated in "src/agent/tools/handlers/bash.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "mid-stream hard cap: protects stderr from unbounded accumulation". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: kill ESRCH ❯ process.kill node:internal/process/per_thread:281:13 ❯ Timeout._onTimeout src/agent/tools/handlers/bash.ts:255:17 ❯ listOnTimeout node:internal/timers:585:17 ❯ processTimers node:internal/timers:521:7 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { errno: -4040, code: 'ESRCH', syscall: 'kill' } This error originated in "src/agent/tools/handlers/bash.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "mid-stream hard cap: SIGKILLs a runaway before it completes (V8 overflow guard)". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: kill ESRCH ❯ process.kill node:internal/process/per_thread:281:13 ❯ AbortSignal.abortHandler src/agent/tools/handlers/bash.ts:341:17 ❯ AbortSignal.[nodejs.internal.kHybridDispatch] node:internal/event_target:843:20 ❯ AbortSignal.dispatchEvent node:internal/event_target:776:26 ❯ runAbort node:internal/abort_controller:486:10 ❯ abortSignal node:internal/abort_controller:457:3 ❯ AbortController.abort node:internal/abort_controller:505:5 ❯ Timeout._onTimeout src/agent/tools/handlers/bash.test.ts:24:33 ❯ listOnTimeout node:internal/timers:585:17 ❯ processTimers node:internal/timers:521:7 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { errno: -4040, code: 'ESRCH', syscall: 'kill' } This error originated in "src/agent/tools/handlers/bash.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "aborts command when signal is aborted". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: kill ESRCH ❯ process.kill node:internal/process/per_thread:281:13 ❯ Timeout._onTimeout src/agent/tools/handlers/bash.ts:255:17 ❯ listOnTimeout node:internal/timers:585:17 ❯ processTimers node:internal/timers:521:7 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { errno: -4040, code: 'ESRCH', syscall: 'kill' } This error originated in "src/agent/tools/handlers/bash.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "respects short timeout". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: kill ESRCH ❯ process.kill node:internal/process/per_thread:281:13 ❯ Timeout._onTimeout src/agent/tools/handlers/bash.ts:255:17 ❯ listOnTimeout node:internal/timers:585:17 ❯ processTimers node:internal/timers:521:7 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { errno: -4040, code: 'ESRCH', syscall: 'kill' } This error originated in "src/agent/tools/handlers/bash.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "kills process on timeout and returns isError". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: kill ESRCH ❯ process.kill node:internal/process/per_thread:281:13 ❯ AbortSignal.abortHandler src/agent/tools/handlers/bash.ts:341:17 ❯ AbortSignal.[nodejs.internal.kHybridDispatch] node:internal/event_target:843:20 ❯ AbortSignal.dispatchEvent node:internal/event_target:776:26 ❯ runAbort node:internal/abort_controller:486:10 ❯ abortSignal node:internal/abort_controller:457:3 ❯ AbortController.abort node:internal/abort_controller:505:5 ❯ Timeout._onTimeout src/agent/tools/handlers/bash.test.ts:24:33 ❯ listOnTimeout node:internal/timers:585:17 ❯ processTimers node:internal/timers:521:7 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { errno: -4040, code: 'ESRCH', syscall: 'kill' } This error originated in "src/agent/tools/handlers/bash.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "abort returns "Command aborted", not "exited with code"". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/