This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-02-10
Channels
- # announcements (2)
- # babashka (15)
- # beginners (174)
- # calva (16)
- # chlorine-clover (10)
- # clara (7)
- # clj-kondo (27)
- # cljdoc (10)
- # clojars (4)
- # clojure (50)
- # clojure-europe (10)
- # clojure-gamedev (3)
- # clojure-greece (1)
- # clojure-italy (4)
- # clojure-losangeles (1)
- # clojure-nl (16)
- # clojure-sg (1)
- # clojure-spec (7)
- # clojure-uk (41)
- # clojurescript (22)
- # data-science (15)
- # datascript (38)
- # datomic (2)
- # duct (15)
- # emacs (2)
- # fulcro (110)
- # funcool (9)
- # graphql (10)
- # jackdaw (8)
- # jobs (23)
- # joker (1)
- # leiningen (15)
- # luminus (1)
- # malli (20)
- # off-topic (26)
- # pathom (5)
- # pedestal (1)
- # reitit (19)
- # shadow-cljs (78)
- # spacemacs (2)
- # sql (52)
- # tools-deps (99)
- # vim (13)
Is there a dedicated location where some form of datomic dependency upgrade roadmap is broadcast? Or has that traditionally happened out of necessity or as a result of a request? I find myself in a situation where I have no real urgency to use the newest [email protected]
, but would benefit from knowing if that was planned, not a priority, for sure never going to happen, etc..
Putting together a script to run some integration testing, I'm calling ion.dev/push
from Clojure. That appears to open a s3-transfer-manager-worker
thread pool that doesn't shut down cleanly. I end up needing to call System/exit
. Is this what datomic.ion.dev/-main
does as well? Or is there some other manner I can cleanly shut down that thread pool?