-
Notifications
You must be signed in to change notification settings - Fork 318
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.35.0 proposal #3206
v2.35.0 proposal #3206
Conversation
* Add test for vulnerability evidence scrubber * Fix IAST SQL redaction with tainted contained in sensitive
'process' is the safer export strategy for heap profile export upon oom.
* introduce DD_TRACE_SPAN_ATTRIBUTE_SCHEMA env var * add attribute schema v0 for rhea * add attribute schema v1 for rhea * add test harness for service/operation naming * grab config object from pluginManager init * provide schema autoresolution in consumer/producer plugins * bind service to schema manager at configure time * rename plugins to match inbound/outbound service naming terminology * minimize test dependencies * naming resolution wrt version in the test object uses the Nomenclature, instead of being resolved by the test fixture * we no longer use the test fixture for _all_ existing tests, rather let the default resolution do the work * the testing fixture accepts a callback which is a minimal viable trace retrieval, on which we examine _only_ service and name * split test naming schema from test code * Apply service naming flow to messaging integrations (#2961) * add v0 to all messaging plugins * add v1 to all messaging plugins * test naming schema for all messaging integrations * add naming schema tests for other versions * bake messaging data into producer/consumer plugins * persist kind in plugins and infer naming subtype from kind+type * no logs on empty DD_SPAN_TRACE_ATTRIBUTE_SCHEMA * don't compute service name unless necessary
- attempting to fix flaky windows tests
Co-authored-by: Ugaitz Urien <[email protected]>
Adopt service naming schema in cache integrations --------- Co-authored-by: Thomas Hunter II <[email protected]>
* implement RC custom rules * update waf bindings to 3.2.0
--------- Co-authored-by: Stephen Belanger <[email protected]> Co-authored-by: Igor Unanua <[email protected]>
* Taint cookies and headers * Bump minimum node version for v4 on cookie plugin test * Add test with latest node version for cookie plugin test * Provide iastContext from index when tainting headers * Add test for cookie tainting in taint tracking plugin * Remove iast transaction after taint tracking plugin tests to avoid hiting setMaxTransactions in tests * Add test for taintObject with taintingKeys flag * Address header tainting test for keys shorter than 10 chars
- when DBM is set to full service - the DBM comment falls back to service mode - but only when sending a prepared statement - without this, each prepared statement query is technically different - this causes the pg library to fail as it does an exact string check of the query - ideally the pg library would somehow parse out and not consider comments - at any rate this brings parity with other tracer implementations - see brianc/node-postgres#2735 - previously attempted in 0ff9465
* Detect SSRF vulnerabilities * Fix test * Add space * Understand arguments in publisher instead of the subscriber * Redact sensitive information in SSRF vulnerabilities * Tiny style change * Tiny code styles * Use SSRF enum instead of literal * Try to reduce flaky test * Rename originalArgs to originalUrlAndOptions * Fix comment in PR * Do not normalize arguments twice in http/client.js
* Initial version of insecure-cookie vulnerability * Small fix * Add tests * rename const * Fix test * Exclude express file from insecure cookie stack trace * Some code styles + tests * Small code spaces * intermediate-cookies-analyzer to set-cookies-header-intercepteor * Comments in the PR * Comments in PR * Ignore insecure cookie when cookie value is empty * Reuse excluded paths array
* Update blocking page and status from RC or rules file * Use if/else instead of return * Code styles * Split block in two methods * Fix test * Unapply after test * Fix tests * Reorder params in method * Change the signature of updateBlockingConfiguration method * Clear blocking configuration on clear rules * Update blocking response type by configuration * Fix lint
* move http client to clientPlugin * move http2 client to clientPlugin
Overall package sizeSelf size: 4.23 MB Dependency sizes
🤖 This report was automatically generated by heaviest-objects-in-the-universe |
Codecov Report
@@ Coverage Diff @@
## v2.x #3206 +/- ##
==========================================
- Coverage 93.51% 87.11% -6.40%
==========================================
Files 222 330 +108
Lines 8829 12088 +3259
Branches 0 33 +33
==========================================
+ Hits 8256 10531 +2275
- Misses 573 1557 +984
... and 221 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
BenchmarksComparing candidate commit 2b5778d in PR branch Found 2 performance improvements and 42 performance regressions! Performance is the same for 617 metrics, 47 unstable metrics. scenario:appsec-control-with-attacks-14
scenario:appsec-control-14
scenario:log-skip-log-14
scenario:log-with-error-14
scenario:log-with-debug-14
scenario:log-without-log-14
scenario:appsec-appsec-enabled-with-attacks-14
scenario:log-with-debug-16
scenario:log-skip-log-16
scenario:log-with-error-16
scenario:log-without-log-16
scenario:appsec-appsec-enabled-with-attacks-16
scenario:startup-with-tracer-16
scenario:log-with-debug-18
scenario:log-with-error-18
scenario:log-skip-log-18
scenario:log-without-log-18
|
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.
looks good from ci visibility's perspective. Could we remove this item from the release notes, though, as it isn't interesting for the user at all:
- ci-visibility: Use new endpoint for code coverage ([ci-visibility] Use new endpoint for code coverage #3157)
Features
Improvements
cypress
#3159)Bug Fixes
git.properties
error log #3179)