TonyCTHsu
TonyCTHsu
👋 @rahul342 [1.3.0](https://github.com/DataDog/dd-trace-rb/releases/tag/v1.3.0) has released!
@okhwaja Thanks for the reporting. I will have a look!
https://github.com/DataDog/dd-trace-rb/pull/2201#issuecomment-1204594941 👋 @okhwaja, I have taken a look into your concern about `start_active_span`, this should be fine. Since the empty `datadog_context` would be populated in [tracing](https://github.com/DataDog/dd-trace-rb/blob/master/lib/datadog/opentracer/tracer.rb#L146). From the disjointing flamegraph...
@okhwaja [1.3.0](https://github.com/DataDog/dd-trace-rb/releases/tag/v1.3.0) has released! Give it a try 🎉
@okhwaja Thanks for reporting, I am looking into this!
**TLDR**: The bug seems to be related to referring to stale span context during manual instrumentation with Opentracing, I have failing test ready and currently working on the fix at...
Hi @jorgemanrubia, I have taken a look into this scenario and try to reproduce in https://github.com/DataDog/dd-trace-rb/pull/2186 . (with Ruby 2.7 and Rails 6) In this PR, I could verified the...
👋 Thanks @wilsonehusin , I will be looking into this.
👋 @khrisnagunanasurya, our team is currently working on to figure out how to present those warning events instead of a hard error, using reporting [N+1 query as an example](https://github.com/DataDog/dd-trace-rb/pull/2239). It...
👋 Hi @khrisnagunanasurya, since you already have a workaround for it, and our exploration for solution will take time to mature. Do you think we could close the issue for...