Skip to content

[TOOL-2809] Nebula - make the chat card a link in chat history page (… #17303

[TOOL-2809] Nebula - make the chat card a link in chat history page (…

[TOOL-2809] Nebula - make the chat card a link in chat history page (… #17303

Triggered via push December 20, 2024 11:24
Status Failure
Total duration 2m 13s
Artifacts

CI.yml

on: push
optimize_ci
2s
optimize_ci
Matrix: E2E Tests
Fit to window
Zoom out
Zoom in

Annotations

20 errors and 17 warnings
E2E Tests (npm, vite)
Process completed with exit code 1.
E2E Tests (bun, esbuild)
The job was canceled because "npm_vite" failed.
E2E Tests (bun, vite)
The job was canceled because "npm_vite" failed.
E2E Tests (bun, vite)
The operation was canceled.
E2E Tests (bun, webpack)
The job was canceled because "npm_vite" failed.
E2E Tests (bun, webpack)
The operation was canceled.
E2E Tests (yarn, webpack)
The job was canceled because "npm_vite" failed.
E2E Tests (yarn, webpack)
The operation was canceled.
E2E Tests (yarn, esbuild)
The job was canceled because "npm_vite" failed.
E2E Tests (yarn, esbuild)
The operation was canceled.
E2E Tests (npm, webpack)
The job was canceled because "npm_vite" failed.
E2E Tests (npm, webpack)
The operation was canceled.
E2E Tests (pnpm, esbuild)
The job was canceled because "npm_vite" failed.
E2E Tests (pnpm, esbuild)
The operation was canceled.
E2E Tests (pnpm, vite)
The job was canceled because "npm_vite" failed.
E2E Tests (pnpm, vite)
The operation was canceled.
E2E Tests (pnpm, webpack)
The job was canceled because "npm_vite" failed.
E2E Tests (pnpm, webpack)
The operation was canceled.
E2E Tests (yarn, vite)
The job was canceled because "npm_vite" failed.
E2E Tests (yarn, vite)
The operation was canceled.
optimize_ci
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
optimize_ci
Request body: {"token":"***","caller":{"name":"graphite-ci-action","version":"0.0.0"},"context":{"kind":"GITHUB_ACTIONS","repository":{"owner":"***-dev","name":"js"},"sha":"cfbe8c3810a979ea0e046112ceefbf887d0b1aaf","ref":"refs/heads/main","head_ref":"","run":{"workflow":"CI","job":"optimize_ci","run":12430574415}}}
optimize_ci
Response status: 400
optimize_ci
***-dev/js/undefined
optimize_ci
Response returned a non-200 status. Skipping Graphite checks.
Build Packages
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
E2E Tests (npm, esbuild)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
E2E Tests (npm, vite)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Unit Tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Lint Packages
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Lint Packages: apps/playground-web/src/components/engine/airdrop/TransactionResults.tsx#L163
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
Lint Packages: apps/playground-web/src/components/engine/airdrop/TransactionResults.tsx#L170
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
Lint Packages: apps/playground-web/src/components/engine/airdrop/TransactionResults.tsx#L177
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
Lint Packages: apps/playground-web/src/components/engine/minting/TransactionResults.tsx#L161
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
Lint Packages: apps/playground-web/src/components/engine/minting/TransactionResults.tsx#L168
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
Lint Packages: apps/playground-web/src/components/engine/minting/TransactionResults.tsx#L175
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
Lint Packages: apps/playground-web/src/components/engine/minting/erc1155-mint-to.tsx#L267
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element