tracing Duplicated traceId's when using Baggages

Hi! I've been observing duplicated traceId's when using .contextWrite(ReactorBaggage.append(...)) It looks like everything is fine when contextWrite is used once. Something wrong is happen when used twice. Please checkout this repo from branch baggage-tests: https://github.com/aswarcewicz/spring-demo-otel/tree/baggage-tests and open localhost:8080. I'm sure that some of the requests will have the same traceId

Feb 06 '24 19:02 aswarcewicz

Can you elaborate on "Something wrong is happen when used twice." ?

Feb 07 '24 09:02 marcingrzejszczak

I mean that I don’t know where exactly source of bug is, but I have observed that ‘contextWrite(ReactorBaggage…’ can be used only once, when used second time it causes duplicates of traceid

Feb 07 '24 18:02 aswarcewicz

@chemicL any ideas why is that happening?

Feb 08 '24 08:02 marcingrzejszczak

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Feb 16 '24 01:02 github-actions[bot]

Do you need additional details from me?

Feb 16 '24 15:02 aswarcewicz

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Feb 25 '24 01:02 github-actions[bot]

Is this still a problem? I upgraded to tracing 1.2.6 and have sent a few requests and the trace id is different each time...

May 27 '24 11:05 marcingrzejszczak

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Jun 04 '24 01:06 github-actions[bot]

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open.

Jun 11 '24 01:06 github-actions[bot]