This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-05-03
Channels
- # admin-announcements (6)
- # beginners (73)
- # boot (84)
- # cider (9)
- # cljs-edn (5)
- # cljs-site (8)
- # cljsrn (2)
- # clojure (158)
- # clojure-austin (1)
- # clojure-canada (1)
- # clojure-dusseldorf (2)
- # clojure-ireland (1)
- # clojure-russia (45)
- # clojure-sg (2)
- # clojure-uk (28)
- # clojurebridge (2)
- # clojurescript (142)
- # core-async (43)
- # cursive (23)
- # datascript (5)
- # datomic (9)
- # dirac (4)
- # emacs (23)
- # funcool (1)
- # garden (1)
- # hoplon (280)
- # jobs (1)
- # ldnclj (6)
- # leiningen (37)
- # luminus (6)
- # om (30)
- # om-next (1)
- # onyx (6)
- # perun (24)
- # re-frame (10)
- # reagent (20)
- # remote-jobs (1)
- # rethinkdb (2)
- # ring-swagger (4)
- # rum (3)
- # spacemacs (6)
- # untangled (36)
- # yada (5)
Just running through some more testing, but looks like we'll release 0.9.5 in the next few days.
New static analyzer for error detection came out really nice - http://www.onyxplatform.org/assets/images/better-errors/semantic-error.png
Kafka 0.9 compatible plugin has been patched for resuming from an offset across different task IDs - Clojars coordinates 0.9.4.1-kafka9-20160503.220013-2
.
Will get it reviewed and out officially soon.
> we have the flexibility of doing rolling deployment updates to the Onyx application while the job continues to run on the cluster. So onyx can be upgraded e.g 0.9.0 ->0 .9.5, without jobs stopping?
As long as there arent breaking changes between those two versions, yes. But its more meant to be for rolling upgrades of the application code, not typically Onyx itself