Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Nov 16 2020 20:48
    metasoarous commented #18
  • Nov 16 2020 20:48

    metasoarous on dev

    Bumped version in README.md I … Merge pull request #18 from rem… (compare)

  • Nov 16 2020 20:48
    metasoarous closed #18
  • Oct 27 2020 11:08
    VictorInacio updated the wiki
  • Dec 05 2019 17:37
    remaininlight opened #18
  • Dec 05 2019 17:34
  • Dec 05 2019 17:28
  • Oct 17 2019 08:29
    claj commented #13
  • Oct 17 2019 08:25
    PEZ forked
    PEZ/datsys
  • Sep 03 2019 03:37
    humorless commented #43
  • Sep 03 2019 03:37
    humorless commented #43
  • Aug 19 2019 17:22
    aeberts opened #43
  • Aug 19 2019 17:22
    aeberts opened #43
  • Jun 18 2019 21:23

    metasoarous on dev

    fix some bootstrap/tx things (compare)

  • Jun 18 2019 21:06

    metasoarous on dev

    remove accidental peer.cljc ns (compare)

  • Jun 09 2019 18:12

    bamarco on dev

    pass db to hydrate-bootstrap (compare)

  • May 08 2019 00:20

    metasoarous on dev

    move datsync schema to dat.sync merge in existing (& default da… fire tx handlers to trigger pos… (compare)

  • May 08 2019 00:20

    metasoarous on lx

    move datsync schema to dat.sync merge in existing (& default da… fire tx handlers to trigger pos… (compare)

  • May 02 2019 19:10

    metasoarous on dev

    update datascript version transit handlers and more effic… fix :chsk/ws-ping clobbering db… (compare)

Christopher Small
@metasoarous
Hi @drewverlee! Yes, it's been a little quite around here for a while.
However, I've been dusting off the project of late, so please stay tuned for updates.
Alexander Eberts
@aeberts
Hi all - has anyone tried starting datsys recently? trying to start the server with lein repl results in a REPL server timed out message...
Christopher Small
@metasoarous
That might just be on the first run, as it can take a while to download deps and stuff.
You could try increasing the repl timeout
(google search)
Alexander Eberts
@aeberts
@metasoarous thanks! I'll try increasing the REPL timeout and report back...
Alexander Eberts
@aeberts
@metasoarous I tried repl-timeout values up to 480000 and am still seeing the REPL server timed out message... any other ideas?
Christopher Small
@metasoarous
Add another 0?
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.
Alexander Eberts
@aeberts
lol - ok, thanks anyway. Are you thinking of reviving this project? I think it's a very elegant approach to web dev...
Christopher Small
@metasoarous
Yeah, it's still on my radar. Just has taken second (err... third?) fiddle to some other projects
Sorry it's not in a better state at the moment
Alexander Eberts
@aeberts
re: GH issue: I've logged bug at: metasoarous/datsys#43
Christopher Small
@metasoarous
Great; Thanks!
Alexander Eberts
@aeberts
I'll keep chipping away at the problem on my end and will report back if I make any progress...
Christopher Small
@metasoarous
Excellent; Thanks for that.
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
Alexander Eberts
@aeberts
Thanks for Datsys! "Datalog All the Way Down" FTW! :-)
Christopher Small
@metasoarous
Thank you kindly :-)
Alexander Eberts
@aeberts
I'll checkout lein-gen...
Christopher Small
@metasoarous
FWIW, there is progress happening on the datsync front specifically as far as remote subscriptions, so stay tuned.
Alexander Eberts
@aeberts
that's awesome news... re-frame + datascript + datsync + datomic is what I'm interested in right now with datview a close second. I'm assuming that new stuff will land in the datsync project on GH, right?
Alexander Eberts
@aeberts
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?
Alexander Eberts
@aeberts
@metasoarous - quick update: I was able to get the repl running again by upgrading the deps (and changing a couple of deps e.g. com.cemerick/piggieback to cider/piggieback etc.).
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...
Alexander Eberts
@aeberts
@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...
Alexander Eberts
@aeberts
@metasoarous update: I'm able to get datsys building without errors (yay!). The datview/pull-form and datview/pull-view` are failing with the following errors:
#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...
Christopher Small
@metasoarous
Hey @aeberts ! Thanks for working on this and reporting back!
If you haven't tried already, I'd see if updating posh fixes the issue.
Alexander Eberts
@aeberts
@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?
Christopher Small
@metasoarous
@aeberts Excellent! Glad to hear it :-) And yes! I would love a PR of that to 31-lein-genif you'd be so kind.
Alexander Eberts
@aeberts
@metasoarous Sounds good - I'll put together a PR tomorrow.
Christopher Small
@metasoarous
Wonderful; Thank you!
Alexander Eberts
@aeberts
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 ;-)
Christopher Small
@metasoarous
The dev branch is the most recent we'
ve touched and is the place to run for now
Agree that this all needs to be smoothed out
Alexander Eberts
@aeberts
@metasoarous Do you mean the dev branch of datsys or datview? The dev branch of datsys fails to run because of an error in datview 0.0.1-alpha3.
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.
Christopher Small
@metasoarous
I meant of datview and datsync (maybe also datreactor)
I can try to push a datview release if that would be helpful
Alexander Eberts
@aeberts
@metasoarous yeah, I think pushing new releases of all the dat dependencies from the most recent branches would be the simplest and most robust way of getting datsys to work out of the box.
Alexander Eberts
@aeberts
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