WS Error when trying to connect to nodejs process about indium HOT 20 CLOSED

I found what's wrong: nodejs 7.x.x uses a different version of the remote debugger protocol.
I'll push a fix soon, thanks for reporting the issue!

from indium.

@CSRaghunandan no, it shouldn't be, I'll check what's wrong!

from indium.

from indium.

Chrome version: Version 54.0.2840.98 (64-bit)
Edit: Sorry for being a noob, but do I need to install chromium to get this to work?

from indium.

No, but it looks like you're trying to connect to a nodejs process.
How did you try to connect to chrome?

Can you try starting chrome like this:

chrome --remote-debugging-port=9222

On macOS, it should be something like:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222
Make sure to start a new chrome process (eg close any chrome window before doing this).

Then navigate to the website you want to connect to, and then from Emacs M-x jade-connect-to-chrome.

from indium.

That indeed works. I've an alias for the same. I can connect to a chrome tab no problem.
But, I'm unable to connect to a nodejs process

from indium.

from indium.

nodejs v.7.2.1
Umm is it because I'm emacs master build that the connection to nodejs process is refusing?

from indium.

Thank for taking a look into this 👍

from indium.

I am experiencing this issue with node 6.9.1, 6.9.5, and 7.5.0. So I am not sure it is version-related. The error I get with 6.9.5 is as follows:

Debugger entered--Lisp error: (websocket-invalid-header . "Invalid HTTP status line")
  signal(websocket-invalid-header "Invalid HTTP status line")
  websocket-outer-filter([cl-struct-websocket closed nil (closure ((on-open) (websocket-url . "ws://127.0.0.1:9229/node") (url . "ws://127.0.0.1:9229/node") t) (ws) (if on-open (progn (funcall on-open))) (jade-webkit--handle-ws-open ws url)) jade-webkit--handle-ws-message jade-webkit--handle-ws-closed jade-webkit--handle-ws-error nil nil nil "ws://127.0.0.1:9229/node" nil nil #<process websocket to ws://127.0.0.1:9229/node> nil "zPlBbGHjkz4B4QORFIAc/OlCwdU=" nil] "HTTP/1.0 400 Bad Request
\nContent-Type: text/html; charset=UTF-8
\n
\nWebSockets request was expected
\n")
  #[(process output) "\303�\304\"�\305	\n\")\207" [process websocket output process-get :websocket websocket-outer-filter] 3](#<process websocket to ws://127.0.0.1:9229/node> "HTTP/1.0 400 Bad Request
\nContent-Type: text/html; charset=UTF-8
\n
\nWebSockets request was expected
\n")
  read-event(nil t 2)
  sit-for(2)
  execute-extended-command(nil "jade-connect-to-nodejs" "jade-connect-to-no")
  funcall-interactively(execute-extended-command nil "jade-connect-to-nodejs" "jade-connect-to-no")
  call-interactively(execute-extended-command nil nil)
  command-execute(execute-extended-command)

from indium.

from indium.

The issue should be fixed with commit cc68a20!

from indium.

I have the same error with chromium Version 56.0.2924.87 (64-bit):

Contacting host: 127.0.0.1:9222
WS Error! on-open (wrong-type-argument stringp nil)
WS Error! on-message (wrong-type-argument integer-or-marker-p nil)

from indium.

@s-kostyaev can you give me the version of jade you're using, as well as Emacs?

Also, is Chrome running with the --remote-debugging-port flag set?

from indium.

@NicolasPetton jade 20170224.922, emacs 25.1, chromium has running with --remote-debugging-port flag.

from indium.

@s-kostyaev I cannot reproduce the issue, but I'll investigate more.

What OS are you using?
Can you open another issue as this one was related to nodejs?

from indium.

I use GNU/Linux. I will open another issue a little bit later.

from indium.

@s-kostyaev I need a bit of help to understand what's going on 😄

• When you try to connect to a tab, do you get the list of Chromium tabs in the minibuffer?
• Can you access http://127.0.0.1:9222/ from Chrome?

from indium.

Sorry for wasting your time. I'll try again and all works fine.

from indium.

@s-kostyaev I'm glad it works for you now!

from indium.