Adam Fraser
Adam Fraser
I think those make sense as pipelines.
@eyalfa These operators are potentially quite confusing as the parent pipeline and the child pipelines are both reading from the upstream. It also goes against our idea that pipelines don't...
@eyalfa That is definitely not the signature of `flatMap` and that operator already exists. See `mapStream`.
@domdorn The change in the race semantics would if anything reduce CPU usage because you would be making sure that the connection was closed before continuing. There have been a...
@domdorn We also just released ZIO 2.0.8 with a couple of bug fixes. I don't think they are related to this but would be good to upgrade to make sure.
Yes this is an issue about 2.0.7 and we are on 2.0.13 at this point. I haven't seen any issues similar to this reported in a while so hopefully it...
@jeubank12 Thanks for reporting! Pull requests welcome!
Yes would be good to have a reproducer for this. This completes normally for example: ```scala test("async") { val stream = ZStream.async[Any, Nothing, Int] { cb => scala.scalajs.js.timers.setInterval(1000) { cb(ZIO.succeed(Chunk(1)))...
Okay. If it is an issue with `ZStream.async` we should be able to reproduce it with a simpler asynchronous process.
It isn't clear to me that any of these behaviors are incorrect. The key points are that racing or timing out a workflow does not impact the interruptibility of the...