Error: Test timed out in 5000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ lib/test/lib/http-proxy.test.ts:403:3

Error: Test timed out in 5000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ lib/test/lib/http-proxy.test.ts:403:3

Error: Test timed out in 5000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ lib/test/lib/http-proxy.test.ts:79:3

Error: Test timed out in 5000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ lib/test/lib/http-proxy.test.ts:79:3

Error: Test timed out in 5000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ lib/test/lib/http-proxy.test.ts:52:3

Error: Test timed out in 5000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ lib/test/lib/http-proxy.test.ts:52:3

TypeError: fetch failed ❯ stream2 lib/http-proxy/passes/web-incoming.ts:353:22 This error originated in "lib/test/lib/http-proxy.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 emit open and close events when socket.io client connects and disconnects". 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. Caused by: Caused by: Error: unknown scheme ❯ stream2 lib/http-proxy/passes/web-incoming.ts:353:28 ❯ stream lib/http-proxy/passes/web-incoming.ts:90:12 ❯ ProxyServer.web lib/http-proxy/index.ts:439:13

TypeError: fetch failed ❯ stream2 lib/http-proxy/passes/web-incoming.ts:353:22 This error originated in "lib/test/lib/http-proxy.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 emit open and close events when socket.io client connects and disconnects". 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. Caused by: Caused by: Error: unknown scheme ❯ stream2 lib/http-proxy/passes/web-incoming.ts:353:28 ❯ stream lib/http-proxy/passes/web-incoming.ts:90:12

TypeError: fetch failed ❯ stream2 lib/http-proxy/passes/web-incoming.ts:353:22 This error originated in "lib/test/lib/http-proxy.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 proxy a socket.io stream". 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. Caused by: Caused by: Error: unknown scheme ❯ stream2 lib/http-proxy/passes/web-incoming.ts:353:28 ❯ stream lib/http-proxy/passes/web-incoming.ts:90:12 ❯ ProxyServer.web lib/http-proxy/index.ts:439:13

TypeError: fetch failed ❯ stream2 lib/http-proxy/passes/web-incoming.ts:353:22 This error originated in "lib/test/lib/http-proxy.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 proxy a socket.io stream". 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. Caused by: Caused by: Error: unknown scheme ❯ stream2 lib/http-proxy/passes/web-incoming.ts:353:28 ❯ stream lib/http-proxy/passes/web-incoming.ts:90:12

AssertionError: expected '40811' to deeply equal '35801' ❯ Server.<anonymous> lib/test/lib/https-proxy.test.ts:247:49 This error originated in "lib/test/lib/https-proxy.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 proxy the request, then send back the response". 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.

TypeError: fetch failed ❯ stream2 lib/http-proxy/passes/web-incoming.ts:353:22 This error originated in "lib/test/websocket/websocket-proxy-websocket.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 "Make a client request to outer proxy server". 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. Caused by: Caused by: Error: unknown scheme ❯ stream2 lib/http-proxy/passes/web-incoming.ts:353:28 ❯ stream lib/http-proxy/passes/web-incoming.ts:90:12 ❯ ProxyServer.web lib/http-proxy/index.ts:439:13

TypeError: fetch failed ❯ stream2 lib/http-proxy/passes/web-incoming.ts:353:22 This error originated in "lib/test/websocket/websocket-proxy-websocket.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 "Make a client request to outer proxy server". 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. Caused by: Caused by: Error: unknown scheme ❯ stream2 lib/http-proxy/passes/web-incoming.ts:353:28 ❯ stream lib/http-proxy/passes/web-incoming.ts:90:12

AssertionError: expected '42117' to deeply equal '42221' ❯ Server.<anonymous> lib/test/lib/https-proxy.test.ts:247:49 This error originated in "lib/test/lib/https-proxy.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 proxy the request, then send back the response". 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.

AssertionError: expected '42929' to deeply equal '40857' ❯ Server.<anonymous> lib/test/lib/http-proxy.test.ts:92:51 This error originated in "lib/test/lib/http-proxy.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 make the request on pipe and finish it". 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.

