This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-20
Channels
- # aws (1)
- # beginners (14)
- # boot (30)
- # cider (6)
- # clara (9)
- # cljsjs (3)
- # cljsrn (22)
- # clojure (247)
- # clojure-dusseldorf (75)
- # clojure-france (38)
- # clojure-italy (6)
- # clojure-japan (8)
- # clojure-nl (3)
- # clojure-russia (16)
- # clojure-serbia (4)
- # clojure-spec (1)
- # clojure-uk (53)
- # clojurescript (168)
- # consulting (3)
- # copenhagen-clojurians (1)
- # core-async (7)
- # css (1)
- # datascript (3)
- # datomic (8)
- # dirac (22)
- # events (1)
- # hoplon (2)
- # jobs (1)
- # jobs-discuss (2)
- # leiningen (4)
- # lumo (138)
- # mount (13)
- # nyc (1)
- # off-topic (24)
- # om (34)
- # onyx (15)
- # pedestal (30)
- # re-frame (9)
- # reagent (23)
- # ring (1)
- # ring-swagger (24)
- # rum (6)
- # spacemacs (6)
- # specter (51)
- # uncomplicate (14)
- # unrepl (1)
- # untangled (17)
- # yada (12)
Hi, with Dirac 1.2.4 and Chrome 60.0.3076.0 I am getting Internal Dirac Error: TypeError: target.renderingAgent is not a function, should I create issue, or is it some problem on my side?
btw. @onetom just reported something here: https://github.com/binaryage/dirac-sample/issues/3
btw, it's possible to report issues on slack automatically. who has access to such config on this slack team?
btw. tests passed for .3076: https://travis-ci.org/binaryage/dirac/builds/223805724
is canary still a requirement? can't we use a beta channel version? or is it possible to manually controll the canary update frequency?
betas are several weeks behind chromium master, that would be a problem for me to track
but I’m going to investigate it right now, if it is reproducible here, there is a good chance I will fix it and release a new version right away
ok, it is reproducible here - this looks like a major change in the debugger protocol api
for now you can work around it by disabling “Use backend-supported API & CSS” in Dirac Extension Options
interesting enough this problem is only reproducible on 60.0.3076.0/Mac on Linux it works
this is some kind of mis-match of the debugger protocol API, Mac version does not provide some functions which should be there