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

The \"path\" argument must be of type string. Received type undefined #1426

Closed
3 tasks done
bstaletic opened this issue Sep 11, 2019 · 4 comments
Closed
3 tasks done
Labels

Comments

@bstaletic
Copy link

  • I have searched through existing issues
  • I have read through docs
  • I have read FAQ

Info

  • Platform: Arch Linux for me, but a user of my client reported the issue on macOS
  • Vetur version: Commit hash: f2c73f7, but our user reported the problem after running npm install --production with this package.json
  • VS Code version: None, using YouCompleteMe in vim

Problem

As soon as I start the server, I get, similarly to #1402, The \"path\" argument must be of type string. Received type undefined

Reproducible Case

Currently not using any configuration of the server, but the same happened when I tried to use the default configuration from here.

The json exchange from my client's side looks like this:

2019-08-26 23:37:34,879 - DEBUG - TX: Sending message: b'Content-Length: 431\r\n\r\n{"id": "1", "jsonrpc": "2.0", "method": "initialize", "params": {"capabilities": {"textDocument": {"completion": {"completionItemKind": {"valueSet": [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25]}}}}, "initializationOptions": {}, "processId": 23433, "rootPath": "/Users/nbossard/OtherProjects/mahali/front/webapp", "rootUri": "file:///Users/nbossard/OtherProjects/mahali/front/webapp"}}'
2019-08-26 23:37:35,978 - DEBUG - RX: Received message: b'{"jsonrpc":"2.0","id":"1","error":{"code":-32603,"message":"Request initialize failed with message: The \\"path\\" argument must be of type string. Received type undefined"}}'

Our user issue report can be found here: ycm-core/lsp-examples#7

@octref
Copy link
Member

octref commented Sep 30, 2019

Thanks for your detailed report. This should be fixed in latest release of VLS.

@douglasg14b
Copy link

What is the cause of this error? I'm getting it in 2021,

@wokalek
Copy link

wokalek commented Mar 24, 2022

Same

@Namakete
Copy link

Same 2024...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants