Fork me on GitHub
#dirac
<
2018-01-31
>
pepe10:01:52

Hi, after updating to Chrome Canary 66.0.3335.0 I have strange behavior. When I start Dirac it starts with Dirac 1.2.26 <-> http:/localhost:300/ in the title, but after 3 second it changes to Dirac 1.2.26 <-> ? and in Console I see:

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]
Is it only me? Or does somebody see the same?

pepe10:01:50

@darwin should I open an issue?

darwin10:01:06

try to refresh your app’s browser window once again when dirac is up

darwin10:01:27

I noticed this when preparing .26 release, not sure what is causing it

darwin10:01:39

it happened occasionally to me

pepe10:01:50

refresh does not help

darwin10:01:39

do you see any js errors in the Dirac’s window own devtools?

pepe10:01:18

Hmm, when I press ctrl + shit + I when I have Dirac window open, it only opens the Dirac window again, what I am doing wrong? Sorry

darwin10:01:49

I’m going to try to repro this with dirac-sample project

pepe10:01:46

Thank you very much, I will try to get Dirac Dev Tools open in the meantime 🙂

darwin10:01:21

or maybe better to say, I need to update Dirac with updated sources

darwin10:01:16

to work-around this, you should install 3333.2 version of Chromium for the time being, the link is here https://github.com/binaryage/dirac/releases/tag/v1.2.26

pepe10:01:36

Thank you very much as always! I really appreciate all your work and attention!

darwin10:01:42

I should probably roll updated dirac release ASAP

darwin10:01:10

‘btw. did you manage to open dirac devtools’ own devtools? 🙂

darwin10:01:24

It should really work and you should see the same js error as pasted above 🙂

darwin10:01:56

btw. automated tests against latest chromium failed with the same problem: https://travis-ci.org/binaryage/dirac/builds/335463548

pepe10:01:56

Well I did after all from settings pane, clicking on devtools/front_end/inspector.html link 🙂

pepe10:01:09

The first thing is same as you sent above.

darwin10:01:43

don’t you have a global shortcut set to open dirac devtools overriding the standard one?

pepe10:01:40

Well you know, with me everything is possible.

pepe10:01:05

I was using Chrome Canary, with your recommended version of Chromium everything works, even Dirac DevTools. Thank you very much

darwin10:01:28

this was just a bad luck, dirac’s devtools sources started to be incompatible with latest chrome due to some breaking changes in chrome’s devtools protocol, we cannot realistically avoid this

darwin10:01:04

this would at least properly report incompatibility: https://bugs.chromium.org/p/chromium/issues/detail?id=538300#c20

darwin10:01:14

but it would be extra work for chrome devs

pepe10:01:17

Yea, I don't blame anyone or anything. This is how it is, when you are living on the edge.

pepe10:01:50

Still it is more than worthy for me

pepe10:01:04

Dirac is god send for cljs frontend dev

p-himik10:01:49

@darwin Would it be possible to [optionally] make Leiningen or something similar to always download automatically whatever Chromium version is the best for Dirac?

darwin11:01:56

@p-himik that would be possible, but nobody probably put an effort into making something like this automated 🙂

darwin11:01:05

it is confusing, I agree, but this thing happens very rarely and usually I’m faster with updated Dirac release than people notice it on their machines

p-himik11:01:42

And is it simpler to just check for Chromium version and alert the user when it's not the ideal one, while maybe also giving a link to the ideal one?

darwin11:01:43

@p-himik I would be a range check, and I don’t have the information which versions are compatible

darwin11:01:19

“DevTools frontend can adapt dynamically and does not fatally break when used with a slightly different Chrome version”

darwin11:01:13

simply stick with particular dirac and chromium versions which are tested to work well

darwin11:01:20

and update only manually

darwin11:01:26

both of them in lock-step

p-himik11:01:46

Oh, no, I don't mean the "set of versions that are guaranteed to work", I mean just something like that line in the release you pointed out: "Should work best with Chrome ~66.0.3333.2." The thing is, there's no such thing as Chrome Canary on Linux. And nowhere in the Dirac documentation it says that Chromium is supported as well, so a clearly visible link (just like the one you show when Dirac versions mismatch) would probably ease things for Linux users.

p-himik11:01:26

(but now I know that Chromium is supported as well, which is good 🙂 )

darwin11:01:26

well, I should probably report internal dirac error on all console errors in Dirac’s window, not sure why it wasn’t triggered this time

darwin11:01:45

and in that message I could mention compatible Chromium version

darwin11:01:47

or where would you put that “clearly visible link”

p-himik11:01:58

Somewhere under that green plaque - like the message about Dirac versions mismatch.

darwin11:01:25

but that should not be a warning, that would be displayed all the time I guess, because you will always have slightly different Chrome version than Dirac’s devtools snapshot

darwin11:01:58

but I see, I could add the information there

p-himik11:01:26

Yeah, not a warning - just something that one should check first whenever something doesn't work as it's supposed to. Thanks! 🙂