Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Debug>Start with no debug configurations gives no feedback to the user

See original GitHub issue

Describe the bug

We have several devfiles (https://github.com/eclipse/che-devfile-registry/tree/master/devfiles/angular, https://github.com/eclipse/che-devfile-registry/tree/master/devfiles/dotnet) where there is no option to debug the project. When selecting Debug>Start debuggin (or F5) shortcut, nothing happens. As well as Debug>Start without debugging (Ctrl+F5).

Che version

nightly

Steps to reproduce

create workspace from devfile https://github.com/eclipse/che-devfile-registry/tree/master/devfiles/angular
run yarn install task
open main.ts file
click Debug>Start Debugging
nothing happens

Expected behavior

current file should start and debug should work

Runtime

minikube (include output of minikube version and kubectl version)

Screenshots

debug

Installation method

chectl

Environment

my computer
- Linux

Additional context

Issue Analytics

State:
Created 4 years ago
Comments:9 (9 by maintainers)

Top GitHub Comments

2reactions

vzhukovscommented, Jan 15, 2020

Following PR merged in theia upstream: https://github.com/eclipse-theia/theia/pull/6870

1reaction

sparkoocommented, Jul 30, 2019

@amisevsk Thank you for investigating and renaming the issue. Makes much more sense now. I think that create + launch + notify that debug config was generated is the way to go. We should do the best to prepare workspace for debugging, but we can’t do magic so it should be clear that the configuration was generated and user is supposed to customize it.