This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-05-30
Channels
- # babashka (7)
- # beginners (25)
- # calva (22)
- # cljs-dev (1)
- # clojure (62)
- # clojure-europe (118)
- # clojure-hamburg (4)
- # clojure-israel (2)
- # clojure-nl (2)
- # clojure-uk (6)
- # clojured (1)
- # clojurescript (23)
- # conjure (11)
- # cursive (3)
- # datomic (14)
- # duct (2)
- # emacs (12)
- # figwheel-main (1)
- # gratitude (1)
- # hyperfiddle (4)
- # joyride (72)
- # lsp (46)
- # luminus (1)
- # malli (1)
- # off-topic (54)
- # pathom (19)
- # polylith (11)
- # releases (2)
- # sci (22)
- # shadow-cljs (4)
- # vim (11)
- # xtdb (52)
(on-prem) I’m seeing messages like this one during an import :
[WARN] [org.apache.activemq.artemis.core.client] - AMQ212054: Destination address=os-xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx.tx-submit is blocked. If the system is configured to block make sure you consume messages on this configuration.
I’m guessing it’s because the transactor is blocking? (using d/transact-async
)do you know if there an example of what a message indicating backpressure looks like somewhere? It’s quite a tricky thing to simulate
Hey all, wondering if there's any way to reference the unification set of a variable in a where clause. Something like:
;; more clauses
[?e :attr ?v]
[(count [?v ...]) ?count]
;; more clauses
[(q [:find ?v :in $ ?e :where [?e :attr ?v]] $ ?e) ?vs]
[(count ?vs) ?v-count]
[(identity ?vs) [[?v]]]
Thanks! I had broken it up into two queries, but I was curious if there was a simpler approach.
HEY ALL! So, I've got this error that is happening in the middle of a long chain of functions. I'm hoping someone can tell me the root cause, because I'm having a hard time seeing why it started happening. Cheers!
Execution error (ExceptionInfo) at datomic.core.error/raise (error.clj:55).
:db.error/not-in-system-partition Value of :db.install/attribute must be in :db.part/db partition, found :person/name
Yup, I just arrived to tell people not to worry about me. I dug it out. Thanks @U09R86PA4 for coming quick to the rescue. CHEERS!