Add agentless Feature Flagging configuration source by leoromanovsky · Pull Request #11892 · DataDog/dd-trace-java

leoromanovsky · 2026-07-08T17:33:56Z

NOTE TO REVIEWERS

This PR intentionally keeps the complete feature in one PR so the final architecture remains visible. Its four commits are deliberately layered like a stacked PR, and each commit contains the final production behavior and tests for that layer.

How to Review

Review the commits in the order listed below; each link opens only that commit's diff.
Treat each commit as an independently buildable review unit.
After the fourth commit, use the full Files changed view for a final cross-layer integration pass.
Please leave comments on the commit where the behavior is introduced when possible.

Commit Guide

LOC is rename-aware per commit against its parent.

Commit	Review focus	LOC (+/-)
`b8bbd269e0`	Define the canonical source contract, defaults, metadata, and timing validation. Nonpositive poll intervals and request timeouts are rejected in favor of safe defaults, with tests in this commit.	+165 / -3
`4baefdbf6e`	Add the complete Datadog-managed poller: authenticated HTTP, accepted-200-only ETags, cold `304`, last-known-good, bounded jittered retry, no overlap, in-flight cancellation, shutdown safety, and system-test-parity tests.	+1166 / -1
`d378350cf1`	Extend the same agentless source to custom HTTP endpoints, including bare-host versus exact-path behavior and tests.	+57 / -1
`f9e70e67c4`	Select agentless, Remote Configuration, or reserved offline mode at runtime; make repeated startup idempotent; clean up partial startup; and stop the subsystem from Agent shutdown, with tests.	+246 / -18

Per-Commit Validation

Each commit was checked out and validated independently before publication:

Contract: ConfigTest, feature-flagging lib/agent tests, and relevant Spotless checks.
Managed poller: clean feature-flagging lib tests, Spotless, and JaCoCo coverage gate.
Custom endpoint: feature-flagging lib tests, Spotless, and JaCoCo coverage gate.
Runtime selection: clean feature-flagging lib/agent tests, both JaCoCo gates, bootstrap/internal-api tests, and all relevant Spotless checks.

All four gates completed with BUILD SUCCESSFUL.

Stack Position

You are here: the Java source-mode foundation. It makes Datadog-managed agentless delivery the default, keeps custom HTTP under agentless, and preserves Agent Remote Configuration as explicit opt-in.

flowchart LR
    subgraph JAVA["dd-trace-java"]
        J1["JAVA-01 · #11892<br/>Agentless + RC sources"] --> J2["JAVA-02 · #11639<br/>Aggregate evaluation EVP"]
    end

    subgraph SYSTEM["system-tests"]
        ST1["ST-01 · #7298<br/>Mock agentless backend"] --> ST2["ST-02 · #7299<br/>Side-effect contracts"]
        ST2 --> STM1["ST-M01 · #7300<br/>Enable Java configuration"]
        ST2 --> NEXT["Next drafts<br/>Enable Java side effects"]
    end

    subgraph DOGFOOD["ffe-dogfooding"]
        DOG0["DOG-00 · #92<br/>Agentless evaluation baseline"] --> DOG1["DOG-01 · #93<br/>Side-effect conduit"]
    end

    J1 --> STM1
    J1 --> DOG0
    J2 --> NEXT
    J2 --> DOG1
    STM1 --> GREEN["Java proof<br/>both sources × side effects"]
    NEXT --> GREEN
    DOG1 --> GREEN

    classDef current fill:#fcbf49,stroke:#8a5a00,stroke-width:3px,color:#111;
    class J1 current;

Motivation

Java Feature Flagging needs a tracer-side configuration-source split so SDKs can fetch UFC from an agentless HTTP backend while preserving the existing Agent Remote Configuration path.

Changes

