Artem Bilan

Strange that this is still not fixed. I believe the problem is here in the `BaseAsyncClientHandler.doExecute()`: ``` invoke(marshalled, finalizeSdkHttpRequestContext.asyncRequestBody().orElse(null), inputT, executionContext, new AsyncAfterTransmissionInterceptorCallingResponseHandler(asyncResponseHandler, executionContext)); ``` That `new AsyncAfterTransmissionInterceptorCallingResponseHandler()` is never...

The related Spring Framework issue regarding method argument resolver has been fixed: https://github.com/spring-projects/spring-framework/issues/28945 Now we can produce a message with `Optional.empty()` and it is going to be handled in POJO...

Looks like this is this your SO question, too: https://stackoverflow.com/questions/76015312/how-to-properly-deal-with-zombie-kafka-consumers-in-reactive-spring-boot-appli

I see. Any thoughts about the possible fix? Or share, please, with us what part of the project code you think is producing such a bug?

I think you are right and we definitely can use that `SftpClientDirectoryScanner` in the `list(String path, boolean recurse)` API we propose for this fix. The pattern matching is out of...

Any contribution is welcome! If that really uses Spring Integration concepts and principles, we are fine to accept such a Pull Request. Unfortunately we are not familiar with Kotlin and...

Gary is not with our team any more, so don't expect any answers from him. I'm not familiar with this `out of order commit` and have some other priorities to...

When you mention Spring Boot and its WebFlux server, you don't compare apples with apples in this project. The Reactor Kafka is just a library when you use an API...

See an Observation support in the upcoming release: https://github.com/reactor/reactor-kafka/blob/main/src/docs/asciidoc/api-guide.adoc#micrometer-observation. The rest of questions about parallel scheduler and buffers are out of this project scope. See general Reactor docs: https://projectreactor.io/docs/core/release/reference/#_observation https://projectreactor.io/docs/core/release/reference/#context.propagation...

See `KafkaRecordReceiverContext` source code: https://github.com/reactor/reactor-kafka/blob/main/src/main/java/reactor/kafka/receiver/observation/KafkaRecordReceiverContext.java#L37 So, that is a `receiverId` - a unique id for the `reactor.kafka.client.id` tag in the target span. Logical identifier of your Reactor Kafka service.