Fork me on GitHub
#dirac
<
2016-10-30
>
mattly23:10:19

so I'm trying to get Dirac working in a project

mattly23:10:30

I'm using boot, and went with the powerlaces plugin

mattly23:10:51

along with watch, cljs, reload and serve, this is my output:

mattly23:10:34

I've started Chrome Canary with the --remote-debugging-port=9222 option per the wiki page

mattly23:10:44

but if I'm reading all this right, don't I want 8231 instead?

darwin23:10:39

that is correct, remote debuggin port is something different than port where dirac agent is listening, long read: https://github.com/binaryage/dirac/blob/master/docs/about-repls.md

darwin23:10:00

but Dirac Agent 0.7.1 is pretty old, you should use the latest

mattly23:10:14

I just updated that in my build.boot

mattly23:10:24

after seeing the 0.8 release

mattly23:10:25

congrats btw!

mattly23:10:50

the error I'm getting now when I attempt to start dirac is Cannot attach Dirac DevTools. Likely cause: another instance of DevTools is already attached. target-url=, tab-url=

darwin23:10:14

yes, only one devtools can be connected to your page at time

mattly23:10:16

I don't have any other browsers attached to my url

darwin23:10:21

do you have internal devtools open?

mattly23:10:40

yeah that was it

darwin23:10:41

debugger port is the connection which devtools uses to automate chrome

darwin23:10:30

have to go now, will be back in 15-20mins

mattly23:10:33

now I'm basically getting repl connect timeouts, here's the agent output:

mattly23:10:02

hm, closed and re-opened dirac and it works now!

mattly23:10:25

I got a ton of error output warning about f.e.

mattly23:10:44

...and my newborn just woke up, bbl

darwin23:10:33

"main.out/devtools/main.out/devtools” looks really suspicious

mattly23:10:18

yeah its probably a problem with the asset path

darwin23:10:12

not sure about that timeout you experienced, let me know if it is reproducible

darwin23:10:21

we could enable more verbose logging in dirac agent and nrepl middleware

mattly23:10:24

if I take out the asset-path option from compiler-options though, the js itself can't be served properly

mattly23:10:35

I think that was a one-time fluke

mattly23:10:39

oh i got it, I was missing a leading slash

mattly23:10:14

I've been re-using the same build script since I started using boot eight months ago

superstructor23:10:03

I’ve also seen this first time running after Dirac 0.8.0 upgrade:

12:47:53.599 [async-dispatch-2] ERROR dirac.lib.nrepl-tunnel-server - [NREPLTunnelServer#1 of [NREPLTunnel#1]] Received a bootstrap timeout from client [WebSocketServerClient#1] :
 {:op :bootstrap-timeout}

superstructor23:10:42

Refreshed the page and now it is working fine.