Adds DD_FEATURE_FLAGS_CONFIGURATION_SOURCE with agentless, remote_config, and reserved offline; default is agentless.
Adds agentless endpoint selection through DD_FEATURE_FLAGS_CONFIGURATION_SOURCE_AGENTLESS_BASE_URL.
Adds agentless polling controls: DD_FEATURE_FLAGS_CONFIGURATION_SOURCE_AGENTLESS_POLL_INTERVAL_SECONDS and DD_FEATURE_FLAGS_CONFIGURATION_SOURCE_AGENTLESS_REQUEST_TIMEOUT_SECONDS.
Adds AgentlessConfigurationSource, an HTTP UFC poller used for both the default Datadog-managed endpoint and a configured custom HTTP endpoint.
Keeps remote_config on the existing RemoteConfigServiceImpl / Agent RC path.
Handles DD-API-KEY, accepted-200-only ETags/304, malformed UFC rejection, last-known-good preservation, and no overlapping polls.
Retries timeout/429/5xx failures twice per poll cycle with jittered delays derived from the poll period: clamp(P/6, 2s, 10s) then clamp(P/3, 5s, 30s).
Cancels in-flight HTTP and pending retry work during shutdown, suppresses post-shutdown retries, and makes subsystem startup idempotent.
Rejects nonpositive poll intervals and request timeouts by warning and using the documented defaults.
Removes the proposed DD_FEATURE_FLAGS_ENABLED and extra-header env from this PR.

Decisions

No new provider kill switch. This keeps the existing provider bootstrap behavior through DD_EXPERIMENTAL_FLAGGING_PROVIDER_ENABLED; changing enablement is out of scope for this PR.

Custom HTTP delivery remains under agentless. The source mode describes direct HTTP UFC delivery without the Datadog Agent. With no base URL, the SDK derives the first-party Datadog endpoint as https://api.<site>/api/v2/feature-flagging/config/server-distribution?dd_env=<env>. Setting DD_FEATURE_FLAGS_CONFIGURATION_SOURCE_AGENTLESS_BASE_URL chooses a system-test, dogfood, or operator-managed HTTP endpoint without introducing a fourth source mode. A bare host uses the standard server-distribution path; a URL with a path is used as the exact UFC endpoint.

Remote Configuration remains a distinct mode. It is Agent-mediated and uses the RC protocol's security, signing, targeting, capability, and subscription lifecycle. Those semantics are materially different from direct HTTP polling, so remote_config remains a peer source mode rather than another agentless endpoint choice.

No offline factory yet. offline remains a reserved configuration-source value. This PR does not expose a startup-bytes API or offline factory because that API still needs design work.

Source selection stays SDK-local. DD_FEATURE_FLAGS_CONFIGURATION_SOURCE decides which local source implementation starts. It is not sent to the backend.

Initialization Modes

Solid connectors are implemented in this PR. The dashed offline connector previews startup-provided UFC bytes.

flowchart TD
    Gate{DD_EXPERIMENTAL_FLAGGING_PROVIDER_ENABLED}
    Disabled[Feature Flagging subsystem not started]
    System[FeatureFlaggingSystem.start]
    Select{DD_FEATURE_FLAGS_CONFIGURATION_SOURCE}
    Exposure[ExposureWriter starts for every enabled mode]

    subgraph AgentlessMode[agentless mode - current default]
        AgentlessSource[AgentlessConfigurationSource]
        OperationalDefaults[SDK-owned operation<br/>30s poll default; 2s request timeout default<br/>ETag; retry; last-known-good; no overlap]
        EndpointChoice{agentless base URL set?}
        DatadogManaged[Datadog-managed agentless<br/>first-party; CDN-backed]
        CustomHttp[Custom HTTP endpoint<br/>system tests; dogfood; operator backend]

        AgentlessSource --- OperationalDefaults
        AgentlessSource -- polls --> EndpointChoice
        EndpointChoice -- no --> DatadogManaged
        EndpointChoice -- yes --> CustomHttp
    end

    RemoteConfig[remote_config<br/>explicit opt-in; Agent-mediated]
    RemoteConfigSource[RemoteConfigServiceImpl]
    AgentRc[Datadog Agent Remote Configuration<br/>RC security; signing; targeting; subscriptions]

    OfflineReserved[offline today<br/>reserved; no configuration service]
    OfflineSource[Later: OfflineConfigurationSource<br/>customer UFC JSON bytes at startup; no network]

    Ufc[Shared UFC deserialize and evaluate pipeline]
    Gateway[FeatureFlaggingGateway]
    Provider[OpenFeature provider]

    Gate -- false --> Disabled
    Gate -- true --> System
    System --> Select
    System --> Exposure

    Select -- unset or agentless --> AgentlessSource
    DatadogManaged --> Ufc
    CustomHttp --> Ufc

    Select -- remote_config --> RemoteConfig
    RemoteConfig --> RemoteConfigSource
    RemoteConfigSource -- subscribes --> AgentRc
    RemoteConfigSource --> Ufc

    Select -- offline today --> OfflineReserved
    OfflineReserved -. later .-> OfflineSource
    OfflineSource -. startup UFC bytes .-> Ufc

    Ufc --> Gateway
    Gateway --> Provider

