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

Debugging Fails Silently While LS is Starting #6361

Closed
tsmaeder opened this issue Oct 10, 2019 · 5 comments
Closed

Debugging Fails Silently While LS is Starting #6361

tsmaeder opened this issue Oct 10, 2019 · 5 comments
Labels
bug bugs found in the application debug issues that related to debug functionality Team: Che-Languages issues regarding the che-languages team vscode issues related to VSCode compatibility

Comments

@tsmaeder
Copy link
Contributor

When I tried to attach the debugger to a Java program that was still being imported by the Java LS, nothing happend, no success and no error message.

Reproduction Steps

I reproduced this with the Che 7.1.0 and the spring http-booster example (https://github.com/snowdrop/spring-boot-http-booster). Howerver, I think any example that takes a long time to import might help

  1. Install the vscode-java extension into theia
  2. clear your local .m2 folder
  3. import the example project
  4. Do not open an java files or do anything to activate the vscode-java extension
  5. Run the example in debug mode
    mvn -Duser.home=${HOME} spring-boot:run -Drun.jvmArguments="-Xdebug
    -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000"
  6. Make a "remote attach" debug config and try to run it
  7. Observe: the java language server is started and taking a long time stuck at "57% import maven projects"
  8. Observe: nothing else happens

The browser log showed the following exception:

Uncaught (in promise) Error: It is not possible to provide debug adapter executable.
    at DebugExtImpl.<anonymous> (/home/theia/node_modules/@theia/plugin-ext/lib/plugin/node/debug/debug.js:501)
    at step (/home/theia/node_modules/@theia/plugin-ext/lib/plugin/node/debug/debug.js:32)
    at Object.next (/home/theia/node_modules/@theia/plugin-ext/lib/plugin/node/debug/debug.js:13)
    at fulfilled (/home/theia/node_modules/@theia/plugin-ext/lib/plugin/node/debug/debug.js:4)
    at process._tickCallback (/dashboard/internal/process/next_tick.js:68)
@tsmaeder tsmaeder added debug issues that related to debug functionality Team: Che-Languages issues regarding the che-languages team labels Oct 10, 2019
@tsmaeder
Copy link
Contributor Author

Once the language server is through importing, debugging works fine.

@akosyakov akosyakov added vscode issues related to VSCode compatibility bug bugs found in the application labels Dec 17, 2019
@akosyakov
Copy link
Member

akosyakov commented Dec 17, 2019

@tsmaeder Do you remember which versions of vscode-java-debug and redhat-java was it?

@akosyakov
Copy link
Member

I can reproduce it with redhat.java@0.47.0 and vscode-java-debug@0.21.0.

But not with latest versions, i.e. redhat.java@0.54.2 and vscode-java-debug@0.23.0.

@akosyakov
Copy link
Member

microsoft/vscode-java-debug#728 (comment) - so it is probably not Theia issue

@akosyakov
Copy link
Member

akosyakov commented Dec 20, 2019

Please use redhat.java@0.49.0 or newer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug bugs found in the application debug issues that related to debug functionality Team: Che-Languages issues regarding the che-languages team vscode issues related to VSCode compatibility
Projects
None yet
Development

No branches or pull requests

2 participants