Skip to content

Merge develop into feature/memory-profiling - #4068

Merged
ambushwork merged 98 commits into
feature/memory-profilingfrom
yl/merge-develop-into-feature-memory-profiling
Oct 29, 2026
Merged

ambushwork merged 98 commits into
feature/memory-profilingfrom
yl/merge-develop-into-feature-memory-profiling

Conversation

@ambushwork

Copy link
Copy Markdown
Member

What does this PR do?

Merge develop into feature/memory-profiling

Review checklist (to be filled by reviewers)

  • Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
  • Make sure you discussed the feature or bugfix with the maintaining team in an Issue
  • Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

aleksandr-gringauz and others added 30 commits October 21, 2026 15:14
Add native and OpenFeature opt-out configuration with timestamp validation. Require server acknowledgment and isolate cached assignments and pending contexts.
Bind assignment acknowledgements and persisted caches to the selected mode and exact subject cutoff. Cover request, restart, and stale-response behavior.
Deliver committed state changes and callbacks outside the policy lock. Read one assignment snapshot and retain the attempted subject for error telemetry.
Use Gregorian dates and explicit UTC bounds for opt-out timestamps.
Derive request options from the effective policy and validate acknowledgements.
Update the shared version catalog and regenerate dependency listings.

Ref: RUM-19228
Co-authored-by: 0xnm <4046447+0xnm@users.noreply.github.com>
logApiUsage sent a usage event on every call, so volume scaled with how
often apps call the API (e.g. operation steps). Deduplicate each usage
type and configuration per SDK instance, before sampling.

Ref: RUM-19223
Co-authored-by: aleksandr-gringauz <200633589+aleksandr-gringauz@users.noreply.github.com>
…okhttp-4-12-1-20261023

[RUM-19228] RUM-19228: Bump OkHttp to 4.12.1 to block compromised certificates CVE-2026-111943
Replace the suppressed Collections.newSetFromMap with a ConcurrentHashMap
and list its putIfAbsent call as a known safe call.

Ref: RUM-19223
Co-authored-by: aleksandr-gringauz <200633589+aleksandr-gringauz@users.noreply.github.com>
Ref: RUM-19223
Co-authored-by: aleksandr-gringauz <200633589+aleksandr-gringauz@users.noreply.github.com>
Keep configuration only for usages that have one; other usages are keyed
by type through an else branch.

Ref: RUM-19223
Co-authored-by: aleksandr-gringauz <200633589+aleksandr-gringauz@users.noreply.github.com>
Expect unique vital labels in the shared assertion and both callers.
Exercise repeated names while preserving each event's metadata.

Ref: RUM-19248

DD_U3SWJ8

Co-authored-by: 0xnm <4046447+0xnm@users.noreply.github.com>
Generate distinct keys so concurrent inserts cannot replace the feature
whose context is being updated, and assert its identity after the threads join.

Ref: RUM-19247
DD_SZJABL

Co-authored-by: 0xnm <4046447+0xnm@users.noreply.github.com>
…19247/fix-concurrent-feature-test-20261026

[RUM-19247] Fix flaky `DatadogCoreTest` concurrent feature access
Keep only the Set expectation API and both caller conversions.

Ref: RUM-19248

DD_U3SWJ8

Co-authored-by: 0xnm <4046447+0xnm@users.noreply.github.com>
…um-context

RUM-19153: Migrate readers to shared RUM context
…filing-vital-names-20261026

[RUM-19248] Fix flaky `ProfilingDataWriterTest`
0xnm and others added 2 commits October 29, 2026 12:19
StubSDKCore is AutoCloseable: closing stops its features, which
unregisters it from GlobalRumMonitor, and resets its mocks, whose last
invocation could still reference it. Single-fit tests close their core
with @autoclose. Also replace FeatureScope.getContextFuture with
InternalSdkCore.getDatadogContextFuture.

Ref: RUM-19307
@ambushwork
ambushwork requested review from a team as code owners October 29, 2026 11:32
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 29, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-29T15:40:42.757761Z 9634209 New commits
🔒 Security Review ✅ Completed 2026-10-29T15:38:39.879029Z 9634209 New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@datadog-prod-us1-6

datadog-prod-us1-6 Bot commented Oct 29, 2026 •

Copy link
Copy Markdown

Pipelines  Tests

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 85.71%
• Overall Coverage: 72.23% (+0.31%)

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 9634209 | Docs | View more details | Give us feedback!

@datadog-prod-us1-6 datadog-prod-us1-6 Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Bits Code Review: PASS

More details

Android build and runtime behavior remain unverified because Gradle tests and emulator runs were not executed.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Bits Code Review · Commit 1478912

@0xnm

0xnm commented Oct 29, 2026

Copy link
Copy Markdown
Member

It is better to include a commit with version bump to 3.17.0 here as well.

ambushwork and others added 14 commits October 29, 2026 12:43
Release PRs aggregate already-reviewed changes, so reviewers should not
re-flag breaking changes approved in the original PRs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Clarify review scope for release preparation PRs in AGENTS.md
Ignore vitrine agents directory

Co-authored-by: ambushwork <yi.lu@datadoghq.com>
…pt-out-immediate

FFLSDK-258: Add experimentation opt-out modes
…e-stub-sdk-core

RUM-19307: Release `StubSDKCore` after each test with `@AutoClose`
@ambushwork
ambushwork requested a review from a team as a code owner October 29, 2026 15:31
@ambushwork ambushwork added the ready-for-human-review All agentic review feedback was addressed and PR is ready for the human review. label Oct 29, 2026

@datadog-prod-us1-6 datadog-prod-us1-6 Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Bits Code Review: PASS

More details

Android runtime behavior and CI execution remain unverified because tests were not run; confidence is limited to static inspection.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Bits Code Review · Commit 9634209

@ambushwork
ambushwork merged commit 42f6327 into feature/memory-profiling Oct 29, 2026
25 checks passed
@ambushwork
ambushwork deleted the yl/merge-develop-into-feature-memory-profiling branch October 29, 2026 15:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-for-human-review All agentic review feedback was addressed and PR is ready for the human review.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants