[service-utils] Expose more kafka configs, set max in-flight requests #18681
Triggered via pull request
February 6, 2025 03:51
arcoraven
Status
Cancelled
Total duration
1m 40s
Artifacts
–
CI.yml
on: pull_request
optimize_ci
2s
Build Packages
48s
Lint Packages
1m 17s
Unit Tests
1m 0s
Size
1m 3s
Matrix: E2E Tests
Annotations
14 errors and 7 warnings
|
Unit Tests
Canceling since a higher priority waiting request for 'CI-refs/pull/6181/merge' exists
|
|
E2E Tests (bun, webpack)
Canceling since a higher priority waiting request for 'CI-refs/pull/6181/merge' exists
|
|
E2E Tests (yarn, webpack)
Canceling since a higher priority waiting request for 'CI-refs/pull/6181/merge' exists
|
|
E2E Tests (yarn, webpack)
The operation was canceled.
|
|
Size
Canceling since a higher priority waiting request for 'CI-refs/pull/6181/merge' exists
|
|
Size
The operation was canceled.
|
|
E2E Tests (yarn, vite)
Canceling since a higher priority waiting request for 'CI-refs/pull/6181/merge' exists
|
|
E2E Tests (yarn, vite)
The operation was canceled.
|
|
E2E Tests (yarn, esbuild)
Canceling since a higher priority waiting request for 'CI-refs/pull/6181/merge' exists
|
|
E2E Tests (yarn, esbuild)
The operation was canceled.
|
|
E2E Tests (bun, vite)
Canceling since a higher priority waiting request for 'CI-refs/pull/6181/merge' exists
|
|
E2E Tests (bun, vite)
The operation was canceled.
|
|
Lint Packages
Canceling since a higher priority waiting request for 'CI-refs/pull/6181/merge' exists
|
|
Lint Packages
The operation was canceled.
|
|
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
|