Fork me on GitHub
#core-async
<
2016-07-18
>
hlship17:07:05

Is anyone else seeing an issue with using Clojure 1.9.0-alpha10 w/ core.async 9.2.385? I have code that works using Clojure 1.8 that fails, with no other code changes.

hlship17:07:37

10:35:08 ~/workspaces/github/active-status > lein deps :tree
 [clojure-complete "0.2.4" :exclusions [[org.clojure/clojure]]]
 [io.aviso/pretty "0.1.28"]
 [io.aviso/toolchest "0.1.4"]
 [medley "0.8.2"]
 [org.clojure/clojure "1.9.0-alpha10"]
 [org.clojure/core.async "0.2.385"]
   [org.clojure/tools.analyzer.jvm "0.6.10"]
     [org.clojure/core.memoize "0.5.9"]
       [org.clojure/core.cache "0.6.5"]
         [org.clojure/data.priority-map "0.0.7"]
     [org.clojure/tools.analyzer "0.6.9"]
     [org.clojure/tools.reader "1.0.0-beta2"]
     [org.ow2.asm/asm-all "4.2"]
 [org.clojure/tools.nrepl "0.2.12" :exclusions [[org.clojure/clojure]]]

hlship17:07:44

It hangs. I’m reducing some other dependencies, and then I need to figure out whats going on.

hlship17:07:57

Seems like only the first value is passing through my system of channels.

hlship17:07:08

Failure states in core.async are hard to diagnose or discuss!

hlship18:07:20

I’m seeing some error; I may have a bad destructuring, leading to a NPE inside a go block. Hilarity ensues.

hlship18:07:02

Yep, I had one of those destructures with a :or that reference the keyword, not the symbol.

hlship18:07:07

and I was redirecting failure output to a file, so it looked like a hang, when it was more of a crash

Alex Miller (Clojure team)18:07:23

soon there will a let spec that will catch that error at compile time :)