Skip to content

chore: upgrade Prettier and ESLint #1434

chore: upgrade Prettier and ESLint

chore: upgrade Prettier and ESLint #1434

Triggered via pull request February 28, 2025 23:26
Status Success
Total duration 30s
Artifacts

unit.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

3 errors
Unhandled error: src/token_manager.ts#L152
Error: Both secret and user tokens are not set. Either client.connectUser wasn't called or client.disconnect was called ❯ TokenManager.getToken src/token_manager.ts:152:11 ❯ StreamChat._getToken src/client.ts:3179:30 ❯ StreamChat._enrichAxiosOptions src/client.ts:3134:24 ❯ StreamChat.doAxiosRequest src/client.ts:1086:32 ❯ processTicksAndRejections node:internal/process/task_queues:105:5 ❯ Channel.query src/channel.ts:1270:19 This error originated in "test/unit/channel.test.js" 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 "test/unit/channel.test.js". 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: test/unit/connection_fallback.test.js#L238
Error: Error ❯ Object.rejects node_modules/sinon/pkg/sinon-esm.js:960:22 ❯ Object.proto.<computed> [as rejects] node_modules/sinon/pkg/sinon-esm.js:616:12 ❯ test/unit/connection_fallback.test.js:238:6 ❯ node_modules/@vitest/runner/dist/index.js:174:14 ❯ node_modules/@vitest/runner/dist/index.js:558:28 ❯ node_modules/@vitest/runner/dist/index.js:61:24 ❯ runWithTimeout node_modules/@vitest/runner/dist/index.js:41:12 ❯ runTest node_modules/@vitest/runner/dist/index.js:1137:17 ❯ processTicksAndRejections node:internal/process/task_queues:105:5 This error originated in "test/unit/connection_fallback.test.js" 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 "test/unit/connection_fallback.test.js". 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: test/unit/connection_fallback.test.js#L240
Error: Error ❯ Object.rejects node_modules/sinon/pkg/sinon-esm.js:960:22 ❯ Object.proto.<computed> [as rejects] node_modules/sinon/pkg/sinon-esm.js:616:12 ❯ test/unit/connection_fallback.test.js:240:6 ❯ node_modules/@vitest/runner/dist/index.js:174:14 ❯ node_modules/@vitest/runner/dist/index.js:558:28 ❯ node_modules/@vitest/runner/dist/index.js:61:24 ❯ runWithTimeout node_modules/@vitest/runner/dist/index.js:41:12 ❯ runTest node_modules/@vitest/runner/dist/index.js:1137:17 ❯ processTicksAndRejections node:internal/process/task_queues:105:5 This error originated in "test/unit/connection_fallback.test.js" 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 "test/unit/connection_fallback.test.js". 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.