Process completed with exit code 1.

Error: [vitest] No "KnowledgeBaseConflictError" export is defined on the "@/lib/knowledge/service" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: vi.mock(import("@/lib/knowledge/service"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ Module.PUT app/api/knowledge/[id]/route.ts:170:26 ❯ app/api/knowledge/[id]/route.test.ts:360:24

AssertionError: expected 500 to be 200 // Object.is equality - Expected + Received - 200 + 500 ❯ app/api/knowledge/route.test.ts:246:31

AssertionError: expected 500 to be 200 // Object.is equality - Expected + Received - 200 + 500 ❯ app/api/knowledge/route.test.ts:175:31

sim#test: command (/home/runner/_work/sim/sim/apps/sim) /home/runner/.bun/bin/bun run test exited (1)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, useblacksmith/stickydisk@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Skipping sticky disk commit due to previous step failures

- Step: unknown (failed)

Found 2 failed/cancelled steps in previous workflow steps

Skipping sticky disk commit due to previous step failures

- Step: unknown (failed)