Debugger no working anymore (java.nio.file.InvalidPathException)

Hello,

from one day to another the Webstorm debugger is not working anymore.

No breakpoints are hit an dthe console output log in is only singleline (before it was multiline)

My solution ist a Angular2 CLI + Typescript.

 

I looked into the idea.log and saw some errros from the debugger:

The paths are broken and the debugger does not find the source file anymore. Why is the path so broken? I did not change anything in my configuration. Perhaps this comes from an npm update? Reinstalling and reconfigurating the debugger does not help (I tried already).

 

Can you help me with this issue?

----------------------------------------------------------------------------------------------------

2017-07-10 11:58:53,137 [1832878] ERROR - til.concurrency.QueueProcessor - Illegal char <:> at index 40: D:/develop/dialogcrm6/trunk/Web\/webpack:/D:/develop/dialogcrm6/trunk/Web/src/app/services/global/offline.service.ts
java.nio.file.InvalidPathException: Illegal char <:> at index 40: D:/develop/dialogcrm6/trunk/Web\/webpack:/D:/develop/dialogcrm6/trunk/Web/src/app/services/global/offline.service.ts
at sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)
at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)
at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)
at sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)
at sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)
at java.nio.file.Paths.get(Paths.java:84)
at org.jetbrains.builtInWebServer.WebServerPathToFileManagerKt$RELATIVE_PATH_RESOLVER$1.resolve(WebServerPathToFileManager.kt:167)
at org.jetbrains.builtInWebServer.FileResolver$DefaultImpls.resolve$default(WebServerPathToFileManager.kt:156)
at org.jetbrains.builtInWebServer.DefaultWebServerRootsProviderKt.a(DefaultWebServerRootsProvider.kt:252)
at org.jetbrains.builtInWebServer.DefaultWebServerRootsProviderKt.access$findByRelativePath(DefaultWebServerRootsProvider.kt:1)
at org.jetbrains.builtInWebServer.DefaultWebServerRootsProvider.resolve(DefaultWebServerRootsProvider.kt:86)
at org.jetbrains.builtInWebServer.WebServerPathToFileManager.doFindByRelativePath$built_in_server(WebServerPathToFileManager.kt:145)
at org.jetbrains.builtInWebServer.WebServerPathToFileManager.getPathInfo(WebServerPathToFileManager.kt:118)
at org.jetbrains.builtInWebServer.WebServerPathToFileManager.findVirtualFile(WebServerPathToFileManager.kt:108)
at org.jetbrains.builtInWebServer.WebServerPathToFileManager.findVirtualFile$default(WebServerPathToFileManager.kt:107)
at com.intellij.javascript.debugger.DebuggableFileFinderImpl.findFileByAuthority(DebuggableFileFinderImpl.kt:96)
at com.intellij.javascript.debugger.DebuggableFileFinderImpl.findFile(DebuggableFileFinderImpl.kt:91)
at com.intellij.javascript.debugger.RemoteDebuggingFileFinder.findFile(RemoteDebuggingFileFinder.kt:87)
at com.intellij.javascript.debugger.JavaScriptDebugProcess.findFile(JavaScriptDebugProcess.kt:246)
at com.intellij.javascript.debugger.JavaScriptDebugProcess.findFile$default(JavaScriptDebugProcess.kt:235)
at com.intellij.javascript.debugger.JavaScriptDebugProcess.getSourceInfo(JavaScriptDebugProcess.kt:511)
at com.intellij.javascript.debugger.JavaScriptDebugProcess.getSourceInfo(JavaScriptDebugProcess.kt:1013)
at com.intellij.javascript.debugger.ConsolePrinter.doAddFileLink(ConsolePrinter.kt:180)
at com.intellij.javascript.debugger.ConsolePrinter.addFileLink(ConsolePrinter.kt:174)
at com.jetbrains.debugger.wip.WipConsoleAPICalled.print(WipConsoleAPICalled.kt:52)
at com.intellij.javascript.debugger.ConsolePrinter.addMessage(ConsolePrinter.kt:77)
at com.jetbrains.debugger.wip.ChromeDebugProcess$ConsoleMessageManager.doAdd(ChromeDebugProcess.kt:165)
at com.jetbrains.debugger.wip.ChromeDebugProcess$ConsoleMessageManager.add(ChromeDebugProcess.kt:95)
at com.jetbrains.debugger.wip.ChromeDebugProcess$1$$special$$inlined$forEach$lambda$1.invoke(ChromeDebugProcess.kt:48)
at com.jetbrains.debugger.wip.ChromeDebugProcess$1$$special$$inlined$forEach$lambda$1.invoke(ChromeDebugProcess.kt:33)
at org.jetbrains.jsonProtocol.EventMap.handleEvent(EventMap.kt:49)
at org.jetbrains.wip.WipCommandProcessor.eventEmitted(WipCommandProcessor.kt:33)
at com.jetbrains.debugger.wip.extension.DebuggerService$invoke$2.invoke(DebuggerService.kt:116)
at com.jetbrains.debugger.wip.extension.DebuggerService$invoke$2.invoke(DebuggerService.kt:65)
at com.jetbrains.debugger.wip.extension.JbWipVm$queueProcessor$1.consume(JbWipVm.kt:16)
at com.jetbrains.debugger.wip.extension.JbWipVm$queueProcessor$1.consume(JbWipVm.kt:13)
at com.intellij.util.concurrency.QueueProcessor.lambda$null$0(QueueProcessor.java:106)
at com.intellij.util.concurrency.QueueProcessor.runSafely(QueueProcessor.java:223)
at com.intellij.util.concurrency.QueueProcessor.lambda$wrappingProcessor$1(QueueProcessor.java:106)
at com.intellij.util.concurrency.QueueProcessor.lambda$null$2(QueueProcessor.java:203)
at com.intellij.util.concurrency.QueueProcessor.runSafely(QueueProcessor.java:223)
at com.intellij.util.concurrency.QueueProcessor.lambda$startProcessing$3(QueueProcessor.java:203)
at com.intellij.openapi.application.impl.ApplicationImpl$2.run(ApplicationImpl.java:334)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

 

Regards,

Thomas

 

 

 

 

 

 

 

3 comments
Comment actions Permalink

We already found the described problem here:

 

https://intellij-support.jetbrains.com/hc/en-us/community/posts/115000405184-Breakpoints-aren-t-hit-in-Angular-project-

 

I applied the solution and the debugger works now, but the solution complies very weird.

Some classes are not found anymore (I need to comment them temporarliy), the and compile time increased up to 50% percent.

What happend with this settings?

0
Comment actions Permalink

We solved the issue by downgrading to angular-cli 1.1.0

0
Comment actions Permalink

https://youtrack.jetbrains.com/issue/WEB-27381 is fixed in 2017.2 - now debugger accepts the paths generated by angular-cli

0

Please sign in to leave a comment.