Imrpoved debugging output for slow indexing #6177
Replies: 3 comments
-
Thanks for reaching out. The error you're encountering happens during the enumerations of files in your workspace, not during the indexing step. The process is taking longer than 10 seconds as indicated by the log. Could you please check the root of your workspace to see if it matches any of the scenarios described in the error message? Addressing these factors should help speed up the file enumeration process. |
Beta Was this translation helpful? Give feedback.
-
I just mean it would be nice if it gave a more clear output in terms of which folders were taking a long time. For example, if I had accidentally included the .venv directory it would be nice to see that it's taking a long time so I can exclude from the pyright config. |
Beta Was this translation helpful? Give feedback.
-
Moving this issue to discussion as an enhancement request for comments and upvotes. |
Beta Was this translation helpful? Give feedback.
-
Currently when I start vscode for the first time and it indexes my workspace, it tends to take a long time and it outputs the following error:
However, it would be helpful to have more insights about which files and directories are taking longer than others so that I can take action more effectively. For example, having a list of directories and the time it took for pylance to index them.
Beta Was this translation helpful? Give feedback.
All reactions