Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2019-02-22

Channels

#datomic
<
2019-02-22
>
benoit00:02:11

@bkamphaus Of course, I'm tired tonight. Thanks 🙂

🙏 5
jaret19:02:00

no unfortunately we had already submitted the CFT to AWS at the time of your report. We are still investigating that issue.

👍 5
henrik05:02:08

On eu-central-1, I'm getting the following error for updating query groups: 

1 validation error detected: Value '' at 'imageId' failed to satisfy constraint: Member must have length greater than or equal to 1

henrik05:02:00

I'm guessing there's something going on with this bit in the template: 

"ImageId": {
          "Fn::FindInMap": [
            "RegionMap",
            {
              "Ref": "AWS::Region"
            },
            "Datomic"
          ]
        },

henrik05:02:45

Yeah, no AMIs for most regions. Is this intentional? 

"RegionMap": {
      "us-east-1": {
        "Datomic": "ami-069156466c1112347"
      },
      "us-east-2": {
        "Datomic": ""
      },
      "us-west-2": {
        "Datomic": ""
      },
      "eu-west-1": {
        "Datomic": ""
      },
      "eu-central-1": {
        "Datomic": ""
      },
      "ap-southeast-2": {
        "Datomic": "",
        "Bastion": ""
      }
    }

jaret16:02:03

@U06B8J0AJ is this only with the query group template? Or have you identified it in another template?

jaret16:02:26

Ah Yes! We’ve confirmed an issue with the query-group template on the Marketplace page

henrik16:02:36

Only the query group as far as I can see. Storage and compute updated just fine.

jaret16:02:38

we have the correct template on our releases page and will contact AWS to update

👍 5
jaret16:02:11

@U06B8J0AJ use the template from the releases page for now

👍 5
henrik16:02:41

Now it works. 🙂

johnj20:02:20

Enhancement: Improved valcache cleanup algorithm. <- will Pro get this?

marshall23:02:53

Yes. Likely in the next release

mss21:02:32

is there a way to pull the actual ident value as opposed to a :db/id if that ident is a ref on another fact? I have something like :todo/type and where type is a ref to an ident. pulling :todo/type returns the :db/id of the ref, but I’d like it to return e.g. todo.types/chore

favila21:02:09

pull :db/ident

👍 5
mss21:02:10

ah it’s just :db/ident, makes sense

mss21:02:17

yep thank you!

favila21:02:48

unfortunately if you want a d/entity-style representation of the ref you will need to postprocess the result of the pull

favila21:02:07

there's no way to make the pull expression do it