build #1710
glasstigerAnnotations
10 errors and 3 warnings
|
test/sender.transport.test.ts > Sender TCP suite > guards against concurrent connect calls:
test/sender.transport.test.ts#L494
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/sender.transport.test.ts:494:3
|
|
test/sender.transport.test.ts > Sender TCP suite > guards against multiple connect calls:
test/sender.transport.test.ts#L484
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/sender.transport.test.ts:484:3
|
|
test/sender.transport.test.ts > Sender TCP suite > can connect unauthenticated and send data to server via secure connection:
test/sender.transport.test.ts#L452
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/sender.transport.test.ts:452:3
|
|
test/sender.transport.test.ts > Sender TCP suite > can authenticate and send data to server via secure connection:
test/sender.transport.test.ts#L439
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/sender.transport.test.ts:439:3
|
|
test/sender.transport.test.ts > Sender TCP suite > can connect unauthenticated and send data to server:
test/sender.transport.test.ts#L425
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/sender.transport.test.ts:425:3
|
|
test/sender.transport.test.ts > Sender TCP suite > can authenticate and send data to server:
test/sender.transport.test.ts#L412
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/sender.transport.test.ts:412:3
|
|
test/sender.transport.test.ts > Sender TCP suite > can connect unauthenticated:
test/sender.transport.test.ts#L403
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/sender.transport.test.ts:403:3
|
|
test/sender.transport.test.ts > Sender TCP suite > is backwards compatible and still can authenticate with full JWK:
test/sender.transport.test.ts#L378
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/sender.transport.test.ts:378:3
|
|
test/sender.transport.test.ts > Sender TCP suite > can authenticate with a different private key:
test/sender.transport.test.ts#L367
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/sender.transport.test.ts:367:3
|
|
Unhandled error:
src/transport/tcp.ts#L223
TypeError: Invalid JWK EC key
❯ Object.createPrivateKey node:internal/crypto/keys:951:10
❯ TcpTransport.authenticate src/transport/tcp.ts:223:32
❯ Socket.<anonymous> src/transport/tcp.ts:119:40
❯ Socket.emit node:events:514:20
❯ addChunk node:internal/streams/readable:576:12
❯ readableAddChunkPushByteMode node:internal/streams/readable:527:3
❯ Socket.Readable.push node:internal/streams/readable:407:5
❯ TCP.onStreamRead node:internal/stream_base_commons:189:23
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_CRYPTO_INVALID_JWK' }
This error originated in "test/sender.transport.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 "can authenticate with a different private key". 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.
|
|
Build with Node.js 22
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build with Node.js 20
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Build with Node.js latest
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|