grassehh

Hello, any update about this ?

> I have just added the last part of Spring Framework 6.1 `CoroutineContext` refinement: it is now possible to propagate it via `CoWebFilter`. [spring-projects/spring-framework#27522](https://github.com/spring-projects/spring-framework/issues/27522) Thanks for these new features. However,...

Hello, I just wanted to share the sample I created (which I shared already in other issues). I thought it could be useful for you to try : https://github.com/grassehh/spring-boot-3-tracing-coroutine In...

> @grassehh here are the changes I made to your repo - basically just upgrading versions to get to Spring Framework 6.1 snapshots and the code in [#174 (comment)](https://github.com/micrometer-metrics/tracing/issues/174#issuecomment-1727691192). With...

> PS: The receive pipeline can be manually triggered by something like this (here, I added `call.receiveText()` to your code): > > ```kotlin > data class SomeData(val someProp: String) >...

Hello, @ChristianLohmann @msdousti, is there any update about the `No instance for key AttributeKey: Logbook.ResponseProcessingStage` issue ?

Hello, I just noticed the same issue is true for logbook-ktor-client. As soon as I as a logback.xml file in my classpath, the `Content-Type` gets removed. This also means that...

Thanks @msdousti. I have added some comments. As for the `logbook-ktor-client` I have created the issue with a possible fix: [https://github.com/zalando/logbook/issues/1821](https://github.com/zalando/logbook/issues/1821) I have detected another issue when sending/receiving requests with...

@kasmarian indeed, the traceId and spanId appears, but not the custom baggages. Also, the traceId is not the same. Here's an example: ``` -MDC:[traceId=657345d5ade6a80c2d65bba5e4f03aaa, spanId=9f7e35b0d94b7997, myBaggageController=5aefb488-62a3-48ea-961b-ec07a6a7e2f2, myBaggageFilter=658a418b-1222-40d0-8bc4-75e4a7cff490] -2023-12-08T17:35:33.867+01:00 -DEBUG 85932...

@kasmarian It's quite confusing because I think there were multiple problems in the same issue.. But to sum it up, with 6.1.2-SNAPSHOT, the "traceId" and "spanId" reappear in the context....