TonyCTHsu

👋 @bpastiu , thanks for reporting. It seems to be a DNS failure. Could you provide more diagnostic information for us? like which version of `resque` and how do you...

Thanks @zmariscal , I will have a look!

> From [MySQL Bug #40986](https://bugs.mysql.com/bug.php?id=40986): > > ``` > '/* */'-style comments are fine and do not affect caching. > ``` > > This is possibly a workaround. This is...

Obsolete by: https://github.com/DataDog/dd-trace-rb/pull/4137

👋 @luc-financeit Thanks for reporting. I can reproduce it with ```ruby require "bundler/inline" gemfile { gem "datadog", "2.3.0", source: "https://rubygems.org" } require "datadog" Datadog.configure {} Process.waitall ``` Indeed, `Process.waitall` is...

We just released v2.2.0. Give it a try!

👋 @c2ofh , Thanks for reaching out. There are fields being removed from `Correlation::Identifier` in 2.x , https://github.com/DataDog/dd-trace-rb/blob/master/docs/UpgradeGuide2.md#log-correlation . > Information about trace_name, trace_resource, trace_service Those fields were not part...

👋 @Leee-xx Have you taken a look at this? https://github.com/danmayer/coverband?tab=readme-ov-file#solving-stack-level-too-deep-errors It seems like other gems are causing this with `alias_method`. We've documented here: https://github.com/DataDog/dd-trace-rb/blob/master/docs/GettingStarted.md#stack-level-too-deep

BTW, this change in gemspec should propagates to all the lockfiles under `gemfiles/*`. However, our automation does not kicked in. https://github.com/DataDog/dd-trace-rb/actions/runs/13176490545/attempts/1

I triggered again: https://github.com/DataDog/dd-trace-rb/actions/runs/13176490545