Skip to content

improvement(timeouts): files/base64 should use max timeouts + auth centralization #9937

improvement(timeouts): files/base64 should use max timeouts + auth centralization

improvement(timeouts): files/base64 should use max timeouts + auth centralization #9937

Triggered via pull request February 10, 2026 22:57
Status Failure
Total duration 1m 25s
Artifacts

ci.yml

on: pull_request
Detect Version
0s
Detect Version
Test and Build  /  Test and Build
1m 19s
Test and Build / Test and Build
Check Docs Changes
0s
Check Docs Changes
Matrix: Build AMD64
Matrix: Build ARM64 (GHCR Only)
Process Docs  /  Process Documentation Embeddings
Process Docs / Process Documentation Embeddings
Matrix: Create GHCR Manifests
Create GitHub Release
0s
Create GitHub Release
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 3 warnings
app/api/form/utils.test.ts > Form API Utils > Form auth validation > should allow access to public forms: apps/sim/lib/auth/auth.ts#L465
Error: [vitest] No "isEmailVerificationEnabled" export is defined on the "@/lib/core/config/feature-flags" 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/core/config/feature-flags"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ lib/auth/auth.ts:465:31 ❯ lib/auth/index.ts:3:1
app/api/form/utils.test.ts > Form API Utils > Cookie handling > should set auth cookie correctly: apps/sim/lib/auth/auth.ts#L465
Error: [vitest] No "isEmailVerificationEnabled" export is defined on the "@/lib/core/config/feature-flags" 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/core/config/feature-flags"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ lib/auth/auth.ts:465:31 ❯ lib/auth/index.ts:3:1
app/api/chat/utils.test.ts > Chat API Utils > Chat auth validation > should check allowed emails for email auth: apps/sim/app/api/chat/utils.test.ts#L298
Error: [vitest] There was an error when mocking a module. If you are using "vi.mock" factory, make sure there are no top level variables inside, since this call is hoisted to top of the file. Read more: https://vitest.dev/api/vi.html#vi-mock ❯ app/api/chat/utils.test.ts:298:36 Caused by: Caused by: Error: [vitest] No "isEmailVerificationEnabled" export is defined on the "@/lib/core/config/feature-flags" 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/core/config/feature-flags"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ lib/auth/auth.ts:465:31 ❯ lib/auth/index.ts:3:1
app/api/chat/utils.test.ts > Chat API Utils > Chat auth validation > should request email auth for email-protected chats: apps/sim/app/api/chat/utils.test.ts#L276
Error: [vitest] There was an error when mocking a module. If you are using "vi.mock" factory, make sure there are no top level variables inside, since this call is hoisted to top of the file. Read more: https://vitest.dev/api/vi.html#vi-mock ❯ app/api/chat/utils.test.ts:276:36 Caused by: Caused by: Error: [vitest] No "isEmailVerificationEnabled" export is defined on the "@/lib/core/config/feature-flags" 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/core/config/feature-flags"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ lib/auth/auth.ts:465:31 ❯ lib/auth/index.ts:3:1
app/api/chat/utils.test.ts > Chat API Utils > Chat auth validation > should reject incorrect password: apps/sim/app/api/chat/utils.test.ts#L250
Error: [vitest] There was an error when mocking a module. If you are using "vi.mock" factory, make sure there are no top level variables inside, since this call is hoisted to top of the file. Read more: https://vitest.dev/api/vi.html#vi-mock ❯ app/api/chat/utils.test.ts:250:36 Caused by: Caused by: Error: [vitest] No "isEmailVerificationEnabled" export is defined on the "@/lib/core/config/feature-flags" 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/core/config/feature-flags"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ lib/auth/auth.ts:465:31 ❯ lib/auth/index.ts:3:1
app/api/chat/utils.test.ts > Chat API Utils > Chat auth validation > should validate password for POST requests: apps/sim/app/api/chat/utils.test.ts#L223
Error: [vitest] There was an error when mocking a module. If you are using "vi.mock" factory, make sure there are no top level variables inside, since this call is hoisted to top of the file. Read more: https://vitest.dev/api/vi.html#vi-mock ❯ app/api/chat/utils.test.ts:223:36 Caused by: Caused by: Error: [vitest] No "isEmailVerificationEnabled" export is defined on the "@/lib/core/config/feature-flags" 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/core/config/feature-flags"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ lib/auth/auth.ts:465:31 ❯ lib/auth/index.ts:3:1
app/api/chat/utils.test.ts > Chat API Utils > Chat auth validation > should request password auth for GET requests: apps/sim/app/api/chat/utils.test.ts#L202
Error: [vitest] There was an error when mocking a module. If you are using "vi.mock" factory, make sure there are no top level variables inside, since this call is hoisted to top of the file. Read more: https://vitest.dev/api/vi.html#vi-mock ❯ app/api/chat/utils.test.ts:202:36 Caused by: Caused by: Error: [vitest] No "isEmailVerificationEnabled" export is defined on the "@/lib/core/config/feature-flags" 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/core/config/feature-flags"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ lib/auth/auth.ts:465:31 ❯ lib/auth/index.ts:3:1
app/api/chat/utils.test.ts > Chat API Utils > Chat auth validation > should allow access to public chats: apps/sim/app/api/chat/utils.test.ts#L182
Error: [vitest] There was an error when mocking a module. If you are using "vi.mock" factory, make sure there are no top level variables inside, since this call is hoisted to top of the file. Read more: https://vitest.dev/api/vi.html#vi-mock ❯ app/api/chat/utils.test.ts:182:21 Caused by: Caused by: Error: [vitest] No "isEmailVerificationEnabled" export is defined on the "@/lib/core/config/feature-flags" 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/core/config/feature-flags"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ lib/auth/auth.ts:465:31 ❯ lib/auth/index.ts:3:1
app/api/chat/utils.test.ts > Chat API Utils > Cookie handling > should set auth cookie correctly: apps/sim/lib/auth/auth.ts#L465
Error: [vitest] No "isEmailVerificationEnabled" export is defined on the "@/lib/core/config/feature-flags" 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/core/config/feature-flags"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ lib/auth/auth.ts:465:31 ❯ lib/auth/index.ts:3:1
Test and Build / Test and Build
sim#test: command (/home/runner/_work/sim/sim/apps/sim) /home/runner/.bun/bin/bun run test exited (1)
Test and Build / Test and Build
Skipping sticky disk commit due to previous step failures
Test and Build / Test and Build
- Step: unknown (failed)
Test and Build / Test and Build
Found 2 failed/cancelled steps in previous workflow steps