AssertionError: expected '34225' to deeply equal '37111' ❯ Server.<anonymous> lib/test/lib/http-proxy.test.ts:92:51 This error originated in "lib/test/lib/http-proxy.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 make the request on pipe and finish it". 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.

TypeError: fetch failed ❯ stream2 lib/http-proxy/passes/web-incoming.ts:353:22 This error originated in "lib/test/websocket/websocket-proxy-websocket.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 "Make a client request to inner proxy server". 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. Caused by: Caused by: Error: unknown scheme ❯ stream2 lib/http-proxy/passes/web-incoming.ts:353:28 ❯ stream lib/http-proxy/passes/web-incoming.ts:90:12

TypeError: fetch failed ❯ stream2 lib/http-proxy/passes/web-incoming.ts:353:22 This error originated in "lib/test/websocket/websocket-proxy-websocket.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 "Make a client request to inner proxy server". 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. Caused by: Caused by: Error: unknown scheme ❯ stream2 lib/http-proxy/passes/web-incoming.ts:353:28 ❯ stream lib/http-proxy/passes/web-incoming.ts:90:12 ❯ ProxyServer.web lib/http-proxy/index.ts:439:13

AssertionError: expected '34157' to deeply equal '39203' ❯ Server.<anonymous> lib/test/lib/http-proxy.test.ts:65:51 This error originated in "lib/test/lib/http-proxy.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 pipe the request using web-incoming#stream method". 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.

AssertionError: expected '41501' to deeply equal '44691' ❯ Server.<anonymous> lib/test/lib/http-proxy.test.ts:65:51 This error originated in "lib/test/lib/http-proxy.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 pipe the request using web-incoming#stream method". 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.

The strategy configuration was canceled because "build._20" failed

Error: Test timed out in 5000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ lib/test/lib/http-proxy.test.ts:403:3

Error: Test timed out in 5000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ lib/test/lib/http-proxy.test.ts:79:3

Error: Test timed out in 5000ms. If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout". ❯ lib/test/lib/http-proxy.test.ts:52:3

TypeError: fetch failed ❯ stream2 lib/http-proxy/passes/web-incoming.ts:353:22 This error originated in "lib/test/lib/http-proxy.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 emit open and close events when socket.io client connects and disconnects". 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. Caused by: Caused by: Error: unknown scheme ❯ stream2 lib/http-proxy/passes/web-incoming.ts:353:28 ❯ stream lib/http-proxy/passes/web-incoming.ts:90:12

TypeError: fetch failed ❯ stream2 lib/http-proxy/passes/web-incoming.ts:353:22 This error originated in "lib/test/lib/http-proxy.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 proxy a socket.io stream". 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. Caused by: Caused by: Error: unknown scheme ❯ stream2 lib/http-proxy/passes/web-incoming.ts:353:28 ❯ stream lib/http-proxy/passes/web-incoming.ts:90:12

AssertionError: expected '33213' to deeply equal '46053' ❯ Server.<anonymous> lib/test/lib/https-proxy.test.ts:247:49 This error originated in "lib/test/lib/https-proxy.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 proxy the request, then send back the response". 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.

TypeError: fetch failed ❯ stream2 lib/http-proxy/passes/web-incoming.ts:353:22 This error originated in "lib/test/websocket/websocket-proxy-websocket.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 "Make a client request to outer proxy server". 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. Caused by: Caused by: Error: unknown scheme ❯ stream2 lib/http-proxy/passes/web-incoming.ts:353:28 ❯ stream lib/http-proxy/passes/web-incoming.ts:90:12

AssertionError: expected '39451' to deeply equal '46661' ❯ Server.<anonymous> lib/test/lib/http-proxy.test.ts:92:51 This error originated in "lib/test/lib/http-proxy.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 make the request on pipe and finish it". 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.

TypeError: fetch failed ❯ stream2 lib/http-proxy/passes/web-incoming.ts:353:22 This error originated in "lib/test/websocket/websocket-proxy-websocket.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 "Make a client request to inner proxy server". 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. Caused by: Caused by: Error: unknown scheme ❯ stream2 lib/http-proxy/passes/web-incoming.ts:353:28 ❯ stream lib/http-proxy/passes/web-incoming.ts:90:12