Skip to content

Gateway exports

Gateway exports #7001

Re-run triggered May 4, 2026 07:48
Status Failure
Total duration 54s
Artifacts 7

build.yml

on: pull_request
compute-version
3s
compute-version
build-docs  /  build-docs
1m 15s
build-docs / build-docs
build-artifacts  /  code-lint
51s
build-artifacts / code-lint
build-artifacts  /  frontend-build
10s
build-artifacts / frontend-build
Matrix: build-artifacts / runner-test
build-artifacts  /  gateway-build
15s
build-artifacts / gateway-build
build-artifacts  /  generate-json-schema
17s
build-artifacts / generate-json-schema
Matrix: build-artifacts / python-test
build-artifacts  /  python-build
21s
build-artifacts / python-build
Matrix: build-artifacts / runner-compile
upload-post-pypi-artifacts  /  upload-post-pypi-artifacts
upload-post-pypi-artifacts / upload-post-pypi-artifacts
upload-pre-pypi-artifacts  /  upload-pre-pypi-artifacts
upload-pre-pypi-artifacts / upload-pre-pypi-artifacts
Fit to window
Zoom out
Zoom in

Annotations

25 errors and 12 warnings
build-artifacts / python-test (ubuntu-latest, 3.10): src/dstack/_internal/core/backends/aws/compute.py#L190
"get_offers_post_filter" overrides method of same name in class "ComputeWithAllOffersCached" with incompatible type "_cachedmethod_wrapper[((InstanceOfferWithAvailability) -> bool) | None]" (reportIncompatibleMethodOverride)
build-artifacts / python-test (macos-latest, 3.12)
The strategy configuration was canceled because "build-artifacts.python-test.ubuntu-latest_3_10" failed
build-artifacts / python-test (macos-latest, 3.12): src/dstack/_internal/core/backends/aws/compute.py#L190
"get_offers_post_filter" overrides method of same name in class "ComputeWithAllOffersCached" with incompatible type "_cachedmethod_wrapper[((InstanceOfferWithAvailability) -> bool) | None]" (reportIncompatibleMethodOverride)
build-artifacts / python-test (ubuntu-latest, 3.11)
The strategy configuration was canceled because "build-artifacts.python-test.ubuntu-latest_3_10" failed
build-artifacts / python-test (ubuntu-latest, 3.11)
The operation was canceled.
build-artifacts / python-test (macos-latest, 3.10)
The strategy configuration was canceled because "build-artifacts.python-test.ubuntu-latest_3_10" failed
build-artifacts / python-test (macos-latest, 3.10)
The operation was canceled.
build-artifacts / python-test (windows-latest, 3.10)
The strategy configuration was canceled because "build-artifacts.python-test.ubuntu-latest_3_10" failed
build-artifacts / python-test (windows-latest, 3.10)
The operation was canceled.
build-artifacts / python-test (ubuntu-latest, 3.13)
The strategy configuration was canceled because "build-artifacts.python-test.ubuntu-latest_3_10" failed
build-artifacts / python-test (ubuntu-latest, 3.13)
The operation was canceled.
build-artifacts / python-test (ubuntu-latest, 3.12)
The strategy configuration was canceled because "build-artifacts.python-test.ubuntu-latest_3_10" failed
build-artifacts / python-test (ubuntu-latest, 3.12)
The operation was canceled.
build-artifacts / python-test (windows-latest, 3.12)
The strategy configuration was canceled because "build-artifacts.python-test.ubuntu-latest_3_10" failed
build-artifacts / python-test (windows-latest, 3.12)
The operation was canceled.
build-artifacts / python-test (macos-latest, 3.11)
The strategy configuration was canceled because "build-artifacts.python-test.ubuntu-latest_3_10" failed
build-artifacts / python-test (macos-latest, 3.11)
The operation was canceled.
build-artifacts / python-test (windows-latest, 3.13)
The strategy configuration was canceled because "build-artifacts.python-test.ubuntu-latest_3_10" failed
build-artifacts / python-test (windows-latest, 3.13)
The operation was canceled.
build-artifacts / python-test (macos-latest, 3.13)
The strategy configuration was canceled because "build-artifacts.python-test.ubuntu-latest_3_10" failed
build-artifacts / python-test (macos-latest, 3.13)
The operation was canceled.
build-artifacts / python-test (windows-latest, 3.11)
The strategy configuration was canceled because "build-artifacts.python-test.ubuntu-latest_3_10" failed
build-artifacts / python-test (windows-latest, 3.11)
The operation was canceled.
build-artifacts / python-test (ubuntu-latest, 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@v4, astral-sh/setup-uv@v5, jakebailey/pyright-action@v2. 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/
build-artifacts / python-test (macos-latest, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, astral-sh/setup-uv@v5, jakebailey/pyright-action@v2. 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/
build-artifacts / python-test (ubuntu-latest, 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@v4, astral-sh/setup-uv@v5, jakebailey/pyright-action@v2. 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/
build-artifacts / python-test (macos-latest, 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@v4, astral-sh/setup-uv@v5. 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/
build-artifacts / python-test (windows-latest, 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@v4, astral-sh/setup-uv@v5. 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/
build-artifacts / python-test (ubuntu-latest, 3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, astral-sh/setup-uv@v5, jakebailey/pyright-action@v2. 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/
build-artifacts / python-test (ubuntu-latest, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, astral-sh/setup-uv@v5, jakebailey/pyright-action@v2. 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/
build-artifacts / python-test (windows-latest, 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, astral-sh/setup-uv@v5. 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/
build-artifacts / python-test (macos-latest, 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@v4, astral-sh/setup-uv@v5, jakebailey/pyright-action@v2. 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/
build-artifacts / python-test (windows-latest, 3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, astral-sh/setup-uv@v5, jakebailey/pyright-action@v2. 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/
build-artifacts / python-test (macos-latest, 3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, astral-sh/setup-uv@v5, jakebailey/pyright-action@v2. 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/
build-artifacts / python-test (windows-latest, 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@v4, astral-sh/setup-uv@v5. 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/