style(mcp): drop issue-tracker comments from KG cache block
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:
@@ -105,18 +105,8 @@ if _args.palace:
|
||||
|
||||
_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_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)
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user