frontend: Add websocket multiplexer #6609
frontend.yml
on: pull_request
Matrix: build
Matrix: build docs
Matrix: build storybook
Matrix: lint
Matrix: test
Matrix: test plugins
Annotations
11 errors
Unhandled error:
frontend/src/lib/k8s/api/v1/apiProxy.test.ts#L518
AssertionError: expected 1st "spy" call to have been called with [ [] ], but called only 0 times
❯ Server.<anonymous> src/lib/k8s/api/v1/apiProxy.test.ts:518:24
❯ node_modules/mock-socket/dist/mock-socket.js:857:16
❯ Server.dispatchEvent node_modules/mock-socket/dist/mock-socket.js:855:13
❯ WebSocket.delayCallback node_modules/mock-socket/dist/mock-socket.js:1526:18
❯ Timeout._onTimeout node_modules/mock-socket/dist/mock-socket.js:757:58
❯ listOnTimeout node:internal/timers:583:11
❯ processTimers node:internal/timers:519:7
This error originated in "src/lib/k8s/api/v1/apiProxy.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 "Successfully handles ADDED, MODIFIED, and DELETED types". 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.
|
Unhandled error:
frontend/src/lib/k8s/api/v1/apiProxy.test.ts#L518
AssertionError: expected 1st "spy" call to have been called with [ [] ], but called only 0 times
❯ Server.<anonymous> src/lib/k8s/api/v1/apiProxy.test.ts:518:24
❯ node_modules/mock-socket/dist/mock-socket.js:857:16
❯ Server.dispatchEvent node_modules/mock-socket/dist/mock-socket.js:855:13
❯ WebSocket.delayCallback node_modules/mock-socket/dist/mock-socket.js:1526:18
❯ Timeout._onTimeout node_modules/mock-socket/dist/mock-socket.js:757:58
❯ listOnTimeout node:internal/timers:583:11
❯ processTimers node:internal/timers:519:7
This error originated in "src/lib/k8s/api/v1/apiProxy.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 "Successfully handles ADDED, MODIFIED, and DELETED types". 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.
|
Unhandled error:
frontend/src/lib/k8s/api/v1/apiProxy.test.ts#L518
AssertionError: expected 1st "spy" call to have been called with [ [] ], but called only 0 times
❯ Server.<anonymous> src/lib/k8s/api/v1/apiProxy.test.ts:518:24
❯ node_modules/mock-socket/dist/mock-socket.js:857:16
❯ Server.dispatchEvent node_modules/mock-socket/dist/mock-socket.js:855:13
❯ WebSocket.delayCallback node_modules/mock-socket/dist/mock-socket.js:1526:18
❯ Timeout._onTimeout node_modules/mock-socket/dist/mock-socket.js:757:58
❯ listOnTimeout node:internal/timers:583:11
❯ processTimers node:internal/timers:519:7
This error originated in "src/lib/k8s/api/v1/apiProxy.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 "Successfully handles ADDED, MODIFIED, and DELETED types". 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.
|
Unhandled error:
frontend/src/lib/k8s/api/v1/apiProxy.test.ts#L518
AssertionError: expected 1st "spy" call to have been called with [ [] ], but called only 0 times
❯ Server.<anonymous> src/lib/k8s/api/v1/apiProxy.test.ts:518:24
❯ node_modules/mock-socket/dist/mock-socket.js:857:16
❯ Server.dispatchEvent node_modules/mock-socket/dist/mock-socket.js:855:13
❯ WebSocket.delayCallback node_modules/mock-socket/dist/mock-socket.js:1526:18
❯ Timeout._onTimeout node_modules/mock-socket/dist/mock-socket.js:757:58
❯ listOnTimeout node:internal/timers:583:11
❯ processTimers node:internal/timers:519:7
This error originated in "src/lib/k8s/api/v1/apiProxy.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 "Successfully handles ADDED, MODIFIED, and DELETED types". 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.
|
Unhandled error:
frontend/src/lib/k8s/api/v1/apiProxy.test.ts#L573
AssertionError: expected "spy" to be called with arguments: [ [ { actionType: 'ADDED', …(4) } ] ]
Received:
Number of calls: 0
❯ Proxy.<anonymous> node_modules/vitest/node_modules/@vitest/expect/dist/index.js:1423:13
❯ Proxy.<anonymous> node_modules/vitest/node_modules/@vitest/expect/dist/index.js:930:17
❯ Proxy.methodWrapper node_modules/chai/chai.js:1591:25
❯ Server.<anonymous> src/lib/k8s/api/v1/apiProxy.test.ts:573:28
❯ node_modules/mock-socket/dist/mock-socket.js:857:16
❯ Server.dispatchEvent node_modules/mock-socket/dist/mock-socket.js:855:13
❯ WebSocket.delayCallback node_modules/mock-socket/dist/mock-socket.js:1526:18
❯ Timeout._onTimeout node_modules/mock-socket/dist/mock-socket.js:757:58
❯ listOnTimeout node:internal/timers:583:11
This error originated in "src/lib/k8s/api/v1/apiProxy.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 "Successfully handles stream cancellation". 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.
|
Unhandled error:
frontend/src/lib/k8s/api/v1/apiProxy.test.ts#L573
AssertionError: expected "spy" to be called with arguments: [ [ { actionType: 'ADDED', …(4) } ] ]
Received:
Number of calls: 0
❯ Proxy.<anonymous> node_modules/vitest/node_modules/@vitest/expect/dist/index.js:1423:13
❯ Proxy.<anonymous> node_modules/vitest/node_modules/@vitest/expect/dist/index.js:930:17
❯ Proxy.methodWrapper node_modules/chai/chai.js:1591:25
❯ Server.<anonymous> src/lib/k8s/api/v1/apiProxy.test.ts:573:28
❯ node_modules/mock-socket/dist/mock-socket.js:857:16
❯ Server.dispatchEvent node_modules/mock-socket/dist/mock-socket.js:855:13
❯ WebSocket.delayCallback node_modules/mock-socket/dist/mock-socket.js:1526:18
❯ Timeout._onTimeout node_modules/mock-socket/dist/mock-socket.js:757:58
❯ listOnTimeout node:internal/timers:583:11
This error originated in "src/lib/k8s/api/v1/apiProxy.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 "Successfully handles stream cancellation". 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.
|
Unhandled error:
frontend/src/lib/k8s/api/v1/apiProxy.test.ts#L573
AssertionError: expected "spy" to be called with arguments: [ [ { actionType: 'ADDED', …(4) } ] ]
Received:
Number of calls: 0
❯ Proxy.<anonymous> node_modules/vitest/node_modules/@vitest/expect/dist/index.js:1423:13
❯ Proxy.<anonymous> node_modules/vitest/node_modules/@vitest/expect/dist/index.js:930:17
❯ Proxy.methodWrapper node_modules/chai/chai.js:1591:25
❯ Server.<anonymous> src/lib/k8s/api/v1/apiProxy.test.ts:573:28
❯ node_modules/mock-socket/dist/mock-socket.js:857:16
❯ Server.dispatchEvent node_modules/mock-socket/dist/mock-socket.js:855:13
❯ WebSocket.delayCallback node_modules/mock-socket/dist/mock-socket.js:1526:18
❯ Timeout._onTimeout node_modules/mock-socket/dist/mock-socket.js:757:58
❯ listOnTimeout node:internal/timers:583:11
This error originated in "src/lib/k8s/api/v1/apiProxy.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 "Successfully handles stream cancellation". 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.
|
Unhandled error:
frontend/src/lib/k8s/api/v1/apiProxy.test.ts#L573
AssertionError: expected "spy" to be called with arguments: [ [ { actionType: 'ADDED', …(4) } ] ]
Received:
Number of calls: 0
❯ Proxy.<anonymous> node_modules/vitest/node_modules/@vitest/expect/dist/index.js:1423:13
❯ Proxy.<anonymous> node_modules/vitest/node_modules/@vitest/expect/dist/index.js:930:17
❯ Proxy.methodWrapper node_modules/chai/chai.js:1591:25
❯ Server.<anonymous> src/lib/k8s/api/v1/apiProxy.test.ts:573:28
❯ node_modules/mock-socket/dist/mock-socket.js:857:16
❯ Server.dispatchEvent node_modules/mock-socket/dist/mock-socket.js:855:13
❯ WebSocket.delayCallback node_modules/mock-socket/dist/mock-socket.js:1526:18
❯ Timeout._onTimeout node_modules/mock-socket/dist/mock-socket.js:757:58
❯ listOnTimeout node:internal/timers:583:11
This error originated in "src/lib/k8s/api/v1/apiProxy.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 "Successfully handles stream cancellation". 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.
|
Unhandled error:
frontend/src/lib/k8s/api/v1/apiProxy.test.ts#L573
AssertionError: expected "spy" to be called with arguments: [ [ { actionType: 'ADDED', …(4) } ] ]
Received:
Number of calls: 0
❯ Proxy.<anonymous> node_modules/vitest/node_modules/@vitest/expect/dist/index.js:1423:13
❯ Proxy.<anonymous> node_modules/vitest/node_modules/@vitest/expect/dist/index.js:930:17
❯ Proxy.methodWrapper node_modules/chai/chai.js:1591:25
❯ Server.<anonymous> src/lib/k8s/api/v1/apiProxy.test.ts:573:28
❯ node_modules/mock-socket/dist/mock-socket.js:857:16
❯ Server.dispatchEvent node_modules/mock-socket/dist/mock-socket.js:855:13
❯ WebSocket.delayCallback node_modules/mock-socket/dist/mock-socket.js:1526:18
❯ Timeout._onTimeout node_modules/mock-socket/dist/mock-socket.js:757:58
❯ listOnTimeout node:internal/timers:583:11
This error originated in "src/lib/k8s/api/v1/apiProxy.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 "Successfully handles stream cancellation". 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.
|
Unhandled error:
frontend/src/lib/k8s/api/v1/apiProxy.test.ts#L573
AssertionError: expected "spy" to be called with arguments: [ [ { actionType: 'ADDED', …(4) } ] ]
Received:
Number of calls: 0
❯ Proxy.<anonymous> node_modules/vitest/node_modules/@vitest/expect/dist/index.js:1423:13
❯ Proxy.<anonymous> node_modules/vitest/node_modules/@vitest/expect/dist/index.js:930:17
❯ Proxy.methodWrapper node_modules/chai/chai.js:1591:25
❯ Server.<anonymous> src/lib/k8s/api/v1/apiProxy.test.ts:573:28
❯ node_modules/mock-socket/dist/mock-socket.js:857:16
❯ Server.dispatchEvent node_modules/mock-socket/dist/mock-socket.js:855:13
❯ WebSocket.delayCallback node_modules/mock-socket/dist/mock-socket.js:1526:18
❯ Timeout._onTimeout node_modules/mock-socket/dist/mock-socket.js:757:58
❯ listOnTimeout node:internal/timers:583:11
This error originated in "src/lib/k8s/api/v1/apiProxy.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 "Successfully handles stream cancellation". 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.
|
test plugins (20.x, ubuntu-22.04)
Process completed with exit code 2.
|