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.

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]]]

“fails” == ??

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

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

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

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

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

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

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