Fork me on GitHub
#datomic
<
2019-01-02
>
Oliver George01:01:21

Should I see cast/dev in Cloudwatch Logs? Both cast/alert and cast/event come though okay. Perhaps "fine-grained logging to troubleshoot a problem during development" implies that it's not something which isn't intended to be logged after deployment. https://docs.datomic.com/cloud/ions/ions-monitoring.html#dev

lilactown02:01:49

> NOTE Configuring a destination for cast/dev when running in Datomic Cloud is currently not supported.

lilactown02:01:17

No, you currently can't see them

lilactown02:01:58

I've been using event to do Dev loving because if that 😕

johanatan06:01:10

anyone else experiencing a problem where Datomic Cloud insists on version 0.1.23 of com.cognitect/s3-creds but that version isn't found in any maven repos when running locally. local run works fine with 0.1.22. if i try pushing and deploying 0.1.22, after getting the warning that my 0.1.22 was overridden by the cloud's 0.1.23 version, it gets stuck in ValidateService (times out after 5 minutes).

johanatan06:01:37

[this is with a fresh project created in the last few days following the latest templates and advices per the Getting Started guide]

marshall17:01:02

@johanatan Are you using s3-creds directly?

johanatan17:01:24

it's one of the 8 or so deps that Datomic Cloud is adding

marshall17:01:46

is your Ion doing something with another AWS lib of some sort? or are you just trying the basic ion tutorial?

johanatan17:01:55

nope, it's very basic

johanatan17:01:25

here's the ns form for my code:

(ns core
  (:require [datomic.client.api :as d]
            [datomic.client.api.async :as da]
            [aleph.http :as http]
            [manifold.deferred :as deferred]
            [manifold.time :as mt]
            [manifold.stream :as st]
            [byte-streams :as bs]
            [clojure.data.json :as json]
            [clj-time.core :as t]
            [clj-time.local :as l]
            [clj-time.format :as f]
            [clj-time.coerce :as c]
            [com.rpl.specter :as s]))

marshall17:01:39

ah. you said it gets stuck in validate service

marshall17:01:46

you mean the deploy step fails?

marshall17:01:04

and eventually the codedeploy times out?

johanatan17:01:39

@marshall yes, that’s right

marshall17:01:04

Solo or Production?

marshall17:01:36

not that it matters overly much, but you can set the Java thread stack size per my last comment on that ^ thread

marshall17:01:10

I suspect you’re hitting a thread stack overflow given the largeish set of dependencies you listed there

marshall17:01:36

I should also note that you can’t use the datomic async client in an ion

johanatan19:01:23

Why no async?

johanatan19:01:43

Also, even if the thread size tweak fixes this, how can I get 0.1.23 locally? Do I need to add another repo?

marshall19:01:54

the deps mismatch is not related to the issue you’re hitting

marshall19:01:27

@johanatan Did you look in your CloudFormation logs for your datomic stack to see the specific error responsible for the failure? i suspect it’s the stack overflow

johanatan20:01:47

Let me check

johanatan20:01:11

I have three stacks (two are nested under the first): datomic, datomic-Compute-XXX, and datomic-StorageXXX. all three are in CREATE_COMPLETE state and have never had an "UPDATE" attempted on them.

grzm20:01:07

How does one get the “basis t” value of a db returned by since? The value of :t that I see is equivalent to the :t of the current database.

marshall20:01:15

@johanatan Sorry I meant CloudWatch logs

marshall20:01:01

go to the CloudWatch logs dashboard and find the log group named “datomic-<yourSystemName>”

marshall20:01:24

then you can search for “Exception”