This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-07-03
Channels
- # aleph (3)
- # beginners (139)
- # boot (3)
- # cider (12)
- # cljs-dev (18)
- # clojure (100)
- # clojure-dev (21)
- # clojure-dusseldorf (5)
- # clojure-germany (1)
- # clojure-italy (35)
- # clojure-nl (26)
- # clojure-spec (4)
- # clojure-uk (60)
- # clojurescript (11)
- # clojutre (4)
- # cursive (21)
- # data-science (21)
- # datomic (47)
- # editors (3)
- # emacs (2)
- # events (4)
- # figwheel (2)
- # fulcro (28)
- # jobs (27)
- # jobs-discuss (21)
- # lein-figwheel (3)
- # midje (2)
- # off-topic (20)
- # om-next (4)
- # onyx (10)
- # overtone (1)
- # pedestal (2)
- # portkey (14)
- # re-frame (71)
- # reagent (44)
- # reitit (11)
- # remote-jobs (1)
- # ring-swagger (4)
- # shadow-cljs (64)
- # spacemacs (11)
- # testing (2)
- # tools-deps (8)
- # vim (8)
Are the slack logs still collected at the clojurians log link in the header? Was looking for a the discussion about a previous question, and the onyx logs there only go through 20180417.
Ah damn. I think that must be because slack deprecated their slack gateway
Our application is all about scaling cluster resources, and I want to dogfood it using our onyx cluster. Is there an API to get a list of pending jobs?
onyx.api/job-state allows you to get the current state for a particular job ID. I could add another which returns the state for all jobs
lib-onyx also has a bunch of helpful code for that sort of thing
Looks like I could use the replica HTTP query server, just get a list of all jobs, and figure it out from there. That would be perfect.
That’d work fine.
Preferable to a job-state fn approach, as that has the play back the log each time