Fork me on GitHub
#clojure-dev
<
2017-01-25
>
bronsa17:01:42

@alexmiller re: TANAL-121, can you use t.a.jvm 0.6.11-SNAPSHOT? I've pushed a change to analyze+eval that makes it so that exceptions are thrown by default rather than wrapped, so that should make it easier to pinpoint what's happening -- when you have some time are you able to share a minimal example repo/steps to reproduce under lein? I still haven't managed to repro even using intellij

alexmiller17:01:30

afaict no exception is being thrown in ns’es so my suspicion is that it will make no difference

alexmiller21:01:24

I think the core.async require is a requirement

alexmiller22:01:11

things that make it work: a) remove the :require of core.async, b) require the namespace first before analyzing it

bronsa22:01:39

oh wow, that is really odd :/

alexmiller22:01:56

I’m having this premonition that its going to be some core.async bug that we already have a patch for

alexmiller22:01:01

in my own project I’m seeing many different failure modes, but they’re all potentially traceable to a ns call that did not have the intended effects

alexmiller22:01:20

classes not being found, namespaces not being found, etc

alexmiller22:01:51

the snapshot didn’t have any effect btw

alexmiller22:01:07

but I haven’t looked for errors there yet

alexmiller22:01:50

the other maybe interesting thing is that occasionally I was oome’ing which had other weird failure modes

bronsa22:01:10

I narrowed it down to simply (analyze+eval '(require 'clojure.core.async))

bronsa22:01:40

apparently loading from within t.a.jvm code that uses t.a.jvm breaks

bronsa22:01:59

btw I had to :exclusions t.a.jvm from core.async to get the actual last SNAPSHOT