we literally move the project to open source and then depend on the open source one for our production needs
Rob Norris
@tpolecat
ok
Timothy Perrett
@timperrett
none of this periodically throwing stuff over the wall
@tpolecat thanks for sticking around with all the back and forth on the builds
i know that was pretty tedious
but i think we’re in a good place now
Rob Norris
@tpolecat
yeah no worries, it was educational.
Timothy Perrett
@timperrett
so take a look at the chemist module - i think that has one of the most interesting parts in terms of design
its basically a stream transducer for work orchestration
oh and the use of free applicatives for metric derivitives is pretty interesting
Rob Norris
@tpolecat
yep i'm going to make an instrumented version of doobie and mess around with it
alright i'm out for a bit. thanks!
Timothy Perrett
@timperrett
cheers
Timothy Perrett
@timperrett
@tpolecat lol we hilariously overlooked something there… we forgot to update the release build to not cross publish, so they race to publish jars for both versions :-D fixed in master and rebuilding
@runarorama@stew so i revived this, as some people want the direct-push model, so i didnt see any reason to restrict that from happening. WDYT? oncue/funnel#20
but whatever if people want it, they should probaboly have what they want
Timothy Perrett
@timperrett
@stew yeah, that bit is weird. I cant recall why we did that - i think its just to batch into groups of a 1000 or something. i should probally look into making this more like the elastic module
literally just revived this from the history
so i made more progress on getting the quickstart docker compose setup
need to revise something in the way chemist expects configs but should have it running tomorrow
its pretty neat though: spins up elastic search, kibana, 2 flasks, 3 targets and a chemist
_
Dan Billings
@danbills
@runarorama I'm trying to validate via unit test that the Discard command to a Flask will disconnect from a host.
I don't think that append(schedule.kill) is necessary. The zip w/ the schedule should run any cleanup code. Moreover, the schedule in flask's case doesn't need to be cleaned up.