This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-02-24
Channels
- # admin-announcements (1)
- # aleph (3)
- # announcements (4)
- # beginners (30)
- # boot (296)
- # cider (21)
- # cljsjs (2)
- # cljsrn (18)
- # clojure (124)
- # clojure-poland (23)
- # clojure-russia (4)
- # clojurescript (73)
- # core-async (58)
- # css (3)
- # datomic (31)
- # editors (4)
- # emacs (35)
- # euroclojure (3)
- # hoplon (104)
- # immutant (8)
- # jobs (3)
- # jobs-discuss (1)
- # keechma (1)
- # ldnclj (33)
- # leiningen (5)
- # liberator (1)
- # mount (20)
- # off-topic (2)
- # om (104)
- # onyx (54)
- # parinfer (80)
- # proton (1)
- # re-frame (59)
- # remote-jobs (1)
- # ring-swagger (9)
- # slack-help (15)
- # spacemacs (7)
- # yada (12)
I think those would be more than enough
They'll mostly sit idle, but I'm not sure how much lower you can safely push it
@lucasbradstreet: the groupid for lib-onyx
is onyx-platform
, but readme says onyxplatform
. The groupid for onyx
is onyxplatform
. Assuming that the documentation is correct but the dep has been uploaded to clojars incorrectly?
ew, ok
Yes, it should be onyxplatform
I’ll fix it up and will get a release out for you
Thanks
lib-onyx-0.8.12.0-20160224.152123-1 is up
on the group-id that’s in the readme
Whoops, my bad. T_T
no biggy
I pushed onyx-amazon-sqs to no group-id 😞
One downside of immutable artifacts 😕
We can ask the Clojars folks to remove some of those bad deploys. Its not the first time
Yeah, I’ve done it before
We’ll queue some up and batch them 😛
Decided to take the big plunge. Happy to announce that I'm supporting Onyx full time now! http://www.onyxplatform.org/jekyll/update/2016/02/24/Doubling-Down-on-Onyx.html
@michaeldrogalis: Congratulations!
@michaeldrogalis: Congratulations indeed!!
Thanks @leonfs @lsnape! Really looking forward to working closer with companies that are dipping their toes into the water with Onyx. The extra time will be great.
@nha: We're likely to make a serious effort on Ruby or Python first, but JavaScript would be the 3rd. It mostly depends on who we're working with.
I'll release a roadmap in the next 2-3 weeks
I think the main thing is that we have an overall strategy
For 3rd party languages
It hits home for a lot of machine learning applications.
Congratulations! I learnt a lot about the problem space in general from the amazing docs that you guys produced and your pointers on slack/gitter. Wish you luck in securing some lucrative contracts
Thanks @cddr. I actually pointed a new client at integrity a few days back
Which part specifically? I feel in hindsight it maybe bundles too many disparate things together.
They are using Onyx + Datomic and were going to build their own meta-language for validation between the two and their web client
I’m not sure if they’ll end up using it, but I think they’ll probably at least use some of the ideas
i'm having a nasty problem in production atm - occasionally (monthly or so) the AWS cluster seems to fall to bits, and ZK and kafka go down for a while... whatever network hiccup is causing the problem goes away after a while, ZK recovers and mesos/kafka restarts the brokers - problem is onyx never recovers - the process seems to get wedged, and so far the only solution seems to be to submit a job to a new onyx-id with a new kafka consumer-id (a new onyx-id with the old consumer-id stays wedged)
@lucasbradstreet previously suggested i kill and restart the job when this happens... i couldn't do that because i hadn't wired up the kill api (i have now)... but since creating a new onyx-id still stays wedged i'm guessing the problem is elsewhere
dyu have any ideas for debugging this ?
and congratulations on the next phase of onyx !
@mccraigmccraig: Thanks! As far as your deployment, there's a lot there. It's hard to know where to start looking when AWS, Mesos, Kafka, Onyx, and your app are involved. I'd need to have a better idea of what the application itself is doing and what the configuration of the Kafka catalog entries are.
Will switch to PM for this one.
@michaeldrogalis: just read this: http://www.onyxplatform.org/jekyll/update/2016/02/24/Doubling-Down-on-Onyx.html
@thomas: Thanks, we're looking forward to trying - that's for sure!
@michaeldrogalis: I'm excited you have the ability to work on onyx full-time!!! 🎉
@drewverlee: Me too! Looking forward to building some awesome back end systems in the wild.