Skip to content
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

tsserver won't start - WSL? #88388

Closed
alexpaluzzi opened this issue Jan 9, 2020 · 8 comments
Closed

tsserver won't start - WSL? #88388

alexpaluzzi opened this issue Jan 9, 2020 · 8 comments
Assignees
Labels
javascript JavaScript support issues upstream-issue-linked This is an upstream issue that has been reported upstream

Comments

@alexpaluzzi
Copy link

Version: 1.41.1 (user setup)
Commit: 26076a4
Date: 2019-12-18T14:58:56.166Z
Electron: 6.1.5
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Windows_NT x64 10.0.19041

Steps to Reproduce:

  1. Open any .js or .ts file in my project

After opening and watching "Initializing js/ts server...". I verbose logging shows a whole mess of stuff, happy to put it all here if needed.
Some that stick out:

[Trace - 19:30:30.496] Response received: updateOpen (2). Request took 137986 ms. Success: true

This took over 2 minutes.

[Trace - 19:30:31.120] Response received: getSupportedCodeFixes (3). Request took 138609 ms. Success: true

This took another 2 minutes.

[Trace - 19:30:37.291] Response received: configure (4). Request took 144779 ms. Success: true

Again.

Then it just kind of hangs. I noticed when I try to force some intellisense (with ctrl+space) I see these errors:

[Error  - 19:35:46.867] ReaderError
RangeError [ERR_OUT_OF_RANGE]: The value of "length" is out of range. It must be an integer. Received NaN
	at Function.concat (buffer.js:449:5)
	at l.append (/home/alex/.vscode-server/bin/26076a4de974ead31f97692a0d32f90d735645c0/extensions/typescript-language-features/dist/extension.js:1:210613)
	at t.Reader.onLengthData (/home/alex/.vscode-server/bin/26076a4de974ead31f97692a0d32f90d735645c0/extensions/typescript-language-features/dist/extension.js:1:211680)
	at Socket.<anonymous> (/home/alex/.vscode-server/bin/26076a4de974ead31f97692a0d32f90d735645c0/extensions/typescript-language-features/dist/extension.js:1:211607)
	at Socket.emit (events.js:200:13)
	at addChunk (_stream_readable.js:294:12)
	at readableAddChunk (_stream_readable.js:275:11)
	at Socket.Readable.push (_stream_readable.js:210:10)
	at Pipe.onStreamRead (internal/stream_base_commons.js:166:17)

I tried reinstalling VS Code. I tried Insiders. All my extensions (except for WSL Remote) are disabled. Happy to help or get more information if needed.

@vscodebot vscodebot bot assigned mjbvz Jan 9, 2020
@vscodebot vscodebot bot added the javascript JavaScript support issues label Jan 9, 2020
@mjbvz
Copy link
Collaborator

mjbvz commented Jan 9, 2020

Where is your code stored? Somewhere besides the c: drive?

@alexpaluzzi
Copy link
Author

Where is your code stored? Somewhere besides the c: drive?

Yes sir. It's on a separate drive entirely d:. I didn't think of that one. I've always had my code there but could move it if needed.

@mjbvz
Copy link
Collaborator

mjbvz commented Jan 9, 2020

Duplicate of microsoft/TypeScript#35512

To workaround this, upgrade your workspace to use typescript@next by installing this extension

@mjbvz mjbvz closed this as completed Jan 9, 2020
@mjbvz mjbvz added *duplicate Issue identified as a duplicate of another issue(s) upstream-issue-linked This is an upstream issue that has been reported upstream labels Jan 9, 2020
@alexpaluzzi
Copy link
Author

@mjbvz it turns out I actually don't have these on the d: drive like I thought. They are in the home directory inside WSL2. It also seems like installing the extension didn't help. Apologies, I forgot I moved over to WSL2 a couple months ago.

@mjbvz mjbvz reopened this Jan 9, 2020
@mjbvz
Copy link
Collaborator

mjbvz commented Jan 9, 2020

Are you using the vscode wsl-remote extension? If not, can you please explain how you are opening the folder

@alexpaluzzi
Copy link
Author

alexpaluzzi commented Jan 9, 2020

Yes, using ms-vscode-remote.remote-wsl. I either open VS Code directly from Windows (and the project shows up since it was last opened), or I simply code . from the Ubuntu shell. They both behave the same.

@alexpaluzzi
Copy link
Author

alexpaluzzi commented Jan 9, 2020

I also just started getting this pop-up too:
image

No idea if it's related but it's new all of the sudden. My max user watches are already 524288 (there are not nearly that many files in this project, not including node_modules) but I'm not ruling out some serious WSL2 weirdness here.

@mjbvz mjbvz removed the *duplicate Issue identified as a duplicate of another issue(s) label Jan 10, 2020
@alexpaluzzi
Copy link
Author

Opening new issue to avoid confusion.

@vscodebot vscodebot bot locked and limited conversation to collaborators Mar 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
javascript JavaScript support issues upstream-issue-linked This is an upstream issue that has been reported upstream
Projects
None yet
Development

No branches or pull requests

2 participants