-
Notifications
You must be signed in to change notification settings - Fork 13
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
Missing dependencies #2
Comments
Hi, thanks! Sorry about that:
Let me know if there's anything else I can assist with! |
all good also added datomic repository
so I can build now all good no errors. however starting repl I get; any ideas; thanks again
|
wow, odd. Try a otherwise try link it to checkouts (in the project folder):
|
thanks for the help; soz but same problem remains. I will try a few things |
ai, I'm sorry - I tried a clean clone on my machine and I can't replicate this :( The radical alternative is to remove prismatic/schema as a dep and simply make the validation step a no-op? that way you can at least get going. |
Same thing here FWIW:
The above came after trying the clean checkout schema suggestion. How would we make the validation a no-op? i.e. when I simply comment out the schema dep I get:
update: I was able to get to setup complete with the following changes:
|
Thanks for the diff @jackdempsey - You'd probably need a tweak in the cqrs.clj as well? It should be a matter of tweaking the validation function out. Again, apologies - I'll be able to look into this more carefully in the coming week |
Cool, glad to help even a little. Unfortunately when I started running things like register user, the event was tracked but the user didn't seem to make it. This is less an issue and more question, but since we're here: when things go wrong, as they always do, would you worry about this many pieces and their coordination making things more difficult to debug? Or do you think that part is easier, but keeping everything running perfectly is more the challenge? One of the hardest things to do is determine the right level of abstraction, complexity, and splitting apart of components, and without having a lot of experience with any of these pieces, intuitively I'd wonder if incidental complexity created with this sort of setup is manageable because once it's set and understood it pretty much doesn't break? You can probably tell at this point I'm working with something on the other side of things that's fairly simple but likely needs to be rewritten to run in a system more like this example. Thanks for any thoughts you can share from your experiences! |
Hey guys, really interested in the project and was trying to get it setup properly. I managed to work out why prismatic/schema isn't working. You can't just run However, I currently can't get datomic to say it's recorded anything. Am I still missing something?
|
That was my issue as well and I don't know datomic well enough to dice
|
Not a problem, I'm still poking it to see where it's failing, hopefully I can work out why datomic isn't recording anything. |
Oh yes, @Folcon - I remember having that same cljx once issue while I was developing now.. ai. Should have made a note back then! Thanks :) I'll make a note of the deps in the main README I'm seeing the same behaviour regarding the datomic recording - I'm looking into it and will let you know - I suspect it something fairly trivial missing. @jackdempsey , regarding the debugging and problem solving - what I've found with this kind of setup is that you can test the pieces independently on a much smaller scale to make sure all your basic building blocks are solid. Currently, Onyx is pre-production ready (they're busy working hard on 0.6.0, which is much closer to production ready), so there's still some bit being ironed out. But once you have the underlying system and all the pieces in place, they effectively disappear, and you can build your applications at a comfortable level of abstraction. I always think of it like this - You need all the pieces, some systems just hide the bits from you. This system brings out all the pieces, which forces you to understand them all (as architect), but gives you a far more solid system down the line. Hope the kinda answers your concern? |
@CmdrDats No problem. One thing I've noticed, is that I'm getting a lot of
Is there some part of the setup that's missing? I'm running this on osx if that helps. |
@Folcon ye, those are no problems - Zookeeper and Kafka are both somewhat noisy - one place that's particularly useful is checking the onyx.log under cqrs-server while you're running. I did find that I needed to checkout onyx and trim down the logging in the lifecycle.clj to make this feasible though :) I've updated to onyx 0.5.2 and onyx-datomic 0.5.2 in the deps - This runs on mine with : cqrs-server.core=> (start)
"Setup complete"
cqrs-server.core=> (send-command :user/register {:name "Bob" :age 31})
nil
cqrs-server.core=> (d/q '[:find [?e ...] :where [?e :user/name]] (d/db (d/connect datomic-uri)))
[17592186045422] |
Beautiful! Now works like a charm.
Now to work out how to create my own commands ;)... |
Strange, FWIW, still nothing in datomic for me after a fresh clone, following updated Schema instructions:
Will give a try another time perhaps. And thanks for the thoughts @CmdrDats . I agree on the benefits of pieces being more apparent. The hard part (especially if you're introducing a new language on top of a new technology) is that you often don't know how good of a decision it is/was until months or more down the line :-) I'll be curious to see how Onyx grows and is compared to Storm, as each time I try to do a bit with the latter I just get stuck in the weeds. |
@jackdempsey Did you try the I'm sorry it's not working out at the moment, thanks for your patience and your feedback! If there's anything else I can do to help, please le me know |
I did wait, no luck, but the bit on checking out onyx log was useful: onyx.log:datomic.impl.Exceptions$IllegalArgumentExceptionInfo: Didn't even realize that log existed. My guess is that when this function's
Any idea why I'd see this but not you? This is a fresh/clean git clone. On Sun, Feb 15, 2015 at 11:53 PM, CmdrDats notifications@github.com wrote:
|
Ah - sorry for the pain - I had this same issue and found that I needed to add a feature to datomic-schema so that I can mix schema with transactor function. I had upversioned and deployed datomic-schema, but never upversioned the dependency from 1.2.1 to 1.2.2 in cqrs-server. Note to self: be a lot more rigid in testing dependencies on release! Anyhow - needless to say, I have pushed an update for the latest version of datomic-schema. Just pull the changes and let me know :) |
I've pulled your updates and my setup still seems ok. |
Woot! At first I thought "still, no" but then waited another second and...success!
That datomic-schema update was definitely it. Thanks for sticking to On Mon, Feb 16, 2015 at 4:59 PM, Folcon notifications@github.com wrote:
|
Fantastic, enjoy! :) I'm going to close this issue now, but please feel free to fire any questions in my direction. |
hi there great article BTW
Could not find artifact prismatic:schema:jar:0.3.8-SNAPSHOT in clojars (https://clojars.org/repo/)
Could not find artifact com.datomic:datomic-pro:jar:0.9.5130 in central (https://repo1.maven.org/maven2/)
Could not find artifact com.datomic:datomic-pro:jar:0.9.5130 in clojars (https://clojars.org/repo/)
Could not find artifact yuppiechef:onyx-dynamodb:jar:0.5.0 in central (https://repo1.maven.org/maven2/)
Could not find artifact yuppiechef:onyx-dynamodb:jar:0.5.0 in clojars (https://clojars.org/repo/)
The text was updated successfully, but these errors were encountered: