These are chat archives for oncue/funnel

14th
Apr 2016
Dan Billings
@danbills
Apr 14 2016 18:36
@runarorama I'm trying to validate via unit test that the Discard command to a Flask will disconnect from a host.
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
Apr 14 2016 18:40
that's a good idae
idea
Dan Billings
@danbills
Apr 14 2016 18:41
brb
Rúnar
@runarorama
Apr 14 2016 18:57
seems like maybe processMirroringEvents is doing something nefarious
Dan Billings
@danbills
Apr 14 2016 18:58
My hunch is attemptRepeatedly
Rúnar
@runarorama
Apr 14 2016 18:59
p.append(schedule.kill).attempt(e => Process.eval { Task.delay { maskedError(e); e }})
append(schedule.kill) specifically
Dan Billings
@danbills
Apr 14 2016 19:00
going by documentation that kill command should "giving chance for any cleanup actions to be run"
Rúnar
@runarorama
Apr 14 2016 19:01
check if io.resource cleanup actually survives appends
Dan Billings
@danbills
Apr 14 2016 19:01
ok
Rúnar
@runarorama
Apr 14 2016 19:01
also, is attempt somehow interfering here?
Daniel Spiewak might have a good idea
Dan Billings
@danbills
Apr 14 2016 19:10
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
Apr 14 2016 19:34
pretty sure I get it now. p.append appends a kill to an endless process
Dan Billings
@danbills
Apr 14 2016 19:39
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
Apr 14 2016 19:57
Awesome. Thanks!