Fork me on GitHub
#onyx
<
2016-11-24
>
lucasbradstreet04:11:40

@akiel I think it was removed in a refactor, since we didn’t think anyone was using it, but I’m open to it being added back in

lucasbradstreet04:11:00

@mariusz_jachimowicz adding the kill button to onyx-dashboard might be a good job for you if you’re interested

mariusz_jachimowicz07:11:34

Sure, I will take a look. I am experimenting with some kind of a supervising mechanism for handling failures in Onyx for now.

lucasbradstreet07:11:03

What kind of failures? I'm putting better, more robust failure detection in the ABS branch, that will use heartbeats and won't rely completely on ZooKeeper watches

mariusz_jachimowicz07:11:44

I have idea of supervisor component that is notified about failures and can broadcast this event to all components to handle it properly.

lucasbradstreet07:11:06

Ah this is more at the component level.

lucasbradstreet07:11:48

OK, feel free to investigate it, but know that we're mostly frozen for non bug fixes on the master/develop branches as ABS is getting all of the attention, and we're trying to reduce the cost of a later merge

mariusz_jachimowicz07:11:56

I want to have some history what failures was seen and orchestrate how system handle each kind of failure.

mariusz_jachimowicz07:11:25

Sure. It's early stage experiment.

lucasbradstreet07:11:06

Mostly wanted to let you know where things are currently at

Drew Verlee14:11:59

Just in case it hasn’t been mentioned Clojure Remote is looking for speakers. The organizer just announced that speakers will receive profit sharing of 1%/hr for their session. I think this might go a long way to make it worth the time to put together a talk or a workshop. Actual, it might be possible if we finish the Onyx Online tutorial within a couple months to use that as a 2 hour workshop online! I think that would be super cool.