Junit project: Cannot determine executable for debug adapter '{0}'  #167

Activity

1. Andy Xu(devdiv) (andxu)

   assigned

   Xuan Zhou (ansyral)

   on Nov 17, 2017
2. Andy Xu(devdiv) (andxu)

   added

   bug

   on Nov 17, 2017
3. supersonicclay commented on Nov 17, 2017

   

   Clay Anderson (supersonicclay)

   on Nov 17, 2017

   More actions

   I have the same after updating to VSCode 1.18.1. I downgraded to VSCode 1.18.0, but am still experiencing the issue. My environment:

   macOS Sierra: 10.12.6
   VSCode: 1.18.1 and 1.18.0 (did not see the issue when on 1.18.0 prior to upgrade)

   VSCode extensions:
   redhat.java: 0.14.0
   vscjava.vscode-java-debug: 0.3.1

   java -version

   java version "1.8.0_144"
   Java(TM) SE Runtime Environment (build 1.8.0_144-b01)
   Java HotSpot(TM) 64-Bit Server VM (build 25.144-b01, mixed mode)
   
4. supersonicclay commented on Nov 17, 2017

   

   Clay Anderson (supersonicclay)

   on Nov 17, 2017

   More actions

   No idea why, but this fixed it for me.

   • Exit VS Code
   • rm -rf ~/Library/Application\ Support/Code/User/workspaceStorage/
   • Re-open VS Code

   This is working with VS Code 1.18.1.

   👍React with 👍4Reacted by William Lang, Christopher Kümmel, Candace Wrather and rerosum

   👎React with 👎5Reacted by Daniel White, Nobody, Santosh Giri, Raj Kundu and rerosum

   😕React with 😕5Reacted by Titus Rwantare, Lourenço Viana, Michel Kaporin, gbowd and Fred Helmesjö
5. testforstephen commented on Nov 20, 2017

   

   Jinbo Wang (testforstephen)

   on Nov 20, 2017

   Last edited by testforstephen

   Contributor

   More actions

   Reproduced this bug on my windows 10 machine.

   I enabled the language server in debug mode, and found Build workspace command would get problem marker as follows:

   [Marker [on: /10.junit, id: 3, type: org.eclipse.buildship.core.gradleprojectconfigurationmarker, attributes: [message: Missing Gradle project configuration folder: .settings, severity: 2], created: 11/20/17 10:50 AM]]
   

   The java debugger just shows Build failed, please fix build error first., but doesn't show the problems on VSCode PROBLEMS view.

   Xuan Zhou (@ansyral) Refer to the eclipse behavior, if there are problems in workspace, should pop up a message box to allow user to Proceed or Cancel the debugging operation instead of Just failed. Besides, should show the error information in VSCode PROBLEMS view.
6. GrubbyHalo commented on Nov 20, 2017

   

   Garfield Watkins (GrubbyHalo)

   on Nov 20, 2017

   More actions

   Jinbo Wang (@testforstephen) How do you enable the language server in debug mode ? I have the same error on my linux box. When i open up my project using eclipse i don't get any errors
7. testforstephen commented on Nov 20, 2017

   

   Jinbo Wang (testforstephen)

   on Nov 20, 2017

   Contributor

   More actions

   Garfield Watkins (@GrubbyHalo) There are two ways to launch language server in debug mode.

   1. java language server extension will detect if the extension is in development mode, if so, it will start with debug port localhost:1044 enabled.

   so if i run java debugger in extension development mode, the language server will be in debug mode too.
   

   You can download language server and java debug server source code from github, and attach to 1044 port to debug the extension code.

   2. The second way is a little hack.
      Find javaServerStarter.js under the directory C:\Users\jinbwan\.vscode\extensions\redhat.java-0.14.0\out\src\javaServerStarter.js, and modify const DEBUG = (typeof v8debug === 'object') || startedInDebugMode(); to const DEBUG = true;. Restart VSCode.

   👍React with 👍1Reacted by Garfield Watkins
8. GrubbyHalo commented on Nov 21, 2017

   

   Garfield Watkins (GrubbyHalo)

   on Nov 21, 2017

   More actions

   Well this is bizarre. I fired up the extension in development mode and got the same error i got above while trying to debug it. No other meaningful messages. I then closed the extension dev host and on a whim removed the eclipse generated folders in my workspace (I used eclipse for this project before trying vscode) and tried debugging the project again and it worked! no error messages. I thought that maybe the eclipse generated folders might be responsible in some way for the errors so to test the theory i put them back again, but still got no errors! So now i am not sure what fixed it.
9. testforstephen commented on Nov 22, 2017

   

   Jinbo Wang (testforstephen)

   on Nov 22, 2017

   Contributor

   More actions

   Garfield Watkins (@GrubbyHalo) Refer to #170, Jérôme Saliba (@wokhan) provides a workaround, that should work.

   👍React with 👍1Reacted by Garfield Watkins
10. wokhan commented on Nov 22, 2017

    

    Jérôme Saliba (wokhan)

    on Nov 22, 2017

    More actions

    Jinbo Wang (@testforstephen) In fact the workaround I reintroduced was already there in the previous version of the extension (0.3.0), and has been "removed" (i.e. uncommented) by Andy Xu(devdiv) (@andxu) for 0.3.1 when RedHat Java support extension was upgraded to 0.14, so I guess there was a good reason for this.
11. yaohaizh commented on Nov 29, 2017

    

    Yaohai Zheng (yaohaizh)

    on Nov 29, 2017

    Contributor

    More actions

    Fixed on PR: #176
12. Yaohai Zheng (yaohaizh)

    closed this as completedon Nov 29, 2017
13. danvsantos commented on Feb 6, 2018

    

    Daniel Vieira (danvsantos)

    on Feb 6, 2018

    Last edited by danvsantos

    More actions

    On windows 10 I solved it like this:

    • Remove Java Plugins from the folder ---> C:\Users\{Your user}\.vscode ;
    • And install plugins again

    My version is 1.19.3