Brian Clozel

@chemicL If I understand correctly, without this setting context propagation is only managed with the `tap`/`handle` operators, or by using `contextCapture`. Using this hook provided by reactor turns it on...

> Could it make sense to call Hooks.disableAutomaticContextPropagation() on context shutdown and/or when ContextPropagationMode != AUTO? > I was wondering if this particular solution could otherwise impact other Spring Context's...

>Given the Micrometer requirement for the hook to have an effect, I wonder if this should be auto-configured in spring-boot-actuator-autoconfigure rather than spring-boot-autoconfigure. I also wonder if the property prefix...

Hello @Ardreon The fact that your custom convention is called twice is an expected behavior in Micrometer Observations: conventions are called [once when the observation `start()`, and once more when...

Thanks very much for the analysis @Ardreon - I'm sure this will be useful to others!

Hello @Telamon-m, This sounds similar to #33921 - is there a Java agent somehow involved? Can you upgrade it or disable it to confirm?

@marcomima I guess the request you're sharing is from the point of view of the client? It would be interesting to see the same from the server's perspective. Could you...

@marcomima the fact that Tomcat 9.0.70 works with Spring Boot 2.7.8 leads me to think that this is indeed a Java agent issue - probably an instrumentation not being compatible...

We've added support for `ProblemDetail` in #32634 with a configuration flag. This support was brand new at the time and we wanted to introduce it progressively to avoid too much...

I think this issue is conflating several existing issues in Spring Framework and Spring Boot. First, the fact that a regular JSON serialization can use the `application/problemdetails+json` media type, without...