Uh oh!
There was an error while loading. Please reload this page.
Unify usage of OperatingSystem.architecture() - #11816
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This comment has been minimized.
This comment has been minimized.
🟢 Java Benchmark SLOs — All performance SLOs passed
PR vs. master results
Commit: Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion. |
AlexeyKuznetsov-DD
commented
Jul 1, 2026
/merge |
View all feedbacks in Devflow UI.
The expected merge time in
|
466cc7c
into
masterUh oh!
There was an error while loading. Please reload this page.
What Does This Do
Unifies all call sites to use
OperatingSystem.architecture()instead of the statically-importedarchitecture(), removing theimport static datadog.environment.OperatingSystem.architectureimports across the codebase.Motivation
Addresses PR #11364 review feedback to keep usage of the
OperatingSystemutility consistent. Qualifying calls withOperatingSystem.architecture()makes it explicit where the architecture check comes from and avoids ambiguity at the call site.Additional Notes