Skip to content

Conversation

@BridgeAR
Copy link
Collaborator

@BridgeAR BridgeAR commented Jan 16, 2026

To make sure this does not happen anywhere else, generally throw an error in our tests to verify our instrumentations do not trigger any of deprecation warning.

The positive side effect is, that we will know earlier when things are deprecated and can fix them before things actually get changed and we keep customers happier that way due to better overall support.

Fixes: #7267

@github-actions
Copy link

github-actions bot commented Jan 16, 2026

Overall package size

Self size: 4.4 MB
Deduped: 5.22 MB
No deduping: 5.22 MB

Dependency sizes | name | version | self size | total size | |------|---------|-----------|------------| | import-in-the-middle | 2.0.0 | 68.46 kB | 797.03 kB | | dc-polyfill | 0.1.10 | 26.73 kB | 26.73 kB |

🤖 This report was automatically generated by heaviest-objects-in-the-universe

@datadog-official
Copy link

datadog-official bot commented Jan 16, 2026

✅ Tests

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 0dd0883 | Docs | Datadog PR Page | Was this helpful? Give us feedback!

@codecov
Copy link

codecov bot commented Jan 16, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.17%. Comparing base (271f39d) to head (0dd0883).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #7269      +/-   ##
==========================================
+ Coverage   80.04%   85.17%   +5.13%     
==========================================
  Files         393      532     +139     
  Lines       18155    22788    +4633     
==========================================
+ Hits        14532    19410    +4878     
+ Misses       3623     3378     -245     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@pr-commenter
Copy link

pr-commenter bot commented Jan 17, 2026

Benchmarks

Benchmark execution time: 2026-01-19 15:58:46

Comparing candidate commit 0dd0883 in PR branch BridgeAR/2026-01-16-check-against-deprecations with baseline commit 271f39d in branch master.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 230 metrics, 30 unstable metrics.

Just do a brief check what property exists before accessing it.

To make sure this does not happen anywhere else, generally throw
an error in our tests to verify our instrumentations do not trigger
any of deprecation warning.

The positive side effect is, that we will know earlier when things
are deprecated and can fix them before things actually get changed
and we keep customers happier that way due to better overall support.

Fixes: #7267
@BridgeAR BridgeAR force-pushed the BridgeAR/2026-01-16-check-against-deprecations branch from 07f537e to 0dd0883 Compare January 19, 2026 15:50
@BridgeAR BridgeAR marked this pull request as ready for review January 19, 2026 15:51
@BridgeAR BridgeAR requested review from a team as code owners January 19, 2026 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG]: pg deprecation warning when accesing Client.activeQuery

2 participants