Customer Usage Example

Default Datadog-managed agentless delivery:

export DD_API_KEY=<datadog-api-key>
export DD_SITE=datadoghq.com
export DD_ENV=prod

# Optional because agentless is the default configuration source.
export DD_FEATURE_FLAGS_CONFIGURATION_SOURCE=agentless
export DD_FEATURE_FLAGS_CONFIGURATION_SOURCE_AGENTLESS_POLL_INTERVAL_SECONDS=30
export DD_FEATURE_FLAGS_CONFIGURATION_SOURCE_AGENTLESS_REQUEST_TIMEOUT_SECONDS=2

java -javaagent:/path/to/dd-java-agent.jar -jar app.jar

Custom HTTP delivery keeps agentless mode and changes only the endpoint:

export DD_FEATURE_FLAGS_CONFIGURATION_SOURCE=agentless
export DD_FEATURE_FLAGS_CONFIGURATION_SOURCE_AGENTLESS_BASE_URL=https://flags.example.com/ufc

java -javaagent:/path/to/dd-java-agent.jar -jar app.jar

Explicit Agent Remote Configuration delivery still uses the existing Agent path:

export DD_FEATURE_FLAGS_CONFIGURATION_SOURCE=remote_config
export DD_REMOTE_CONFIGURATION_ENABLED=true

java -javaagent:/path/to/dd-java-agent.jar -jar app.jar

Verification

./gradlew :products:feature-flagging:feature-flagging-agent:test :products:feature-flagging:feature-flagging-lib:test --no-daemon
result: BUILD SUCCESSFUL

./gradlew :products:feature-flagging:feature-flagging-agent:jacocoTestCoverageVerification :products:feature-flagging:feature-flagging-lib:jacocoTestCoverageVerification :products:feature-flagging:feature-flagging-agent:spotlessCheck :products:feature-flagging:feature-flagging-lib:spotlessCheck --no-daemon
result: BUILD SUCCESSFUL

./gradlew :dd-smoke-tests:openfeature:cleanTest :dd-smoke-tests:openfeature:test --tests datadog.smoketest.springboot.OpenFeatureProviderSmokeTest --no-daemon
result: BUILD SUCCESSFUL

git diff --check
result: clean

System Test Evidence

I built dd-java-agent, dd-trace-api, and dd-openfeature from the rewritten
head f9e70e67c4, rebuilt the Java Spring Boot weblog image with those local
artifacts, and verified the JAR inside the image matched the local agent JAR.
I then ran the Java manifest-enabled agentless scenario from the companion
system-tests draft:

TEST_LIBRARY=java ./run.sh +v \
  FEATURE_FLAGGING_AND_EXPERIMENTATION_AGENTLESS \
  tests/ffe/test_agentless_configuration.py

Scenario: FEATURE_FLAGGING_AND_EXPERIMENTATION_AGENTLESS
Library: java@1.65.0-SNAPSHOT+f9e70e67c4
Weblog variant: spring-boot
collected 1 item
tests/ffe/test_agentless_configuration.py .                        [100%]
1 passed

This exercises the Java manifest row proposed by the companion draft against
the exact code currently published in this PR.

Next Steps

Review the draft Java manifest activation:
DataDog/system-tests#7300.
Keep that PR draft until this Java behavior is available to system-tests CI.
After this PR lands, rerun the manifest activation in Java development CI and
merge the activation only when that gate is green.

dd-octo-sts · 2026-07-08T17:57:28Z

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	13.98 s	13.92 s	[-0.4%; +1.3%] (no difference)
startup:insecure-bank:tracing:Agent	12.93 s	12.94 s	[-0.6%; +0.4%] (no difference)
startup:petclinic:appsec:Agent	16.50 s	16.20 s	[-4.4%; +8.1%] (unstable)
startup:petclinic:iast:Agent	16.55 s	16.80 s	[-6.0%; +3.0%] (no difference)
startup:petclinic:profiling:Agent	16.76 s	16.73 s	[-1.0%; +1.4%] (no difference)
startup:petclinic:sca:Agent	16.88 s	16.88 s	[-1.4%; +1.5%] (no difference)
startup:petclinic:tracing:Agent	16.08 s	15.78 s	[-2.4%; +6.1%] (no difference)

Commit: 7aa2181b · CI Pipeline · Benchmarking Platform UI

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

leoromanovsky · 2026-07-12T00:54:01Z

+    final StringBuilder endpoint =
+        new StringBuilder("https://api.")
+            .append(config.getSite().toLowerCase(Locale.ROOT))
+            .append(DATADOG_API_SERVER_DISTRIBUTION_PATH);


🟡 Blocker: This is going to be a CDN-backed API. We are waiting on the DNS to be settled.

leoromanovsky · 2026-07-12T00:55:10Z

+  // TODO before merge: confirm the final backend route with the server-distribution API owners.
+  private static final String DATADOG_API_SERVER_DISTRIBUTION_PATH =
+      "/api/v2/feature-flagging/config/server-distribution";


🟡 Blocker: The path is not settled yet.

dd-octo-sts · 2026-07-12T12:10:36Z

Hi! 👋 Thanks for your pull request! 🎉

To help us review it, please make sure to:

Add at least one type, and one component or instrumentation label to the pull request

If you need help, please check our contributing guidelines.

datadog-datadog-prod-us1-2

All retry, ETag, shutdown, and idempotency paths look correct. One real gap: apply() silently returns false for 401/403 with no log above DEBUG — users with a wrong or missing DD_API_KEY have no way to diagnose why feature flags never load. Fixed by separating the auth-failure branch in apply() with a LOGGER.warn(...) call.

_{Open Bits AI session}

