dirac

Dirac v1.7.2 is out: https://github.com/binaryage/dirac/releases/tag/v1.7.2
mattly 2016-10-30T23:19:19.002255Z

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

mattly 2016-10-30T23:19:30.002256Z

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

mattly 2016-10-30T23:19:51.002257Z

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

mattly 2016-10-30T23:20:34.002259Z

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

mattly 2016-10-30T23:20:44.002260Z

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

2016-10-30T23:21:39.002261Z

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

mattly 2016-10-30T23:21:50.002263Z

ok

2016-10-30T23:22:00.002264Z

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

2016-10-30T23:22:02.002265Z

0.8.0

mattly 2016-10-30T23:22:14.002266Z

I just updated that in my build.boot

mattly 2016-10-30T23:22:24.002267Z

after seeing the 0.8 release

mattly 2016-10-30T23:22:25.002268Z

congrats btw!

😁 1
mattly 2016-10-30T23:22:50.002269Z

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=<http://localhost:9222>, tab-url=<http://localhost:3000/>

2016-10-30T23:23:14.002270Z

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

mattly 2016-10-30T23:23:16.002271Z

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

2016-10-30T23:23:21.002272Z

do you have internal devtools open?

mattly 2016-10-30T23:23:35.002273Z

oh

mattly 2016-10-30T23:23:40.002274Z

yeah that was it

2016-10-30T23:23:41.002275Z

debugger port is the connection which devtools uses to automate chrome

2016-10-30T23:26:30.002276Z

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

mattly 2016-10-30T23:27:11.002277Z

k, thanks

mattly 2016-10-30T23:38:33.002278Z

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

mattly 2016-10-30T23:39:02.002280Z

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

mattly 2016-10-30T23:39:25.002281Z

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

mattly 2016-10-30T23:39:44.002283Z

...and my newborn just woke up, bbl

2016-10-30T23:40:33.002284Z

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

mattly 2016-10-30T23:44:18.002285Z

yeah its probably a problem with the asset path

2016-10-30T23:45:01.002287Z

yep

2016-10-30T23:46:12.002288Z

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

2016-10-30T23:46:21.002289Z

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

mattly 2016-10-30T23:46:24.002290Z

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

mattly 2016-10-30T23:46:35.002291Z

I think that was a one-time fluke

mattly 2016-10-30T23:47:39.002292Z

oh i got it, I was missing a leading slash

mattly 2016-10-30T23:48:00.002293Z

derp

mattly 2016-10-30T23:48:14.002294Z

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

superstructor 2016-10-30T23:49:03.002295Z

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}

superstructor 2016-10-30T23:49:42.002296Z

Refreshed the page and now it is working fine.