jason/mempalace
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

style(mcp): drop issue-tracker comments from KG cache block

Browse Source 
Inline comments referencing #1136 and #540 add no information the
identifiers do not already convey. PR description carries the context;
code stays quiet.
This commit is contained in:
mvalentsev
2026-04-24 13:07:34 +05:00
parent 84f9726a39
commit 19f8a4ff68
1 changed files with 0 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
mempalace/mcp_server.py
-10
View File
@@ -105,18 +105,8 @@ if _args.palace:
_config = MempalaceConfig() _config = MempalaceConfig()
# Lazy per-path KG cache. Import no longer creates the sqlite file as a side
# effect (see issue #1136). The path is resolved on each tool call so that a
# multi-tenant host rotating MEMPALACE_PALACE_PATH between calls routes each
# call to the correct KG file, matching the per-call behavior of _get_client()
# on the ChromaDB side.
_kg_by_path: dict[str, KnowledgeGraph] = {} _kg_by_path: dict[str, KnowledgeGraph] = {}
_kg_cache_lock = threading.Lock() _kg_cache_lock = threading.Lock()
# Whether --palace was given at startup. Controls default-path resolution:
# with the flag, KG follows _config.palace_path per call; without it, KG stays
# on DEFAULT_KG_PATH regardless of env var (issue #540's territory, out of
# scope here).
_palace_flag_given: bool = bool(_args.palace) _palace_flag_given: bool = bool(_args.palace)