AssertionError: expected "error" to be called with arguments: [ StringContaining "Parse error" ] Received: 1st error call: Array [ - StringContaining "Parse error", + "[MCP Stdio] Connected", ] 2nd error call: Array [ - StringContaining "Parse error", + "[MCP Stdio] Stdin closed", ] Number of calls: 2 ❯ Timeout._onTimeout tests/mcp/transports/stdio.test.ts:583:33 This error originated in "tests/mcp/transports/stdio.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 "should clear message handler on close". 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: Queue cleared ❯ src/utils/queue.ts:117:19 ❯ ConcurrencyQueue.clear src/utils/queue.ts:116:18 ❯ tests/utils/queue.test.ts:407:13 This error originated in "tests/utils/queue.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 "should handle drain after clear". 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: Queue cleared ❯ src/utils/queue.ts:117:19 ❯ ConcurrencyQueue.clear src/utils/queue.ts:116:18 ❯ tests/utils/queue.test.ts:346:13 This error originated in "tests/utils/queue.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 "should not affect running tasks". 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: done() callback is deprecated, use promise instead ❯ Timeout._onTimeout tests/mcp/transports/stdio.test.ts:419:9 This error originated in "tests/mcp/transports/stdio.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 "should handle request and response cycle". 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: done() callback is deprecated, use promise instead ❯ Timeout._onTimeout tests/mcp/transports/stdio.test.ts:404:9 This error originated in "tests/mcp/transports/stdio.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 "should handle request and response cycle". 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: done() callback is deprecated, use promise instead ❯ Timeout._onTimeout tests/mcp/transports/stdio.test.ts:390:9 This error originated in "tests/mcp/transports/stdio.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 "should handle request and response cycle". 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: done() callback is deprecated, use promise instead ❯ Timeout._onTimeout tests/mcp/transports/stdio.test.ts:375:9 This error originated in "tests/mcp/transports/stdio.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 "should handle request and response cycle". 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: done() callback is deprecated, use promise instead ❯ Timeout._onTimeout tests/mcp/transports/stdio.test.ts:358:9 This error originated in "tests/mcp/transports/stdio.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 "should handle request and response cycle". 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: Connection pool cleared ❯ ConnectionPool.clear src/runtime/providers/connection-pool.ts:211:22 ❯ tests/runtime/providers/connection-pool.test.ts:571:12 This error originated in "tests/runtime/providers/connection-pool.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 "should handle async operations". 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: Connection pool cleared ❯ ConnectionPool.clear src/runtime/providers/connection-pool.ts:211:22 ❯ ConnectionPool.destroy src/runtime/providers/connection-pool.ts:224:10 ❯ tests/runtime/providers/connection-pool.test.ts:41:12 This error originated in "tests/runtime/providers/connection-pool.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 "should clear idle connections past 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.