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

Fixing DD_TRACE_OBFUSCATION_QUERY_STRING_REGEXP Empty Value Behavior #2909

Merged
merged 9 commits into from
Nov 5, 2024

Conversation

link04
Copy link
Contributor

@link04 link04 commented Oct 21, 2024

Description

Updating what should happen if the value for DD_TRACE_OBFUSCATION_QUERY_STRING_REGEXP is set to an empty string since as of today it was redacting everything in system tests.

https://datadoghq.atlassian.net/browse/APMAPI-499

Reviewer checklist

  • Test coverage seems ok.
  • Appropriate labels assigned.

@codecov-commenter
Copy link

codecov-commenter commented Oct 21, 2024

Codecov Report

Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 72.35%. Comparing base (1b40137) to head (d77bcda).
Report is 2 commits behind head on master.

Files with missing lines Patch % Lines
src/DDTrace/Util/Normalizer.php 0.00% 1 Missing ⚠️
Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff              @@
##             master    #2909      +/-   ##
============================================
- Coverage     72.39%   72.35%   -0.05%     
- Complexity     2526     2527       +1     
============================================
  Files           135      135              
  Lines         14400    14399       -1     
  Branches        989      989              
============================================
- Hits          10425    10418       -7     
- Misses         3433     3439       +6     
  Partials        542      542              
Flag Coverage Δ
appsec-extension 68.36% <ø> (ø)
tracer-php 73.90% <0.00%> (-0.07%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
src/DDTrace/Util/Normalizer.php 68.38% <0.00%> (+0.49%) ⬆️

... and 1 file with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1b40137...d77bcda. Read the comment docs.

@pr-commenter
Copy link

pr-commenter bot commented Oct 22, 2024

Benchmarks [ tracer ]

Benchmark execution time: 2024-11-05 19:48:14

Comparing candidate commit d77bcda in PR branch maximo/consistent-query-string-regexp-config with baseline commit 1b40137 in branch master.

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

scenario:TraceFlushBench/benchFlushTrace

  • 🟥 execution_time [+1000.000ns; +1000.000ns] or [+100.000%; +100.000%]

@link04 link04 marked this pull request as ready for review October 23, 2024 19:05
@link04 link04 requested a review from a team as a code owner October 23, 2024 19:05
@bwoebi
Copy link
Collaborator

bwoebi commented Oct 23, 2024

I think empty string handling is missing in Normalizer.php. I.e. it should also always match there with an empty string.

@bwoebi
Copy link
Collaborator

bwoebi commented Oct 23, 2024

In fact I'm just seeing 5f1f193, is there a specific reason you reverted that? (it should just return [$postKey => $postVal]; unconditionally, when the string is empty, too.)

@link04 link04 requested a review from a team as a code owner October 23, 2024 19:38
Copy link
Collaborator

@bwoebi bwoebi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks right. Merging :-)

@link04 link04 merged commit a1ec6f8 into master Nov 5, 2024
552 of 576 checks passed
@link04 link04 deleted the maximo/consistent-query-string-regexp-config branch November 5, 2024 23:56
@github-actions github-actions bot added this to the 1.5.0 milestone Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants