This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-20
Channels
- # aleph (12)
- # announcements (7)
- # aws (6)
- # babashka (36)
- # beginners (161)
- # boot (1)
- # calva (6)
- # cider (21)
- # clj-kondo (13)
- # cljs-dev (28)
- # cljsrn (1)
- # clojars (3)
- # clojure (13)
- # clojure-colombia (1)
- # clojure-europe (10)
- # clojure-spec (12)
- # clojure-uk (47)
- # clojuredesign-podcast (2)
- # clojurescript (67)
- # datascript (8)
- # datomic (21)
- # duct (3)
- # emacs (6)
- # events (1)
- # fulcro (6)
- # graalvm (98)
- # jobs (1)
- # kaocha (18)
- # luminus (1)
- # malli (7)
- # off-topic (56)
- # pathom (5)
- # re-frame (18)
- # reagent (3)
- # reitit (9)
- # remote-jobs (3)
- # rewrite-clj (10)
- # ring (1)
- # shadow-cljs (155)
- # spacemacs (2)
- # sql (5)
- # tools-deps (27)
- # vim (86)
- # xtdb (2)
has anyone run into an issue where a "local/root" dependency will not be included in the zip file when doing a push? I'm getting a class not found error on deploy for one of the namespaces in a local root and when I unzipped the s3 asset it turned out that the source files are not being pulled into the build. I can compile and execute the code locally , so I'm at a loss for what's going on. There are also other local/root dependencies that are being included in the build.
local dep deps.edn changes may not force a recompute (at least in clj in general, not sure exactly about push). you might try using -Sforce
any reason the datomic ions dev code couldn't be open sourced? This would make debugging problems like this at last tractable instead of poking random buttons of the opaque box.
Figured out a way around this for now - to compile the app:
mkdir classes
clj -A:dev -e "(compile 'user-settings.core)"
;; add "classes" to deps.edn :paths
I have no idea why ions push is not working but the local/root deps are all in the classes and the deploy is now working. This seems like a bug.I think only the files in the default class path are pushed, not paths in aliases. Maybe that could be it?
Also, the compile
strategy stopped working and deploy was trying to run some very old version of the app. I'm not sure how this is happening or how I'm the first to run into this..
OMG... it turned out to be that the local/root project did not have a :paths []
set. Add this :paths ["src"]
got the dep to be included in the push....
Figured it out because other local deps were being included just fine but they had :paths
set.
@stuarthalloway As mentioned in person: Two nice-to-haves for the datomic cloud client api:
- some system generated unique value identifying a Datomic database so the application can confirm the database it's connecting to (say, a database with a particular db-name has been deleted and another created with the same name: I'd like to be able to detect that at an application level for things like automated testing)
- a way to map t
value to tx
eid, say I have a database, which returns a t
value, I'd like to also know what tx that corresponds to.
when i was looking into how to get the uri of a database object i found this:
(.-db_id ^datomic.peer.Connection conn)
=> "m13n-8ba32b12-7f6e-4d64-bf95-f3e32c95d589"
im wondering if that uuid is actually such a db id u were talking about@jaret Looking forward to seeing you at the Conj! As an aside, what's the current story with AWS integration testing with CodeDeploy/CodeBuild and cross-region S3 buckets? Is that still busticated? (Not that I consider it a Cognitect thing: I fully place that on AWS silliness.)
Still busticated in the sense you have to copy to a bucket in each region as far as I am aware. > AWS CodeDeploy performs deployments with AWS resources located in the same region. To deploy an application to multiple regions, define the application in your target regions, copy the application bundle to an Amazon S3 bucket in each region, and then start the deployments using either a serial or parallel rollout across the regions.
That would be AWSome. Feel free to invoke "our paying customers are (im)patiently waiting for this" on my behalf.
Cheers. There are somethings that I really like about immutability: AWS immutability with respect to this issue is not one of them 😉
I've been getting some AWS emails about Nodejs 8.10 begin deprecated/removed in early 2020. I see that Datomic Cloud stuff spun up with the most recent versions of the templates includes Nodejs 8.10 runtimes. Is there going to be a release sometime soon that will include a newer runtime?
Hope everyone on the Datomic team has a great time at the Conj - wish I could be there! I found a bad link on the docs - https://docs.datomic.com/cloud/troubleshooting.html#troubleshooting-ions has a link to https://docs.datomic.com/ions/ions-reference.html#lambda-ion which doesn't seem to exist.