This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-06-26
Channels
- # announcements (6)
- # beginners (328)
- # boot (2)
- # cider (72)
- # clara (6)
- # cljdoc (4)
- # cljsrn (5)
- # clojure (78)
- # clojure-europe (3)
- # clojure-italy (22)
- # clojure-nl (4)
- # clojure-spec (3)
- # clojure-uk (114)
- # clojurescript (22)
- # clojurex (54)
- # copenhagen-clojurians (1)
- # core-async (20)
- # cursive (8)
- # data-science (1)
- # datomic (22)
- # duct (11)
- # emacs (32)
- # events (1)
- # figwheel (2)
- # fulcro (18)
- # graalvm (53)
- # graphql (39)
- # luminus (6)
- # nrepl (6)
- # off-topic (53)
- # om (1)
- # re-frame (8)
- # reagent (19)
- # reitit (3)
- # shadow-cljs (28)
- # spacemacs (10)
- # sql (37)
- # tools-deps (33)
- # vim (9)
- # xtdb (6)
(into #{} (comp (map :make) (map str/lower-case)) [{:make “Volvo”} {:make “Audi”} {:make “volvo”}])
For https://docs.datomic.com/cloud/query/query-data-reference.html#return-maps , is there a way to return namespaced keys?
Yeah, that works - thanks!
and it's not doing something silly like making the name part "ns/name" (i.e. with a slash in it)
Everything seems to work right! Thanks so much, I couldn't think of what syntax to even try with it 🙂
Neither would have I. It would be helpful to get an example of this added to the docs.
@jaret Might be worth adding how to return namespaced keys in return maps to the docs, I wasn't able to figure it out without help
Not sure how active #ions-aws. Maybe this is a better channel for this issue. https://clojurians.slack.com/archives/CC0A7PUHF/p1561577826007800
I think I just crashed my datomic cloud - I retracted an entity, then tried to pull the entity and everything hung (using datomic-socks-proxy to connect). My cloudwatch sat stuck at 6 pending ops for a while and I couldn't reconnect to the socks proxy so I tried rebooting the EC2 instances. When I tried to restart the compute instance, it went from "starting up" to "shutting down" and was then terminated by AWS - I don't think I told it to do that! My socks proxy instance started back up without a problem, but of course it can't do anything. I'm going to try a compute-only upgrade and see if things come back.
This is all with the solo topology.
what version of Datomic solo template @shaun-mahood?
I'm not sure which version I was on, it looks like I originally created the compute stack on 2019-03-28, and I think that was an upgrade from the original combined stack. So I probably used CFT 470-8654, is there a way I can find out? It was pretty recent, but I just upgraded to 477-8741. Both my compute node and socks proxy are running again but the socks proxy can't connect now.
Bastion security group looks ok to me, I just followed the instructions on the getting started page and nothing changed. The bastion is hung on the line client_input_global_request: rtype
I tried updating it to remove and put back on the bastion, still nothing. Going to put in a ticket for it.