[martinwestacott]

Hi, I’m using Eclipse and CodeMix and trying to launch the debugger in order to debug a TypeScript unit test. When Eclipse is trying to start the debugger (after I click on the little green chevron in the generated launch.json file) it just hangs. It shows as ‘Launching: Launching delegate…’ but gets stuck at 45% and nothing happens.

Any help gratefully received. Thank you.

[support-swapna]

Martin,

Sorry that you are seeing this issue.

Can you please get in touch with us via Live Chat (Help > CodeMix > Live Chat) to quickly diagnose the problem?
If you cannot initiate a live chat session right now, then please share the .log file located at workspace dir/.metadata/.log (change the extension to .txt and attach it here)

Apologies for inconvenience caused.

–Swapna
Genuitec Support

[martinwestacott]

Hi Swapna,

Thanks for your response. The live chat doesn’t seem to be working but I have attached the .log file as requested.

Also, here is the entry from my launch.json file:

{

// Use IntelliSense to learn about possible attributes.

// Hover to view descriptions of existing attributes.

// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387

“version”: “0.2.0”,

“configurations”: [

{

“name”: “Launch index.spec.unit.ts”,

“type”: “node”,

“console”: “integratedTerminal”,

“request”: “launch”,

“program”: “${workspaceFolder}/test/routes/index.spec.unit.ts”,

“cwd”: “${workspaceFolder}/test/routes”,

“sourceMaps”: true

}

]

}

And tsconfig.json file:

{

“compilerOptions”: {

“module”: “commonjs”,

“moduleResolution”: “node”,

“pretty”: true,

“sourceMap”: true,

“target”: “es6”,

“outDir”: “./dist”,

“baseUrl”: “./src”,

“emitDecoratorMetadata”: true,

“experimentalDecorators”: true,

“strictNullChecks”: true,

“sourceRoot”: “workspace:test-project-web/dist/”

},

“include”: [

“src/**/*”

],

“exclude”: [

“node_modules”

]

}

Thanks for your help,

Martin

Attachments:

You must be logged in to view attached files.

[support-swapna]

Martin,

Thank you for the details and the log file. Sorry that you couldn’t reach us via Live Chat. What exact error did you see when trying to initiate a live chat session?

Can you please check if adding outFiles entry to the launch.json as suggested here helps? : https://stackoverflow.com/questions/46206394/cannot-launch-and-debug-typescript-using-node

–Swapna
Genuitec Support

[martinwestacott]

Hi Swapna,

I tried adding that config but it didn’t help. My launch file looked like this (I tried a couple of configs based on that link):

{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
“version”: “0.2.0”,
“configurations”: [
{
“name”: “Launch index.spec.unit.ts”,
“type”: “node”,
“console”: “integratedTerminal”,
“request”: “launch”,
“program”: “${workspaceFolder}/test/routes/index.spec.unit.ts”,
“cwd”: “${workspaceFolder}/test/routes”,
“sourceMaps”: true
},

{
“type”: “node”,
“request”: “launch”,
“name”: “Launch Program”,
“program”: “${file}”,
“outFiles”: [
“${workspaceFolder}/**/*.js”
]
}
]
}

The error when initiating live chat was: Unable to Create Chat – Could not create thread: Launching Debug Is Stuck

And the stack trace in the Eclipse log was:

