This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aws-lambda (3)
- # beginners (57)
- # boot (3)
- # bristol-clojurians (1)
- # cider (38)
- # cljs-dev (23)
- # clojure (35)
- # clojure-italy (32)
- # clojure-nl (6)
- # clojure-spec (35)
- # clojure-uk (132)
- # clojurescript (34)
- # cursive (22)
- # data-science (1)
- # datomic (54)
- # devcards (1)
- # duct (5)
- # editors (7)
- # euroclojure (4)
- # fulcro (40)
- # graphql (1)
- # hoplon (6)
- # immutant (5)
- # jobs (1)
- # off-topic (22)
- # om (1)
- # planck (17)
- # portkey (1)
- # protorepl (12)
- # re-frame (97)
- # reagent (67)
- # reitit (16)
- # ring-swagger (1)
- # shadow-cljs (98)
- # spacemacs (8)
- # sql (20)
- # tools-deps (60)
@steveb8n your premise is incorrect. Ion transaction functions work exactly like database transaction functions. They differ only in how the code is loaded.
Is there something in the docs that made this unclear? If so I would like to fix it.
@steveb8n the next release of ion-dev will have a better error message when you specify the wrong region -- thanks for the report!
this is a bit frustrating, i cannot deploy, every time it fails and i have no way to know what's wrong
@gabriele.carrettoni and can you look in your Datomic Cloud system logs via these instructions and search for Ion or Exception?
@gabriele.carrettoni ah you have buddy. I think thats the problem. let me confirm, we had a user run into this previously.
@stuarthalloway when using the old transactor fns, it was a single api call and it ran on the transactor, where the transactor called any txn fns as part of that single call. with Ions, it’s 2 api calls. 1/ to generate the extra datoms https://github.com/Datomic/ion-starter/blob/master/src/datomic/ion/starter.clj#L154 and 2/ to make them persist https://github.com/Datomic/ion-starter/blob/master/src/datomic/ion/starter.clj#L155
in my use case I am using a transactor fn to run a query and then throw an exception if I find a conflict
with the Ion pattern, another thread could transact in between those 2 api calls and my check would miss it
FWIW I really like new pattern as it matches the pure db command pattern I am using for all my txns
while we’re chatting, re my other hiccup with testing the web ion sample, I learned about API gateway, resources and methods and made it work without needing /foo in the uri
but I think the docs could help avoid that by providing a bit more detail in setting up the API gateway routes
it’s a deep rabbit hole so helping noobs not fall straight in will be good for first impressions
with that, I’m off to work. but generally stoked about Ion and all the devops work I don’t have to do. great work!
@steveb8n agreed, and/or maybe have some automation for API Gateway. It is a deep well.
@gabriele.carrettoni it looks like code deploy is having some issues. I am also not able to deploy.
@gabriele.carrettoni can you look in your cloudwatch logs for a message “Cluster node starting”
@gabriele.carrettoni and you aren’t seeing any alerts in cloudwatch to the left? Do you see a datomic instance with your system name when looking at the ec2 dashboard with a status of “running”
Well now I am thoroughly confused. You removed all the added deps from the previous project so it should have been effectively the same.
Ha! Well just to warn you on the buddy front. Buddy and Pedestal use Cheshire which uses jackson and we’ve previously found a conflict with the versions there. The previous client was able to drop buddy altogether, but you should be able to force a newer version of the jackson dep to make it work if you do run into an issue including buddy.
As Stu mentioned we’re working on a new release of Ion-dev that will show deps conflicts at the time of deploy to help troubleshoot those issues without going into the logs.