Pylance does not boot properly and fails to highlight text when used on an SSH remote #6710
Assignees
Labels
needs repro
Issue has not been reproduced yet
Comments
|
Is there any command I can run? After enabling traces, nothing appears in the terminal, "output", etc. |
|
The Python output tab should indicate whether or not it could load Pylance or not. Sounds like it's failing to load Pylance at all. |
|
That's interesting. I don't see anything in the "Python" tab. |
|
If you run 'Toggle Developer Tools', the console on that page might show something. The
|
|
Ah I didn't know that! After switching to Python, I found those logs: |
|
The error is this one: You're using an older version of VS code. You can't install the latest pylance into it. |
|
How did you install pylance? The extension tab in VS code should only show versions that are supported. |
|
I'm using the "Extensions" tab, so not sure why vscode allowed me to install that. I will try to update vscode |
|
It could be the remote machine needs to be updated. The extensions actually run on the remote box in SSH. I thought the remote SSH extension auto updated, but I could be wrong. |
|
How can I check and update the version? |
|
I don't use SSH myself, but in WSL it gets updated by just running According to this, the Remote SSH extension is supposed to do it for you. So maybe your local version is out of date too. |
|
Might be related to permissions though: |
|
SHould I open a different issue to say that the Remote SSH extension does not auto-update the vscode server? |
|
Assuming your local VS code isn't 1.89, then yeah that sounds like a bug. Although I'd check that last link first to make sure it isn't because the remote server is locked down too tight. |
|
My local version is indeed 1.89 (took a while to figure out since mac zsh doesn't work well with the How do I update the local? I don't use WSL. |
|
Oh seems that "checking for update" gives me this error: Except it's not a read-only volume, as I am capable of editing file on this volume. |
|
My guess would be to uninstall and reinstall VS code. |
|
Actually it was indeed in my downloads folder (I tried searching "Code" but it somehow didn't find it, had to manually look and move to "Applications" folder. |
|
Ok, using Cmd+P to find the update procedure seems to work ("Code: Check for updates..." and "Code: Restart to Update"). Never would have guessed but seems like i was 6 version behind the latest! So probably means vscode never updated since I installed it (given it was in Downloads rather than Applications). I think it would be good to have a notification popup that says "Your VS code is X version behind. Auto-update did not work, consider moving the file "Visual Studio Code" from "~/Downloads" to "Applications"). I think this would be really be helpful! |
If you wanted this to happen, I'd recommend logging this in the VS code issues. That wouldn't be something that Pylance would be able to do. |
|
Makes sense! This seems indeed a vscode-specific issue. I will create one. THank you for debugging this with me! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A follow up on #6442.
This issue still happens a lot to me, when i'm ssh'd to a remote. Using the "exclude" trick above doesn't help.
Usually i would change to pre-release then reload, sometimes that fixes it, but the next time I SSH to the remote the issue arises again (everything unhighlighted). I'm not sure what's the cause as I didn't change much from my workflow apart, this simply started happening a month or two ago.
I'm creating an issue based on advice from: #6442 (comment)
Environment data
Code Snippet
N/A
Repro Steps
Expected behavior
Pylance should work
Actual behavior
Pylance does not boot, there's no error message
Logs
I enabled traces but there are not traces that appear.
The text was updated successfully, but these errors were encountered: