Skip to content

feat: use fetch for Flyte API HTTP client #1581

feat: use fetch for Flyte API HTTP client

feat: use fetch for Flyte API HTTP client #1581

Triggered via pull request March 31, 2026 14:02
Status Failure
Total duration 5m 25s
Artifacts

checks.yml

on: pull_request
extract_branch
3s
extract_branch
unit_tests_with_coverage
5m 21s
unit_tests_with_coverage
lint_project
2m 43s
lint_project
Build Flyteconsole Image  /  Push to Github Registry
5m 1s
Build Flyteconsole Image / Push to Github Registry
Generate Release
Generate Release
Get Release Tag
Get Release Tag
Build & Push FlyteConsole Image  /  Push to Github Registry
Build & Push FlyteConsole Image / Push to Github Registry
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 19 warnings
lint_project
Process completed with exit code 2.
Build Flyteconsole Image / Push to Github Registry
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c : --mount=type=cache,target=/root/.yarn && BASE_URL=/console yarn workspace @clients/console run build:prod" did not complete successfully: exit code: 1
extract_branch
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
lint_project
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, 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/
lint_project: packages/oss-console/src/components/Breadcrumbs/registry/index.ts#L136
'breadcrumbRegistry' was used before it was defined
lint_project: packages/oss-console/src/components/Breadcrumbs/registry/index.ts#L103
Unexpected dangling '_' in '_makeRenderHash'
lint_project: packages/oss-console/src/components/Breadcrumbs/registry/index.ts#L92
Unexpected dangling '_' in '_makeRenderHash'
lint_project: packages/oss-console/src/components/Breadcrumbs/registry/index.ts#L87
Unexpected dangling '_' in '_makeRenderHash'
lint_project: packages/oss-console/src/components/Breadcrumbs/registry/index.ts#L38
Unexpected dangling '_' in '_makeRenderHash'
lint_project: packages/oss-console/src/common/decodeMsgPackLiterals.ts#L15
'convertToValue' was used before it was defined
lint_project: packages/common/src/flyteidl/coreTypes.ts#L19
'SchemaColumnType' is already defined
lint_project: packages/common/src/flyteidl/coreTypes.ts#L17
'BlobDimensionality' is already defined
lint_project: packages/common/src/flyteidl/coreTypes.ts#L15
'EnumType' is already defined
lint_project: packages/common/src/flyteidl/coreTypes.ts#L13
'SimpleType' is already defined
Build Flyteconsole Image / Push to Github Registry
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, docker/build-push-action@v3, docker/metadata-action@v3, docker/setup-buildx-action@v2, docker/setup-qemu-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 Flyteconsole Image / Push to Github Registry
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build Flyteconsole Image / Push to Github Registry
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build Flyteconsole Image / Push to Github Registry
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build Flyteconsole Image / Push to Github Registry
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build Flyteconsole Image / Push to Github Registry
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
unit_tests_with_coverage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3, codecov/codecov-action@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/