Error at `(go)` in "Developing" instructions about metabase-datomic

[plexus]

That looks like a jigsaw issue, can you stick to Java 8 for now?

[daveliepmann]

Switched to java8, no change in the error.

user> (.. System getProperties (get "java.version"))
"1.8.0_212"

[plexus]

I'll see if I can reproduce this. You have metabase and metabase-datomic checked out next to each other? What git revision are you looking at for each?

…

On Wed, May 29, 2019, 12:44 Dave Liepmann ***@***.***> wrote: Switched to java8, no change in the error. user> (.. System getProperties (get "java.version"))"1.8.0_212" — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAH3VAUFES7VWQOBYEKBBTPXZNALANCNFSM4HQB2SZA> .

[daveliepmann]

Both repos live in a src/forks directory, as siblings (with a couple dozen others):

metabase        
metabase-datomic

Metabase-datomic was on 54fb631 (fix-install-instructions branch) but I just switched to 85bf6c3 (master branch) and no change. Metabase is on 7fb6363c9 with the changes introduced by start_metabase script. (I also experience the issue with or without changing the refactor-nrepl version injected into Metabase from 2.4.1-SNAPSHOT to 2.4.0. This suppresses REPL warnings about mismatched versions but does not affect the reported issue.)

Also FYI the CIDER REPL shows a warning:

WARNING: requiring-resolve already refers to: #'clojure.core/requiring-resolve in namespace: datomic.common, being replaced by: #'datomic.common/requiring-resolve

[plexus]

I think I found the issue, since metabase/metabase@eea171f#diff-0bd07e71f50064f6df5bcf24bc16f4feR477 setup-db! no longer takes arguments. If you do pass arguments, they get passed as extra arguments to deref, which makes deref assume that you're derefing something that can take a timeout like a future.

Will push a fix in a second.