Skip to content

Pipeline Fix

Pipeline Fix #39

Re-run triggered April 1, 2026 11:30
Status Failure
Total duration 24s
Artifacts

ci-thing-model.yaml

on: pull_request
Matrix: setup-and-test
Fit to window
Zoom out
Zoom in

Annotations

21 errors and 2 warnings
Tests (ubuntu-latest), Node 20.x
Property 'asyncDispose' does not exist on type 'SymbolConstructor'.
Tests (ubuntu-latest), Node 20.x
A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.
Tests (ubuntu-latest), Node 20.x
Property 'dispose' does not exist on type 'SymbolConstructor'.
Tests (ubuntu-latest), Node 20.x
A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.
Tests (ubuntu-latest), Node 20.x
'ReadableStreamBYOBRequest' is referenced directly or indirectly in its own type annotation.
Tests (ubuntu-latest), Node 20.x
'ReadableStreamBYOBReader' is referenced directly or indirectly in its own type annotation.
Tests (ubuntu-latest), Node 20.x
'ReadableByteStreamController' is referenced directly or indirectly in its own type annotation.
Tests (ubuntu-latest), Node 20.x
'DecompressionStream' is referenced directly or indirectly in its own type annotation.
Tests (ubuntu-latest), Node 20.x
'CompressionStream' is referenced directly or indirectly in its own type annotation.
Tests (ubuntu-latest), Node 20.x
Interface 'TextEncoder' incorrectly extends interface 'import("node:util").TextEncoder'.
Tests (ubuntu-latest), Node 22.x
The strategy configuration was canceled because "setup-and-test.ubuntu-latest_20_x" failed
Tests (ubuntu-latest), Node 22.x
Property 'asyncDispose' does not exist on type 'SymbolConstructor'.
Tests (ubuntu-latest), Node 22.x
A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.
Tests (ubuntu-latest), Node 22.x
Property 'dispose' does not exist on type 'SymbolConstructor'.
Tests (ubuntu-latest), Node 22.x
A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.
Tests (ubuntu-latest), Node 22.x
'ReadableStreamBYOBRequest' is referenced directly or indirectly in its own type annotation.
Tests (ubuntu-latest), Node 22.x
'ReadableStreamBYOBReader' is referenced directly or indirectly in its own type annotation.
Tests (ubuntu-latest), Node 22.x
'ReadableByteStreamController' is referenced directly or indirectly in its own type annotation.
Tests (ubuntu-latest), Node 22.x
'DecompressionStream' is referenced directly or indirectly in its own type annotation.
Tests (ubuntu-latest), Node 22.x
'CompressionStream' is referenced directly or indirectly in its own type annotation.
Tests (ubuntu-latest), Node 22.x
Interface 'TextEncoder' incorrectly extends interface 'import("node:util").TextEncoder'.
Tests (ubuntu-latest), Node 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@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Tests (ubuntu-latest), Node 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@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/