Fork me on GitHub
#datomic
<
2020-02-21
>
shaunxcode00:02:28

you might consider [... :where ... [(untuple ?period) [?starts ?ends]] ...]

csm01:02:47

that’s exactly what I wanted… the docs for untuple confused me

tatut10:02:34

I'm trying to run tests in github actions (just clojure -A:test command) and it seems it doesn't find datomic jars (I have the s3 releases bucket as a repo)

tatut10:02:21

specifically the com.datomic/ion {:mvn/version "0.9.35"} can't be found

maxt13:02:10

My first guess would be missing aws credentials. You need to be authed to fetch from that repo.

tatut13:02:34

I don't think our codebuild in aws is authed, it's just in the n. virginia region

m0smith17:02:11

In Datomic cloud, is it possible to do a dry run of a retractEntity. That is, have it return what it would retract but not actual do the retraction?

m0smith17:02:54

Thanks @lanejo01! That did the trick

dvingo23:02:57

datomic cloud question: We are attempting to set up a new cloudformation stack of an existing system (existing ions code, datomic schema, and data) The stack is setup, schema is transacted and we're attempting to confirm that data is loaded. When executing a query via HTTP through API gateway an exception is thrown. It appears to happen on the invocation to datomic.client.api/connect. The relevant stack trace lines are:

[
                "datomic.anomalies$throw_if_anom",
                "invoke",
                "anomalies.clj",
                113
            ],
            [
                "datomic.client.impl.local.Client",
                "connect",
                "local.clj",
                192
            ],
            [
                "datomic.client.api$connect",
                "invokeStatic",
                "api.clj",
                133
            ],
and
"Cause": "Supplied AttributeValue is empty, must contain exactly one of the supported datatypes (Service: AmazonDynamoDBv2; Status Code: 400; Error Code: ValidationException; Request ID: JF41UQTURAKQ0ITO8LFP94LBEVVV4KQNSO5AEMVJF66Q9)"
                        }
                    }
                },
                "At": [
                    "datomic.anomalies$throw_if_anom",
                    "invokeStatic",
                    "anomalies.clj",
                    119
                ]
The config map supplied to connect are read from amazon SSM parameters:
(defn cloud-db-config []
  {:server-type :ion
   :region      (ssm/get-ssm-param "region")
   :system      (ssm/get-ssm-param "system")
   :endpoint    (ssm/get-db-endpoint)
   :timeout     (ssm/get-ssm-param "timeout")
   :proxy-port  8182})
I believe these values are all present in SSM (I have to debug through an ops team member due to restricted environment access... so taking their word for it) We confirmed that we can query the database from a REPL connection by passing a manually constructed db-config map. I'm wondering if anyone has seem something like this before or if there is something obvious that I'm overlooking.