Websocket_closed and Detached from the target !!

[bindugh]

Hi My node version is 0.10V

Using the below URL : http://c4milo.github.io/node-webkit-agent/26.0.1410.65/inspector.html?host=localhost:80&page=0

It says websocket_closed. Detached from the target. What does it mean ? The NODE runs there on the console.

For running - node webkit.js

I am using to run the file. Code I am testing with sample program

var agent = require('webkit-devtools-agent'); var http = require('http'); http.createServer(function (req, res) { res.writeHead(200, {'Content-Type': 'text/plain'}); res.end('Hello World\n'); }).listen(80, '0.0.0.0'); console.log('[%s] Server running at http://localhost:80/', process.pid);

[c4milo]

You are using it wrongly, please read carefully the instructions in the README. I'm closing since this is not an issue.

[ddevault]

I'm having a similar problem, and I can't for the life of me figure out what I'm doing wrong. Could you shed some light on the matter? I have tests.js, whose first line is simply var agent = require('webkit-devtools-agent');. I opened http://c4milo.github.io/node-webkit-agent/26.0.1410.65/inspector.html?host=localhost:9999&page=0 in Chrome while it was running and I hit this same issue (after sending SIGUSR2).

[ghost]

maybe node isn't the answer?

sent from an automatic reply.

On Feb 12, 2014, at 10:31 PM, Drew DeVault notifications@github.com<mailto:notifications@github.com> wrote:

I'm having a similar problem, and I can't for the life of me figure out what I'm doing wrong. Could you shed some light on the matter? I have tests.js, whose first line is simply var agent = require('webkit-devtools-agent');. I opened http://c4milo.github.io/node-webkit-agent/26.0.1410.65/inspector.html?host=localhost:9999&page=0 in Chrome while it was running and I hit this same issue.

— Reply to this email directly or view it on GitHubhttps://github.com/c4milo/node-webkit-agent/issues/40#issuecomment-34947613.

[ddevault]

What do you mean?

[D1plo1d]

Same issue, but I got it working in the end. My problem was that I forgot to run kill -USR2 <PID>.

[ddevault]

Glad to hear that you solved it. I had done kill -USR2 <PID>, but I still had the issue.