-
Notifications
You must be signed in to change notification settings - Fork 133
"Object reference not set to an instance of an object" when trying Go To Symbol in Workspace #378
Comments
I know that the scikit-learn project is pretty large and PLS takes a while to go through it, but are you doing this Ctrl+T and I think I have an idea of the problem, but haven't been able to reproduce it with scikit-learn using what you had reported in the VSC extension repo. |
I did ctrl-t while it was indexing I think (100% cpu). I did ctrl-t at the end as well and it did not work either. Does VS Code symbol navigation work for you on the scikit-learn source folder with the MS language server? I have never see it work so far. |
I think I could not see the error output without waiting for 10+ minutes though (if I recall correctly). |
The current implementation waits for the entire analysis to complete before allowing these sorts of lookups to happen (for better or worse). But, even when I remove those checks and allow queries through when it's still working, I wasn't able to get the issue to happen, and I'll get search results (though it's slow to finish, maybe 10 seconds to find "kmeans"). I'm still looking for ways this nullref is happening, though. I may just have to "fix" it for now by ignoring nulls until we can actually catch the null while debugging. |
I tried a fresh clone of scikit-learn in my When done I pressed ctrl-T only once (without typing anything else) and got the error message I already reported earlier (and no results in the navigation menu). I am running Linux, maybe this is a Linux specific bug? |
I'll give it a go on my Arch machine with the instructions you've given and see how it goes. |
Aha, yes, after letting it run to completion (I opened I'll look into it, but might only be able to actually figure it out on Monday when I have VS in front of me. |
Glad you could reproduce it. Thanks. |
This is a follow up on #137 that was closed prior to version 0.1.60.0.
Here is the full error message with the new version:
The text was updated successfully, but these errors were encountered: