Backend fails type-check — 14 TS errors across agent/job/worker modules #23

New issue

Closed

opened 2026-05-14 13:22:03 +00:00 by Mark · 1 comment

Mark commented

2026-05-14 13:22:03 +00:00

Owner

Bug

cd backend && npx tsc --noEmit fails with 14 TypeScript errors across 5 files:

Errors by file

api/routes/agent-api.ts (1 error)

Line 207: Type mismatch on job status assignment — "completed" | "failed" not assignable to "running" | "uploading" | "verifying"

api/routes/agents.ts (4 errors)

Line 145, 218: Property secret does not exist on Agent response type
Line 154: Property volumes does not exist on type unknown
Line 224: secret not in Agent update input type

core/agent/heartbeat.ts (4 errors)

Lines 54, 56: Property secret does not exist on Agent type
Lines 121, 155: secret not in Agent update input type

core/agent/jobs.ts (3 errors)

Line 66: Dubious type conversion from string to Record<string, unknown>
Line 93: Property error does not exist on type unknown
Line 183: bigint not assignable to number

core/queue/worker.ts (2 errors)

Line 23: Record<string, unknown> not assignable to JobStatusUpdate
Line 55: progress not in JobProgressUpdate type

Severity

🔴 Critical — tsc --noEmit fails entirely. While tsx allows runtime execution, CI/CD builds that enforce type-checking will fail. The secret property issue suggests the Prisma schema and TypeScript types have drifted.

Suggested Fix

Add secret field to the Agent Prisma model or remove it from the handlers
Fix type cast in jobs.ts line 66 with proper type guard
Fix Worker types in worker.ts to match actual usage

## Bug `cd backend && npx tsc --noEmit` fails with 14 TypeScript errors across 5 files: ### Errors by file **api/routes/agent-api.ts** (1 error) - Line 207: Type mismatch on job status assignment — `"completed" | "failed"` not assignable to `"running" | "uploading" | "verifying"` **api/routes/agents.ts** (4 errors) - Line 145, 218: Property `secret` does not exist on Agent response type - Line 154: Property `volumes` does not exist on type `unknown` - Line 224: `secret` not in Agent update input type **core/agent/heartbeat.ts** (4 errors) - Lines 54, 56: Property `secret` does not exist on Agent type - Lines 121, 155: `secret` not in Agent update input type **core/agent/jobs.ts** (3 errors) - Line 66: Dubious type conversion from `string` to `Record<string, unknown>` - Line 93: Property `error` does not exist on type `unknown` - Line 183: `bigint` not assignable to `number` **core/queue/worker.ts** (2 errors) - Line 23: `Record<string, unknown>` not assignable to `JobStatusUpdate` - Line 55: `progress` not in `JobProgressUpdate` type ## Severity 🔴 **Critical** — `tsc --noEmit` fails entirely. While `tsx` allows runtime execution, CI/CD builds that enforce type-checking will fail. The `secret` property issue suggests the Prisma schema and TypeScript types have drifted. ## Suggested Fix - Add `secret` field to the Agent Prisma model or remove it from the handlers - Fix type cast in jobs.ts line 66 with proper type guard - Fix Worker types in worker.ts to match actual usage