Showing logs for build greencapitaltrade/flash/pr-580 #3 stage from-build-pack and container prepare 2026/10/30 05:24:42 Entrypoint initialization Showing logs for build greencapitaltrade/flash/pr-580 #3 stage from-build-pack and container place-scripts 2026/10/30 05:24:43 Decoded script /tekton/scripts/script-0-pwfpg 2026/10/30 05:24:43 Decoded script /tekton/scripts/script-1-fqsn7 2026/10/30 05:24:43 Decoded script /tekton/scripts/script-2-bdqgv 2026/10/30 05:24:43 Decoded script /tekton/scripts/script-3-qv49l 2026/10/30 05:24:43 Decoded script /tekton/scripts/script-4-rcnj6 2026/10/30 05:24:43 Decoded script /tekton/scripts/script-5-dq897 2026/10/30 05:24:43 Decoded script /tekton/scripts/script-6-gbl2q 2026/10/30 05:24:43 Decoded script /tekton/scripts/script-7-4msgw 2026/10/30 05:24:43 Decoded script /tekton/scripts/script-8-642kw 2026/10/30 05:24:43 Decoded script /tekton/scripts/script-9-pkdhm 2026/10/30 05:24:43 Decoded script /tekton/scripts/script-10-n4zrn 2026/10/30 05:24:43 Decoded script /tekton/scripts/script-11-lvc57 2026/10/30 05:24:43 Decoded script /tekton/scripts/script-12-dtrlv 2026/10/30 05:24:43 Decoded script /tekton/scripts/script-13-zq7v6 2026/10/30 05:24:43 Decoded script /tekton/scripts/script-14-66tsp 2026/10/30 05:24:43 Decoded script /tekton/scripts/script-16-kpgn9 2026/10/30 05:24:43 Decoded script /tekton/scripts/script-17-hmx29 Showing logs for build greencapitaltrade/flash/pr-580 #3 stage from-build-pack and container working-dir-initializer Showing logs for build greencapitaltrade/flash/pr-580 #3 stage from-build-pack and container step-git-clone git cloning url: https://github.com/greencapitaltrade/flash.git version refs/pull/580/head:PR-580@2e055c0c11d0ef1b0eb29cd2e20f97f3b3a31f32 to dir: source Cloning into 'source'... From https://github.com/greencapitaltrade/flash * [new ref] refs/pull/580/head -> PR-580 Switched to branch 'PR-580' HEAD is now at 2e055c0c chore: preserve current main release pipeline checked out revision: refs/pull/580/head:PR-580@2e055c0c11d0ef1b0eb29cd2e20f97f3b3a31f32 to dir: source Showing logs for build greencapitaltrade/flash/pr-580 #3 stage from-build-pack and container step-git-merge setup git user email jenkins-x@googlegroups.com Using SHAs from PULL_REFS=main:4d9e38f22d61408696cf9f0f0ce3314141395e25,580:2e055c0c11d0ef1b0eb29cd2e20f97f3b3a31f32:refs/pull/580/head using base branch main and base sha 4d9e38f22d61408696cf9f0f0ce3314141395e25 merging sha: 2e055c0c11d0ef1b0eb29cd2e20f97f3b3a31f32 Showing logs for build greencapitaltrade/flash/pr-580 #3 stage from-build-pack and container step-jx-variables WARNING: no $GIT_SECRET_MOUNT_PATH environment variable set about to run: git clone --no-checkout --filter=blob:none --depth=1 https://github.com/greencapitaltrade/mcu.git /tmp/jx-git-1057902718 in dir /tmp Cloning into '/tmp/jx-git-1057902718'... about to run: git sparse-checkout set --no-cone jx-requirements.yml .jx/gitops/source-config.yaml in dir /tmp/jx-git-1057902718 about to run: git checkout in dir /tmp/jx-git-1057902718 Your branch is up to date with 'origin/main'. export APP_NAME='flash' export BRANCH_NAME='PR-580' export BUILD_NUMBER='3' export DOCKERFILE_PATH='Dockerfile' export DOCKER_REGISTRY='417755753340.dkr.ecr.ap-south-1.amazonaws.com' export DOCKER_REGISTRY_ORG='greencapitaltrade' export DOMAIN='gc-t.in' about to run: git rev-parse --abbrev-ref HEAD in dir . main export GIT_BRANCH='main' export JENKINS_X_URL='https://dashboard-jx.gc-t.in/greencapitaltrade/flash/PR-580/3' export JX_CHART_REPOSITORY='http://jenkins-x-chartmuseum.jx.svc.cluster.local:8080' export KANIKO_FLAGS='--skip-unused-stages --snapshotMode=redo' export MINK_AS='tekton-bot' version file VERSION does not exist export MINK_IMAGE='417755753340.dkr.ecr.ap-south-1.amazonaws.com/greencapitaltrade/flash:0.0.0-PR-580-3-SNAPSHOT' export NAMESPACE_SUB_DOMAIN='-jx.' export PIPELINE_KIND='pullrequest' export PUSH_CONTAINER_REGISTRY='417755753340.dkr.ecr.ap-south-1.amazonaws.com' export REPO_NAME='flash' export REPO_OWNER='greencapitaltrade' version file VERSION does not exist export VERSION='0.0.0-PR-580-3-SNAPSHOT' added variables to file: .jx/variables.sh added variables to file: .jx/variables.sh Showing logs for build greencapitaltrade/flash/pr-580 #3 stage from-build-pack and container step-build-yarn-install ➤ YN0000: Successfully set npmScopes.greencapitaltrade.npmRegistryServer to 'https://npm.pkg.github.com' ➤ YN0000: Successfully set npmScopes.greencapitaltrade.npmAuthToken to '********' ➤ YN0000: · Yarn 4.5.0 ➤ YN0000: ┌ Resolution step ➤ YN0000: └ Completed in 0s 224ms ➤ YN0000: ┌ Post-resolution validation ➤ YN0086: │ Some peer dependencies are incorrectly met by dependencies; run yarn explain peer-requirements for details. ➤ YN0000: └ Completed ➤ YN0000: ┌ Fetch step ➤ YN0066: │ typescript@patch:typescript@npm%3A6.0.3#optional!builtin::version=6.0.3&hash=8c6c40: Cannot apply hunk #1 ➤ YN0000: └ Completed in 52s 88ms ➤ YN0000: ┌ Link step ➤ YN0007: │ @biomejs/biome@npm:1.9.4 must be built because it never has been before or the last one failed ➤ YN0007: │ esbuild@npm:0.21.5 must be built because it never has been before or the last one failed ➤ YN0007: │ esbuild@npm:0.27.2 must be built because it never has been before or the last one failed ➤ YN0007: │ esbuild@npm:0.27.7 must be built because it never has been before or the last one failed ➤ YN0007: │ @pact-foundation/pact-core@npm:19.2.0 must be built because it never has been before or the last one failed ➤ YN0007: │ @scarf/scarf@npm:1.4.0 must be built because it never has been before or the last one failed ➤ YN0007: │ esbuild@npm:0.14.47 must be built because it never has been before or the last one failed ➤ YN0007: │ sharp@npm:0.34.5 must be built because it never has been before or the last one failed ➤ YN0007: │ unrs-resolver@npm:1.11.1 must be built because it never has been before or the last one failed ➤ YN0007: │ protobufjs@npm:7.6.4 must be built because it never has been before or the last one failed ➤ YN0007: │ starter-free@workspace:. must be built because it never has been before or the last one failed ➤ YN0000: │ starter-free@workspace:. STDOUT Attention: Next.js now collects completely anonymous telemetry regarding usage. ➤ YN0000: │ starter-free@workspace:. STDOUT This information is used to shape Next.js' roadmap and prioritize features. ➤ YN0000: │ starter-free@workspace:. STDOUT You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL: ➤ YN0000: │ starter-free@workspace:. STDOUT https://nextjs.org/telemetry ➤ YN0000: │ starter-free@workspace:. STDOUT ➤ YN0000: │ starter-free@workspace:. STDOUT ▲ Next.js 16.1.1 (Turbopack) ➤ YN0000: │ starter-free@workspace:. STDOUT - Experiments (use with caution): ➤ YN0000: │ starter-free@workspace:. STDOUT ✓ scrollRestoration ➤ YN0000: │ starter-free@workspace:. STDOUT ➤ YN0000: │ starter-free@workspace:. STDERR ⚠ The "middleware" file convention is deprecated. Please use "proxy" instead. Learn more: https://nextjs.org/docs/messages/middleware-to-proxy ➤ YN0000: │ starter-free@workspace:. STDOUT Creating an optimized production build ... ➤ YN0000: │ starter-free@workspace:. STDOUT ✓ Compiled successfully in 19.0s ➤ YN0000: │ starter-free@workspace:. STDOUT Running TypeScript ... ➤ YN0000: │ starter-free@workspace:. STDOUT Collecting page data using 1 worker ... ➤ YN0000: │ starter-free@workspace:. STDOUT Generating static pages using 1 worker (0/46) ... ➤ YN0000: │ starter-free@workspace:. STDERR Failed to resolve default team for members: Error: Dynamic server usage: Route /members couldn't be rendered statically because it used `cookies`. See more info here: https://nextjs.org/docs/messages/dynamic-server-error ➤ YN0000: │ starter-free@workspace:. STDERR at h (.next/server/chunks/ssr/_5f9ddff0._.js:13:7831) ➤ YN0000: │ starter-free@workspace:. STDERR at (.next/server/chunks/ssr/_5f9ddff0._.js:1:258503) ➤ YN0000: │ starter-free@workspace:. STDERR at (.next/server/chunks/ssr/_5f9ddff0._.js:6:23) ➤ YN0000: │ starter-free@workspace:. STDERR at query (.next/server/chunks/ssr/_5f9ddff0._.js:23:28) ➤ YN0000: │ starter-free@workspace:. STDERR at f (.next/server/chunks/ssr/[root-of-the-server]__c23fb9d7._.js:1:593) { ➤ YN0000: │ starter-free@workspace:. STDERR description: "Route /members couldn't be rendered statically because it used `cookies`. See more info here: https://nextjs.org/docs/messages/dynamic-server-error", ➤ YN0000: │ starter-free@workspace:. STDERR digest: 'DYNAMIC_SERVER_USAGE' ➤ YN0000: │ starter-free@workspace:. STDERR } ➤ YN0000: │ starter-free@workspace:. STDOUT Generating static pages using 1 worker (11/46) ➤ YN0000: │ starter-free@workspace:. STDOUT Generating static pages using 1 worker (22/46) ➤ YN0000: │ starter-free@workspace:. STDERR Failed to resolve default team: Error: Dynamic server usage: Route / couldn't be rendered statically because it used `cookies`. See more info here: https://nextjs.org/docs/messages/dynamic-server-error ➤ YN0000: │ starter-free@workspace:. STDERR at h (.next/server/chunks/ssr/_5f9ddff0._.js:13:7831) ➤ YN0000: │ starter-free@workspace:. STDERR at (.next/server/chunks/ssr/_5f9ddff0._.js:1:258503) ➤ YN0000: │ starter-free@workspace:. STDERR at (.next/server/chunks/ssr/_5f9ddff0._.js:6:23) ➤ YN0000: │ starter-free@workspace:. STDERR at query (.next/server/chunks/ssr/_5f9ddff0._.js:23:28) ➤ YN0000: │ starter-free@workspace:. STDERR at f (.next/server/chunks/ssr/[root-of-the-server]__e57a3bbe._.js:7:66) { ➤ YN0000: │ starter-free@workspace:. STDERR description: "Route / couldn't be rendered statically because it used `cookies`. See more info here: https://nextjs.org/docs/messages/dynamic-server-error", ➤ YN0000: │ starter-free@workspace:. STDERR digest: 'DYNAMIC_SERVER_USAGE' ➤ YN0000: │ starter-free@workspace:. STDERR } ➤ YN0000: │ starter-free@workspace:. STDERR Failed to resolve default team for team management: Error: Dynamic server usage: Route /team-management couldn't be rendered statically because it used `cookies`. See more info here: https://nextjs.org/docs/messages/dynamic-server-error ➤ YN0000: │ starter-free@workspace:. STDERR at h (.next/server/chunks/ssr/_5f9ddff0._.js:13:7831) ➤ YN0000: │ starter-free@workspace:. STDERR at (.next/server/chunks/ssr/_5f9ddff0._.js:1:258503) ➤ YN0000: │ starter-free@workspace:. STDERR at (.next/server/chunks/ssr/_5f9ddff0._.js:6:23) ➤ YN0000: │ starter-free@workspace:. STDERR at query (.next/server/chunks/ssr/_5f9ddff0._.js:23:28) ➤ YN0000: │ starter-free@workspace:. STDERR at f (.next/server/chunks/ssr/[root-of-the-server]__07793ec6._.js:1:600) { ➤ YN0000: │ starter-free@workspace:. STDERR description: "Route /team-management couldn't be rendered statically because it used `cookies`. See more info here: https://nextjs.org/docs/messages/dynamic-server-error", ➤ YN0000: │ starter-free@workspace:. STDERR digest: 'DYNAMIC_SERVER_USAGE' ➤ YN0000: │ starter-free@workspace:. STDERR } ➤ YN0000: │ starter-free@workspace:. STDOUT Generating static pages using 1 worker (34/46) ➤ YN0000: │ starter-free@workspace:. STDOUT ✓ Generating static pages using 1 worker (46/46) in 418.8ms ➤ YN0000: │ starter-free@workspace:. STDOUT Finalizing page optimization ... ➤ YN0000: │ starter-free@workspace:. STDOUT ➤ YN0000: │ starter-free@workspace:. STDOUT Route (app) ➤ YN0000: │ starter-free@workspace:. STDOUT ┌ ƒ / ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /_not-found ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /[team_id] ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /[team_id]/assets ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /[team_id]/assets/[id] ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /[team_id]/assets/[id]/devices/[deviceId] ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /[team_id]/assets/[id]/devices/[deviceId]/replay ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /[team_id]/assets/[id]/events ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /[team_id]/assets/[id]/geofence ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /[team_id]/assets/[id]/geofence/[geofenceId] ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /[team_id]/assets/[id]/replay ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /[team_id]/assets/[id]/settings ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /[team_id]/assets/documents ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /[team_id]/assets/iot-types ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /[team_id]/assets/maintenance ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /[team_id]/assets/models ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /[team_id]/assets/types ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /[team_id]/delivery/jobs ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /[team_id]/members ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /[team_id]/my-dues ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /[team_id]/onboarding ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /[team_id]/ondc/orders ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /[team_id]/reports ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /alerts ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /api/auth/magic-link/request ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /api/auth/session-expired ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /api/health ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /auth/google/callback ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /auth/magic-link/[token] ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /customer ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /customer/assets ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /customer/commands ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /customer/profile ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /customer/track ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /driver-management ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /expenses/petty-cash ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /forgot-password ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /geofences ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /geofences/new ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /hubs ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /join/[token] ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /login ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /members ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /my-dues ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /no-team ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /notifications ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /notifications/activity ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /notifications/digest/[digestId] ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /onboarding ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /operations ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /operations/assignments ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /operations/challans ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /operations/checklists ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /operations/driver-performance ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /operations/gatepasses ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /operations/live-tracking ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /operations/payments ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /operations/tags ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /operations/trips ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /operations/trips/[id] ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /operations/violations ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /operations/voltcred-trips ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /payments/return/[orderUuid] ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /profile ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /routes ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /settings ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /signup ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /team ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /team-management ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /teams ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /teams/[id] ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /teams/[id]/business-models ➤ YN0000: │ starter-free@workspace:. STDOUT ├ ƒ /teams/new ➤ YN0000: │ starter-free@workspace:. STDOUT └ ƒ /user/[id] ➤ YN0000: │ starter-free@workspace:. STDOUT ➤ YN0000: │ starter-free@workspace:. STDOUT ➤ YN0000: │ starter-free@workspace:. STDOUT ƒ Proxy (Middleware) ➤ YN0000: │ starter-free@workspace:. STDOUT ➤ YN0000: │ starter-free@workspace:. STDOUT ƒ (Dynamic) server-rendered on demand ➤ YN0000: │ starter-free@workspace:. STDOUT ➤ YN0000: └ Completed in 55s 562ms ➤ YN0000: · Done with warnings in 1m 49s Showing logs for build greencapitaltrade/flash/pr-580 #3 stage from-build-pack and container step-build-yarn-install-errors Showing logs for build greencapitaltrade/flash/pr-580 #3 stage from-build-pack and container step-pact-consumer RUN v2.1.9 /workspace/source 2026-10-30T05:26:52.713417Z WARN ThreadId(01) pact_models::pact: Note: Existing pact is an older specification version (V3), and will be upgraded ✓ web/__tests__/pact/telemetry-consumer.pact.test.ts (2 tests) 36ms Test Files 1 passed (1) Tests 2 passed (2) Start at 05:26:51 Duration 1.02s (transform 67ms, setup 0ms, collect 743ms, tests 36ms, environment 0ms, prepare 89ms) Showing logs for build greencapitaltrade/flash/pr-580 #3 stage from-build-pack and container step-pact-publish ➤ YN0000: · Yarn 4.5.0 ➤ YN0000: ┌ Resolution step ➤ YN0085: │ + @pact-foundation/pact-cli@npm:18.10.9, @pact-foundation/pact-cli-darwin-arm64@npm:18.10.9, @pact-foundation/pact-cli-darwin-x64@npm:18.10.9, and 4 more. ➤ YN0000: └ Completed ➤ YN0000: ┌ Fetch step ➤ YN0000: └ Completed in 2s 580ms ➤ YN0000: ┌ Link step ➤ YN0000: └ Completed in 0s 204ms ➤ YN0000: · Done in 2s 960ms warning: pact-broker is deprecated; use 'pact broker' instead 📨 Attempting to publish pact for consumer: flash against provider: deadpool ✅ Updated flash version 2e055c0c with tags main Next steps: Configure the version branch to be the value of your repository branch. Pact successfully republished for flash version 2e055c0c and provider deadpool with no content changes. View the published pact at http://pact-broker.jx.svc.cluster.local/pacts/provider/deadpool/consumer/flash/version/2e055c0c Events detected: contract_published Next steps: * Add Pact verification tests to the deadpool build. See https://docs.pact.io/go/provider_verification * Configure separate deadpool pact verification build and webhook to trigger it when the pact content changes. See https://docs.pact.io/go/webhooks Showing logs for build greencapitaltrade/flash/pr-580 #3 stage from-build-pack and container step-typecheck Showing logs for build greencapitaltrade/flash/pr-580 #3 stage from-build-pack and container step-typecheck-errors Showing logs for build greencapitaltrade/flash/pr-580 #3 stage from-build-pack and container step-unit-tests RUN v2.1.9 /workspace/source stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > opens only the expense history deep link and marks the item read React does not recognize the `justifyContent` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `justifycontent` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `alignItems` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `alignitems` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `flexWrap` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `flexwrap` instead. If you accidentally passed it from a parent component, remove it from the DOM element. Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. React does not recognize the `minWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `minwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `borderWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `borderColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `bordercolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `borderRadius` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderradius` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `maxWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `maxwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `alignSelf` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `alignself` instead. If you accidentally passed it from a parent component, remove it from the DOM element. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > mounts inbox updates without an IoT gate and refetches only this company rows and count Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > opens an authorized generic event by its public UUID and source reference Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > disables inbox navigation for unrecognized deep-link types Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > pauses a rule using the selected company and rule ID Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > keeps future automation schemas read-only even when their action kinds are known Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > keeps schema 5 read-only while capability readiness is off Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > migrates a schema 3 rule with an untouched scope checkbox and applies the fresh paused detail before CAS save Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > creates a schema 5 rule when supported and sends nullable condition and schedule roots Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > blocks blank and out-of-range notification ages before sending a schema 5 mutation Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > accepts notification age boundary 1 seconds Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > accepts notification age boundary 604800 seconds Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > drops a stale preview result after its draft changes while the request is in flight Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > blocks resuming a paused future schema while keeping archive available Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > updates only the chosen action with its returned control generation and preserves sibling actions Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > allows pausing an enabled action when current schema 4 readiness has been lost Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > blocks resuming an action until its current scoped schema readiness is available Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > shows nullable action controls as unavailable and read-only Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > refreshes and reports an action control conflict without retrying the mutation Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > ignores an action mutation completion after switching companies Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > ignores a conflict after its rules refresh resolves for a previous company Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > handles a future rule with no readable definition without crashing Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > keeps descendant scope visible and read-only when the selected event lacks backend support Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > creates a supported event rule and keeps its secret one-time Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > creates a supported event rule and keeps its secret one-time Received `true` for a non-boolean attribute `selectable`. If you want to write it to the DOM, pass a string instead: selectable="true" or selectable={value.toString()}. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > previews a mixed schema 4 definition with mail, app, and command actions intact Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > uses the server event catalogue without requiring expense entitlements Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > keeps notification access server-authorized when petty cash reader access is missing Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > previews the backend-authorized payload for an explicitly selected recorded event Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > previews the backend-authorized payload for an explicitly selected recorded event React does not recognize the `paddingVertical` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddingvertical` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `borderBottomWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderbottomwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > sends lowercase run action filters and exports the selected bounded page Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > discards an export response after the run filters change Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > discards an export response after the principal changes within the same company Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > discards an export response after selecting a different rule in the same company Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > continues a bounded export when continuation is indicated only by incomplete scan metadata Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > only offers scopes allowed by the selected event family Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. stderr | web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx > AssetNotificationsScreen > does not infer scope availability from client-side team permissions Encountered two children with the same key, `9`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version. ✓ web/features/asset/screens/__tests__/AssetNotificationsScreen.test.tsx (35 tests) 4365ms stderr | web/features/asset/screens/__tests__/reports-filters.test.tsx > end-to-end report contract behavior > team scope reaches metrics and paginated asset/operator queries React does not recognize the `alignItems` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `alignitems` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `justifyContent` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `justifycontent` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `flexBasis` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `flexbasis` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `flexGrow` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `flexgrow` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `maxWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `maxwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `minWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `minwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `numberOfLines` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `numberoflines` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `zIndex` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `zindex` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `flexWrap` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `flexwrap` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `backgroundColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `backgroundcolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `hoverStyle` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `hoverstyle` instead. If you accidentally passed it from a parent component, remove it from the DOM element. Received `true` for a non-boolean attribute `horizontal`. If you want to write it to the DOM, pass a string instead: horizontal="true" or horizontal={value.toString()}. React does not recognize the `showsHorizontalScrollIndicator` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `showshorizontalscrollindicator` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `paddingTop` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddingtop` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `showsVerticalScrollIndicator` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `showsverticalscrollindicator` instead. If you accidentally passed it from a parent component, remove it from the DOM element. Unknown event handler property `onValueChange`. It will be ignored. React does not recognize the `flexDirection` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `flexdirection` instead. If you accidentally passed it from a parent component, remove it from the DOM element. stderr | web/features/asset/screens/__tests__/reports-filters.test.tsx > ReportsScreen — legacy filter bar (flag OFF) > clicking the Asset trigger opens the options panel React does not recognize the `paddingHorizontal` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddinghorizontal` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `paddingVertical` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddingvertical` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `maxHeight` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `maxheight` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `marginTop` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `margintop` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `borderWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `borderColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `bordercolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `borderRadius` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderradius` instead. If you accidentally passed it from a parent component, remove it from the DOM element. stderr | web/features/asset/screens/__tests__/reports-filters.test.tsx > ReportsScreen — v2 flag ON: filter bar, search, error, trips gating > renders the v2 filter bar with a Search input Invalid attribute name: `$lg` stderr | web/features/asset/screens/__tests__/reports-filters.test.tsx > ReportsScreen — v2 flag ON: filter bar, search, error, trips gating > search input filters rows by license_plate after 300ms debounce React does not recognize the `textAlign` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `textalign` instead. If you accidentally passed it from a parent component, remove it from the DOM element. Invalid attribute name: `$md` ✓ web/features/asset/screens/__tests__/reports-filters.test.tsx (29 tests) 530ms stderr | web/features/notifications/__tests__/ChannelTest.test.tsx > retries an ambiguous submit with the same request ID and payload In HTML,
cannot be a child of >
... ...