-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lein repl fails with "REPL server launch timed out" #43
Comments
I put something like:
to solve timeout problem. However, there are other problems. |
It's late 2021, booting this on an ubuntu 18 box |
Hi folks; Thanks for your queries and responses here. @KnowledgeGarden You may want to try the Really, we need to migrate this template repository towards That having been said, there are very likely quite a few other issues here, and I haven't given this project much attention in the last few years, but I'd like to try and do a bit more work here in the coming months. Right now, most of my attention has been on some major new features for Oz, but I'll try to make a bit of bandwidth to help get things moving here again. Thanks again |
Hi!
I'm diving back into datsys after learning more about reagent and re-frame. The idea of having a data-driven datascript <-> datomic system is very appealing! Unfortunately, the project doesn't build out of the box when following the instructions in the readme.
Summary: Running the command
lein repl
results in aREPL server launch timed out
error.Steps to Reproduce:
datomic-free-0.9.5697.zip
fromhttps://my.datomic.com/downloads/free
https://github.com/metasoarous/datsys.git
dev
branch withgit checkout -b dev
project.clj
to use[com.datomic/datomic-free "0.9.5697" :exclusions [joda-time org.slf4j/slf4j-nop com.google.guava/guava commons-codec]]
datsys/config/local/env.sh
and update config to match local settingdatsys/config/local/dev-transactor.properties
and update file to match local settings.lein repl
in thedatsys
directoryExpected Result:
Actual Result:
The text was updated successfully, but these errors were encountered: