Fork me on GitHub
#datomic
<
2021-06-06
>
cjsauer18:06:21

I’ve just launched a brand new datomic cloud production topology stack of version 781-9041 and am working out a bunch of dep conflicts. One of which is particularly confusing to me. Running ion push shows me this:

:dependency-conflicts
 {:deps
  #:com.datomic{client-api #:mvn{:version "0.8.37"},
                client #:mvn{:version "0.8.86"},
                client-impl-shared #:mvn{:version "0.8.69"},
                query-support #:mvn{:version "0.8.16"},
                client-cloud #:mvn{:version "0.8.80"}}
These versions seems extremely old…when I pin them locally to test I receive exceptions like “d/qseq is not a function”, which was released all the way back in 668-8927

cjsauer18:06:37

Oh man….I just on a whim bumped ion-dev to 0.9.282 and suddenly the dep conflicts are much more minimal. I had followed the instructions to install ion-dev here on this page: https://docs.datomic.com/cloud/operation/howto.html#ion-dev

cjsauer19:06:49

That version is out of date. I suppose ion’s pinned versions are baked into the ion-dev artifact, which is why my conflicts were so old. Would be great if that page could be updated, and ideally kept in sync automatically to spare others the same dep chasing pain.

👍 2
onetom06:06:10

i was also fighting with those conflicts lately. luckily, you don't HAVE TO necessarily fix all of them, but obviously that's an unsupported situation. in my case, the main conflict was caused by the jackson lib and it actually prevented my program to start, even locally. after applying these adjustments: https://github.com/metosin/muuntaja/issues/121 and ignoring some of the remaining conflicts, things seem to work. so far...