This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-02-16
Channels
- # announcements (33)
- # asami (37)
- # autochrome-github (1)
- # aws (5)
- # babashka (26)
- # babashka-sci-dev (18)
- # beginners (63)
- # biff (1)
- # calva (66)
- # cider (15)
- # clj-kondo (24)
- # cljs-dev (2)
- # cljsrn (14)
- # clojure (62)
- # clojure-doc (1)
- # clojure-europe (15)
- # clojure-nl (11)
- # clojure-spec (12)
- # clojure-uk (4)
- # clojurescript (45)
- # community-development (2)
- # cursive (34)
- # datahike (7)
- # datomic (7)
- # events (1)
- # figwheel-main (5)
- # fulcro (19)
- # gratitude (7)
- # holy-lambda (85)
- # hyperfiddle (4)
- # jobs (7)
- # jobs-discuss (25)
- # kaocha (4)
- # lsp (11)
- # off-topic (1)
- # polylith (20)
- # portal (14)
- # practicalli (6)
- # proletarian (5)
- # rdf (52)
- # re-frame (13)
- # reagent (48)
- # releases (1)
- # remote-jobs (3)
- # shadow-cljs (7)
- # tools-deps (17)
I'd like to schedule a repeating job and I see that there’s a process_at
column on jobs. Is there a way to set this to something other than now
? I guess I could write my own wrapper on db/enqueue
. (The use case is a job that enqueues its successor job on completion).
Oops meant to link to the line https://github.com/msolli/proletarian/blob/e74e43d7c3710d4906c0ab474ecb59c807a48a83/src/proletarian/job.clj#L50
Yes, that’s precisely what that column is for. I haven’t needed the functionality yet myself, so I haven’t implemented a enqueue-at!
function. Or maybe it’s enqueue-delayed!
. Or both?
Would you mind opening an issue at https://github.com/msolli/proletarian/issues describing the use case, as above? We can work out the details there.