feat: add initial python 3.14 support#14264
Conversation
|
|
Bootstrap import analysisComparison of import times between this PR and base. SummaryThe average import time from this PR is: 242 ± 3 ms. The average import time from base is: 245 ± 3 ms. The import time difference between this PR and base is: -2.4 ± 0.1 ms. Import time breakdownThe following import paths have shrunk:
|
Performance SLOsComparing candidate bump-3-14-riotfile (3ab2dd6) with baseline main (967ff6d) 🟡 Near SLO Breach (5 suites)🟡 djangosimple - 30/30✅ appsecTime: ✅ 20.473ms (SLO: <22.300ms -8.2%) vs baseline: ~same Memory: ✅ 65.517MB (SLO: <67.000MB -2.2%) vs baseline: +4.9% ✅ exception-replay-enabledTime: ✅ 1.347ms (SLO: <1.450ms -7.1%) vs baseline: -0.4% Memory: ✅ 64.472MB (SLO: <67.000MB -3.8%) vs baseline: +4.8% ✅ iastTime: ✅ 20.435ms (SLO: <22.250ms -8.2%) vs baseline: -0.3% Memory: ✅ 65.563MB (SLO: <67.000MB -2.1%) vs baseline: +4.8% ✅ profilerTime: ✅ 15.260ms (SLO: <16.550ms -7.8%) vs baseline: ~same Memory: ✅ 53.725MB (SLO: <54.500MB 🟡 -1.4%) vs baseline: +4.9% ✅ resource-renamingTime: ✅ 20.585ms (SLO: <21.750ms -5.4%) vs baseline: +0.1% Memory: ✅ 65.493MB (SLO: <67.000MB -2.2%) vs baseline: +4.7% ✅ span-code-originTime: ✅ 26.145ms (SLO: <28.200ms -7.3%) vs baseline: -0.2% Memory: ✅ 67.685MB (SLO: <69.500MB -2.6%) vs baseline: +5.0% ✅ tracerTime: ✅ 20.485ms (SLO: <21.750ms -5.8%) vs baseline: ~same Memory: ✅ 65.483MB (SLO: <67.000MB -2.3%) vs baseline: +4.8% ✅ tracer-and-profilerTime: ✅ 22.054ms (SLO: <23.500ms -6.2%) vs baseline: ~same Memory: ✅ 66.827MB (SLO: <67.500MB 🟡 -1.0%) vs baseline: +5.2% ✅ tracer-dont-create-db-spansTime: ✅ 19.316ms (SLO: <21.500ms 📉 -10.2%) vs baseline: ~same Memory: ✅ 65.419MB (SLO: <66.000MB 🟡 -0.9%) vs baseline: +4.6% ✅ tracer-minimalTime: ✅ 16.629ms (SLO: <17.500ms -5.0%) vs baseline: ~same Memory: ✅ 65.178MB (SLO: <66.000MB 🟡 -1.2%) vs baseline: +4.8% ✅ tracer-nativeTime: ✅ 20.466ms (SLO: <21.750ms -5.9%) vs baseline: ~same Memory: ✅ 71.349MB (SLO: <72.500MB 🟡 -1.6%) vs baseline: +4.8% ✅ tracer-no-cachesTime: ✅ 18.464ms (SLO: <19.650ms -6.0%) vs baseline: +0.1% Memory: ✅ 65.426MB (SLO: <67.000MB -2.3%) vs baseline: +4.9% ✅ tracer-no-databasesTime: ✅ 18.763ms (SLO: <20.100ms -6.7%) vs baseline: -0.2% Memory: ✅ 65.181MB (SLO: <67.000MB -2.7%) vs baseline: +5.0% ✅ tracer-no-middlewareTime: ✅ 20.188ms (SLO: <21.500ms -6.1%) vs baseline: ~same Memory: ✅ 65.484MB (SLO: <67.000MB -2.3%) vs baseline: +4.7% ✅ tracer-no-templatesTime: ✅ 20.307ms (SLO: <22.000ms -7.7%) vs baseline: -0.3% Memory: ✅ 65.414MB (SLO: <67.000MB -2.4%) vs baseline: +4.7% 🟡 errortrackingdjangosimple - 6/6✅ errortracking-enabled-allTime: ✅ 18.124ms (SLO: <19.850ms -8.7%) vs baseline: +0.2% Memory: ✅ 65.372MB (SLO: <66.500MB 🟡 -1.7%) vs baseline: +4.9% ✅ errortracking-enabled-userTime: ✅ 18.057ms (SLO: <19.400ms -6.9%) vs baseline: ~same Memory: ✅ 65.392MB (SLO: <66.500MB 🟡 -1.7%) vs baseline: +5.1% ✅ tracer-enabledTime: ✅ 18.185ms (SLO: <19.450ms -6.5%) vs baseline: +0.6% Memory: ✅ 65.294MB (SLO: <66.500MB 🟡 -1.8%) vs baseline: +4.7% 🟡 flasksimple - 18/18✅ appsec-getTime: ✅ 4.572ms (SLO: <4.750ms -3.7%) vs baseline: -0.2% Memory: ✅ 61.912MB (SLO: <65.000MB -4.8%) vs baseline: +4.7% ✅ appsec-postTime: ✅ 6.559ms (SLO: <6.750ms -2.8%) vs baseline: -0.3% Memory: ✅ 61.951MB (SLO: <65.000MB -4.7%) vs baseline: +4.8% ✅ appsec-telemetryTime: ✅ 4.572ms (SLO: <4.750ms -3.8%) vs baseline: +0.2% Memory: ✅ 62.010MB (SLO: <65.000MB -4.6%) vs baseline: +5.1% ✅ debuggerTime: ✅ 1.854ms (SLO: <2.000ms -7.3%) vs baseline: -0.5% Memory: ✅ 45.436MB (SLO: <47.000MB -3.3%) vs baseline: +4.9% ✅ iast-getTime: ✅ 1.860ms (SLO: <2.000ms -7.0%) vs baseline: -0.6% Memory: ✅ 42.369MB (SLO: <49.000MB 📉 -13.5%) vs baseline: +5.2% ✅ profilerTime: ✅ 1.907ms (SLO: <2.100ms -9.2%) vs baseline: -0.5% Memory: ✅ 46.616MB (SLO: <47.000MB 🟡 -0.8%) vs baseline: +5.2% ✅ resource-renamingTime: ✅ 3.380ms (SLO: <3.650ms -7.4%) vs baseline: -0.3% Memory: ✅ 52.199MB (SLO: <53.500MB -2.4%) vs baseline: +4.8% ✅ tracerTime: ✅ 3.369ms (SLO: <3.650ms -7.7%) vs baseline: ~same Memory: ✅ 52.219MB (SLO: <53.500MB -2.4%) vs baseline: +4.9% ✅ tracer-nativeTime: ✅ 3.371ms (SLO: <3.650ms -7.6%) vs baseline: +0.1% Memory: ✅ 57.990MB (SLO: <60.000MB -3.3%) vs baseline: +4.4% 🟡 otelspan - 22/22✅ add-eventTime: ✅ 45.325ms (SLO: <47.150ms -3.9%) vs baseline: +0.3% Memory: ✅ 45.268MB (SLO: <47.000MB -3.7%) vs baseline: +4.8% ✅ add-metricsTime: ✅ 321.384ms (SLO: <344.800ms -6.8%) vs baseline: +0.5% Memory: ✅ 553.279MB (SLO: <562.000MB 🟡 -1.6%) vs baseline: +4.9% ✅ add-tagsTime: ✅ 291.302ms (SLO: <314.000ms -7.2%) vs baseline: +0.2% Memory: ✅ 554.971MB (SLO: <563.500MB 🟡 -1.5%) vs baseline: +5.0% ✅ get-contextTime: ✅ 82.819ms (SLO: <92.350ms 📉 -10.3%) vs baseline: +0.3% Memory: ✅ 40.279MB (SLO: <46.500MB 📉 -13.4%) vs baseline: +5.0% ✅ is-recordingTime: ✅ 43.468ms (SLO: <44.500ms -2.3%) vs baseline: +1.1% Memory: ✅ 44.583MB (SLO: <47.500MB -6.1%) vs baseline: +4.5% ✅ record-exceptionTime: ✅ 61.638ms (SLO: <67.650ms -8.9%) vs baseline: -0.4% Memory: ✅ 40.589MB (SLO: <47.000MB 📉 -13.6%) vs baseline: +4.7% ✅ set-statusTime: ✅ 48.754ms (SLO: <50.400ms -3.3%) vs baseline: +0.6% Memory: ✅ 44.720MB (SLO: <47.000MB -4.9%) vs baseline: +5.2% ✅ startTime: ✅ 42.091ms (SLO: <43.450ms -3.1%) vs baseline: ~same Memory: ✅ 44.596MB (SLO: <47.000MB -5.1%) vs baseline: +4.6% ✅ start-finishTime: ✅ 84.617ms (SLO: <88.000ms -3.8%) vs baseline: +2.0% Memory: ✅ 34.583MB (SLO: <46.500MB 📉 -25.6%) vs baseline: +4.8% ✅ start-finish-telemetryTime: ✅ 84.480ms (SLO: <89.000ms -5.1%) vs baseline: +0.4% Memory: ✅ 34.623MB (SLO: <46.500MB 📉 -25.5%) vs baseline: +5.0% ✅ update-nameTime: ✅ 44.265ms (SLO: <45.150ms 🟡 -2.0%) vs baseline: ~same Memory: ✅ 44.948MB (SLO: <47.000MB -4.4%) vs baseline: +4.7% 🟡 packagesupdateimporteddependencies - 24/24✅ import_manyTime: ✅ 155.838µs (SLO: <170.000µs -8.3%) vs baseline: +0.4% Memory: ✅ 37.083MB (SLO: <38.500MB -3.7%) vs baseline: +3.3% ✅ import_many_cachedTime: ✅ 121.479µs (SLO: <130.000µs -6.6%) vs baseline: ~same Memory: ✅ 37.101MB (SLO: <38.500MB -3.6%) vs baseline: +4.0% ✅ import_many_stdlibTime: ✅ 1.625ms (SLO: <1.750ms -7.2%) vs baseline: ~same Memory: ✅ 37.275MB (SLO: <38.500MB -3.2%) vs baseline: +4.4% ✅ import_many_stdlib_cachedTime: ✅ 0.967ms (SLO: <1.100ms 📉 -12.1%) vs baseline: -0.4% Memory: ✅ 37.803MB (SLO: <38.500MB 🟡 -1.8%) vs baseline: +6.0% ✅ import_many_unknownTime: ✅ 834.401µs (SLO: <890.000µs -6.2%) vs baseline: +0.2% Memory: ✅ 37.182MB (SLO: <38.500MB -3.4%) vs baseline: +3.2% ✅ import_many_unknown_cachedTime: ✅ 788.588µs (SLO: <870.000µs -9.4%) vs baseline: -1.0% Memory: ✅ 37.275MB (SLO: <38.500MB -3.2%) vs baseline: +3.9% ✅ import_oneTime: ✅ 19.958µs (SLO: <30.000µs 📉 -33.5%) vs baseline: +0.4% Memory: ✅ 36.953MB (SLO: <39.000MB -5.2%) vs baseline: +3.9% ✅ import_one_cacheTime: ✅ 6.266µs (SLO: <10.000µs 📉 -37.3%) vs baseline: -1.1% Memory: ✅ 37.080MB (SLO: <38.500MB -3.7%) vs baseline: +4.5% ✅ import_one_stdlibTime: ✅ 18.737µs (SLO: <20.000µs -6.3%) vs baseline: -0.7% Memory: ✅ 37.228MB (SLO: <38.500MB -3.3%) vs baseline: +5.0% ✅ import_one_stdlib_cacheTime: ✅ 6.259µs (SLO: <10.000µs 📉 -37.4%) vs baseline: -0.5% Memory: ✅ 37.035MB (SLO: <38.500MB -3.8%) vs baseline: +4.5% ✅ import_one_unknownTime: ✅ 45.520µs (SLO: <50.000µs -9.0%) vs baseline: -0.2% Memory: ✅ 36.975MB (SLO: <38.500MB -4.0%) vs baseline: +4.1% ✅ import_one_unknown_cacheTime: ✅ 6.253µs (SLO: <10.000µs 📉 -37.5%) vs baseline: -1.2% Memory: ✅ 36.995MB (SLO: <38.500MB -3.9%) vs baseline: +4.0%
|
Allow users to omit any traces they want by returning none in the user_span_processor method. Motivation: I am trying to prevent some auto traces from cluttering my Datadog observability dashboards. These traces create noise and make it harder to focus on the more critical traces. My LLM observability overview is filled with what is clustered as empty input which is incorrect. e.g. all embedding traces are are just a spammer. To do that, I am using the new span_processor, and the new way to omit specific spans, will be to return null by the relevant span processor. I have added a test for that. The only risk is that there is no indication that span was omitted but I was afraid that a debug log would be too spammy. But please let me know if that will help. Also there are some telemetric collected about sent span which might also need to be changed, will be great to hear your thoughts Co-authored-by: amirbenami <amir@linxsecurity.io>
Annotates LangGraph agents (compiled state graphs, even those created through `create_react_agent`) with the following agent metadata information: - name (always) - tools (always - best effort, depending on the presence of `ToolNode`s within the agent) - instructions (if done through `create_react_agent`) - model name, provider, & settings (if done through `create_react_agent`) - handoffs (always - assuming the agent is directly a part of a supergraph) - framework (always) - dependencies (since state should always be passed in, always) - max_iterations (always, defaulting to 25 if not provided explicitly) Additionally, to help accomplish this, we patch the `create_react_agent` function to record agent manifest data on agent instance creation, should it be invoked. The means of doing this is a bit strange, as it is in completely different submodule (`langgraph.prebuilt`), and it required me to do what I think are some pretty not normal things for patching 😅 so, happy to discuss/change as needed! MLOB-3102 ## Checklist - [x] PR author has checked that all the criteria below are met - The PR description includes an overview of the change - The PR description articulates the motivation for the change - The change includes tests OR the PR description describes a testing strategy - The PR description notes risks associated with the change, if any - Newly-added code is easy to change - The change follows the [library release note guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html) - The change includes or references documentation updates if necessary - Backport labels are set (if [applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)) ## Reviewer Checklist - [x] Reviewer has checked that all the criteria below are met - Title is accurate - All changes are related to the pull request's stated goal - Avoids breaking [API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces) changes - Testing strategy adequately addresses listed risks - Newly-added code is easy to change - Release note makes sense to a user of the library - If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment - Backport labels are set in a manner that is consistent with the [release branch maintenance policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)
Remove importlib_metadata dependency since it is no longer needed. Support for Python 3.7 has been dropped, and dd-trace-py now requires Python 3.8 or later, which includes importlib.metadata in the standard library. ## Checklist - [x] PR author has checked that all the criteria below are met - The PR description includes an overview of the change - The PR description articulates the motivation for the change - The change includes tests OR the PR description describes a testing strategy - The PR description notes risks associated with the change, if any - Newly-added code is easy to change - The change follows the [library release note guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html) - The change includes or references documentation updates if necessary - Backport labels are set (if [applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)) ## Reviewer Checklist - [x] Reviewer has checked that all the criteria below are met - Title is accurate - All changes are related to the pull request's stated goal - Avoids breaking [API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces) changes - Testing strategy adequately addresses listed risks - Newly-added code is easy to change - Release note makes sense to a user of the library - If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment - Backport labels are set in a manner that is consistent with the [release branch maintenance policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting) --------- Co-authored-by: Munir Abdinur <munir_abdinur@hotmail.com> Co-authored-by: Munir Abdinur <munir.abdinur@datadoghq.com>
This PR introduces: - remove of the `_appsec_processor` in the tracer. The appsec processor is now part of the list of regular processors. This fixes several problems. - change the logic order of how appsec is enabled and loaded This is removing 2 static import cycles, only 2 left (none with appsec). Context: Before that PR, the appsec product was loaded through the tracer, by creating an instance of AppSecSpanProcessor. After that PR, the appsec product or the remote config layer will register the AppSecSpanProcessor into the list of regular span processors of the tracer. **Bonus**: As the appsec processor is not reset anymore at fork time by the respawn of the tracer (because it does not depend on the tracer object anymore), it looks like it's also fixing the gap time we could have where appsec was back to factory setting at work respawn time. APPSEC-57505 ## Checklist - [x] PR author has checked that all the criteria below are met - The PR description includes an overview of the change - The PR description articulates the motivation for the change - The change includes tests OR the PR description describes a testing strategy - The PR description notes risks associated with the change, if any - Newly-added code is easy to change - The change follows the [library release note guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html) - The change includes or references documentation updates if necessary - Backport labels are set (if [applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)) ## Reviewer Checklist - [x] Reviewer has checked that all the criteria below are met - Title is accurate - All changes are related to the pull request's stated goal - Avoids breaking [API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces) changes - Testing strategy adequately addresses listed risks - Newly-added code is easy to change - Release note makes sense to a user of the library - If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment - Backport labels are set in a manner that is consistent with the [release branch maintenance policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)
See builds here https://app.readthedocs.org/projects/ddtrace/builds/?version__slug=taegyunkim-native-cargo-home ## Checklist - [x] PR author has checked that all the criteria below are met - The PR description includes an overview of the change - The PR description articulates the motivation for the change - The change includes tests OR the PR description describes a testing strategy - The PR description notes risks associated with the change, if any - Newly-added code is easy to change - The change follows the [library release note guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html) - The change includes or references documentation updates if necessary - Backport labels are set (if [applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)) ## Reviewer Checklist - [ ] Reviewer has checked that all the criteria below are met - Title is accurate - All changes are related to the pull request's stated goal - Avoids breaking [API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces) changes - Testing strategy adequately addresses listed risks - Newly-added code is easy to change - Release note makes sense to a user of the library - If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment - Backport labels are set in a manner that is consistent with the [release branch maintenance policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)
…nGroup (#14250) ## Description When an Appsec `BlockingException` is raised within a fastapi middleware, it can be aggregated and nested in a `BaseExceptionGroup` multiple levels deep. The behaviour occurs when using http middlewares. ## Checklist - [x] PR author has checked that all the criteria below are met - The PR description includes an overview of the change - The PR description articulates the motivation for the change - The change includes tests OR the PR description describes a testing strategy - The PR description notes risks associated with the change, if any - Newly-added code is easy to change - The change follows the [library release note guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html) - The change includes or references documentation updates if necessary - Backport labels are set (if [applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)) ## Reviewer Checklist - [x] Reviewer has checked that all the criteria below are met - Title is accurate - All changes are related to the pull request's stated goal - Avoids breaking [API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces) changes - Testing strategy adequately addresses listed risks - Newly-added code is easy to change - Release note makes sense to a user of the library - If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment - Backport labels are set in a manner that is consistent with the [release branch maintenance policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)
fixing issue #14258 Also little change to the django app for threats tests to have a regression test. ## Checklist - [x] PR author has checked that all the criteria below are met - The PR description includes an overview of the change - The PR description articulates the motivation for the change - The change includes tests OR the PR description describes a testing strategy - The PR description notes risks associated with the change, if any - Newly-added code is easy to change - The change follows the [library release note guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html) - The change includes or references documentation updates if necessary - Backport labels are set (if [applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)) ## Reviewer Checklist - [x] Reviewer has checked that all the criteria below are met - Title is accurate - All changes are related to the pull request's stated goal - Avoids breaking [API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces) changes - Testing strategy adequately addresses listed risks - Newly-added code is easy to change - Release note makes sense to a user of the library - If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment - Backport labels are set in a manner that is consistent with the [release branch maintenance policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting) --------- Co-authored-by: Brett Langdon <brett.langdon@datadoghq.com>
Follows #14248 and DataDog/images#7477 Also adds parallelism to `azure_functions` tests since they were finishing right around the 20 minute timeout following the upgrade of `azure-functions-core-tools. ## Checklist - [x] PR author has checked that all the criteria below are met - The PR description includes an overview of the change - The PR description articulates the motivation for the change - The change includes tests OR the PR description describes a testing strategy - The PR description notes risks associated with the change, if any - Newly-added code is easy to change - The change follows the [library release note guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html) - The change includes or references documentation updates if necessary - Backport labels are set (if [applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)) ## Reviewer Checklist - [ ] Reviewer has checked that all the criteria below are met - Title is accurate - All changes are related to the pull request's stated goal - Avoids breaking [API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces) changes - Testing strategy adequately addresses listed risks - Newly-added code is easy to change - Release note makes sense to a user of the library - If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment - Backport labels are set in a manner that is consistent with the [release branch maintenance policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)
CI Visibility: Fix for a bug introduced in #14115 where session tags would not have the proper count of tests skipped by ITR, counting the suite number instead when ITR is configured at suite level skipping. Regression tests added for both suite level skipping and test level skipping. ## Checklist - [x] PR author has checked that all the criteria below are met - The PR description includes an overview of the change - The PR description articulates the motivation for the change - The change includes tests OR the PR description describes a testing strategy - The PR description notes risks associated with the change, if any - Newly-added code is easy to change - The change follows the [library release note guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html) - The change includes or references documentation updates if necessary - Backport labels are set (if [applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)) ## Reviewer Checklist - [x] Reviewer has checked that all the criteria below are met - Title is accurate - All changes are related to the pull request's stated goal - Avoids breaking [API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces) changes - Testing strategy adequately addresses listed risks - Newly-added code is easy to change - Release note makes sense to a user of the library - If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment - Backport labels are set in a manner that is consistent with the [release branch maintenance policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)
Update celery lockfiles and dependency package lockfiles. This performs the following updates: 1) Some celery lockfiles use celery `latest`. This will update celery and dependencies. 2) Some celery lockfiles use a pinned (non-latest) version of celery, but require the `latest` version of another package. This will update all such packages. ## Checklist - [x] PR author has checked that all the criteria below are met - The PR description includes an overview of the change - The PR description articulates the motivation for the change - The change includes tests OR the PR description describes a testing strategy - The PR description notes risks associated with the change, if any - Newly-added code is easy to change - The change follows the [library release note guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html) - The change includes or references documentation updates if necessary - Backport labels are set (if [applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)) ## Reviewer Checklist - [x] Reviewer has checked that all the criteria below are met - Title is accurate - All changes are related to the pull request's stated goal - Avoids breaking [API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces) changes - Testing strategy adequately addresses listed risks - Newly-added code is easy to change - Release note makes sense to a user of the library - If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment - Backport labels are set in a manner that is consistent with the [release branch maintenance policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting) Co-authored-by: quinna-h <175135214+quinna-h@users.noreply.github.com>
|
bytecode doesn't yet support Python 3.14 |
Broken out from #14361 `ddtrace.trace.Pin` is being deprecated ## Checklist - [x] PR author has checked that all the criteria below are met - The PR description includes an overview of the change - The PR description articulates the motivation for the change - The change includes tests OR the PR description describes a testing strategy - The PR description notes risks associated with the change, if any - Newly-added code is easy to change - The change follows the [library release note guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html) - The change includes or references documentation updates if necessary - Backport labels are set (if [applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)) ## Reviewer Checklist - [ ] Reviewer has checked that all the criteria below are met - Title is accurate - All changes are related to the pull request's stated goal - Avoids breaking [API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces) changes - Testing strategy adequately addresses listed risks - Newly-added code is easy to change - Release note makes sense to a user of the library - If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment - Backport labels are set in a manner that is consistent with the [release branch maintenance policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)
Broken out from #14361 `ddtrace.trace.Pin` is being deprecated ## Checklist - [x] PR author has checked that all the criteria below are met - The PR description includes an overview of the change - The PR description articulates the motivation for the change - The change includes tests OR the PR description describes a testing strategy - The PR description notes risks associated with the change, if any - Newly-added code is easy to change - The change follows the [library release note guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html) - The change includes or references documentation updates if necessary - Backport labels are set (if [applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)) ## Reviewer Checklist - [ ] Reviewer has checked that all the criteria below are met - Title is accurate - All changes are related to the pull request's stated goal - Avoids breaking [API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces) changes - Testing strategy adequately addresses listed risks - Newly-added code is easy to change - Release note makes sense to a user of the library - If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment - Backport labels are set in a manner that is consistent with the [release branch maintenance policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)
Following #14113, this PR adds endpoint discovery at startup for Flask. Also: - add blueprints in Flask testing app for threat tests (to make sure blueprints are properly supported) - Improve endpoint discovery test to ensure that we get the expected endpoint reported - Moved endpoint_collection away from asm settings to neutral file endpoints as this is a feature not directly related to security. - Kept flag enabling/disabling this feature inside asm settings as security team will maintain this feature. This was also tested on new endpoint discovery system tests. APPSEC-58374 ## Checklist - [x] PR author has checked that all the criteria below are met - The PR description includes an overview of the change - The PR description articulates the motivation for the change - The change includes tests OR the PR description describes a testing strategy - The PR description notes risks associated with the change, if any - Newly-added code is easy to change - The change follows the [library release note guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html) - The change includes or references documentation updates if necessary - Backport labels are set (if [applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)) ## Reviewer Checklist - [x] Reviewer has checked that all the criteria below are met - Title is accurate - All changes are related to the pull request's stated goal - Avoids breaking [API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces) changes - Testing strategy adequately addresses listed risks - Newly-added code is easy to change - Release note makes sense to a user of the library - If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment - Backport labels are set in a manner that is consistent with the [release branch maintenance policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)
emmettbutler
requested review from
christophe-papazian,
dubloom,
emmettbutler and
juan-fernandez
|
@brettlangdon @wantsui this is ready for review and merge. |
emmettbutler
changed the base branch from
main
to
emmett.butler/systests-latest-sept30
emmettbutler
removed
the
changelog/no-changelog
This change updates the riotfile to run 3.14 tests for all suites that i was able to get working that were not already enabled in #14264. --------- Co-authored-by: wan <26727996+wantsui@users.noreply.github.com> Co-authored-by: kyle <kyle@verhoog.ca> Co-authored-by: amirbenami <amir@linxsecurity.io> Co-authored-by: Sam Brenner <106700075+sabrenner@users.noreply.github.com> Co-authored-by: Mohammad A Islam <73513662+chojomok@users.noreply.github.com> Co-authored-by: Munir Abdinur <munir_abdinur@hotmail.com> Co-authored-by: Munir Abdinur <munir.abdinur@datadoghq.com> Co-authored-by: Christophe Papazian <114495376+christophe-papazian@users.noreply.github.com> Co-authored-by: Taegyun Kim <taegyun.kim@datadoghq.com> Co-authored-by: Florentin Labelle <florentin.labelle@datadoghq.com> Co-authored-by: Brett Langdon <brett.langdon@datadoghq.com> Co-authored-by: Duncan Harvey <35278470+duncanpharvey@users.noreply.github.com> Co-authored-by: Federico Mon <federico.mon@datadoghq.com> Co-authored-by: dd-octo-sts[bot] <200755185+dd-octo-sts[bot]@users.noreply.github.com> Co-authored-by: quinna-h <175135214+quinna-h@users.noreply.github.com> Co-authored-by: wantsui <wan.tsui@datadoghq.com> Co-authored-by: Baptiste Foy <baptiste.foy@datadoghq.com> Co-authored-by: maxzhangdd <max.zhang@datadoghq.com> Co-authored-by: Yun Kim <35776586+Yun-Kim@users.noreply.github.com> Co-authored-by: Taegyun Kim <k.taegyun@gmail.com> Co-authored-by: Gabriele N. Tornetta <P403n1x87@users.noreply.github.com>
14 participants
This change runs most of the test suite against Python 3.14.0rc1. There are additional suites enabled in #14720
Exceptions: riot envs and products that are not tested under 3.14 for various reasons