Skip to content

Fix typescript linter errors #11949

Fix typescript linter errors

Fix typescript linter errors #11949

Triggered via pull request March 20, 2026 20:50
Status Failure
Total duration 43m 26s
Artifacts 2

ci.yml

on: pull_request
Matrix: lint-python-flake8
lint-python-yaml-docs
21s
lint-python-yaml-docs
lint-frontend
1m 24s
lint-frontend
lint-misc
15s
lint-misc
Matrix: build-data-server-pip
Matrix: lint-rust
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 9 warnings
lint-frontend
Process completed with exit code 1.
build (tf, 3.9)
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
build (tf, 3.9)
Process completed with exit code 1.
build (tf, 3.9)
Error: ScriptExecutorError when trying to execute: "Error: Job failed with exit code 1."
build (tf, 3.9)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
build (notf, 3.9)
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
build (notf, 3.9)
Process completed with exit code 1.
build (notf, 3.9)
Error: ScriptExecutorError when trying to execute: "Error: Job failed with exit code 1."
build (notf, 3.9)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
lint-misc
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@ac593985615ec2ede58e132d2e21d2b1cbd6127c. 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/
lint-python-flake8 (3.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@ac593985615ec2ede58e132d2e21d2b1cbd6127c, actions/setup-python@13ae5bb136fac2878aff31522b9efb785519f984. 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/
lint-python-flake8 (3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@ac593985615ec2ede58e132d2e21d2b1cbd6127c, actions/setup-python@13ae5bb136fac2878aff31522b9efb785519f984. 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/
build-data-server-pip (universal, ubuntu-22.04, 1.65.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@ac593985615ec2ede58e132d2e21d2b1cbd6127c, actions/setup-python@13ae5bb136fac2878aff31522b9efb785519f984, actions/upload-artifact@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/
lint-python-yaml-docs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@ac593985615ec2ede58e132d2e21d2b1cbd6127c, actions/setup-python@13ae5bb136fac2878aff31522b9efb785519f984. 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/
lint-python-flake8 (3.9)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@ac593985615ec2ede58e132d2e21d2b1cbd6127c, actions/setup-python@13ae5bb136fac2878aff31522b9efb785519f984. 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/
lint-rust (1.65.0, 0.16.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@ac593985615ec2ede58e132d2e21d2b1cbd6127c. 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/
build-data-server-pip (native, ubuntu-22.04, 1.65.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@ac593985615ec2ede58e132d2e21d2b1cbd6127c, actions/setup-python@13ae5bb136fac2878aff31522b9efb785519f984, actions/upload-artifact@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/
lint-frontend
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@ac593985615ec2ede58e132d2e21d2b1cbd6127c, actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c. 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/

Artifacts

Produced during runtime
Name Size Digest
tensorboard-data-server_native_ubuntu-22.04_1.65.0
4.2 MB
sha256:c75a80f6f707ed9a6c7e7fad2431326d5ab97e1352d0a292601bba1a9d1af652
tensorboard-data-server_universal_ubuntu-22.04_1.65.0
2.05 KB
sha256:b2ad73f752aedd20493e8d2fe0252dd86242555da7f1d9d6de52972e9710d534