Default service instance

[noootch]

Hello,

I have a problem/question for my setup as I do not understand what is happening exactly. I use following workspace config in vscode:
"{folders": [ { "path": "./frontend" }, { "path": "./backend" }, { "path": "../utils" }, { "path": ".", "name": "root" } ]}

In the backend folder I have a pyproject.toml with some settings and a "hmi" folder with my python code.

The "Python language server" output looks like this:

2024-09-25 12:00:34.526 [info] [Info - 12:00:34 PM] (61500) Starting service instance "frontend"
2024-09-25 12:00:34.559 [info] [Info - 12:00:34 PM] (61500) Starting service instance "backend"
2024-09-25 12:00:34.562 [info] [Info - 12:00:34 PM] (61500) Starting service instance "root"
2024-09-25 12:00:34.562 [info] [Info - 12:00:34 PM] (61500) Starting service instance "utils"
2024-09-25 12:02:49.221 [info] [Info - 12:02:49 PM] (61500) Loading pyproject.toml file at backend\pyproject.toml
2024-09-25 12:02:49.225 [info] [Info - 12:02:49 PM] (61500) Setting pythonPath for service "backend": "backend.venv\Scripts\python.exe"
2024-09-25 12:02:49.221 [info] [Info - 12:02:49 PM] (61500) Loading pyproject.toml file at ..\utils\pyproject.toml
2024-09-25 12:02:49.225 [info] [Info - 12:02:49 PM] (61500) Setting pythonPath for service "utils": "backend.venv\Scripts\python.exe"

I install my package in editable mode from the backend folder with pip install -e.

Now when I open a python file from my src folder the language server creates another instance with following output:

2024-09-25 12:00:46.051 [info] [Info - 12:00:46 PM] (61500) Starting service instance ""
2024-09-25 12:00:46.601 [info] [Info - 12:00:46 PM] (61500) Setting environmentName for service "": "3.11.9 (.venv venv)"
2024-09-25 12:00:46.603 [info] [Info - 12:00:46 PM] (61500) Setting pythonPath for service "": "backend.venv\Scripts\python.exe"
2024-09-25 12:00:46.606 [info] [Info - 12:00:46 PM] (61500) No include entries specified; assuming <default workspace root>
2024-09-25 12:00:46.606 [info] [Info - 12:00:46 PM] (61500) Auto-excluding **/node_modules
2024-09-25 12:00:46.607 [info] [Info - 12:00:46 PM] (61500) Auto-excluding **/pycache
2024-09-25 12:00:46.607 [info] [Info - 12:00:46 PM] (61500) Auto-excluding */.
2024-09-25 12:00:47.266 [info] [Info - 12:00:47 PM] (61500) Assuming Python version 3.11.9.final.0
2024-09-25 12:00:48.195 [info] [Error - 12:00:48 PM] (61500) File or directory "<default workspace root>" does not exist.
2024-09-25 12:00:48.198 [info] [Info - 12:00:48 PM] (61500) No source files found.

It seems that the file is analysed with this "default" service instance. It seems like this is leading to pylance/pylint ignoring all other settings.

I would like to know:

• if I can control which service instances are created in the first place
• why the default instance is created
• how could I configure the default instance

Edit:
I looked at the code and it seems like the language server is looking for a matching service instance for my file, but it does not find one thous creating the "default" one. So I guess the question is: why is the file not included in the service instance?
Is it because of the editable mode or am I missing some configuration?

Also it seems that since version 2024.9.1 I am not able to disable typeCheckingMode.

Kind regards,
Chris

[rchiodo]

Your typecheckingmode problem is likely this:
https://github.com/microsoft/pylance-release/wiki/Settings.json-overridden-by-Pyrightconfig.json-or-Pyproject.toml

Default instances are created whenever a file that's opened doesn't fall under a workspace root. Can you turn on 'trace' mode for logging? It will show the actual analysis and for what file path.

[noootch]

Thank you for the answer.

I made the mistake to set tracemode only in the vscode terminal which did not affect the plugin.
Now that I enabled tracemode I learnt a bit more about how the stub packages are searched and how the language server works in general.

What I did:

• put a pyrightconfig.json with "exclude": ["*"] resulting in root service not watching any files (big performance +)
• added include=["hmi"] to pyproject.toml in backend -> reduce search paths
• added extraPaths=["*venv/Lib/site-packages"] to pyproject.toml in backend (don't know if this is really necessary)
• added both entries to pyproject.toml in my utils module

My guess is that the root server interfered with the backend server as they both observed the same files. Now the analysis settings work properly.