Skip to content

Memory

Memory #81

Triggered via pull request June 16, 2026 07:08
Status Failure
Total duration 1m 20s
Artifacts

pr-check.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 14 warnings
test
Process completed with exit code 1.
packages/codingcode/test/memory/index.test.ts > Memory Index > loadMemoryForPrompt > truncates memory when exceeds promptMaxBytes: packages/codingcode/test/memory/index.test.ts#L136
AssertionError: expected 457 to be less than or equal to 100 ❯ packages/codingcode/test/memory/index.test.ts:136:21
packages/codingcode/test/ci/tooling-scripts.test.ts > CI tooling configuration > pnpm run format:check exits successfully: packages/codingcode/test/ci/tooling-scripts.test.ts#L48
AssertionError: expected [Function] to not throw an error but 'Error: Command failed: pnpm run forma…' was thrown - Expected: undefined + Received: "Error: Command failed: pnpm run format:check [WARN] The \"pnpm\" field in package.json is no longer read by pnpm. The following keys were ignored: \"pnpm.overrides\". See https://pnpm.io/settings for the new home of each setting. $ prettier --check \"packages/**/*.{ts,tsx,json}\" \"*.json\" \"*.ts\" [warn] packages/codingcode/test/server/settings-routes.test.ts [warn] packages/desktop/src/settings/MemoryPanel.tsx [warn] Code style issues found in 2 files. Run Prettier with --write to fix. " ❯ packages/codingcode/test/ci/tooling-scripts.test.ts:48:87
packages/codingcode/test/agent/memory-snapshot.test.ts > Memory snapshot stability > injects <system-reminder> when memory changed since snapshot: packages/codingcode/test/agent/memory-snapshot.test.ts#L169
AssertionError: expected 'hi' to contain '<system-reminder>' Expected: "<system-reminder>" Received: "hi" ❯ packages/codingcode/test/agent/memory-snapshot.test.ts:169:33
changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, dorny/paths-filter@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
typecheck
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, pnpm/action-setup@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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, pnpm/action-setup@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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: packages/codingcode/src/hooks/config.ts#L5
'HookPoint' is defined but never used. Allowed unused vars must match /^_/u
lint: packages/codingcode/src/context/service.ts#L36
'REACTIVE_COMPACT_MAX_RETRIES' is assigned a value but never used. Allowed unused vars must match /^_/u
lint: packages/codingcode/src/client/direct/settings.ts#L40
'resolveHookDisabled' is defined but never used. Allowed unused vars must match /^_/u
lint: packages/codingcode/src/client/direct/settings.ts#L12
'resolveMcpDisabled' is defined but never used. Allowed unused vars must match /^_/u
lint: packages/codingcode/src/checkpoint/checkpoint-service.ts#L15
This generator function does not have 'yield'
lint: packages/codingcode/src/approval/async-confirm.ts#L10
This generator function does not have 'yield'
lint: packages/codingcode/src/agent/prompt.ts#L107
Unnecessary escape character: \'
lint: packages/codingcode/src/agent/agent.ts#L136
'context' is assigned a value but never used. Allowed unused vars must match /^_/u
lint: packages/codingcode/src/agent/agent.ts#L134
'todo' is assigned a value but never used. Allowed unused vars must match /^_/u
lint: packages/codingcode/src/agent/agent.ts#L131
'approval' is assigned a value but never used. Allowed unused vars must match /^_/u
test
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, pnpm/action-setup@v3. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/