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

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

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

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

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

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

ok

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

0.8.0

I just updated that in my build.boot

after seeing the 0.8 release

congrats btw!

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=

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

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

do you have internal devtools open?

oh

yeah that was it

debugger port is the connection which devtools uses to automate chrome

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

k, thanks

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

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

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

...and my newborn just woke up, bbl

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

yeah its probably a problem with the asset path

yep

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

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

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

I think that was a one-time fluke

oh i got it, I was missing a leading slash

derp

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

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}

Refreshed the page and now it is working fine.