This repository was archived by the owner on Apr 14, 2022. It is now read-only.
Python Language Server crash "Value cannot be null." #383
Comments
|
From @hvdklauw on November 12, 2018 8:29 VS Code version: 1.28.2 Then The same error keeps showing up: |
This was referenced Nov 12, 2018
|
I am also seeing the Occasionally I get the following error instead (EDITED: this is unrelated, see #379 as @jakebailey mentioned below). If I hover a token lower down in the file first and wait for it to return results, the hovers mentioned above do not throw an error and do return the correct value. So there could be some path-dependency or nondeterminism here. BTW, this lang server is amazing! 🎉 Thank you! |
|
Thanks for giving a possible test case. Are you also on macOS when you get the exception, or another OS? That second trace you've provided is tracked in #379, for reference. It's not good, but shouldn't cause any "true" exceptions in a release build (since debug assertions wouldn't fire). Things are certainly non-deterministic because of our current implementation of the analysis order, which will be changed in the future with a true dependency graph. |
|
Ah, I just read your stack trace more closely and saw |
|
The issue with changed hash typically happens when there is a bug in comparing elements. Item comparer says iterm is the same as one that is already in the bag, and yet hash comes different. Maybe related to the overloads comparison issue fixed post release. See #359. Technically the discrepancy can be ignored and item can be accepted as identical so the collection remains the same. |
Merged
|
Will the python extension for VScode automatically download a new version of python language server once the fix is merged/released? Or do we then need to also wait for that package to be updated? Kinda annoyed that nothing works anymore while it was working just fine for me before. |
This comment has been minimized.
This comment has been minimized.
|
The extension will download a new build if it is available, yes. It'll do a check once a day, if my memory is correct. That check is separate from the extension's release schedule so we can do out-of-band releases. We manually decide which revisions to release as stable/beta/daily releases (the latter for almost every master revision). After #418 is merged, we'll do a build which will go to daily, but we'd have to decide if we think it's stable enough for the stable version. If you want to get that build before we even decide to publish it as stable, you can switch release channels in VSC by adding the following to your "python.analysis.downloadChannel": "daily"To go back to stable, remove that entry, but be aware that the extension won't automatically downgrade (you'd need to delete its copy of the language server). |
|
Awesome, thanks ! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
From @saulshanabrook on November 11, 2018 19:10
Environment data
Actual behavior
No python intellisense when not using jedi.
Expected behavior
Python intellesense even when jedi is off
Steps to reproduce:
Logs
Output for
Pythonin theOutputpanel (View→Output, change the drop-down the upper-right of theOutputpanel toPython)Output from
Consoleunder theDeveloper Toolspanel (toggle Developer Tools on underHelp)Copied from original issue: microsoft/vscode-python#3302
The text was updated successfully, but these errors were encountered: