-
Notifications
You must be signed in to change notification settings - Fork 767
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pylance slow to start analysis after vscode start #1281
Comments
Your workspace root is Are there any directories that should be ignored? What's in this directory? The bazel output sounds suspect, but I'm not sure if that contains importable code or not. |
We also support symlinks (and avoid recursion); I believe bazel might use symlinks so we might be picking up more files that way. |
Using Thanks, I guess this is either resolved or made into a feature request to provide visibility into the slow startup issues. |
Feedback about the startup scan is certainly important; if we can speed this up somehow that would be great. It's one of the few things we have that isn't lazy. |
I also meet this problem. Once I @jakebailey Really appreciate your help.! |
closing dup of this #1569 |
Environment data
Expected behaviour
Pylance can start providing language support within a few seconds of vscode starting.
Actual behaviour
On "fast" hardware Pylance takes 60+ seconds to start analysis of the first open file. On slow hardware it can take several minutes.
Logs
Code Snippet / Additional information
I suspect the issue is the large number of source files being found by pylance. The workspace its self only contains ~6k python files.
Looking at the search paths listed the bulk of the files seem to be in
/usr/local/lib/python3.6/dist-packages
. Yet there only appear to be ~100k.py
or.pyi
files across all of the directories so it is unclear where pylance is coming with its565581 source files
. I have also been unable to find a way to exclude the search directories included by pylance (e.g. pip directories), so isolate the issue.The text was updated successfully, but these errors were encountered: