Fork me on GitHub
#leiningen
<
2017-03-03
>
hlship17:03:19

I’m hitting some issues moving to lein-sub/lein-parent with managed dependencies at scale. As in, 48 sub-modules, 100 managed dependencies. Looks like for each sub-module, it re-evaluates all 100 managed dependencies. This gets very, very slow. Has anyone else done things at this scale?

nberger17:03:31

@devth you probably have something in your environment that is redefining clojure.test/reportwhich is originally a multimethod and test.check expects it to be a multimethod. What editor are you using?

nberger17:03:29

Asked about the editor because I fixed a similar issue in vim-fireplace a few months ago. But most people have reported it to happen when using cider and clojure.spec (https://github.com/clojure-emacs/cider/issues/1841) and in that case the solution for now seems to be adding the require

devth17:03:37

oh really? i'm using vim-fireplace

devth17:03:28

how'd you fix it there?

nberger17:03:13

And updating vim-fireplace should fix it for you

devth17:03:20

awesome, but i'm running latest vim-fireplace

nberger17:03:51

Oh. Then maybe it's still the issue with clojure.spec?

devth17:03:11

yeah, can't remember where the root issue was. test.check i thought

devth17:03:38

i read an issue awhile back where they basically said WONTFIX so i have to require test.check in every test instead

nberger17:03:51

I had the issue when just using test.check... and it wouldn't be fixed by just adding the test.check require, because I already had it...

devth17:03:09

i need to dig in more to figure out what's going on

nberger17:03:49

Yeah, I'll do the same as soon as I have some time, I'm curious about this issue

devth17:03:06

https://github.com/technomancy/leiningen/issues/2173 – the :monkeypatch-clojure-test false suggestion fixes for running lein test (i believe) but not running tests via vim-fireplace

devth17:03:59

(i am using clojure.spec in 1.9 alpha)

nberger17:03:21

Oh, so it's broken in test.check's latest release but in master it should be fixed. There's no set date for the next test.check release but hopefully it will happen soon