Unnecessary re-indexing with shared parent

[aldem]

Not sure if this intended behavior, but if projects share same root, like project/sub-project-a and project/sub-project-b, then, after indexing project, attempt to index children project/sub-project-[ab] creates new indexes, so we have triple indexing.

I encountered this when Claude attempted to descend into sub-projects - this triggered re-indexing.

[aeneasr]

Thank you for the report! I had similar issues in the past but I believe those have been resolved, at least I didn’t have reindex issues recently despite subdirs and worktrees - so just checking if your plugin is on the latest published version?

Also are you in a git directory or is it without git?

[aldem]

In my case, project is just a container (no git) while both subdirs are with git.

I used 0.0.25 binary from releases.

[aeneasr]

Thank you for the answer, could you say if I understood this correctly:

• project has no git
• project/sub-project-a has git
• project/sub-project-b has git (other git remote though)

you ran lumen index project and then lumen index project/sub-project-a which created another fresh index?

[aldem]

Yes, almost. To be precise:

• I ran lumen index . while in project (which has no git)
• Then I ran lumen index sub-project-a and also for b (both have independent git repos) - it started to index them too.
• Also tried full paths - same story.

[aeneasr]

Thank you! Unfortunately this is a limitation right now, lumen is primarily for working in git trees - that is in order to solve (a) git worktrees and (b) properly map subdirectories within git directories.

So ideally, you would index only directories with git. We could probably throw a warning in lumen when you try to index a non-git directory, or add some mode of "find all git directories in this directory and index them"

[aldem]

Well, this is quite serious limitation... as not everything is stored in git :)

[aeneasr]

I probably explained it wrong - You CAN index stuff thats not in git, but when you index a parent that has no git but children that have, it currently runs into the triple index issue :) But I had an idea where we simply identify if a subdir is git in a parent that isn’t, and then just create a separate index then

[aldem]

Actually this is a really good idea, simplifies things a lot 👍

[aldem]

BTW... Not sure if it makes sense to open a new issue... but what about if all sub-dirs are without git? Seems that we have the same problem - sub-dirs are re-indexed if explicitly specified.

[aeneasr]

In that case, it should figure out that it's in a subdirectory of an existing index and use the existing index