Skip to content
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

chore(iast): test code injection performance in ci #12195

Merged

Conversation

avara1986
Copy link
Member

@avara1986 avara1986 commented Feb 3, 2025

Checklist

  • 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
  • The change includes or references documentation updates if necessary
  • Backport labels are set (if applicable)

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 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

@avara1986 avara1986 added the ASM Application Security Monitoring label Feb 3, 2025
Copy link
Contributor

github-actions bot commented Feb 3, 2025

CODEOWNERS have been resolved as:

hatch.toml                                                              @DataDog/python-guild
scripts/iast/mod_leak_functions.py                                      @DataDog/asm-python

@avara1986 avara1986 changed the title chore(iast): test code injection in ci chore(iast): test code injection performance in ci Feb 3, 2025
@datadog-dd-trace-py-rkomorn
Copy link

datadog-dd-trace-py-rkomorn bot commented Feb 3, 2025

Datadog Report

Branch report: avara1986/add_eval_to_iast_aggregated_leak_testing
Commit report: f6a2597
Test service: dd-trace-py

✅ 0 Failed, 130 Passed, 1184 Skipped, 3m 49.87s Total duration (24m 48.8s time saved)

@pr-commenter
Copy link

pr-commenter bot commented Feb 3, 2025

Benchmarks

Benchmark execution time: 2025-02-04 08:49:28

Comparing candidate commit f6a2597 in PR branch avara1986/add_eval_to_iast_aggregated_leak_testing with baseline commit 63d13ab in branch 3.x-staging.

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

@avara1986 avara1986 marked this pull request as ready for review February 3, 2025 14:32
@avara1986 avara1986 requested review from a team as code owners February 3, 2025 14:32
@avara1986 avara1986 requested a review from taegyunkim February 3, 2025 14:32
wconti27 and others added 3 commits February 4, 2025 08:54
…le (#12035)

Refactors all web server integrations still using `tracer.trace` to
instead use `core.context_with_data`. This is in preparation for
supporting AWS API Gateway to ensure all web servers share the same code
path.

- [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))

- [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)
The shared pipeline is introducing support for windows OCI packages.
This PR ensure dd-trace-py doesn't generate nonsensical packages.
Windows support can be added later.

This was tested by using the WIP branch of one-pipeline

## 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 <[email protected]>
@avara1986 avara1986 force-pushed the avara1986/add_eval_to_iast_aggregated_leak_testing branch from e9ea612 to f573140 Compare February 4, 2025 07:56
@avara1986 avara1986 requested review from a team as code owners February 4, 2025 07:56
@avara1986 avara1986 changed the base branch from main to 3.x-staging February 4, 2025 07:56
@avara1986 avara1986 marked this pull request as draft February 4, 2025 07:57
@avara1986 avara1986 marked this pull request as ready for review February 4, 2025 07:59
@avara1986 avara1986 added the changelog/no-changelog A changelog entry is not required for this PR. label Feb 4, 2025
@avara1986 avara1986 merged commit 56a6ca2 into 3.x-staging Feb 4, 2025
734 of 737 checks passed
@avara1986 avara1986 deleted the avara1986/add_eval_to_iast_aggregated_leak_testing branch February 4, 2025 08:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ASM Application Security Monitoring changelog/no-changelog A changelog entry is not required for this PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants