Skip to content

Memory System Fixes - #16

Merged
ngduyanhece merged 13 commits into
mainfrom
feat/add-milvus-vector-store-service
Jul 7, 2025
Merged

Memory System Fixes #16
ngduyanhece merged 13 commits into
mainfrom
feat/add-milvus-vector-store-service

Conversation

@RyanNg1403

Copy link
Copy Markdown
Contributor

🔧 Fix: Resolve Test Failures for Memory System Refactor

Overview

This PR addresses and resolves all test failures from PR #15.

Key Fixes

  • Services context: Added default mock services to InternalToolManager for reliable tool execution in tests.
  • Tool name resolution: Improved handling of both prefixed and non-prefixed tool names.
  • Statistics tracking: Fixed execution stats recording and reporting.
  • TypeScript types: Resolved all type errors in test mocks and context.
    Note: A dedicated test file, @pr-validation.test.ts, is included for validation, and all test cases now pass.

Display Order Note

The logic for switching the display order of the agent response and cipher_extract_and_operate_memory logs (as described in the previous PR and shown in your image) remains unchanged.
The relevant code in src/core/session/conversation-session.ts (lines ~60-65) is still accurate, and the display order can still be easily switched as before.

Related PRs

meanthai added 13 commits July 6, 2025 18:06
…us from qdrant and also adding env variables and updating search filter supports basic syntax including in, and, or, gte, le, ge, lte
…us from qdrant and also adding env variables and updating search filter supports basic syntax including in, and, or, gte, le, ge, lte
…us from qdrant and also adding env variables and updating search filter supports basic syntax including in, and, or, gte, le, ge, lte
@ngduyanhece
ngduyanhece merged commit dfb71d3 into main Jul 7, 2025
@RyanNg1403
RyanNg1403 deleted the feat/add-milvus-vector-store-service branch July 19, 2025 00:49
Ptah-CT pushed a commit to DerAuctor/ct-cipher that referenced this pull request Oct 2, 2025
hieuntg81 added a commit that referenced this pull request Apr 22, 2026
…iew #16)

resolveHome only expands a leading ~. Relative paths like `./id_ed25519`
or bare `id_ed25519` passed straight through and then resolved against
the daemon's CWD — so the same config value worked today and broke
tomorrow if the daemon restarted from a different directory.

Reject non-absolute paths at both entry points (handleConfig set and
handleImportGitSigning) with INVALID_CONFIG_VALUE. Matches the semantic
of `git config user.signingKey`, which also requires an absolute path.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants