-
Notifications
You must be signed in to change notification settings - Fork 15
refactor: harden and simplify ProfileStatus more #1419
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
Conversation
BenchmarksComparisonBenchmark execution time: 2025-12-19 01:09:45 Comparing candidate commit 033e544 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 57 metrics, 2 unstable metrics. CandidateCandidate benchmark detailsGroup 1
Group 2
Group 3
Group 4
Group 5
Group 6
Group 7
Group 8
Group 9
Group 10
Group 11
Group 12
Group 13
Group 14
Group 15
Group 16
Group 17
Group 18
Group 19
BaselineOmitted due to size. |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #1419 +/- ##
==========================================
- Coverage 71.51% 71.42% -0.10%
==========================================
Files 411 411
Lines 66083 66028 -55
==========================================
- Hits 47260 47161 -99
- Misses 18823 18867 +44
🚀 New features to boost your workflow:
|
Artifact Size Benchmark Reportaarch64-alpine-linux-musl
aarch64-apple-darwin
aarch64-unknown-linux-gnu
libdatadog-x64-windows
libdatadog-x86-windows
x86_64-alpine-linux-musl
x86_64-apple-darwin
x86_64-unknown-linux-gnu
|
|
LGTM! |
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
What does this PR do?
This simplifies ProfileStatus and hardens it:
FLAG_STATICandFLAG_ALLOCATEDwith a singleIS_ALLOCATED_MASK. This is not a breaking change, these were private and the observable FFI semantics are the same.It also notes that it could be modified in the future to hold error codes as well.
Motivation
We merged in a PR to simplify things in #1416 to make it into a release, and it came up in review that as part of that, we did lose a bit of hardening to detect bad flags. Since the release was already slightly delayed, we chose to push a small bit of that into a new PR and not delay the release.
Additional Notes
None.
How to test the change?