Skip to content

Estimated xlm fee component #86

Estimated xlm fee component

Estimated xlm fee component #86

Re-run triggered May 29, 2026 13:17
Status Failure
Total duration 43s
Artifacts

ci.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

13 errors and 22 warnings
build (20.x)
Process completed with exit code 1.
build (20.x): hooks/__tests__/useTxTracker.test.ts#L36
Component definition is missing display name
build (20.x): hooks/__tests__/useFeeEstimate.test.ts#L35
Component definition is missing display name
build (20.x): hooks/__tests__/useFeeEstimate.test.ts#L22
Component definition is missing display name
build (20.x): components/wallet/__tests__/FeeEstimator.test.tsx#L31
Component definition is missing display name
build (20.x): components/__tests__/DeliveryList.test.tsx#L56
Component definition is missing display name
build (22.x)
The strategy configuration was canceled because "build._20_x" failed
build (22.x)
The operation was canceled.
build (22.x): hooks/__tests__/useTxTracker.test.ts#L36
Component definition is missing display name
build (22.x): hooks/__tests__/useFeeEstimate.test.ts#L35
Component definition is missing display name
build (22.x): hooks/__tests__/useFeeEstimate.test.ts#L22
Component definition is missing display name
build (22.x): components/wallet/__tests__/FeeEstimator.test.tsx#L31
Component definition is missing display name
build (22.x): components/__tests__/DeliveryList.test.tsx#L56
Component definition is missing display name
build (20.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. 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 (20.x): components/layout/AppLayout.tsx#L10
'useState' is defined but never used
build (20.x): components/layout/AppLayout.tsx#L10
'useEffect' is defined but never used
build (20.x): components/forms/type.ts#L14
'value' is defined but never used
build (20.x): components/forms/__tests__/LoginForm.test.tsx#L97
'rerender' is assigned a value but never used
build (20.x): components/forms/__tests__/LoginForm.test.tsx#L25
'href' is defined but never used
build (20.x): components/forms/__tests__/LoginForm.test.tsx#L1
'waitFor' is defined but never used
build (20.x): components/forms/RegisterForm.tsx#L39
'setDriverDetails' is assigned a value but never used
build (20.x): components/forms/RegisterForm.tsx#L38
'setPersonalDetails' is assigned a value but never used
build (20.x): app/page.tsx#L1
'DeliveryList' is defined but never used
build (20.x)
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
build (22.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. 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 (22.x): components/layout/AppLayout.tsx#L10
'useState' is defined but never used
build (22.x): components/layout/AppLayout.tsx#L10
'useEffect' is defined but never used
build (22.x): components/forms/type.ts#L14
'value' is defined but never used
build (22.x): components/forms/__tests__/LoginForm.test.tsx#L97
'rerender' is assigned a value but never used
build (22.x): components/forms/__tests__/LoginForm.test.tsx#L25
'href' is defined but never used
build (22.x): components/forms/__tests__/LoginForm.test.tsx#L1
'waitFor' is defined but never used
build (22.x): components/forms/RegisterForm.tsx#L39
'setDriverDetails' is assigned a value but never used
build (22.x): components/forms/RegisterForm.tsx#L38
'setPersonalDetails' is assigned a value but never used
build (22.x): app/page.tsx#L1
'DeliveryList' is defined but never used
build (22.x)
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