This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-02-21
Channels
- # admin-announcements (3)
- # beginners (15)
- # boot (96)
- # cider (5)
- # cljsjs (2)
- # cljsrn (3)
- # clojure (22)
- # clojure-austin (2)
- # clojure-russia (16)
- # clojured (2)
- # clojurescript (65)
- # css (4)
- # cursive (89)
- # datomic (7)
- # emacs (89)
- # events (1)
- # hoplon (126)
- # leiningen (2)
- # off-topic (2)
- # om (268)
- # onyx (19)
- # parinfer (42)
- # re-frame (5)
- # reagent (30)
- # yada (8)
@lucasbradstreet, sometimes when i submit jobs, i get lots of the following, which prevents the start-job process from exiting
which prevents the peer daemon process from starting
the actual start-then-kill-jobs stuff appears to run fine
Hmm. Are you submitting the job before the peers have started? I thought that works but maybe I was wrong
submit, kill, stop, start
ba12, remember
Okay, maybe I was wrong about that then. I'll check.
I'm not on a computer atm
sorry to pester you on a sunday. let’s tackle tomorrow
enjoy the rest of your weekend!
No problem anyway. Thanks for the report
You too!
@robert-stuttaford: looks like submit job works OK even when the peers aren’t started up yet, so I’m going to have to ask you some more questions when you’re around
ok lucasbradstreet - we can tackle it tomorrow
hey lucas, are you around?
oh, i see you’re Z, no worries
I'm curious how onyx compares to google's dataflow. They seem to share some underlying principles. I feel i could learn a lot by trying to compare the two. http://blog.acolyer.org/2015/08/18/the-dataflow-model-a-practical-approach-to-balancing-correctness-latency-and-cost-in-massive-scale-unbounded-out-of-order-data-processing/
@drewverlee: Onyx’s state management features are based off of the dataflow paper