Johan Andrén

Hmm, maybe not, we do have `assertNoChildren` in a fixture that should be used.

https://github.com/akka/akka/actions/runs/4856177177/jobs/8655457782#step:5:16462

You will have to condense that down to a more minimal reproducer, without any pools or synchronization primitives, preferably just a single actor that you send messages to concurrently that...

The pattern matching in your PriorityGenerator is incorrect and will return priority 7 for all your messages.

I think this is more of a question than anything else, please use the forums over at https://discuss.akka.io to ask for help about how to achieve what you want to...

@shobull it does propagate cancellations, but errors is not propagated upstream across reactive streams publishers/subscribers, so they will look like a cancellation on the sink side, while for pure Akka...

I agree that can be surprising. We should at least document it clearly in the `preMaterialize` API and operator docs. A new implementation of `preMaterialize` that works more like any...

I think the compression rate is the most curios thing, since `Compression.gzip` and `GZIPOutputstream` are both backed with `java.util.zip.Deflater`/`zlib`.

One of the failing tests was ftps, let's run again and see if it was a random failure

As in, it was already failing?