Fork me on GitHub
#dirac
<
2016-08-26
>
denisj01:08:46

@darwin Thanks for the work on :preloads We're coming along in leaps and bounds. I've switched to using :preload for both devtools + dirac. I'm seeing a fair bit of this, should I create an issue ?

Internal Dirac Error: DevTools code has thrown an unhandled exception
Dirac v0.6.4, Chrome/54.0.2816.0, Linux/?, Backend API/54.0.2839.3/8b3f5df/internal (1 registrations), Backend CSS/54.0.2839.3/8b3f5df/internal (1 definitions)
TypeError: Cannot read property 'text' of undefined
    at Function.WebInspector.ConsoleMessage.simpleTextFromException ()
    at Function.WebInspector.ConsoleMessage.fromException ()
    at WebInspector.RuntimeDispatcher.exceptionThrown ()
    at Object.dispatch ()
    at WebInspector.WebSocketConnection.dispatch ()
    at WebInspector.WebSocketConnection._onMessage ()

denisj01:08:14

Also

Internal Dirac Error: an error was logged into the internal DevTools console
Dirac v0.6.4, Chrome/54.0.2816.0, Linux/?, Backend API/54.0.2839.3/8b3f5df/internal (1 registrations), Backend CSS/54.0.2839.3/8b3f5df/internal (1 definitions)
("Request Runtime.runIfWaitingForDebugger failed. {\"code\":-32601,\"message\":\"'Runtime.runIfWaitingForDebugger' wasn't found\"}")

giles02:08:53

@darwin let me know what I can do to help you help me - would you like me to send the entire log output? (I've set the agent and nrepl to log-level trace and verbose true

denisj02:08:44

I may just be slightly behind the recommended Chrome Version 54.0.2816.0 dev (64-bit) vs release notes ~54.0.2840.0

darwin09:08:31

@denisj can you try with chrome unstable? here is how I install it: https://github.com/binaryage/dirac/blob/master/.travis.yml#L19-L23

darwin09:08:39

you have two problems I think, first is due to old Chrome: https://github.com/binaryage/dirac/issues/32 and second one may be a bug in 0.6.4, because your extension tried to use bakend-in API definitions and has only 1, so that is wrong - I suppose it is because under linux there are different new-line feeds and my code didn’t work as expected

denisj13:08:45

@darwin: already using unstable but I will see if I can force upgrade to a later unstable tomorrow and I will report back. Thx

darwin14:08:19

@giles I’m testing it right now with dirac-sample on my machine with version 0.6.4, I have enabled debug logging for lein repl process and also verbose logging for client side[1] and here is my output for localhost communication: https://gist.github.com/darwin/59bd7f6e08c721be22cc3088df633e2c [1] https://github.com/binaryage/dirac-sample/commit/ed60cf3983ef0bf8abca017772fda7c8bd4d9919

darwin14:08:23

unfortunately the messages on client side cannot be expanded because it is compiled under :advanced mode, but at least we have a list of logs that should appear during REPL initialization

darwin14:08:00

please try to do the same and send me a full log from your server-side REPL process and also similar log from client-side (with enabled verbosity)

darwin14:08:29

also wondering why :weasel-url in the log you pasted is "<ws://localhost:8232>”, shouldn’t it be pointing to the right IP address of your client-side machine?

darwin14:08:14

in your case, you have to specify an IP address of your weasel (your client-side machine with the browser), it is “localhost" by default

darwin14:08:01

for quick testing you can set env variable DIRAC-NREPL-WEASEL-HOST, if you wanted to set this on per-project basis, you should be able to specify such overrides via :repl-config in dirac runtime options: https://github.com/binaryage/dirac/blob/master/src/runtime/dirac/runtime/prefs.cljs#L31