Dariusz Jędrzejczyk

Hi. Thanks for providing the background and suggestions. I am no Kotlin expert by any means, so I can't speak whether the `ContextInjector` mechanism combined with `@OptIn` is a desired...

@mp911de Hey :) I was summoned here from https://github.com/reactor/reactor-core/issues/3695. Please note that the original reporter is not using the `usingWhen` operator. I am trying to understand the issues that users...

@agorbachenko thanks for the quick response. I was not aware of the internals in Spring, I just had a look at r2dbc sources. I'll have a look then!

Thanks @SimoneGiusso. We experimented together with @mp911de today with both examples. Thanks for providing your version of it! What I can say is that `usingWhen` is definitely not at fault...

What I have found is that the connection acquisition is working properly and the connection is not stuck in the pool, but is being held by an actor that fails...

Hey, @cyberluke 👋 I'm afraid I don't understand - r2dbc-lab has no actual dependency on H2 nor Postgresql. It uses only mocks with r2dbc-pool, r2dbc-spi, and r2dbc-spi-test. Can you elaborate?...

As a follow up to this issue, if desired, reactor-kotlin-extensions could replace the usage of `Retry` and `Repeat` from reactor-extras with the equivalents from reactor-core and de-deprecate the methods that...

AFAIK, Spring has no official gRPC support. Whichever community supported project that the `GrpcGlobalServerInterceptor` comes from would need to support `Observation` just like Spring does for this to work without...

Be my guest @injae-kim :)

It looks like it's not the test configuration that is broken but some operator along doesn't honour the demand. If the TCK's Subscriber demands 15 items, any configuration that we...