This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-08-30
Channels
- # announcements (3)
- # asami (20)
- # babashka (15)
- # beginners (47)
- # biff (25)
- # calva (11)
- # cider (11)
- # clojure (24)
- # clojure-brasil (3)
- # clojure-europe (21)
- # clojure-norway (34)
- # clojure-uk (2)
- # clojurescript (9)
- # clr (2)
- # datomic (10)
- # fulcro (14)
- # hyperfiddle (58)
- # introduce-yourself (1)
- # jobs (3)
- # life (2)
- # malli (5)
- # meander (6)
- # missionary (4)
- # nbb (30)
- # off-topic (6)
- # podcasts-discuss (1)
- # shadow-cljs (13)
- # slack-help (5)
- # tools-build (4)
- # vim (20)
- # xtdb (20)
Another weird inconsistency with :db/id
and pull on cloud: aliasing (e.g. [:db/id :as :x]
) does not work. Output map still shows :db/id
.
(let [{conn :datomic/connection} @user/sysref]
(d/pull (d/db conn) [[:db/id :as :eid] [:st.generator/nominal-power :as :power]] [:st.generator/sysid "o0vi3xej"]))
=> {:db/id 92358976747775, :power 9.24}
I see that the latest com.datomic/peer
(version 1.0.6735) uses a several libraries with known CVEs.
Any plans to fix/improve this?
For example upping com.amazonaws/aws-java-sdk-ec2
to 1.12.540
removes a bunch of CVEs as reported by https://github.com/rm-hull/nvd-clojure.
Datomic team is aware of the issue, and seems to be committed to resolving them, but no ETA im aware of .
Just asking to confirm: there’s currently no way to configure datomic on-prem to use the spymemcached client in TEXT mode so it can be proxied via e.g. mcrouter? We maintain a fork of spymemcached with this and other patches related to IO threads dying. The IO thread death issues were supposedly solved with some kind of supervisor, but I’m checking that we still need the fork for the protocol override.
This is the fork for reference https://github.com/useshortcut/spymemcached