https://twitter.com/CursiveIDE/status/1204229229606367232

@denik That has your fix, out now ^^^

@cfleming I’m fairly certain I was seeing that issue with that exact form, but I can only replicate when I do:

{:foo (sequence (comp (take 10)
                      (map (fn [i]
                             (when (= i 9)
                               (throw (RuntimeException.))))))
                (range))}

the CLI repl says:

{:foo (sequence (comp (take 10)
                      (map (fn [i]
                             (when (= i 9)
                               (throw (RuntimeException.))))))
                (range))}
Error printing return value at user/eval345$fn (NO_SOURCE_FILE:3).
null
{:foo (user=>

(the thing that tipped me off was the {:foo ( partial form there at the bottom)

Ugh, I think I know what I did. My very first example had take 100 and I threw on the 90th element. It must have started printing. I pruned it down for clarity, and I must not have checked it properly after I did that.

@cfleming is it safe to update to IDEA 2019.3?

I’ve seen Cursive release notes with support for 2019.3, but IDEA still warns about Cursive being uncompatible

I updated to 2019.3 yesterday and everything has been working as expected.

I'm using 2019.3 with 1.9.0 (well, 1.9.1-eap1 since this morning) and it's grand

Cool, thanks!

I updated to 1.9.1-eap1-2019.3 today and noticed that links in my exceptions now ask me to choose a "target file". This did not happen before and is likely a regression. In the below screenshot you can see Cursive asking me this. The 3 files shown do have a namespace with final portion of the namespace matching "metric-query". Cursive seems to not be taking into account the rest of the namespace though.

after upgrading to IntelliJ 2019.3 and the latest Cursive build (including EPA), my colleagues and i discovered that running our nREPLs configured with a deps.edn alias does not execute the alias's :main-opts [ ... ] instructions. has anyone else run into this problem?