Fork me on GitHub
#dirac
<
2016-06-06
>
richiardiandrea14:06:38

@martinklepsch: make sure you have the remote debugging enabled. If so, it requires some fiddling sometimes, as in: close the panel, reload, reopen.

martinklepsch14:06:02

I do have the remote debugging enabled (I think otherwise the panel wouldn't open)

martinklepsch14:06:17

Tried restarting a few times but didn't help, will look more into it later

darwin16:06:22

@martinklepsch: Iโ€™m back. The Dirac Runtime installed in your page is too old. Current version is 0.6.0, yours is 0.2.0.

martinklepsch18:06:08

@darwin: thanks, that helps. I noticed the difference but somehow assumed that there might be different versions for runtime/server/extension

martinklepsch18:06:51

That solves it ๐Ÿ™‚

darwin18:06:53

no problem, newer versions should give you better error feedback, it just happened that the 0.2.0 is so old that it donโ€™t even have dirac.runtime/installed? function

darwin18:06:32

enjoy! bug reports / feedback welcome ๐Ÿ™‚

martinklepsch19:06:25

is there a way to tell chrome to always set the remote debugging port as expected by dirac?

darwin19:06:56

no, AFAIK, you have to do it from command-line

darwin19:06:23

but a simple wrapper script solves it for me, or a bash alias

darwin19:06:17

it is also good practice to use a separate chrome profile when developing, so such script is handy anyways

darwin19:06:28

not only for that chrome debugger port setting

superstructor22:06:16

> WARNING: The version of connected DevTools is old. Expected '0.6.0', got โ€˜0.4.0โ€ฆ @darwin: nice! the improved documentation and sanity checks in the latest version work great ๐Ÿ‘