-
Notifications
You must be signed in to change notification settings - Fork 306
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v2.38.0 #3315
v2.38.0 #3315
Conversation
Co-authored-by: Thomas Hunter II <tlhunter@datadog.com>
Overall package sizeSelf size: 4.74 MB Dependency sizes
🤖 This report was automatically generated by heaviest-objects-in-the-universe |
Codecov Report
@@ Coverage Diff @@
## v2.x #3315 +/- ##
==========================================
- Coverage 93.51% 86.24% -7.27%
==========================================
Files 222 202 -20
Lines 8829 7940 -889
Branches 0 33 +33
==========================================
- Hits 8256 6848 -1408
- Misses 573 1092 +519
... and 318 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
BenchmarksComparing candidate commit e14b13d in PR branch Found 1 performance improvements and 0 performance regressions! Performance is the same for 692 metrics, 45 unstable metrics. scenario:plugin-graphql-with-depth-off-18
|
FailuresPostgresThis issue isn't obvious. Seems like we're expecting
HTTPPossibly due to the merge conflict from first commit but I'm not sure.
Integration (all 5 of them)Probably due to the merge conflict in the first commit.
|
So the conflict comes down to this file in this pull request. In the pull request the following line remains the same: const span = web.startSpan(this.tracer, this.config, req, res, 'web.request') However, in the conflicted change, the line changes like so: - const span = web.startSpan(this.tracer, this.config, req, res, 'http.request')
+ const span = web.startSpan(this.tracer, this.config, req, res, 'web.request') So it seems that the v2.x branch expects a value of http.request while v3.x and v4.x expects web.request. |
* add cassandra-driver versions * add elasticsearch/opensearch versions * add mongodb versions * add pg versions * add oracledb versions
5cc7de6
to
c846514
Compare
According to Roch, |
Alright, it looks like that change (a new commit, the second in line) fixed everything except for the pg bug. For that maybe we bump the supported pg version range since the failing version is incredibly old? |
c846514
to
5736df9
Compare
The final failing test, aws-sdk, has started failing everywhere as of an hour or two ago: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK from ci visibility's perspective
* introduce peer service computation for outbound edges: * add DD_TRACE_SPAN_PEER_SERVICE environment variable * add peer service computation logic * TODO: add tests for config, outbound, tracer (?) * provide a helper for testing peer service computation * defer plugin `finish` to TracingPlugin in children
- adds support for the OpenAI package - includes many things that aren't typical with our other integrations - also sends metrics, even when runtime metrics are disabled for the tracer - also sends logs directly to the datadog backend, bypassing the agent - overall this is the most intricate of any integration we've had so far
* Wrap express process_params to taint route params * Add taint tracking plugin test for route params * Change name of express process params channel * Return process_param result * Address taint tracking plugin subscriptions test
* Add passport local and http instrumentations. * Add automated event tracking in appsec.. --------- Co-authored-by: Carles Capell <107924659+CarlesDD@users.noreply.github.com> Co-authored-by: simon-id <simon.id@datadoghq.com>
5736df9
to
e14b13d
Compare
Features
Improvements
ServerPlugins
(moveHttpServer
,Http2Server
plugins toServerPlugin
s #3261)Bug Fixes