chore(deps): update all non-major dependencies #524
Annotations
6 errors
|
Run pnpm vitest --coverage
Process completed with exit code 1.
|
|
Run pnpm vitest --coverage:
test/http-proxy.test.ts#L66
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".
❯ test/http-proxy.test.ts:66:5
|
|
Run pnpm vitest --coverage:
test/https-proxy.test.ts#L120
AssertionError: expected 'data: Hello over SSE\n\n' to deeply equal 'Hello from 1026'
- Expected
+ Received
- Hello from 1026
+ data: Hello over SSE
+
+
❯ IncomingMessage.<anonymous> test/https-proxy.test.ts:120:44
❯ IncomingMessage.emit node:events:519:28
❯ IncomingMessage.Readable.read node:internal/streams/readable:782:10
❯ flow node:internal/streams/readable:1283:53
❯ emitReadable_ node:internal/streams/readable:847:3
❯ onEofChunk node:internal/streams/readable:812:5
❯ readableAddChunkPushByteMode node:internal/streams/readable:466:5
❯ IncomingMessage.Readable.push node:internal/streams/readable:392:5
❯ HTTPParser.parserOnMessageComplete node:_http_common:154:12
❯ Socket.socketOnData node:_http_client:558:22
This error originated in "test/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 en 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.
|
|
Run pnpm vitest --coverage:
test/https-proxy.test.ts#L120
AssertionError: expected ':ok\n\n' to deeply equal 'Hello from 1026'
- Expected
+ Received
- Hello from 1026
+ :ok
+
+
❯ IncomingMessage.<anonymous> test/https-proxy.test.ts:120:44
❯ IncomingMessage.emit node:events:519:28
❯ IncomingMessage.Readable.read node:internal/streams/readable:782:10
❯ flow node:internal/streams/readable:1283:53
❯ resume_ node:internal/streams/readable:1262:3
❯ processTicksAndRejections node:internal/process/task_queues:90:21
This error originated in "test/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 en 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.
|
|
Run pnpm vitest --coverage:
src/server.ts#L71
Error: listen EADDRINUSE: address already in use :::1027
❯ Server.setupListenHandle [as _listen2] node:net:1940:16
❯ listenInCluster node:net:1997:12
❯ Server.listen node:net:2102:7
❯ ProxyServer.listen src/server.ts:71:18
❯ test/https-proxy.test.ts:107:12
❯ node_modules/.pnpm/@vitest[email protected]/node_modules/@vitest/runner/dist/chunk-hooks.js:155:11
❯ node_modules/.pnpm/@vitest[email protected]/node_modules/@vitest/runner/dist/chunk-hooks.js:752:26
❯ node_modules/.pnpm/@vitest[email protected]/node_modules/@vitest/runner/dist/chunk-hooks.js:1897:20
❯ runWithTimeout node_modules/.pnpm/@vitest[email protected]/node_modules/@vitest/runner/dist/chunk-hooks.js:1863:10
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'EADDRINUSE', errno: -98, syscall: 'listen', address: '::', port: 1027 }
This error originated in "test/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 en 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.
|
|
Run pnpm vitest --coverage:
test/https-proxy.test.ts#L99
Error: listen EADDRINUSE: address already in use :::1026
❯ Server.setupListenHandle [as _listen2] node:net:1940:16
❯ listenInCluster node:net:1997:12
❯ Server.listen node:net:2102:7
❯ test/https-proxy.test.ts:99:16
❯ node_modules/.pnpm/@vitest[email protected]/node_modules/@vitest/runner/dist/chunk-hooks.js:155:11
❯ node_modules/.pnpm/@vitest[email protected]/node_modules/@vitest/runner/dist/chunk-hooks.js:752:26
❯ node_modules/.pnpm/@vitest[email protected]/node_modules/@vitest/runner/dist/chunk-hooks.js:1897:20
❯ runWithTimeout node_modules/.pnpm/@vitest[email protected]/node_modules/@vitest/runner/dist/chunk-hooks.js:1863:10
❯ runTest node_modules/.pnpm/@vitest[email protected]/node_modules/@vitest/runner/dist/chunk-hooks.js:1574:12
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'EADDRINUSE', errno: -98, syscall: 'listen', address: '::', port: 1026 }
This error originated in "test/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 en 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.
|
Loading