This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-25
Channels
- # aws (2)
- # bangalore-clj (2)
- # beginners (90)
- # boot (89)
- # bristol-clojurians (1)
- # cider (23)
- # cljs-dev (48)
- # cljsjs (2)
- # cljsrn (3)
- # clojure (118)
- # clojure-argentina (3)
- # clojure-austin (8)
- # clojure-czech (1)
- # clojure-dev (18)
- # clojure-ireland (1)
- # clojure-italy (4)
- # clojure-russia (6)
- # clojure-spec (75)
- # clojure-uk (224)
- # clojurescript (103)
- # core-async (28)
- # cursive (3)
- # datascript (7)
- # datomic (15)
- # dirac (30)
- # emacs (14)
- # events (3)
- # figwheel (1)
- # hispano (1)
- # hoplon (176)
- # lambdaisland (1)
- # lein-figwheel (6)
- # off-topic (21)
- # om (7)
- # onyx (2)
- # pedestal (6)
- # re-frame (4)
- # reagent (15)
- # spacemacs (67)
- # specter (13)
- # testing (9)
- # untangled (65)
- # vim (6)
- # yada (1)
@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
afaict no exception is being thrown in ns’es so my suspicion is that it will make no difference
@bronsa added repro project at https://github.com/puredanger/tajvm121
I think the core.async require is a requirement
things that make it work: a) remove the :require of core.async, b) require the namespace first before analyzing it
I’m having this premonition that its going to be some core.async bug that we already have a patch for
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
classes not being found, namespaces not being found, etc
the snapshot didn’t have any effect btw
but I haven’t looked for errors there yet
the other maybe interesting thing is that occasionally I was oome’ing which had other weird failure modes