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

Not working #5

Open
kalitine opened this issue Mar 22, 2019 · 5 comments
Open

Not working #5

kalitine opened this issue Mar 22, 2019 · 5 comments
Labels
invalid This doesn't seem right

Comments

@kalitine
Copy link

My launch.json file is as follow:

{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "node",
      "request": "launch",
      "name": "Jasmine Current File",
      "program": "${workspaceFolder}/node_modules/.bin/jasmine-ts",
      "args": [
        "--config=${workspaceFolder}/jasmine.json",
        "--project=${workspaceFolder}/tsconfig.test.json"
      ],
      "console": "integratedTerminal",
      "internalConsoleOptions": "neverOpen",
      "useWSL": true,
      "localRoot": "${workspaceFolder}",
      "remoteRoot": "${command:extension.vscode-wsl-workspaceFolder}"
    }
  ]
}

But I'm getting the following output:

cd c:\Users\phili\Documents.{90F8C996-7C70-4331-9D70-FB357D559FD5}\workspace\server-
translator && C:\Windows\System32\bash.exe -ic "node --inspect-brk=28807 
node_modules/.bin/jasmine-ts --config=C:\Users\phili\Documents.{90F8C996-7C70-4331-9D70-
FB357D559FD5}\workspace\server-translator/jasmine.json --project=C:\Users\phili\Documents.
{90F8C996-7C70-4331-9D70-FB357D559FD5}\workspace\server-translator/tsconfig.test.json"-
bash: cd: c:UsersphiliDocuments.{90F8C996-7C70-4331-9D70-FB357D559FD5}workspaceserver-
translator: No such file or directory

Look at config option for example from the output above:

--config=C:\Users\phili\Documents.{90F8C996-7C70-4331-9D70-
FB357D559FD5}\workspace\server-translator/jasmine.json

Is there is something I've misconfigured?

@lfurzewaddock
Copy link
Owner

Your output complains about the config and project args. If you want to pass the MS Windows path try using backslashes, i.e.

{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "node",
      "request": "launch",
      "name": "Jasmine Current File",
      "program": "${workspaceFolder}/node_modules/.bin/jasmine-ts",
      "args": [
        "--config=${workspaceFolder}\jasmine.json",
        "--project=${workspaceFolder}\tsconfig.test.json"
      ],
      "console": "integratedTerminal",
      "internalConsoleOptions": "neverOpen",
      "useWSL": true,
      "localRoot": "${workspaceFolder}",
      "remoteRoot": "${command:extension.vscode-wsl-workspaceFolder}"
    }
  ]
}

Otherwise you can pass the WSL paths with;

{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "node",
      "request": "launch",
      "name": "Jasmine Current File",
      "program": "${workspaceFolder}/node_modules/.bin/jasmine-ts",
      "args": [
        "--config=${command:extension.vscode-wsl-workspaceFolder}/jasmine.json",
        "--project=${command:extension.vscode-wsl-workspaceFolder}/tsconfig.test.json"
      ],
      "console": "integratedTerminal",
      "internalConsoleOptions": "neverOpen",
      "useWSL": true,
      "localRoot": "${workspaceFolder}",
      "remoteRoot": "${command:extension.vscode-wsl-workspaceFolder}"
    }
  ]
}

@kalitine
Copy link
Author

kalitine commented Mar 25, 2019

Ok, I made your suggestion:

"args": [
  "--config=${command:extension.vscode-wsl-workspaceFolder}/jasmine.json",
  "--project=${command:extension.vscode-wsl-workspaceFolder}/tsconfig.test.json"
]

But there is still this last line in my output that is problematic:

bash: cd: c:UsersphiliDocuments.{90F8C996-7C70-4331-9D70-FB357D559FD5}workspaceserver-
translator: No such file or directory

It looks like a right path, but slashes are missing. Have you any idea why this?

@lfurzewaddock
Copy link
Owner

The output missing slashes appears to be the same as in your first comment.

Looks like the issue occurs before the args are being processed, otherwise the output would have been in WSL format, although perhaps with slashes missing too.

@kalitine
Copy link
Author

I haven't found a solution for this yet. I pause this problem for now and will post here once make it work. Anyway it looks like not a vscode-wsl-workspacefolder issue. Thanks for your responses.

@lfurzewaddock lfurzewaddock added the invalid This doesn't seem right label Mar 27, 2019
@lfurzewaddock
Copy link
Owner

Thanks for the update @kalitine.

Yes, please do post the fix to your issue when you discover it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right
Projects
None yet
Development

No branches or pull requests

2 participants