Simon Baslé

for reference, this is the kind of boilerplate needed to make the wrapping scheduler approach work: code ```java public static final class DecoratingSchedulerFactory implements Factory { private static final Factory...

one other workaround would be to avoid fusion by including a `.hide()` between `sink.asFlux()` and `.publish()`. or even to avoid `.publish()` at all, since the `sink` is already multicast?? that...

this might be related to other issues with `windowTimeout`, which is under heavy rework in #2822

This seems related to #2897 as well. `publish()` and `autoConnect()` don't play well together, and I spent another day looking at it from multiple angles without finding a way to...

we'll consider it. note this is unlikely to happen soon as we would have to consider the building and hosting infrastructure for this, comparing with what our Spring siblings did,...

if somebody wants to have a try at the splitting of the documentation, go ahead and submit a PR. This is currently not something we have the bandwidth to deal...

This could be interesting, yes. Would take a bit of time shuffling through all the operators, so putting this in the [backburner] for now, but PRs would be welcome at...

This is low priority at the moment, so a bit of a stretch goal for 3.4.x, but one avenue to explore is to add a `Scannable.Attr`ibute, like what is currently...

This indeed sounds like something that needs fixing. Thanks for adding that other test case, we'll look into it 👍

Note: a probably partial answer would be to integrate notes about such support directly in the javadoc body (#2136), since the existing custom javadoc tag information is not displayed in...