Sébastien Deleuze

Results 631 comments of Sébastien Deleuze

I have added the repro as a unit test [here](https://github.com/sdeleuze/spring-framework/commit/gh-22313). With declaration-site variance, there is a type mismatch in `GenericTypeAwareAutowireCandidateResolver#checkGenericTypeMatch` [here](https://github.com/spring-projects/spring-framework/blob/9eb1fbd5c38244f0878cd4ea3e3253decef2f8d0/spring-beans/src/main/java/org/springframework/beans/factory/support/GenericTypeAwareAutowireCandidateResolver.java#L155) because in `ResolvableType#isAssignableFrom(ResolvableType, Map)`: - The type of `fun...

I am waiting a feedback from Kotlin team, so I will move this issue to M3.

Kotlin team is on PTO, so I have to move this issue to RC1 (tentatively).

Kotlin team confirmed my proposal to resolve generic types with variance make sense, ~~should be testable on Java via use-site variance~~. So I will move forward with that strategy and...

After a deeper look, it looks like we are going to need to leverage Kotlin reflection in either `GenericTypeAwareAutowireCandidateResolver` or `ResolvableType` bounds resolution because the Java algorithm looks correct, but...

I move this issue to `6.1.x` bucket in order to be able to move forward on CRaC and Coroutines refinements. Since this issue will likely be about Kotlin-specific refinements, it...

@qnnn Is this use case of headers filtering/reconstruction in `org.springframework.cloud.gateway.filter.headers.RemoveHopByHopHeadersFilter` is the only concrete bug you face or are there other ones (if yes, which ones)?

Thanks, that helps. We are discussing the best strategy to fix those bugs while keeping a great performance/efficiency. We will get back to you once we have made a decision.

This error easy to reproduce is super difficult to diagnose. The best I had was by adding `io.projectreactor:reactor-core` dependency and `-H:AbortOnTypeReachable=reactor.core.publisher.Mono` which gave me the following error message: "Type reactor.core.publisher.Mono...

@mp911de The functional scope of those utils make sense to me, we may end up to refine some public API and implementation, especially if we are able to move forward...