Severity: medium — data-integrity foot-gun.
index_repository(repo_path="/path/to/proj") created a new project whose name
was derived from the absolute filesystem path, while the existing index of the same
root_path stayed untouched. Both then appear in list_projects with identical
root_path. The failure is silent and looks like a successful reindex; the symptom
is metrics that do not move at all after a "successful" reindex — which is exactly
how a stale index gets read as fresh.
Ask: when an indexed project already exists with the same root_path, update it
or fail loudly rather than forking a second index under a derived name.
Observed on v0.10.8 (build 996bad5fe6fb), macOS arm64, Python monorepo (~36k nodes / ~179k edges). Happy to provide a minimal reproduction repo if useful.
Severity: medium — data-integrity foot-gun.
index_repository(repo_path="/path/to/proj")created a new project whose namewas derived from the absolute filesystem path, while the existing index of the same
root_pathstayed untouched. Both then appear inlist_projectswith identicalroot_path. The failure is silent and looks like a successful reindex; the symptomis metrics that do not move at all after a "successful" reindex — which is exactly
how a stale index gets read as fresh.
Ask: when an indexed project already exists with the same
root_path, update itor fail loudly rather than forking a second index under a derived name.
Observed on v0.10.8 (build
996bad5fe6fb), macOS arm64, Python monorepo (~36k nodes / ~179k edges). Happy to provide a minimal reproduction repo if useful.