feat(webapp): billing limits — pause, reject, recovery, and settings UI #7531
kathiekiwipr_checks.yml
on: pull_request
Detect changes
3s
Matrix: e2e / cli-v3
Waiting for pending jobs
Matrix: internal / 🧪 Unit Tests: Internal
Matrix: packages / 🧪 Unit Tests: Packages
Waiting for pending jobs
Matrix: sdk-compat / node-compat
Waiting for pending jobs
Matrix: webapp / 🧪 Unit Tests: Webapp
typecheck
/
typecheck
7m 21s
e2e-webapp
/
🧪 E2E Tests: Webapp
4m 12s
sdk-compat
/
Bun Runtime
sdk-compat
/
Cloudflare Workers
sdk-compat
/
Deno Runtime
All PR Checks
4s
Annotations
8 errors
|
webapp / 🧪 Unit Tests: Webapp (2, 10)
Process completed with exit code 1.
|
|
webapp / 🧪 Unit Tests: Webapp (8, 10)
Process completed with exit code 1.
|
|
webapp / 🧪 Unit Tests: Webapp (7, 10)
Process completed with exit code 1.
|
|
webapp / 🧪 Unit Tests: Webapp (4, 10)
Process completed with exit code 1.
|
|
webapp / 📊 Merge Reports
Process completed with exit code 1.
|
|
Unhandled error:
apps/webapp/app/v3/models/workerDeployment.server.ts#L88
PrismaClientInitializationError:
Invalid `$prisma.workerDeploymentPromotion.findFirst()` invocation in
/home/runner/work/trigger.dev/trigger.dev/apps/webapp/app/v3/models/workerDeployment.server.ts:88:61
85 }): Promise<WorkerDeploymentWithWorkerTasks | undefined> {
86 const $prisma = prismaClient ?? prisma;
87
→ 88 const promotion = await $prisma.workerDeploymentPromotion.findFirst(
Can't reach database server at `localhost:32776`
Please make sure your database server is running at `localhost:32776`.
❯ ei.handleRequestError internal-packages/database/generated/prisma/runtime/library.js:124:7583
❯ ei.handleAndLogRequestError internal-packages/database/generated/prisma/runtime/library.js:124:6608
❯ ei.request internal-packages/database/generated/prisma/runtime/library.js:124:6315
❯ a internal-packages/database/generated/prisma/runtime/library.js:133:9551
❯ findCurrentWorkerDeployment apps/webapp/app/v3/models/workerDeployment.server.ts:88:21
❯ findCurrentWorkerFromEnvironment apps/webapp/app/v3/models/workerDeployment.server.ts:219:24
❯ DefaultQueueManager.resolveCurrentTaskMetadata apps/webapp/app/runEngine/concerns/queues.server.ts:362:20
❯ DefaultQueueManager.getTaskQueueInfo apps/webapp/app/runEngine/concerns/queues.server.ts:229:18
❯ DefaultQueueManager.resolveQueueProperties apps/webapp/app/runEngine/concerns/queues.server.ts:190:24
❯ apps/webapp/app/runEngine/services/triggerTask.server.ts:308:13
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { clientVersion: '6.14.0' }
This error originated in "apps/webapp/test/engine/triggerTask.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "should accept valid debounce.delay formats". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
|
Unhandled error:
apps/webapp/app/v3/models/workerDeployment.server.ts#L88
PrismaClientInitializationError:
Invalid `$prisma.workerDeploymentPromotion.findFirst()` invocation in
/home/runner/work/trigger.dev/trigger.dev/apps/webapp/app/v3/models/workerDeployment.server.ts:88:61
85 }): Promise<WorkerDeploymentWithWorkerTasks | undefined> {
86 const $prisma = prismaClient ?? prisma;
87
→ 88 const promotion = await $prisma.workerDeploymentPromotion.findFirst(
Can't reach database server at `localhost:32776`
Please make sure your database server is running at `localhost:32776`.
❯ ei.handleRequestError internal-packages/database/generated/prisma/runtime/library.js:124:7583
❯ ei.handleAndLogRequestError internal-packages/database/generated/prisma/runtime/library.js:124:6608
❯ ei.request internal-packages/database/generated/prisma/runtime/library.js:124:6315
❯ a internal-packages/database/generated/prisma/runtime/library.js:133:9551
❯ findCurrentWorkerDeployment apps/webapp/app/v3/models/workerDeployment.server.ts:88:21
❯ findCurrentWorkerFromEnvironment apps/webapp/app/v3/models/workerDeployment.server.ts:219:24
❯ DefaultQueueManager.resolveCurrentTaskMetadata apps/webapp/app/runEngine/concerns/queues.server.ts:362:20
❯ DefaultQueueManager.getTaskQueueInfo apps/webapp/app/runEngine/concerns/queues.server.ts:229:18
❯ DefaultQueueManager.resolveQueueProperties apps/webapp/app/runEngine/concerns/queues.server.ts:190:24
❯ apps/webapp/app/runEngine/services/triggerTask.server.ts:308:13
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { clientVersion: '6.14.0' }
This error originated in "apps/webapp/test/engine/triggerTask.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "should resolve queue names correctly when locked to version". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
|
All PR Checks
Process completed with exit code 1.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
internal-blob-report-1
|
62.7 KB |
sha256:9ac7198020926e4f3373230f5f100a6ae8cca4de15c04c7db8b92093e55c0bd0
|
|
|
internal-blob-report-10
|
47.1 KB |
sha256:8b3e4e004ed96078e73050038055fea6d3d099b1ef93de15edda7ad30a39055d
|
|
|
internal-blob-report-11
|
31.4 KB |
sha256:3378911f196602d7b82e47382f879e1c0603b12900c7e46a65062f9b90cf07e7
|
|
|
internal-blob-report-12
|
34.5 KB |
sha256:371209cedeb483fe584089b757ec4aa94eb63761b0ef6b0f317d3b5b8b0700c2
|
|
|
internal-blob-report-2
|
69.5 KB |
sha256:1d4af3568c1decaf869425e9697cb1606fdaf9ad166bb7bc2f531795ab5b6a0d
|
|
|
internal-blob-report-3
|
29 KB |
sha256:8382dcdec2a44dcddfd49eea255334a859ee684dd03d195f9610500333ccd307
|
|
|
internal-blob-report-4
|
22.7 KB |
sha256:c7b08fdcb8c775723f8ebd233344501b97e513edbfba271823ac26f85d1a0d7e
|
|
|
internal-blob-report-5
|
22.4 KB |
sha256:7fc0332eee80dc8e4c79440fca3b5a07bf594c2ca93f45920326f49fc7f8f3ac
|
|
|
internal-blob-report-6
|
40.7 KB |
sha256:ec95dc972567a8d4d0b3f264576221ebb646bfee9b45a81d9d723bc30323007a
|
|
|
internal-blob-report-7
|
42 KB |
sha256:eaae3ceedae79df548eddfa0e8f9a9cc4c563dc3b565df3a867555532748d263
|
|
|
internal-blob-report-8
|
32.9 KB |
sha256:85f588b459ce99c3b6362ff239ee0fb715ffd48e4f3b34bb817375a4a077f4a0
|
|
|
internal-blob-report-9
|
33.2 KB |
sha256:f073bcfae50ac590c9b5407838eb38f0d275eb05c3c9fc555054d1662c06601c
|
|
|
webapp-blob-report-1
|
45.1 KB |
sha256:ccf972d86ca437895eae22bf332394a6ceb3c651c8298a06c2c4270e26751b99
|
|
|
webapp-blob-report-10
|
43.7 KB |
sha256:777fa4acc3f39533bcf66862796450f3cb99fb90f8650d49412dfc840b40577e
|
|
|
webapp-blob-report-2
|
88.9 KB |
sha256:8327b83d5eb888df2326c73265d2d5bebeeba74dd24f754f53deee40cffe1ff3
|
|
|
webapp-blob-report-3
|
50.5 KB |
sha256:af7d90d2af864017c77b958c781d8221a6f1d46e1a5b83afd09aed0443225e5a
|
|
|
webapp-blob-report-4
|
308 KB |
sha256:2d8ec5898909e5d22612f4101fb7529e8cf82aa7f79c6bbe7937e6bfd36e4b74
|
|
|
webapp-blob-report-5
|
69.4 KB |
sha256:8636b1fac3103e870582b51b92eeaadeebbde02ea8af5b4c6fe34e7407b2bed9
|
|
|
webapp-blob-report-6
|
31.7 KB |
sha256:4306a4137f7478864a1aac431b39ff871803e43f765c573f2bc0bc239191e371
|
|
|
webapp-blob-report-7
|
54 KB |
sha256:f63db5d0d846e96ccf127f8fbb18ee4b89ae5d3cd1ade12adcfc82941823aba9
|
|
|
webapp-blob-report-8
|
36.2 KB |
sha256:01a258281a19693f33b1b4e3fedabcf9f0a8a014a941787f1282ba5529d2c3f1
|
|
|
webapp-blob-report-9
|
194 KB |
sha256:22cac07e8a0ca8afff0c27966726d7e8212b3c74fea35627f18136ffae15cec0
|
|