[🤖] Update Latest Dependency by dd-apm-ecosystems-autobot[bot] · Pull Request #5331 · DataDog/dd-trace-rb

dd-apm-ecosystems-autobot · 2026-02-08T00:31:13Z

This is an auto-generated PR from here, which creates a pull request that will be continually updated with new changes until it is merged or closed)

The PR updates latest versions of defined dependencies. Please review the changes and merge when ready.

github-actions · 2026-02-08T00:31:24Z

👋 Hey @DataDog/ruby-guild, please fill "Change log entry" section in the pull request description.

If changes need to be present in CHANGELOG.md you can state it this way

**Change log entry**

Yes. A brief summary to be placed into the CHANGELOG.md

(possible answers Yes/Yep/Yeah)

Or you can opt out like that

**Change log entry**

None.

(possible answers No/Nope/None)

^{Visited at: 2026-02-15 00:30:06 UTC}

datadog-official · 2026-02-08T00:49:23Z

⚠️ Tests

✨ Fix all issues with BitsAI or with Cursor

⚠️ Warnings

🧪 30 Tests failed

Dalli instrumentation behaves like environment service name when given `DD_TRACE_DALLI_SERVICE_NAME` environment variable when given service_name

from rspec (Datadog) (Fix with Cursor)

Response error: CLIENT_ERROR

Failure/Error: client.set('abc', 123)

Dalli::DalliError:
  Response error: CLIENT_ERROR
Shared Example Group: "environment service name" called from ./spec/datadog/tracing/contrib/dalli/instrumentation_spec.rb:33
/usr/local/bundle/gems/dalli-5.0.2/lib/dalli/protocol/response_processor.rb:199:in 'error_on_unexpected!'
/usr/local/bundle/gems/dalli-5.0.2/lib/dalli/protocol/response_processor.rb:90:in 'meta_set_with_cas'
/usr/local/bundle/gems/dalli-5.0.2/lib/dalli/protocol/meta.rb:130:in 'set'
...

Dalli instrumentation behaves like environment service name when given `DD_TRACE_DALLI_SERVICE_NAME` environment variable when none configured

from rspec (Datadog) (Fix with Cursor)

Response error: CLIENT_ERROR

Failure/Error: client.set('abc', 123)

Dalli::DalliError:
  Response error: CLIENT_ERROR
Shared Example Group: "environment service name" called from ./spec/datadog/tracing/contrib/dalli/instrumentation_spec.rb:33
/usr/local/bundle/gems/dalli-5.0.2/lib/dalli/protocol/response_processor.rb:199:in 'error_on_unexpected!'
/usr/local/bundle/gems/dalli-5.0.2/lib/dalli/protocol/response_processor.rb:90:in 'meta_set_with_cas'
/usr/local/bundle/gems/dalli-5.0.2/lib/dalli/protocol/meta.rb:130:in 'set'
...

Dalli instrumentation behaves like schema version span service name env var testing service name test with integration service name

from rspec (Datadog) (Fix with Cursor)

Response error: CLIENT_ERROR

Failure/Error: client.set('abc', 123)

Dalli::DalliError:
  Response error: CLIENT_ERROR
Shared Example Group: "schema version span" called from ./spec/datadog/tracing/contrib/dalli/instrumentation_spec.rb:47
/usr/local/bundle/gems/dalli-5.0.2/lib/dalli/protocol/response_processor.rb:199:in 'error_on_unexpected!'
/usr/local/bundle/gems/dalli-5.0.2/lib/dalli/protocol/response_processor.rb:90:in 'meta_set_with_cas'
/usr/local/bundle/gems/dalli-5.0.2/lib/dalli/protocol/meta.rb:130:in 'set'
...

View all

ℹ️ Info

❄️ No new flaky tests detected

_{This comment will be updated automatically if new data arrives.

🔗 Commit SHA: a2b0ff9 | Docs | Datadog PR Page | Was this helpful? React with 👍/👎 or give us feedback!}

