pass team instead of project to rateLimit #18407
Triggered via pull request
January 29, 2025 18:22
jnsdls
Status
Cancelled
Total duration
2m 59s
Artifacts
–
CI.yml
on: pull_request
optimize_ci
3s
Build Packages
52s
Lint Packages
1m 55s
Unit Tests
52s
Size
2m 15s
Matrix: E2E Tests
Annotations
9 errors and 7 warnings
|
Unit Tests
@***-dev/service-utils#test: command (/home/runner/work/js/js/packages/service-utils) /home/runner/setup-pnpm/node_modules/.bin/pnpm run test exited (1)
|
|
Unit Tests
Process completed with exit code 1.
|
|
Size
Canceling since a higher priority waiting request for 'CI-refs/pull/6092/merge' exists
|
|
Size
The operation was canceled.
|
|
E2E Tests (bun, vite)
Canceling since a higher priority waiting request for 'CI-refs/pull/6092/merge' exists
|
|
E2E Tests (npm, esbuild)
Canceling since a higher priority waiting request for 'CI-refs/pull/6092/merge' exists
|
|
E2E Tests (pnpm, vite)
Canceling since a higher priority waiting request for 'CI-refs/pull/6092/merge' exists
|
|
E2E Tests (yarn, esbuild)
Canceling since a higher priority waiting request for 'CI-refs/pull/6092/merge' exists
|
|
E2E Tests (pnpm, esbuild)
Canceling since a higher priority waiting request for 'CI-refs/pull/6092/merge' exists
|
|
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
|