This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-08-31
Channels
- # announcements (6)
- # babashka (32)
- # beginners (78)
- # biff (11)
- # calva (7)
- # clj-kondo (20)
- # clojure (35)
- # clojure-europe (10)
- # clojure-nl (4)
- # clojure-norway (8)
- # clojure-uk (2)
- # clojurescript (41)
- # conjure (14)
- # core-async (10)
- # cursive (7)
- # datomic (12)
- # deps-new (4)
- # emacs (15)
- # fulcro (48)
- # gratitude (11)
- # hugsql (1)
- # hyperfiddle (3)
- # introduce-yourself (3)
- # jobs (3)
- # klipse (2)
- # off-topic (7)
- # polylith (30)
- # reitit (1)
- # remote-jobs (1)
- # reveal (8)
- # scittle (4)
- # shadow-cljs (40)
- # squint (13)
- # tools-deps (7)
- # xtdb (7)
Is @(:closed? node)
part of public API, that is, can we rely on that to keep existing in our lifecycle methods? Trying to check if the node is closed and needs to be reopened
Not exactly 🙂 it would be safer to call status
and catch the IllegalStateException
https://github.com/xtdb/xtdb/blob/6fb56faaa612b68ba1d6c84c6323bfde26358b7a/core/src/xtdb/node.clj#L34
Fair. I mean you can probably really on that atom without too much worry. Maybe add a test for it to repo just in case there ever is a breaking change?
FWIW, this is how we test it https://github.com/xtdb/xtdb/blob/e4f983c9e09f2218ed3ef080403e23c75779043b/test/test/xtdb/node_test.clj#L23-L41