-
Notifications
You must be signed in to change notification settings - Fork 377
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
DEBUG-3316 verify code tracking works in forked processes #4284
Conversation
Thank you for updating Change log entry section 👏 Visited at: 2025-01-13 21:43:31 UTC |
Datadog ReportBranch report: ✅ 0 Failed, 22192 Passed, 1476 Skipped, 6m 2.65s Total Time |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #4284 +/- ##
==========================================
- Coverage 97.72% 97.71% -0.02%
==========================================
Files 1354 1355 +1
Lines 82410 82433 +23
Branches 4213 4213
==========================================
+ Hits 80538 80550 +12
- Misses 1872 1883 +11 ☔ View full report in Codecov by Sentry. |
* master: (161 commits) Bump to version 2.9.0 (#4293) Increase type checking coverage (#4290) DEBUG-3329 rename datadog/di/init to datadog/di/preload (#4288) update supported versions workflow (#4289) DEBUG-3182 DI railtie (#4272) DEBUG-3328 report DI status in environment logger summary (#4285) Move out ostruct gem from test group for Ruby 3.5 DEBUG-3316 verify code tracking works in forked processes (#4284) Fix rebase issue in Rack::RequestMiddleware Improve code style in AppSec rack middlewares Improve variable naming in Rack::RequestBodyMiddleware Improve variable naming in Rack::RequestMiddleware Simplify Rack::RequestMiddleware Switch AppSec rack blocking to throw Extract to .gitlab/scripts Implement polling vaccine Update RBS signatures Add new RSpec negate matcher not_change Replace direct AppSec::Processor::Context calls Change AppSec::Context exposed interface ...
What does this PR do?
Adds test coverage that dynamic instrumentation code tracking works in forked processes.
Motivation:
Verification of DI functionality in various environments
Change log entry
None
Additional Notes:
How to test the change?
Unit tests are included