Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Rob Norris
    @tpolecat
    yeah
    Timothy Perrett
    @timperrett
    yeah
    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
    Mike (stew) O'Connor
    @stew
    :shrug: I dunno, I still don't know what Reimann is. This one seems weird: https://github.com/oncue/funnel/pull/20/files#diff-06764678f4806cde8e5131fa19042f3bR130
    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 wrote this: https://github.com/danbills/funnel/blob/unit_test_key_removal/core/src/test/scala/MonitoringSpec.scala#L667
    I can verify that the io.resource "cleanup" doesn't run. If I throw a println in the "step" function of io.resource, it appears to run forever.
    It now occurs to me that I should validate this bug locally so that i can verify it is indeed a bug and not an issue w/ my test :)
    Rúnar
    @runarorama
    that's a good idae
    idea
    Dan Billings
    @danbills
    brb
    Rúnar
    @runarorama
    seems like maybe processMirroringEvents is doing something nefarious
    Dan Billings
    @danbills
    My hunch is attemptRepeatedly
    Rúnar
    @runarorama
    p.append(schedule.kill).attempt(e => Process.eval { Task.delay { maskedError(e); e }})
    append(schedule.kill) specifically
    Dan Billings
    @danbills
    going by documentation that kill command should "giving chance for any cleanup actions to be run"
    Rúnar
    @runarorama
    check if io.resource cleanup actually survives appends
    Dan Billings
    @danbills
    ok
    Rúnar
    @runarorama
    also, is attempt somehow interfering here?
    Daniel Spiewak might have a good idea
    Dan Billings
    @danbills
    I tested attemptrepeatedly with a schedule of two "ticks". It runs forever
    shouldn't the last line just be retries.XX instead of (step ++ retries)
    since they're zipped
    eh it still would only run once
    Dan Billings
    @danbills
    pretty sure I get it now. p.append appends a kill to an endless process
    in https://github.com/oncue/funnel/blob/master/core%2Fsrc%2Fmain%2Fscala%2FMonitoring.scala#L609
    Dan Billings
    @danbills
    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.
    I'll submit as such
    @runarorama ^
    Rúnar
    @runarorama
    Awesome. Thanks!