Skip to content

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

Closed
aurbjo opened this issue Mar 16, 2017 · 4 comments
Labels
Issue-Bug A bug to squash.

Comments

@aurbjo
Copy link

aurbjo commented Mar 16, 2017

System Details

  • Operating system name and version: Windows Server 2012 R2
  • VS Code version: 1.10.2
  • PowerShell extension version: 0.10.0
  • Output from $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.

image

image

image

Attached Logs

vscode-powershell.zip

@daviwil
Copy link
Contributor

daviwil commented Mar 16, 2017

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:

"powershell.developer.editorServicesLogLevel": "Verbose"

@aurbjo
Copy link
Author

aurbjo commented Mar 16, 2017

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

@daviwil
Copy link
Contributor

daviwil commented Mar 16, 2017

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.

@daviwil daviwil added the Issue-Bug A bug to squash. label Mar 16, 2017
@daviwil daviwil changed the title Could not start language service: Timed out waiting for session file to appear. Extension server times out too soon on lengthy (7-10 sec) language server startup Mar 16, 2017
@daviwil daviwil changed the title Extension server times out too soon on lengthy (7-10 sec) language server startup Extension startup times out too soon on lengthy (7-10 sec) language server startup Mar 16, 2017
@aurbjo
Copy link
Author

aurbjo commented Mar 16, 2017

Thank you 👍

daviwil added a commit that referenced this issue Mar 16, 2017
Fix #562: Extension times out prematurely on long language server startup
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug A bug to squash.
Projects
None yet
Development

No branches or pull requests

2 participants