!ENTRY com.genuitec.eclipse.code.livechat.core 4 0 2020-01-20 09:37:27.918
!MESSAGE Unexpected failure connecting to Live Preview service: [{ext={codemix.livechat.auth={token=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJodHRwczpcL1wvd3d3LmdlbnVpdGVjLmNvbSIsImlhdCI6MTU3ODkwNjYwMSwibmJmIjoxNTc4OTA2NjAxLCJleHAiOjE1OTQ0NTg2MDEsImRhdGEiOnsidXNlciI6eyJpZCI6IjgyNDAwMSIsImVtcGxveWVlIjpmYWxzZX19LCJzeXN0ZW1VaWQiOiI0ZjcxM2Q1ODU2NWFiMTk5NGY5NTc2OWNjYzRmODViYiIsInVzZXJuYW1lIjoiTWFydGluV2VzdGFjb3R0In0.9gqtv-Fk6bxXvwvIYs1Uoa_knVfSN2QOHc1SIt_LuEE}}, channel=/meta/handshake, id=1, supportedConnectionTypes=[long-polling], version=1.0}]
!STACK 0
org.eclipse.jetty.io.EofException
at org.eclipse.jetty.io.ChannelEndPoint.flush(ChannelEndPoint.java:286)
at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.flush(SslConnection.java:882)
at org.eclipse.jetty.io.WriteFlusher.flush(WriteFlusher.java:393)
at org.eclipse.jetty.io.WriteFlusher.write(WriteFlusher.java:277)
at org.eclipse.jetty.io.AbstractEndPoint.write(AbstractEndPoint.java:380)
at org.eclipse.jetty.client.http.HttpSenderOverHTTP$HeadersCallback.process(HttpSenderOverHTTP.java:268)
at org.eclipse.jetty.util.IteratingCallback.processing(IteratingCallback.java:241)
at org.eclipse.jetty.util.IteratingCallback.iterate(IteratingCallback.java:224)
at org.eclipse.jetty.client.http.HttpSenderOverHTTP.sendHeaders(HttpSenderOverHTTP.java:62)
at org.eclipse.jetty.client.HttpSender.send(HttpSender.java:212)
at org.eclipse.jetty.client.http.HttpChannelOverHTTP.send(HttpChannelOverHTTP.java:85)
at org.eclipse.jetty.client.HttpChannel.send(HttpChannel.java:128)
at org.eclipse.jetty.client.HttpConnection.send(HttpConnection.java:201)
at org.eclipse.jetty.client.http.HttpConnectionOverHTTP$Delegate.send(HttpConnectionOverHTTP.java:253)
at org.eclipse.jetty.client.http.HttpConnectionOverHTTP.send(HttpConnectionOverHTTP.java:122)
at org.eclipse.jetty.client.http.HttpDestinationOverHTTP.send(HttpDestinationOverHTTP.java:38)
at org.eclipse.jetty.client.HttpDestination.process(HttpDestination.java:347)
at org.eclipse.jetty.client.HttpDestination.process(HttpDestination.java:305)
at org.eclipse.jetty.client.HttpDestination.send(HttpDestination.java:295)
at org.eclipse.jetty.client.HttpDestination.succeeded(HttpDestination.java:229)
at org.eclipse.jetty.client.AbstractConnectionPool.proceed(AbstractConnectionPool.java:154)
at org.eclipse.jetty.client.AbstractConnectionPool$1.succeeded(AbstractConnectionPool.java:132)
at org.eclipse.jetty.client.AbstractConnectionPool$1.succeeded(AbstractConnectionPool.java:124)
at org.eclipse.jetty.util.Promise$Wrapper.succeeded(Promise.java:130)
at org.eclipse.jetty.client.http.HttpConnectionOverHTTP.onOpen(HttpConnectionOverHTTP.java:130)
at org.eclipse.jetty.io.ssl.SslConnection.onOpen(SslConnection.java:267)
at org.eclipse.jetty.io.AbstractEndPoint.upgrade(AbstractEndPoint.java:440)
at org.eclipse.jetty.client.HttpProxy$CreateTunnelPromise.tunnelSucceeded(HttpProxy.java:212)
at org.eclipse.jetty.client.HttpProxy$CreateTunnelPromise.lambda$tunnel$0(HttpProxy.java:182)
at org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:202)
at org.eclipse.jetty.client.ResponseNotifier.notifyComplete(ResponseNotifier.java:194)
at org.eclipse.jetty.client.HttpReceiver.terminateResponse(HttpReceiver.java:470)
at org.eclipse.jetty.client.HttpReceiver.responseSuccess(HttpReceiver.java:416)
at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.messageComplete(HttpReceiverOverHTTP.java:316)
at org.eclipse.jetty.http.HttpParser.handleContentMessage(HttpParser.java:599)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:1513)
at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.parse(HttpReceiverOverHTTP.java:172)
at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.process(HttpReceiverOverHTTP.java:135)
at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.receive(HttpReceiverOverHTTP.java:73)
at org.eclipse.jetty.client.http.HttpChannelOverHTTP.receive(HttpChannelOverHTTP.java:133)
at org.eclipse.jetty.client.http.HttpConnectionOverHTTP.onFillable(HttpConnectionOverHTTP.java:155)
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:765)
at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.nio.channels.ClosedChannelException
at sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:270)
at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:461)
at org.eclipse.jetty.io.ChannelEndPoint.flush(ChannelEndPoint.java:264)
… 46 more

!ENTRY com.genuitec.eclipse.code.livechat.core 4 0 2020-01-20 09:37:28.041

What else can I try please?

Thanks,

Martin

[support-swapna]

Martin,

Sorry that you are still seeing the issue.
Can you please check if editing the program value as suggested by the latest comment on this thread helps?
https://stackoverflow.com/questions/42747618/unable-to-debug-typescript-in-vscode

–Swapna
Genuitec Support

[martinwestacott]

Swapna,

Thanks for your response. I’ve just managed to get it working, although setting ‘outFiles’ in the end wasn’t needed. Posting my launch.json file below, with the working config.

Thanks and regards,

Martin

{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
“version”: “0.2.0”,
“configurations”: [
{
“type”: “node”,
“request”: “launch”,
“name”: “Debug Jest Tests”,
“cwd”: “${workspaceFolder}”,
“args”: [
“–inspect-brk”,
“${workspaceRoot}/node_modules/.bin/jest”,
“–runInBand”,
“–config”,
“${workspaceRoot}/jest.config.js”
],
“windows”: {
“args”: [
“–inspect-brk”,
“${workspaceRoot}/node_modules/jest/bin/jest.js”,
“–runInBand”,
“–config”,
“${workspaceRoot}/jest.config.json”
],
},
“console”: “integratedTerminal”,
“internalConsoleOptions”: “neverOpen”,
“skipFiles”: [
“<node_internals>/**”
]
}
]
}

[Author]

Posts