-
Notifications
You must be signed in to change notification settings - Fork 511
Extension startup times out too soon on lengthy (7-10 sec) language server startup #562
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
Hey Bjørn, thanks for filing this! I think you forgot to turn on Verbose logging, your log file seems to be missing some lines:
|
Sorry about that. here's the correct logs with Verbose logging enabled, i wrote "Debug" instead of "Verbose" the first time :) 1489672155-12b1df75-c9e1-481c-9072-9837761f96e61489672141705.zip |
Thanks, that did the trick! So it looks like nothing is failing during startup, I think the extension is just not waiting long enough for the language server to initialize before timing out. I'll bump up the timeout length in the patch update I'm shipping today, that should fix it for you. |
Thank you 👍 |
Fix #562: Extension times out prematurely on long language server startup
System Details
$PSVersionTable
:PSVersion 5.0.10514.6
WSManStackVersion 3.0
SerializationVersion 1.1.0.1
CLRVersion 4.0.30319.42000
BuildVersion 10.0.10514.6
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion 2.3`
Issue Description
I am experiencing a problem when i try to start the Integrated terminal. Ii hangs at "Starting Powershell" for some time and finally fails with the following error:
Could not start language service:
Timed out waiting for session file to appear.
Attached Logs
vscode-powershell.zip
The text was updated successfully, but these errors were encountered: