However, I've been dusting off the project of late, so please stay tuned for updates.
You could try increasing the repl timeout
(google search)
lol
The project is in need of some updating and I've seen issues with certain newer javas/clojures, which may be related to the problem
Sorry I don't have more help for you now
Please feel free to post a GH issue (if there isn't one that matches this description already) so we can track this particular problem.
Sorry it's not in a better state at the moment
There's a branch in there somewhere called something like lein-gen, which redoes the project as a leiningen generator
That may be more up to date than master
Hey @metasoarous - I've been poking around in the
31-lein-gen branch and trying to get a handle on how you structured the datsys template. The leiningen docs at https://github.com/technomancy/leiningen/blob/master/doc/TEMPLATES.md talk about having 2 dirs: one called datsys/src/leiningen/new where the template generator files live and datsys/resources/leiningen/new where the template files live. I noticed you only used a datsys/src/leiningen/new dir - are the files in datsys/resources/leiningen/new being generated automatically?
the build is failing with
No such namespace: cljs.spec, could not locate cljs/spec.cljs, cljs/spec.cljc, or JavaScript source providing "cljs.spec". I'll continue to look into that when I have some more free time...
@metasoarous quick update: I got datsys to build again after cloning the
dat* libs, upgrading their deps and installing locally in my local .m2 repository. The app is starting but I'm getting dat.reactor errors in the console which are probably related to datomic not being properly setup. I'll keep chipping away at it...
#object[TypeError TypeError: Cannot read property 'call' of null]TypeError: Cannot read property 'call' of null
at posh$plugin_base$get_db (http://localhost:7467/js/compiled/out/posh/plugin_base.js:193:110)
at Function.cljs$core$IFn$_invoke$arity$5 (http://localhost:7467/js/compiled/out/posh/plugin_base.js:289:43)
at Function.cljs$core$IFn$_invoke$arity$6 (http://localhost:7467/js/compiled/out/cljs/core.js:13232:10)
at Function.cljs$core$IFn$_invoke$arity$variadic (http://localhost:7467/js/compiled/out/cljs/core.js:13523:34)
at Function.G__11282__delegate [as cljs$core$IFn$_invoke$arity$variadic] (http://localhost:7467/js/compiled/out/cljs/core.js:15017:24)
at G__11281 (http://localhost:7467/js/compiled/out/cljs/core.js:15059:20)
at http://localhost:7467/js/compiled/out/dat/view/utils.js:166:79
at reagent$ratom$in_context (http://localhost:7467/js/compiled/out/reagent/ratom.js:62:14)
at reagent$ratom$deref_capture (http://localhost:7467/js/compiled/out/reagent/ratom.js:71:36)
at Object._run (http://localhost:7467/js/compiled/out/reagent/ratom.js:1107:93)
looks like the error originates in
posh - I'm not at all familiar with posh but I'll keep digging to see if I can make any more headway...
If you haven't tried already, I'd see if updating posh fixes the issue.
@metasoarous thanks for the suggestion - I came across your issue in mpdairy/posh: mpdairy/posh#36 which suggests that
posh 0.5.6 breaks get_db. Using posh 0.5.5 appears to get everything working! (at least on the surface). Would you like me to make a pull request with my working changes to 31-lein-gen?
Hi @metasoarous - Question regarding the PR for Datsys. Using the most recent version of Datview published to clojars
[datview "0.0.1-alpha3"] breaks compilation because it refers to cljs.spec and not cljs.spec.alpha. The datview/dev and datview/symmetric branches appears to fix this. How would you like to handle this? The options I see are: 1) cut new, updated builds of the dat dependencies and push to clojars or 2) require datsys users to use checkouts (more complicated and probably more error-prone for most people) or 3) a better approach I haven't thought of ;-)
ve touched and is the place to run for now
Agree that this all needs to be smoothed out
If you're OK pushing a new
datview 0.0.1-alpha4 from the dev branch to Clojars I think that would solve the problem. Updating the other dat library dependencies at the same time would also probably be a good idea.
I can try to push a datview release if that would be helpful
just make sure that they are using
cljs.spec.alpha and not cljs.spec as in: https://github.com/metasoarous/datview/blob/42c1ee973f6b1e52932e2bcf94e783d3e424539b/src/dat/view.cljs#L29