This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-09-15
Channels
- # aws-lambda (3)
- # beginners (37)
- # boot (294)
- # carry (1)
- # cider (38)
- # cljs-dev (37)
- # cljsjs (88)
- # clojure (187)
- # clojure-android (2)
- # clojure-austin (1)
- # clojure-dusseldorf (9)
- # clojure-hk (3)
- # clojure-italy (12)
- # clojure-russia (36)
- # clojure-spec (55)
- # clojure-uk (27)
- # clojurescript (75)
- # community-development (5)
- # conf-proposals (2)
- # copenhagen-clojurians (3)
- # cursive (9)
- # datomic (54)
- # devcards (5)
- # devops (3)
- # dirac (69)
- # emacs (6)
- # ethereum (1)
- # euroclojure (1)
- # events (3)
- # funcool (1)
- # hoplon (20)
- # immutant (4)
- # luminus (14)
- # midje (4)
- # om (178)
- # om-next (2)
- # onyx (47)
- # pedestal (19)
- # protorepl (20)
- # re-frame (14)
- # reagent (54)
- # ring (2)
- # ring-swagger (7)
- # test-check (10)
- # uncomplicate (11)
- # untangled (9)
- # yada (9)
@smw: starter is simpler and easy to understand. The template uses best practices, and more advanced techniques that will help you go to prod
You mean the repl reloaded workflow?
I use clojure.tools.namespace.repl/refresh + with-test-env
https://github.com/onyx-platform/onyx-starter/blob/0.9.x/src/onyx_starter/launcher/dev_system.clj
I almost never have issues ctrl-c'ing it
We're going to add a system as an option to the template but I recommend deving by running individual tests with clojure.test/run-test + repl/refresh. It will pretty much be a repl reloaded workflow when you do it right
Are you having trouble ctrl-c'ing the test, or is it something else?
Yeah… cursive has an ‘interrupt current execution’ button that I believe is effectively ctrl-c
K hmm. Can you open a lein repl and try if manually for a bit? I like to put (clojure.tools.namespace.repl/refresh)(clojure.test/run-test 'your-test-ns) on the same line
The only time you should have to repl bounce is when you're connecting to thinks and they're timing out, or similar issues where it won't get a clean shutdown until you wait
Tasks are on their own threads, and won't cause the peers to die, just the job to be killed
(try
(s/with-fn-validation ~@body)
(catch InterruptedException e#
(Thread/interrupted))
(catch ThreadDeath e#
(Thread/interrupted))
(finally
(component/stop ~symbol-name)))))
Exception message gets written to zookeeper, peers keeps going until the end of with-test-WBC
This is why you want feedback-exception! as it gives you a way to drop out of it if your job dies
so feedback-exception! monitors the zk log for the exception written by the job before it dies, right?
and then re-throws the exception so that it should end the test?
(throw (extensions/read-chunk log :exception job-id)))))
@lucasbradstreet again questions about retry-params (https://github.com/onyx-platform/onyx-http/commit/4b7c985bf065d570600597319027e9cc8b6abcdb) Is it only for Batch http-output ? or it's support also http-output
Only for batch output for now
Since we had a need
I will accept PRs which come with tests
Sorry, we don’t have the time to work on it ourselves for now
It is a very good feature and useful in real life, would be great for a http-output also retry-params
I agree that it’s very useful. We just don’t have the time to work on it. If you are interested in working on it, then I am happy to review PRs to do it
New prod user added. Thanks for the logo @bfaber https://github.com/onyx-platform/onyx/tree/develop#companies-running-onyx-in-production
Just made a PR "Attempt to enable push to SSE encrypted s3 buckets". https://github.com/onyx-platform/onyx-amazon-s3/pull/2 Hope it is useful.