Extension is not working in multi-root workspace

[worm2fed]

Describe the bug
Extension is not working in multi-root workspace. Just showing "loading" forever. But if I open a folder (not workspace) - seems to be ok.
tried to add glossary to multi-root root and to repoA

- root
   - source
      - repoA
      - repoB

Expected behavior
Extension should work with glossary file both in root and in any repo

Screenshots

Desktop (please complete the following information):

• OS: Darwin MacBookPro 24.6.0 Darwin Kernel Version 24.6.0: Mon Jul 14 11:30:29 PDT 2025; root:xnu-11417.140.69~1/RELEASE_ARM64_T6000 arm64
• VSCode Version: 1.99.3
• Version: v1.17.1

Additional context
Extension logs:

[Info  - 12:35:54 PM] Starting Contextive.LanguageServer v1.17.1+063045833e9836d3524c2d7488565f2309578f0b...
Loading contextive from /Users/worm2fed/workspace/.../app.glossary.yaml...
Successfully loaded from /Users/worm2fed/workspace/.../app.glossary.yaml.

[worm2fed]

Also if to put file somewhere in structure
eg:

- .
  - dirA
     - dirAB
        - app.glossary.yaml

then in logs it even cannot detect the file (fine if open just a folder in a new window)

[chrissimon-au]

Hi @worm2fed , thanks for reporting this!

I've just tried to replicate, and it is working for me, so there must be a difference in configuration. To confirm expectations, this is the structure I just tested:

.
./root.glossary.yml
./rootA/
./rootA/a.ts
./rootA/a.glossary.yml
./rootB/
./rootB/b.ts
./rootB/b.glossary.yml

In root.glossary.yml:

contexts:
  - name: "Root"
    terms:
      - name: "A"
        definition: "In the root"

In a.glossary.yml:

contexts:
  - name: "Root A"
    terms:
      - name: "A"
        definition: "In root A"

In b.glossary.yml:

contexts:
  - name: "Root B"
    terms:
      - name: "B"
        definition: "In root B"
      - name: "A"
        definition: "In root B (not in root A)"

If the workspace is configured with just rootA and rootB, then it is expected that root.glossary.yml is ignored (because is is not found in any of the workspace roots), and only a.glossary.yml and b.glossary.yml are applied in their respective path structures:

Workspace config:

In a.ts hovering over A:

In b.ts hovering over a:

If the 'root' folder is added to the workspace, like so:

Then the root.glossary.yml is also picked up as it is found in at least one workspace root, and we get the following:

In a.ts hovering over A:

In b.ts hovering over a:

Can you confirm the exact structure of your multi-root workspace and locations of glossary files? Ideally a minimal git repo that reproduces the problem will help me understand what is different/not working.

One thing I will note that I just discovered is that it does not detect changes to the workspace configuration. When I added the root folder to the workspace, I had to reload the window for it to pick up root.glossary.yml - so be sure to restart vscode after making changes to the workspace configuration to double check. If that does solve the problem, let me know and I'll look into what is needed to have contextive react to changes to the folders available in the workspace.

Thanks!

[worm2fed]

Hi! Thank you for trying this. Let me prepare a dummy repo with test case for you

P.S. I've tried reload window / restart extensions host - same effect.

[worm2fed]

multi-root-demo.zip

@chrissimon-au okay, now I'm confused
because with minimal example it's working. Is there a chance it's failing to load definitions because of amount of code?
Cause actually I see "loading.." which means it's trying to resolve something. Is there a debug mode to see what is happening?

[chrissimon-au]

It generally doesn't have an issue with the amount of code per se - but now that you mention it, I do recall seeing recently that it 'choked' on a devenv.sh folder because of the number of files in the .devenv folder - basically just got stuck forever scanning that folder looking for glossary files. It's been on my mind to implement ignoring .gitignore'd files/folders when scanning for glossary files, thanks for the reminder - I've just added it #109

Is it possible that your workspace has any folders with very large numbers of files/folders - or possible circular loops caused by links in the file system, even in a .gitignore'd folder?

[worm2fed]

well.. it's a monorepo with micro-fronts
amount of source code should not be a problem, but node_modules - may be