-
Notifications
You must be signed in to change notification settings - Fork 511
Language server startup failed: PowerShellEditorServices missing. #775
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
Comments
Thanks @deathly809! Sorry for the trouble with getting that error message, the terminal is supposed to stay open for a bit on error so that you can copy it. I think I missed a case in the startup script which didn't catch this error case. Can you give me the output of running these commands in PowerShell outside of VS Code: gci $HOME/.vscode/extensions/ms-vscode.PowerShell-1.1.0/modules
Get-Module -ListAvailable $HOME/.vscode/extensions/ms-vscode.PowerShell-1.1.0/modules/PowerShellEditorServices/PowerShellEditorServices.psd1
Get-Module -ListAvailable |
gci $HOME/.vscode/extensions/ms-vscode.PowerShell-1.1.0/modules
Get-Module -ListAvailable $HOME/.vscode/extensions/ms-vscode.PowerShell-1.1.0/modules/PowerShellEditorServices/PowerShellEditorServices.psd1
Get-Module -ListAvailable
|
Something is wrong here, the modules folder should not be empty. How did you install the extension, via the VS Code Extensions pane? Can you give me the output of this command: gci $HOME/.vscode/extensions/ms-vscode.PowerShell-1.1.0/ |
I installed through VSCode. I see the problem, it is lowercase on Linux (powershell, not PowerShell). Here is the original command with lowercase PowerShell
|
Hmmm, that's strange, I wonder if VS Code changed how they deal with paths when they install extensions. Thanks for pointing this out, I'll try to get it fixed soon! |
By the way, was this working for you successfully in the past or is this the first time you've tried to use VS Code and the PowerShell extension on Ubuntu? |
I have only just started using it and I don't recall it ever working. |
I believe I'm having a similar issue on OS X 10.12.5.
The language service fails to initialize with the following error:
I've had this behavior since I installed the extension a few weeks back and just now got around to troubleshooting it. When I run the
Output from
Notice in the output for the
If I edit the script and add the
Output for
I'm puzzled as to why PowerShell is not honoring the In any case, I was able to get the language service to load by making the following changes:
Specifically, I'm passing the path to the module into the One issue I'm still experiencing is that the integrated console does not load on the first attempt; it just hangs indefinitely. I have to Hope this helps in correcting the issue permanently. |
Ahh! Sorry guys, I just realized what the problem is. You both need to upgrade to PowerShell 6.0.0-alpha.18 or higher. I'd recommend 6.0.0-beta.1. Once you install that version of PowerShell everything should start working. |
Closing this issue for now since I think a PowerShell Core upgrade fixes the issue. If this is not the case, let me know and I'll reopen for investigation. Thanks! |
I am having this same issue using the following version:
I have just installed the following version of the script: |
Thanks for the info @AJDulk can you open a new issue (easier for us, to track) and |
System Details
Operating system name and version:
Ubuntu 16.04
VS Code version:
1.12.2
PowerShell extension version:
1.1.0
Output from
$PSVersionTable
:Name Value
PSVersion 6.0.0-alpha
PSEdition Core
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 3.0.0.0
GitCommitId v6.0.0-alpha.14
CLRVersion
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
Issue Description
When I start up VSCode the Powershell Language Server fails to load. There is an error message in the 'PowerShell Integrated Terminal" but it is erased before I can read it. I took a screenshot of this error (after many attempts) and attached in zip file. There is no useful error message in the logs, maybe this should be fixed (another bug report?).
Attached Logs
BugReport.zip
The text was updated successfully, but these errors were encountered: