This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-01-02
Channels
- # announcements (1)
- # beginners (15)
- # calva (6)
- # cider (72)
- # clojure (105)
- # clojure-europe (2)
- # clojure-france (1)
- # clojure-italy (4)
- # clojure-nl (2)
- # clojure-uk (32)
- # clojurescript (14)
- # code-reviews (10)
- # cursive (8)
- # data-science (2)
- # datomic (38)
- # events (1)
- # fulcro (31)
- # graphql (1)
- # hyperfiddle (47)
- # java (4)
- # jobs (4)
- # off-topic (18)
- # overtone (2)
- # parinfer (12)
- # pathom (19)
- # pedestal (4)
- # philosophy (2)
- # portkey (22)
- # re-frame (42)
- # reagent (1)
- # rum (1)
- # shadow-cljs (36)
- # specter (3)
- # tools-deps (2)
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
> NOTE Configuring a destination for cast/dev when running in Datomic Cloud is currently not supported.
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).
[this is with a fresh project created in the last few days following the latest templates and advices per the Getting Started guide]
@johanatan Are you using s3-creds directly?
is your Ion doing something with another AWS lib of some sort? or are you just trying the basic ion tutorial?
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]))
@johanatan https://forum.datomic.com/t/loadionsfailed-caused-by-stackoverflowerror-in-clj-antlr/747/3
not that it matters overly much, but you can set the Java thread stack size per my last comment on that ^ thread
I suspect youâre hitting a thread stack overflow given the largeish set of dependencies you listed there
Also, even if the thread size tweak fixes this, how can I get 0.1.23 locally? Do I need to add another repo?
@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
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.
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.
@johanatan Sorry I meant CloudWatch logs