-
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.41.0 proposal #3384
v2.41.0 proposal #3384
Conversation
Overall package sizeSelf size: 4.88 MB Dependency sizes
🤖 This report was automatically generated by heaviest-objects-in-the-universe |
Codecov Report
@@ Coverage Diff @@
## v2.x #3384 +/- ##
==========================================
- Coverage 93.51% 84.95% -8.56%
==========================================
Files 222 212 -10
Lines 8829 8415 -414
Branches 0 33 +33
==========================================
- Hits 8256 7149 -1107
- Misses 573 1266 +693
... and 332 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
* add dc store binding polyfill and migrate http2 * fix error handling for synchronous exceptions * OutboundPlugin#tagPeerService() --------- Co-authored-by: Thomas Hunter II <tlhunter@datadog.com>
* ciapp-3571: add url validator * ciapp-3571: add url validator and change tests from ci-spec * fix variables to follow camelcase * Remove valid import Co-authored-by: Juan Antonio Fernández de Alba <juan.fernandezdealba@datadoghq.com> * Remove unnecessary check Co-authored-by: Juan Antonio Fernández de Alba <juan.fernandezdealba@datadoghq.com> * Remove unnecessary check for CI_PIPELINE_URL Co-authored-by: Juan Antonio Fernández de Alba <juan.fernandezdealba@datadoghq.com> * Format typo Co-authored-by: Juan Antonio Fernández de Alba <juan.fernandezdealba@datadoghq.com> * Use validateMetadata return directly Co-authored-by: Juan Antonio Fernández de Alba <juan.fernandezdealba@datadoghq.com> * use new ci-spec JSONs * fix spacing and sort imports * add test to validateMetadata * Update JSONs and refactor URL checking * Update JSONs and refactor URL checking * Add URL validation tests * Apply suggestions from code review Co-authored-by: Juan Antonio Fernández de Alba <juan.fernandezdealba@datadoghq.com> * Add tag to test suite --------- Co-authored-by: Juan Antonio Fernández de Alba <juan.fernandezdealba@datadoghq.com>
* Add framework type checking * Improve code readability Co-authored-by: Juan Antonio Fernández de Alba <juan.fernandezdealba@datadoghq.com> * Fix imports * Fix styling Co-authored-by: Juan Antonio Fernández de Alba <juan.fernandezdealba@datadoghq.com> * Add cypress and playwright tests * Change browser conditions to detect all playwright instances * Fix include string * Fix some suites still being reported as test type --------- Co-authored-by: Juan Antonio Fernández de Alba <juan.fernandezdealba@datadoghq.com>
* Remove cpu-experimental profiler * Adapt to API changes in pprof-nodejs
…tests were actually skipped (#3369)
Co-authored-by: Ugaitz Urien <ugaitz.urien@datadoghq.com>
* Convert grpc to use tracing channel * Allow addError to accept explicit span rather than delegating to activeSpan
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. Only feedback is to change "civis" to ci-visibility
in the release notes
Supplying a `DD_TRACE_PEER_SERVICE_MAPPING` allows users to modify the `peer.service` tag in the same manner that `DD_SERVICE_MAPPING` does for service name. If the `peer.service` value was matched by the mapping, the original value of the tag before remapping is reported in `_dd.peer.service.remapped_from`.
83990b9
BenchmarksBenchmark execution time: 2023-07-14 00:41:29 Comparing candidate commit c959a66 in PR branch Found 54 performance improvements and 0 performance regressions! Performance is the same for 648 metrics, 33 unstable metrics. scenario:appsec-iast-no-vulnerability-control-12
scenario:appsec-iast-no-vulnerability-control-14
scenario:appsec-iast-no-vulnerability-control-16
scenario:appsec-iast-no-vulnerability-iast-enabled-always-active-12
scenario:appsec-iast-no-vulnerability-iast-enabled-always-active-14
scenario:appsec-iast-no-vulnerability-iast-enabled-always-active-16
scenario:appsec-iast-no-vulnerability-iast-enabled-default-config-12
scenario:appsec-iast-no-vulnerability-iast-enabled-default-config-14
scenario:appsec-iast-no-vulnerability-iast-enabled-default-config-16
scenario:appsec-iast-with-vulnerability-control-12
scenario:appsec-iast-with-vulnerability-control-14
scenario:appsec-iast-with-vulnerability-control-16
scenario:appsec-iast-with-vulnerability-iast-enabled-always-active-12
scenario:appsec-iast-with-vulnerability-iast-enabled-always-active-14
scenario:appsec-iast-with-vulnerability-iast-enabled-always-active-16
scenario:appsec-iast-with-vulnerability-iast-enabled-default-config-12
scenario:appsec-iast-with-vulnerability-iast-enabled-default-config-14
scenario:appsec-iast-with-vulnerability-iast-enabled-default-config-16
scenario:log-without-log-16
|
Features
test.type
in browser tests #3358)Bug Fixes