Fork me on GitHub
#leiningen
<
2018-12-16
>
ikitommi08:12:17

Hi. Related to the lein check, there is another related error. Running lein uberjar compiles the files in non-deterministic order: locally (osx) it works, but with docker (linux x86-64) it fails as the compilation order is different and the satisfy? fails as the protocols have been changed during the compilation process. Here’s a sample (a Luminus template project with few addons) on how to get the error: • https://github.com/ikitommi/uberjar-problem here’s a minimalistic example showing that the compilation order matters: • https://github.com/ikitommi/fun

Alex Miller (Clojure team)14:12:39

Sounds similar to a ticket that’s out there about nondeterministic protocol compilation

Alex Miller (Clojure team)14:12:39

But compilation order definitely matters

ikitommi16:12:18

CLJ-2303 looks related, linked the issue into there. Should this be fixed in Clojure compiler itself or in the build tools (e.g. leiningen)? Leiningen could reorder the compilation files with tools like tools.namespace?

Daouda23:12:48

hey guys, can you help me with this error?

Daouda23:12:55

ERROR in (a-test) (io.clj:288)
Uncaught exception, not in assertion.
expected: nil
  actual: java.lang.IllegalArgumentException: Cannot open <nil> as a Reader.
 at $fn__9544.invokeStatic (io.clj:288)

Daouda23:12:14

i get it when i try to run my test, but the same test was running before and i spend the whole day trying to understand what my cause this but no success