You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have java tests running via dap.run() (I'm using similar method to nvim-jdtls). I have two run & debug modes. In run mode, I just pass in noDebug = true property to launch configuration and tests are running without stopping at debug points.
However, when running main methods, I passed in noDebug = true. When dap.continue() it seems the screen flickers but the main method is never ran (Main method create a file in the current working directory. So if the method ran successfully, it should create a file). When noDebug = false, it stops at debug points and running successfully (creates a new file in the cwd too). Am I missing something?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have java tests running via
dap.run()
(I'm using similar method to nvim-jdtls). I have tworun
&debug
modes. In run mode, I just pass innoDebug = true
property to launch configuration and tests are running without stopping at debug points.However, when running main methods, I passed in
noDebug = true
. Whendap.continue()
it seems the screen flickers but the main method is never ran (Main method create a file in the current working directory. So if the method ran successfully, it should create a file). WhennoDebug = false
, it stops at debug points and running successfully (creates a new file in thecwd
too). Am I missing something?Beta Was this translation helpful? Give feedback.
All reactions