-
Notifications
You must be signed in to change notification settings - Fork 70
Release 11.10 #1091
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
Merged
Release 11.10 #1091
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
`nr_execute_handle_autoload` wasn't accounting for the possibility of txn being null which would lead to unpredictable behavior when accessing it [here](https://github.com/newrelic/newrelic-php-agent/blob/dev/agent/php_execute.c#L894), and we would cause corruption when we [set this value](https://github.com/newrelic/newrelic-php-agent/blob/dev/agent/php_execute.c#L907). txn can be null in cases where nr_php_txn_end has been called. such as: https://github.com/newrelic/newrelic-php-agent/blob/dev/agent/fw_laravel_queue.c#L355-L356
Changes the default configuration value for composer-based package detection to `true`. An additional configuration value, `newrelic.vulnerability_management.composer_api.per_process_detection`, has also been added to control the frequency at which composer sampling occurs. By default, this setting will be enabled, only sampling Composer API data once per php-fpm process. This improves baseline performance to make the enablement of Composer API package detection a negligible overhead impact. --------- Co-authored-by: Michael Fulbright <[email protected]>
Force non-zero duration of helper user function. When tests execute fast enough, the helper function's segment start time and end time are equal and this causes the segment to be dropped. To address this test instability, non-zero duration is forced on test helper user functions. This is a follow up to #781.
This PR: 1) adds the option to run valgrind on integration tests in GHA 2) adds the ability to run valgrind on CGI tests 3) no longer runs valgrind on SKIPIFs 4) changes the valgrind lock mechanism to allow subprocesses (i.e. curl) to not be locked out
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1091 +/- ##
=======================================
Coverage 77.27% 77.27%
=======================================
Files 199 199
Lines 28327 28342 +15
=======================================
+ Hits 21890 21902 +12
- Misses 6437 6440 +3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
mfulb
approved these changes
Jun 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.