Skip to content

Add automatic message encoding/decoding via codec registry #527

Add automatic message encoding/decoding via codec registry

Add automatic message encoding/decoding via codec registry #527

Triggered via pull request March 16, 2026 09:20
Status Failure
Total duration 1m 29s
Artifacts

ci.yml

on: pull_request
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

35 errors and 6 warnings
test (24.x)
Process completed with exit code 2.
test (24.x): test/test.ts#L814
Argument of type 'unknown' is not assignable to parameter of type 'string | ArrayBuffer | Uint8Array<ArrayBufferLike> | Buffer<ArrayBufferLike> | null'.
test (24.x): test/test.ts#L814
Argument of type 'unknown' is not assignable to parameter of type 'string | ArrayBuffer | Uint8Array<ArrayBufferLike> | Buffer<ArrayBufferLike> | null'.
test (24.x): test/test.ts#L799
Property 'length' does not exist on type '{}'.
test (24.x): test-browser/websocket.ts#L743
Argument of type 'unknown' is not assignable to parameter of type 'string | ArrayBuffer | Uint8Array<ArrayBufferLike> | Buffer<ArrayBufferLike> | null'.
test (24.x): test-browser/websocket.ts#L743
Argument of type 'unknown' is not assignable to parameter of type 'string | ArrayBuffer | Uint8Array<ArrayBufferLike> | Buffer<ArrayBufferLike> | null'.
test (24.x): test-browser/websocket.ts#L727
Property 'length' does not exist on type '{}'.
test (18.x)
Process completed with exit code 2.
test (18.x): test/test.ts#L814
Argument of type 'unknown' is not assignable to parameter of type 'string | ArrayBuffer | Uint8Array<ArrayBufferLike> | Buffer<ArrayBufferLike> | null'.
test (18.x): test/test.ts#L814
Argument of type 'unknown' is not assignable to parameter of type 'string | ArrayBuffer | Uint8Array<ArrayBufferLike> | Buffer<ArrayBufferLike> | null'.
test (18.x): test/test.ts#L799
Property 'length' does not exist on type '{}'.
test (18.x): test-browser/websocket.ts#L743
Argument of type 'unknown' is not assignable to parameter of type 'string | ArrayBuffer | Uint8Array<ArrayBufferLike> | Buffer<ArrayBufferLike> | null'.
test (18.x): test-browser/websocket.ts#L743
Argument of type 'unknown' is not assignable to parameter of type 'string | ArrayBuffer | Uint8Array<ArrayBufferLike> | Buffer<ArrayBufferLike> | null'.
test (18.x): test-browser/websocket.ts#L727
Property 'length' does not exist on type '{}'.
test (23.x)
Process completed with exit code 2.
test (23.x): test/test.ts#L814
Argument of type 'unknown' is not assignable to parameter of type 'string | ArrayBuffer | Uint8Array<ArrayBufferLike> | Buffer<ArrayBufferLike> | null'.
test (23.x): test/test.ts#L814
Argument of type 'unknown' is not assignable to parameter of type 'string | ArrayBuffer | Uint8Array<ArrayBufferLike> | Buffer<ArrayBufferLike> | null'.
test (23.x): test/test.ts#L799
Property 'length' does not exist on type '{}'.
test (23.x): test-browser/websocket.ts#L743
Argument of type 'unknown' is not assignable to parameter of type 'string | ArrayBuffer | Uint8Array<ArrayBufferLike> | Buffer<ArrayBufferLike> | null'.
test (23.x): test-browser/websocket.ts#L743
Argument of type 'unknown' is not assignable to parameter of type 'string | ArrayBuffer | Uint8Array<ArrayBufferLike> | Buffer<ArrayBufferLike> | null'.
test (23.x): test-browser/websocket.ts#L727
Property 'length' does not exist on type '{}'.
test (22.x)
Process completed with exit code 2.
test (22.x): test/test.ts#L814
Argument of type 'unknown' is not assignable to parameter of type 'string | ArrayBuffer | Uint8Array<ArrayBufferLike> | Buffer<ArrayBufferLike> | null'.
test (22.x): test/test.ts#L814
Argument of type 'unknown' is not assignable to parameter of type 'string | ArrayBuffer | Uint8Array<ArrayBufferLike> | Buffer<ArrayBufferLike> | null'.
test (22.x): test/test.ts#L799
Property 'length' does not exist on type '{}'.
test (22.x): test-browser/websocket.ts#L743
Argument of type 'unknown' is not assignable to parameter of type 'string | ArrayBuffer | Uint8Array<ArrayBufferLike> | Buffer<ArrayBufferLike> | null'.
test (22.x): test-browser/websocket.ts#L743
Argument of type 'unknown' is not assignable to parameter of type 'string | ArrayBuffer | Uint8Array<ArrayBufferLike> | Buffer<ArrayBufferLike> | null'.
test (22.x): test-browser/websocket.ts#L727
Property 'length' does not exist on type '{}'.
test (20.x)
Process completed with exit code 2.
test (20.x): test/test.ts#L814
Argument of type 'unknown' is not assignable to parameter of type 'string | ArrayBuffer | Uint8Array<ArrayBufferLike> | Buffer<ArrayBufferLike> | null'.
test (20.x): test/test.ts#L814
Argument of type 'unknown' is not assignable to parameter of type 'string | ArrayBuffer | Uint8Array<ArrayBufferLike> | Buffer<ArrayBufferLike> | null'.
test (20.x): test/test.ts#L799
Property 'length' does not exist on type '{}'.
test (20.x): test-browser/websocket.ts#L743
Argument of type 'unknown' is not assignable to parameter of type 'string | ArrayBuffer | Uint8Array<ArrayBufferLike> | Buffer<ArrayBufferLike> | null'.
test (20.x): test-browser/websocket.ts#L743
Argument of type 'unknown' is not assignable to parameter of type 'string | ArrayBuffer | Uint8Array<ArrayBufferLike> | Buffer<ArrayBufferLike> | null'.
test (20.x): test-browser/websocket.ts#L727
Property 'length' does not exist on type '{}'.
test-browser
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test (24.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, Homebrew/actions/setup-homebrew@master. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test (18.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, Homebrew/actions/setup-homebrew@master. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test (23.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, Homebrew/actions/setup-homebrew@master. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test (22.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, Homebrew/actions/setup-homebrew@master. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test (20.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, Homebrew/actions/setup-homebrew@master. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/