Fork me on GitHub
#datomic
<
2018-06-19
>
gabriele08:06:58

@jaret by removing every line/namespace and testing i finally found what is that breaks, if you have a namespace called "datomic.db" in your project, codedeploy fails at validate service

conan10:06:56

Does anybody know whether communication with an on-prem transactor is secure by default? I'm trying to get one running in Heroku, backed with Heroku Postgres; all comms with the DB are over SSL and authenticated, so I'm not worried about the storage, so if comms between peers and the transactor are secure then I'm good to go, but I can't find any mention of the transactor's network protocol anywhere. I'd be very grateful if anyone knows the answer or can point me to a helpful resource, thanks

stuarthalloway13:06:22

@gabriele.carrettoni good catch! You cannot, and should never, use namespaces owned by some other organization in your code

stuarthalloway13:06:50

@conan look at your transactor properties file

conan15:06:47

oh great, i'd missed this. thanks, that reassures me a lot!

stuarthalloway13:06:56

## Set to false to disable SSL between the peers and the transactor.
# Default: true
# encrypt-channel=true

gabriele14:06:47

@stuarthalloway now i get namespace 'cheshire.factory' not found

gabriele14:06:34

java.lang.Exception: namespace 'cheshire.factory' not found, compiling:(cheshire/core.clj:1:1)
what is going on now 😣

stuarthalloway15:06:51

@gabriele.carrettoni I doubt cheshire will work at all until we update jackson in Datomic Cloud, planned for the next release

stuarthalloway15:06:45

Cheshire requires a version of Jackson that uses methods not present in the version currently shipping with Datomic Cloud

gabriele15:06:40

@stuarthalloway i see, i'll remove the dependency and use data.json

stuarthalloway15:06:43

that is a priority fix for us, you are (at least) the second person to hit it

souenzzo01:06:43

There is a roadmap to update on-prem deps too? By default, it has issues with clojurescript and tons of other projects, like onyx

denik15:06:59

can’t connect to datomic cloud:

Caused by: clojure.lang.ExceptionInfo: Unable to connect to system: #:cognitect.anomalies{:category :cognitect.anomalies/unavailable, :message "Connection refused"}

denik15:06:06

ran into this once before a few months ago

denik15:06:22

nothing changed in the code or creds

denik15:06:34

it simply worked, then I restarted the repl and now it doesn’t work anymore

denik15:06:55

since cloud is necessary even for dev, I’m now 100% blocked

marshall15:06:45

@denik you’re getting that error in your local repl? have you restarted your SOCKS proxy? can you run the proxy test (https://docs.datomic.com/cloud/getting-started/connecting.html#test-bastion)

denik15:06:57

I did restart (even the machine which is what fixed it last time)

marshall15:06:16

what do you get from the proxy test?

denik15:06:50

I can’t run the test, we shut down out bastion bc we develop with a machine inside the VPC

marshall15:06:56

have you upgraded Datomic? Is your primary compute node still online?

denik15:06:30

yes, prod db works (same system)

denik15:06:35

haven’t touched deps or creds

denik15:06:43

neither code

denik15:06:10

I might have had an orphan jvm running that was holding a connection but after restart that should be wiped, too

marshall15:06:09

what security group is your dev instance using?

marshall15:06:37

is it possible you opened up SG ingress to a specific IP (the original dev system) and now you have a new IP

denik15:06:17

it’s open within the VPC

denik15:06:31

had no problems for months

marshall15:06:48

your prod db is on the same Datomic cloud system?

marshall15:06:57

and it’s working fine?

denik15:06:04

I guess the prod system hasn’t tried reconnecting yet

gabriele16:06:16

(using ions) i have renamed a namespace and deployed a new version, now the lambda throws that it doesn't find the namespace

marshall16:06:22

That's a known issue with Aws marketplace. You can unsubscribe and resubscribe to get it to go away or you can just choose the one that has the latest

denik16:06:41

unsubscribing and resubscribing will leave the VPC alone?

denik16:06:59

meaning the system will run as usual after resubscribing

marshall16:06:27

Yes. When you launch, choose reuse existing storage

denik16:06:11

and that’s the recommended way to update the system?

marshall16:06:46

No. You can upgrade without resubscribing

denik16:06:30

I’m looking to update the templates, not to upgrade the system

marshall16:06:14

I'm not sure what you mean by update the templates

denik16:06:26

nvmd, found the little copy and paste button

marshall16:06:32

It is automatically copied to clipboard when you click the icon

denik16:06:23

@marshall will our settings around the VPC be overwritten?

marshall16:06:52

Not as long as you select the "reuse existing resources" box

marshall16:06:24

Note that you need to delete the old stack first

denik16:06:35

in the docs I only see Reuse existing storage

denik16:06:43

that includes other resources?

marshall16:06:45

Yes that one

rhansen16:06:25

Is there a way to pass in pull selector to a query? Like:

(d/q '[:find (pull ?e ?fields)
         :in $ ?fields
         :where [?e :game/name _]] 
  (d/db conn) [:db/id :game/name])
This fails when using the datomic client api

okocim17:06:14

Hello, has anyone been able to configure logging inside of ions so that the log entries show up in cloudwatch?

stuarthalloway19:06:33

@okocim you should be able to use CloudWatch like any other API. That said, The ion API does not yet provide a way to put your logs in the same log stream that Datomic uses. That is planned for a future release.

okocim19:06:50

@stuarthalloway Thanks Stu. I was trying to avoid using the API directly and instead make use of either the LambdaAppender or the System.out.println functionality, but I was having a hard time determining exactly which log stream this ends up in. Appreciate the heads up.

stuarthalloway19:06:33

@okocim remember that ion code is not running in a Lambda

stuarthalloway19:06:45

the Lambda is just a proxy

okocim19:06:51

got it. Well that explains why I wasn't seeing what I expected.. I'm going to re-familiarize myself with the docs. Thanks so much 🙂

johnj20:06:39

the datomic cloud license fee in production is per node correct?

johnj20:06:04

so it starts at ~$450/month

Joe Lane21:06:30

@lockdown- that doesn’t sound right.

johnj21:06:16

@lanejo01 which part? I didn't include the bastion but included the cost of the ec2 nodes

Joe Lane21:06:33

2 i3.large instances for 30 days runs you ~$224.64 https://aws.amazon.com/ec2/pricing/on-demand/

Joe Lane21:06:02

So, roughly half.

Joe Lane21:06:23

Thats just for the ec2 instances themselves.

Joe Lane21:06:29

I’ll check the license fee.

Joe Lane21:06:01

Oh, you know what, I think you’re right @lockdown-.

Joe Lane21:06:28

Ultimately I think it depends on the “per node” part of your question. Sorry for adding confusion.

sparkofreason22:06:46

Any guidance on running tests with the cloud client lib? I have a rather big hammer approach right now that involves creating/deleting DBs for tests that need clean data, and it's pretty slow.

Alex Miller (Clojure team)23:06:32

Ive done that and found it to be pretty fast