You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the mono coroutine and awaitSingle for the subscriber context in the suspended function it seems the subscriber context is not "propagated".
This example prints Context0{} when Context1{foo=bar} is expected.
I tried to understand the code to see where this is coming from but sadly couldn't understand it. The sink in Mono.defer has the subscriber context correctly available, this I saw while debugging.
The text was updated successfully, but these errors were encountered:
This is the expected behaviour (for now).
You have two independent monos: one created with CoroutineScope(Dispatchers.Unconfined).mono and another one created and immediately subscribed with Mono.subscriberContext().awaitSingle(). They have nothing in common and thus one context is not propagated to another one.
When using the
mono
coroutine andawaitSingle
for the subscriber context in the suspended function it seems the subscriber context is not "propagated".This example prints
Context0{}
whenContext1{foo=bar}
is expected.Using reactor 3.3.0.M1, kotlin-coroutines 1.2.1
I tried to understand the code to see where this is coming from but sadly couldn't understand it. The
sink
inMono.defer
has the subscriber context correctly available, this I saw while debugging.The text was updated successfully, but these errors were encountered: