Ions push fails with CLIENT_ENDPOINT NoSuchFieldError

After updating my client-cloud and ion-dev dependencies, I get the following error when running ion push.

> clojure -A:ion-dev "{:op :push}"

{:command-failed "{:op :push}",
 :causes ({:message "CLIENT_ENDPOINT", :class NoSuchFieldError})}

I’m running ion-dev v1.0.298, client-cloud v1.0.119, aws-cli v2.4.14
I have a datomic-config.edn that follows the definition in the docs including :endpoint, which is my best guess as to what the error points to.

Any ideas or suggestions would be greatly appreciated!

Hi @adamtait What version of Datomic Cloud are you pushing to? Does your client endpoint in your config match the endpoint that is in the outputs of your client endpoint stack? If you are on an older version of Datomic Cloud I suspect you are encountering the new endpoint we provided in 884-9095:

936-9118 ← (probably) the same version that you helped my upgrade to in the middle of the night! Looks like this is newer than 884-9095

Also, when I try to connect using the client api - I get:

 #:cognitect.anomalies{:category :cognitect.anomalies/fault,
                         :message "SIGNING_NAME"}
                 async.clj:   58  datomic.client.api.async/ares
                 async.clj:   54  datomic.client.api.async/ares
                  sync.clj:   92  datomic.client.api.sync.Client/connect
                   api.clj:  146  datomic.client.api/connect
                   api.clj:  133  datomic.client.api/connect

I think you’re right that it’s related to version mismatches. When I use

com.datomic/client-cloud   {:mvn/version "0.8.105"}
com.datomic/ion-dev        {:mvn/version "0.9.282"}

I can push/deploy and connect.

1 Like