using core.async results in page getting replaced with empty iframe

[Daniel Higginbotham]

I've found that using core.async in one of my projects results in the entire DOM getting replaced with an empty iframe when I view the site in Firefox. I'm using 

[org.clojure/clojure       "1.7.0"]

[org.clojure/clojurescript "1.7.48"]

[org.clojure/core.async    "0.1.346.0-17112a-alpha"]

I've tried to isolate the problem and am unable to reproduce it in a minimal project using only core.async. However - has anyone else run into anything similar? Does core.async use iframes somehow? Any other suggestions or leads?

Thanks!

Daniel

[Malcolm Sparks]

Would you mind pasting the rest of your dependencies? This is the most curious of puzzles and I'd love to know the answer - but I'm really stumped so please provide the next clue!

[Timothy Baldridge]

core.async has nothing to do with the DOM, so I don't know how this could happen. 

--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clo...@googlegroups.com
Note that posts from new members are moderated - please be patient with your first post.
To unsubscribe from this group, send email to
clojure+u...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups "Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clojure+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

“One of the main causes of the fall of the Roman Empire was that–lacking zero–they had no way to indicate successful termination of their C programs.”
(Robert Firth)

[Daniel Higginbotham]

Here you go!

[[org.clojure/clojure       "1.7.0"]

 [org.clojure/clojurescript "1.7.48"]

 [org.clojure/core.async    "0.1.346.0-17112a-alpha"]

 [adzerk/bootlaces          "0.1.11"          :scope "test"]

 [adzerk/boot-reload        "0.3.1"           :scope "test"]

 [pandeiro/boot-http        "0.6.3"           :scope "test"]

 [jeluard/boot-notify       "0.2.0"           :scope "test"]

 [tailrecursion/boot-hoplon "0.1.1"           :scope "test"]

 [adzerk/boot-cljs          "1.7.48-SNAPSHOT" :scope "test"]

 ;; frontend

 [tailrecursion/hoplon      "6.0.0-alpha5"]

 [tailrecursion/castra      "3.0.0-SNAPSHOT"]

 [inflections               "0.9.14"]

 [mathias/boot-sassc        "0.1.5"]

 [cljsjs/moment             "2.9.0-2"]

 ;; backend

 [org.clojure/java.jdbc         "0.3.6"]

 [net.sourceforge.jtds/jtds     "1.2.4"]

 [clj-time                      "0.9.0"]

 [pandect                       "0.5.2"]

 [jumblerg/ring.middleware.cors "1.0.1"]

 [ring                          "1.3.2"]

 [org.clojure/tools.logging     "0.3.1"]

 [clj-http                      "1.1.2"]

 [camel-snake-kebab             "0.3.2"]

 [cheshire                      "5.5.0"]

 [tailrecursion/ring-proxy      "2.0.0-SNAPSHOT"]

 [tailrecursion/castra          "3.0.0-SNAPSHOT"]]

I guess the next step is for me to include these in my minimal setup and see if anything breaks :)

Thanks!

Daniel

[Colin Yates]

Daniel, is the UI constructed based on receiving something from a
channel? which is incorrectly setup and so the UI is 'blocked' pulling
from that channel.

--
Sent with my mu4e

[Malcolm Sparks]

Could you also run

lein deps :tree

and paste the output to the thread. It could be that one of your dependencies is already depending on core.async transitively, and the explicit inclusion of a different version of core.async causes that to break. This is a long shot but it could help.

You received this message because you are subscribed to a topic in the Google Groups "Clojure" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/clojure/kgLcFpTnxL4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to clojure+u...@googlegroups.com.