Clojurians
#dirac
<
2016-10-28
>

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

ghufran05:10:10

I am having trouble getting dirac working: I have the latest canary (Version 56.0.2902.0 canary (64-bit)), dirac “0.7.4”, and I am using figwheel-sidecar “0.5.8”. I can open the page in the browser at localhost:3449. When I click the button for the dirac chrome extension, it opens, and says “Dirac v0.7.4 <->http://localhost:3449/", but this then changes to “Dirac v0.7.4<->? “, and in the console window, tells me "Dirac requires runtime support from your app. Please install Dirac Runtime into your app and enable the :repl feature. [:dirac.implant.eval/install-check-timeout]” . However, if I close this window and open the regular developer tools window, the console says "Installing Dirac Runtime v0.7.4 and enabling features :repl” without any errors shown.

darwin07:10:43

@ghufran I will push a new Dirac release in an hour or two, Chrome devs changed the debugger protocol dramatically in last few days: https://github.com/binaryage/dirac/commit/eef01c4523fd27b68a2e149fa77461898f38a3cf#diff-020d349505d25448d4c7b763efc32119 (click to show suppressed diff)

darwin07:10:49

a pro tip: you would probably see more if opening internal devtools of the Dirac DevTools window itself: https://github.com/binaryage/dirac/blob/master/docs/faq.md#something-broke-how-do-i-debug-dirac-devtools-frontend

darwin07:10:46

btw. if something like this happens in the future (Canary runs away from Dirac), you will have to resort to using matching chromium snapshots as a workaround, look for “Links to matching Chromium snapshots” in the release notes for your Dirac version: https://github.com/binaryage/dirac/releases

ghufran18:10:32

@darwin: thank you!