Clojurians Log v2

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

it worked before 😭

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

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

I was using it yesterday

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

let me try some more debugging first

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

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

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

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

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

@darwin: I see lots of tops

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

because it talks to something else

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

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

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

refers to dirac readme

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

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

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

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

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

yikes

theoretically some malicious code could exploit some dirac vulnerability

hmmmm now the cljs repl never loads in

no more warnings or anything though

oh wait

nvm

pgdn did it

:simple_smile:

ok cool

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

that way you can open internal devtools to debug dirac itself

there you could spot some extra logging and maybe some errors

ah cool

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

thanks for your help!

no problem