Fork me on GitHub

I’ve got a strange issue with core.async where using timeout deep inside an async process causes core.async to lock up completely. I’ve posted a more in depth question & sample code over the and would love to understand what on earth is going wrong


@kennethkalmer I'm not that familiar with transducers, but it's sortof like a more powerful reducer? On line 23, is this result being passed back into process-n?


if that's the case, your async/timeout is receiving an ever increasing n value,


which might make it look like it's locking up, because the timeout hits >1s after only 10 iterations, not sure if this is the case


the values will always be < 10, so the timeout will be up to 1s max


calling (process-n 10) by itself will take 1s, but when (process-n 10) is called inside (async/pipeline) it just blocks, but with (async/pipeline-blocking) it seems to work


however, that means my example no longer matches the issue I’m experiencing in my code facepalm