Gate recall/startup-memory to actual new conversations #1667

Triggered via push April 18, 2026 09:11

im4codes

pushed 087f4a6

dev

Status Failure

Total duration 10m 13s

Artifacts 1

ci.yml

on: push

Matrix: unit-tests

Web Tests (Unit)

53s

Web Tests (Components)

Secret Scan (gitleaks)

Unit Tests (Windows ConPTY)

1m 8s

Server DB Integration Tests

1m 9s

Embedding Integration Tests

41s

E2E Tests

1m 7s

Repo Provider Integration Tests

Android Release Build

Publish to npm

Annotations

20 errors and 22 warnings

server/test/memory-recall.test.ts > memory recall endpoint — I.5 > reranks by composite relevance so same-project high-hit memories can beat slightly higher raw similarity: server/test/memory-recall.test.ts#L548

TypeError: Cannot read properties of undefined (reading 'id') ❯ server/test/memory-recall.test.ts:548:28

server/test/memory-recall.test.ts > memory recall endpoint — I.5 > returns correct shape for each result item: server/test/memory-recall.test.ts#L496

AssertionError: expected [] to have a length of 1 but got +0 - Expected + Received - 1 + 0 ❯ server/test/memory-recall.test.ts:496:26

server/test/memory-recall.test.ts > memory recall endpoint — I.5 > fires hit_count UPDATE for recalled projection ids: server/test/memory-recall.test.ts#L462

AssertionError: expected undefined to be defined ❯ server/test/memory-recall.test.ts:462:23

server/test/memory-recall.test.ts > memory recall endpoint — I.5 > extends up to 5 only when every top-3 item is above the extend bar: server/test/memory-recall.test.ts#L390

AssertionError: expected [] to include 'strong-1' ❯ server/test/memory-recall.test.ts:390:17

server/test/memory-recall.test.ts > memory recall endpoint — I.5 > defaults to top 3 when no limit is specified: server/test/memory-recall.test.ts#L364

AssertionError: expected [] to have a length of 5 but got +0 - Expected + Received - 5 + 0 ❯ server/test/memory-recall.test.ts:364:26

server/test/memory-recall.test.ts > memory recall endpoint — I.5 > shrinks the default cap when client requests fewer than 3: server/test/memory-recall.test.ts#L338

AssertionError: expected [] to have a length of 2 but got +0 - Expected + Received - 2 + 0 ❯ server/test/memory-recall.test.ts:338:26

server/test/memory-recall.test.ts > memory recall endpoint — I.5 > sorts merged results by score descending: server/test/memory-recall.test.ts#L315

AssertionError: expected [] to have a length of 3 but got +0 - Expected + Received - 3 + 0 ❯ server/test/memory-recall.test.ts:315:26

server/test/memory-recall.test.ts > memory recall endpoint — I.5 > deduplicates results by id (personal wins over enterprise for same id): server/test/memory-recall.test.ts#L294

AssertionError: expected [] to have a length of 1 but got +0 - Expected + Received - 1 + 0 ❯ server/test/memory-recall.test.ts:294:26

server/test/memory-recall.test.ts > memory recall endpoint — I.5 > merges personal and enterprise results into a single response: server/test/memory-recall.test.ts#L273

AssertionError: expected [] to have a length of 3 but got +0 - Expected + Received - 3 + 0 ❯ server/test/memory-recall.test.ts:273:26

server/test/memory-recall.test.ts > memory recall endpoint — I.5 > drops template-origin rows from merged results even for a normal query: server/test/memory-recall.test.ts#L244

AssertionError: expected [] to include 'ok-1' ❯ server/test/memory-recall.test.ts:244:17

TypeError: Cannot read properties of undefined (reading 'id') ❯ server/test/memory-recall.test.ts:548:28

server/test/memory-recall.test.ts > memory recall endpoint — I.5 > returns correct shape for each result item: server/test/memory-recall.test.ts#L496

AssertionError: expected [] to have a length of 1 but got +0 - Expected + Received - 1 + 0 ❯ server/test/memory-recall.test.ts:496:26

server/test/memory-recall.test.ts > memory recall endpoint — I.5 > fires hit_count UPDATE for recalled projection ids: server/test/memory-recall.test.ts#L462

AssertionError: expected undefined to be defined ❯ server/test/memory-recall.test.ts:462:23

server/test/memory-recall.test.ts > memory recall endpoint — I.5 > extends up to 5 only when every top-3 item is above the extend bar: server/test/memory-recall.test.ts#L390

AssertionError: expected [] to include 'strong-1' ❯ server/test/memory-recall.test.ts:390:17

server/test/memory-recall.test.ts > memory recall endpoint — I.5 > defaults to top 3 when no limit is specified: server/test/memory-recall.test.ts#L364

AssertionError: expected [] to have a length of 5 but got +0 - Expected + Received - 5 + 0 ❯ server/test/memory-recall.test.ts:364:26

server/test/memory-recall.test.ts > memory recall endpoint — I.5 > shrinks the default cap when client requests fewer than 3: server/test/memory-recall.test.ts#L338

AssertionError: expected [] to have a length of 2 but got +0 - Expected + Received - 2 + 0 ❯ server/test/memory-recall.test.ts:338:26

server/test/memory-recall.test.ts > memory recall endpoint — I.5 > sorts merged results by score descending: server/test/memory-recall.test.ts#L315

AssertionError: expected [] to have a length of 3 but got +0 - Expected + Received - 3 + 0 ❯ server/test/memory-recall.test.ts:315:26

server/test/memory-recall.test.ts > memory recall endpoint — I.5 > deduplicates results by id (personal wins over enterprise for same id): server/test/memory-recall.test.ts#L294

AssertionError: expected [] to have a length of 1 but got +0 - Expected + Received - 1 + 0 ❯ server/test/memory-recall.test.ts:294:26

server/test/memory-recall.test.ts > memory recall endpoint — I.5 > merges personal and enterprise results into a single response: server/test/memory-recall.test.ts#L273

AssertionError: expected [] to have a length of 3 but got +0 - Expected + Received - 3 + 0 ❯ server/test/memory-recall.test.ts:273:26

server/test/memory-recall.test.ts > memory recall endpoint — I.5 > drops template-origin rows from merged results even for a normal query: server/test/memory-recall.test.ts#L244

AssertionError: expected [] to include 'ok-1' ❯ server/test/memory-recall.test.ts:244:17

Secret Scan (gitleaks)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, gitleaks/gitleaks-action@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Lint

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Lint: src/daemon/p2p-orchestrator.ts#L167

'buildOriginalRequestReminder' is defined but never used

Lint: src/daemon/command-handler.ts#L78

'isKnownTestSessionLike' is defined but never used

Lint: src/daemon/command-handler.ts#L16

'getResendCount' is defined but never used

Lint: src/context/embedding.ts#L9

'cosineSimilarity' is defined but never used

Lint: src/agent/transport-runtime-assembly.ts#L104

'namespace' is assigned a value but never used

Lint: src/agent/providers/cursor-headless-stream.ts#L1

'ToolCallEvent' is defined but never used

Embedding Integration Tests

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. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Server Unit Tests