pr-commenter · 2026-02-08T01:02:11Z

Benchmarks

Benchmark execution time: 2026-03-01 01:10:55

Comparing candidate commit f77c707 in PR branch auto-generate/update-latest-dependencies with baseline commit 1f3146f in branch master.

Found 0 performance improvements and 4 performance regressions! Performance is the same for 40 metrics, 2 unstable metrics.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

🟩 = significantly better candidate vs. baseline
🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

scenario:error - error tracking, with_error=true - third_party only

🟥 throughput [-626.607op/s; -578.949op/s] or [-5.604%; -5.178%]

scenario:line instrumentation - targeted

🟥 throughput [-12987.144op/s; -12383.815op/s] or [-9.926%; -9.465%]

scenario:line instrumentation - untargeted

🟥 throughput [-2391.816op/s; -2270.591op/s] or [-6.613%; -6.278%]

scenario:method instrumentation

🟥 throughput [-10975.071op/s; -10340.217op/s] or [-7.164%; -6.749%]

…actions/runs/22531930961

p-datadog · 2026-03-03T15:29:01Z

Closing this on assumption that a replacement PR will be made automatically.

dd-apm-ecosystems-autobot Bot added the dev/internal Other internal work that does not need to be included in the changelog label Feb 8, 2026

dd-apm-ecosystems-autobot Bot requested a review from a team as a code owner February 8, 2026 00:31

dd-apm-ecosystems-autobot Bot added the integrations Involves tracing integrations label Feb 8, 2026

makimoto mentioned this pull request Feb 13, 2026

[BUG]: Dalli 5.0 compatibility - uninitialized constant Dalli::Protocol::Binary #5358

Closed

dd-apm-ecosystems-autobot Bot force-pushed the auto-generate/update-latest-dependencies branch 2 times, most recently from aa4462c to b9f6018 Compare February 22, 2026 00:28

[🤖] Update Latest Dependency: https://github.com/DataDog/dd-trace-rb/…

f77c707

…actions/runs/22531930961

dd-apm-ecosystems-autobot Bot force-pushed the auto-generate/update-latest-dependencies branch from b9f6018 to f77c707 Compare March 1, 2026 00:41

Merge branch 'master' into auto-generate/update-latest-dependencies

a2b0ff9

p-datadog closed this Mar 3, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

[🤖] Update Latest Dependency#5331

[🤖] Update Latest Dependency#5331
dd-apm-ecosystems-autobot[bot] wants to merge 2 commits into
masterfrom
auto-generate/update-latest-dependencies

dd-apm-ecosystems-autobot Bot commented Feb 8, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Feb 8, 2026 •

edited

Loading

Uh oh!

datadog-official Bot commented Feb 8, 2026 •

edited by datadog-datadog-prod-us1-2 Bot

Loading

Uh oh!

pr-commenter Bot commented Feb 8, 2026 •

edited

Loading

Explanation

More details about the CI and significant changes

Uh oh!

p-datadog commented Mar 3, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

dd-apm-ecosystems-autobot Bot commented Feb 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions Bot commented Feb 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

datadog-official Bot commented Feb 8, 2026 • edited by datadog-datadog-prod-us1-2 Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ Warnings

ℹ️ Info

Uh oh!

pr-commenter Bot commented Feb 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Benchmarks

Explanation

More details about the CI and significant changes

scenario:error - error tracking, with_error=true - third_party only

scenario:line instrumentation - targeted

scenario:line instrumentation - untargeted

scenario:method instrumentation

Uh oh!

p-datadog commented Mar 3, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

dd-apm-ecosystems-autobot Bot commented Feb 8, 2026 •

edited

Loading

github-actions Bot commented Feb 8, 2026 •

edited

Loading

datadog-official Bot commented Feb 8, 2026 •

edited by datadog-datadog-prod-us1-2 Bot

Loading

pr-commenter Bot commented Feb 8, 2026 •

edited

Loading