_{🤖 Datadog Autotest · Commit f9e70e6 · What is Autotest? · Any feedback? Reach out in #autotest}

typotter · 2026-07-14T19:34:33Z

  static final boolean DEFAULT_INJECT_DATADOG_ATTRIBUTE = true;
  static final String DEFAULT_SITE = "datadoghq.com";

+  public static final String DEFAULT_FEATURE_FLAGGING_CONFIGURATION_SOURCE = "agentless";


nit: move these up one block to preserve publics and package visibility groups

…ess-narrative # Conflicts: # dd-trace-api/src/main/java/datadog/trace/api/config/FeatureFlaggingConfig.java # products/feature-flagging/feature-flagging-agent/src/main/java/com/datadog/featureflag/FeatureFlaggingSystem.java

pavlokhrebto

Advisory review of the agentless configuration source, cross-checked against the Agentless-mode RFC. The core state machine (cold vs. warm handling, retry classification, readiness, atomic snapshot swap, shutdown / last-known-good) matches the RFC precisely — nice work. Findings below are precision-first and mostly non-blocking; inline comments are attached to the relevant lines.

Descoped config note (C8): The RFC lists DD_FEATURE_FLAGS_CONFIGURATION_SOURCE_AGENTLESS_EXTRA_HEADERS (default empty object); this PR intentionally removes it. Fine if deliberate, but noting it since the mock-CDN test flow may want custom headers — worth tracking as a follow-up.

pavlokhrebto · 2026-07-15T14:31:06Z

+    @Override
+    public UfcHttpResponse fetch(final HttpUrl endpoint, final Config config, final String etag)
+        throws IOException {
+      final Map<String, String> headers = new HashMap<>();


Reconcile source-mode metadata with system-tests. These requests send DD-API-KEY, If-None-Match, and the standard Datadog-Meta-* headers, but no source-mode metadata — matching this PR's decision that source selection is not sent to the backend. However, the RFC's System Tests Validation section lists sending auth/source-mode metadata as required proof, and the mock-CDN flow expects it. This passed the current draft scenario, but if the shared system-tests later assert a source-mode header, this SDK would fail. Worth reconciling with the RFC author / system-tests owner before the manifest (system-tests#7300) leaves draft.

pavlokhrebto · 2026-07-15T14:31:06Z

+          return false;
+        }
+        if (attempt == MAX_ATTEMPTS) {
+          LOGGER.debug("Feature Flagging HTTP configuration source request failed", e);


Sustained non-auth failures are invisible at the default log level. Auth failures (401/403) emit a rate-limited WARN (good), but timeout/5xx exhaustion and IOException only log at DEBUG. A persistently unreachable or 5xx-ing endpoint produces zero default-level signal; the only symptom is PROVIDER_NOT_READY returning defaults forever. Since a failed config source silently means all flags fall back to code defaults, consider a rate-limited WARN on sustained fetch failure too.

Good idea; addressing.

pavlokhrebto · 2026-07-15T14:31:06Z

+    return parsed;
+  }
+
+  private static String endpointFromConfiguredBaseUrl(final String configuredBaseUrl) {


dd_env is dropped for custom base URLs. endpointFromConfiguredBaseUrl never appends ?dd_env=<env>, whereas the Datadog-managed default (datadogApiServerDistributionEndpoint) always does. So pointing ..._BASE_URL at a server-distribution-style backend silently loses env scoping. Likely intentional for opaque custom endpoints, but it is undocumented and an easy footgun — could you confirm the intent and document it (and ideally add a test pinning the behavior)?

Good idea to add dd_env automatically; seems like a handy bit of information to have.

pavlokhrebto · 2026-07-15T14:31:06Z

+    executor.shutdownNow();
+  }
+
+  private void pollOnceSafely() {


Test gap + error handling: scheduled-path crash safety. pollOnceSafely exists to stop a throwing poll from permanently cancelling the scheduleWithFixedDelay task, but no test exercises that on the scheduled path — failedGatewayDispatchDoesNotAdvanceEtag only calls pollOnce() directly. A test that a throwing listener on the scheduled path does not kill subsequent polls would lock this in. Also note this catches only RuntimeException, not Error — a listener throwing an Error would still kill the poller; worth a comment or widening to Throwable.

Interesting! Ok, will improve the testing around this.

pavlokhrebto · 2026-07-15T14:31:06Z

+final class AgentlessConfigurationSource implements ConfigurationSourceService {
+  private static final Logger LOGGER = LoggerFactory.getLogger(AgentlessConfigurationSource.class);
+
+  // TODO before merge: confirm the final backend route with the server-distribution API owners.


Unresolved backend route TODO. Flagging so it is not missed — by its own text this blocks merge: confirm the final server-distribution route with the API owners.

Known; this is a blocker to merging until we get the DNS.

Known; waiting on CDN DNS to be known.

pavlokhrebto · 2026-07-15T14:31:06Z

+        config,
+        millis(config.getFeatureFlaggingConfigurationSourcePollIntervalSeconds()),
+        new OkHttpUfcHttpClient(
+            OkHttpUtils.buildHttpClient(


Request-timeout semantics (no change requested). The 2s default matches the RFC. Just noting the mapping: it is applied as connect + read + write each = 2s (via OkHttpUtils.buildHttpClient), with no overall callTimeout — so large payloads can still stream (good), but a 2s connect could be tight on cold edges. Might be worth confirming with FFE against a real CDN edge.

Thanks for mentioning; I'll think about how to improve this, and yes, we will validate on the real CDN edge. I believe even without that information, that 2s is sufficient.

pavlokhrebto · 2026-07-15T14:31:06Z

+    return parsed.toString();
+  }
+
+  private static String datadogApiServerDistributionEndpoint(final Config config) {


GovCloud not guarded. The RFC scopes direct CDN mode to commercial sites (GovCloud not included), but https://api.<site> is built for any site with no guard. A defensive check or doc note would match the stated scope.

Thanks, yes, GovCloud is not supported; I'll make it explicit.

…figuration-source

This comment has been minimized.

Sign in to view

leoromanovsky commented Jul 8, 2026

View reviewed changes

leoromanovsky commented Jul 9, 2026

View reviewed changes

Comment thread internal-api/src/main/java/datadog/trace/api/Config.java Outdated

leoromanovsky commented Jul 9, 2026

View reviewed changes

Comment thread ...ging/feature-flagging-agent/src/main/java/com/datadog/featureflag/FeatureFlaggingSystem.java Outdated

leoromanovsky mentioned this pull request Jul 11, 2026

test(ffe): pin end-to-end scenario to remote config DataDog/system-tests#7297

Merged

leoromanovsky force-pushed the leo.romanovsky/ffl-2693-java-agentless-configuration-source branch from 1858f32 to 82bb199 Compare July 11, 2026 04:01

leoromanovsky mentioned this pull request Jul 11, 2026

feat(openfeature): emit server-side EVP flagevaluation #11639

Draft

leoromanovsky added 4 commits July 11, 2026 21:32

Define Feature Flagging configuration source contract

b8bbd26

Add Datadog-managed agentless UFC polling

4baefdb

Support custom agentless UFC endpoints

d378350

Select the Feature Flagging configuration source

f9e70e6

leoromanovsky force-pushed the leo.romanovsky/ffl-2693-java-agentless-configuration-source branch from be3f8fc to f9e70e6 Compare July 12, 2026 01:37

leoromanovsky commented Jul 12, 2026

View reviewed changes

leoromanovsky marked this pull request as ready for review July 12, 2026 12:10

leoromanovsky requested review from a team as code owners July 12, 2026 12:10

leoromanovsky requested review from AlexeyKuznetsov-DD, manuel-alvarez-alvarez, pavlokhrebto and typotter and removed request for a team July 12, 2026 12:10

leoromanovsky requested review from sarahchen6 and removed request for manuel-alvarez-alvarez July 12, 2026 12:11

leoromanovsky added comp: openfeature OpenFeature type: feature Enhancements and improvements labels Jul 12, 2026

datadog-datadog-prod-us1-2 Bot reviewed Jul 12, 2026

View reviewed changes

Comment thread ...feature-flagging-lib/src/main/java/com/datadog/featureflag/AgentlessConfigurationSource.java

Warn on agentless authentication failures

17a02ad

leoromanovsky mentioned this pull request Jul 13, 2026

Add offline Feature Flagging reference implementation #11933

Draft

typotter approved these changes Jul 14, 2026

View reviewed changes

leoromanovsky added 2 commits July 14, 2026 22:15

fix(ffe): handle nullable agentless response bodies

5057539

pavlokhrebto reviewed Jul 15, 2026

View reviewed changes

Merge branch 'master' into leo.romanovsky/ffl-2693-java-agentless-con…

7aa2181

…figuration-source

Uh oh!

Conversation

leoromanovsky commented Jul 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

NOTE TO REVIEWERS

How to Review

Commit Guide

Per-Commit Validation

Stack Position

Motivation

Changes

Decisions

Initialization Modes

Customer Usage Example

Verification

System Test Evidence

Next Steps

Uh oh!

This comment has been minimized.

dd-octo-sts Bot commented Jul 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🟢 Java Benchmark SLOs — All performance SLOs passed

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

dd-octo-sts Bot commented Jul 12, 2026

Uh oh!

datadog-datadog-prod-us1-2 Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

pavlokhrebto left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

leoromanovsky commented Jul 8, 2026 •

edited

Loading

dd-octo-sts Bot commented Jul 8, 2026 •

edited

Loading