Clojurians
#dirac
<
2016-03-16
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

frank19:03:55

is anyone else having trouble getting dirac to work with canary?

frank19:03:14

it worked before :sob:

frank19:03:14

it's giving me the message that devtools isn't set up

smw19:03:32

are you running the devtools init stuff in your clojurescript code?

smw19:03:38

I was using it yesterday

darwin19:03:02

@frank: I could try cut a new release with latest devtools merged in

frank19:03:32

let me try some more debugging first

darwin19:03:10

also please check how many js contexts do you have in your page (Console panel -> select box contains “top” and maybe some others)

darwin19:03:43

right now dirac takes the first one in the list as current and executes javascript in it

darwin19:03:04

it happened to me that a chrome extension injected content script into a page and appeared as the first item there

darwin19:03:29

and that borked whole thing because now dirac was targeting that content script js context instead of page’s js context

darwin19:03:42

I’m now trying to figure a way how to implement some heuristics there, maybe selecting a js context which contains cljs-devtools

frank19:03:10

@darwin: I see lots of tops

darwin19:03:41

that will be the problem, if the currently selected is not your real page context, dirac won’t work

darwin19:03:02

because it talks to something else

darwin19:03:37

what do you see in Sources panel, when you switch to “Content Scripts” ?

frank19:03:59

my console output shows "Installing cljs-devtools" so I'm pretty sure that part is fine

darwin19:03:37

start canary with a new chrome user profile, do not use any other extensions than dirac

frank19:03:08

refers to dirac readme

darwin19:03:34

this will be likely fixed in the next release, but for now you have to get rid of any content scripts in your page

darwin19:03:29

you may as well disable those extensions, but it makes better sense to me to do debugging in clean chrome profile, to avoid any interference from extensions

frank19:03:31

oh that makes sense. I skipped the user profiles stuff when i was setting up dirac initially because i didn't know what it was

frank19:03:44

but I'm perfectly happy using canary without my other extensions

darwin19:03:26

also dirac might contain some security issues, so it is not recommended to introduce it into your real chrome profile

darwin19:03:47

theoretically some malicious code could exploit some dirac vulnerability

frank19:03:17

hmmmm now the cljs repl never loads in

frank19:03:43

no more warnings or anything though

frank19:03:59

pgdn did it

darwin19:03:04

:simple_smile:

darwin19:03:34

a pro tip: you can change Dirac extension options on the chrome extensions page, you can instruct it to open as a new window

darwin19:03:44

that way you can open internal devtools to debug dirac itself

darwin19:03:59

there you could spot some extra logging and maybe some errors

frank19:03:53

alright well i guess it's time to update our readme again :simple_smile:

frank19:03:59

thanks for your help!

darwin19:03:15

no problem