Skip to content

chore: update openai latest version to 3.3.1 - #19845

Open
dd-octo-sts[bot] wants to merge 1 commit into
mainfrom
upgrade-latest-openai-version
Open

chore: update openai latest version to 3.3.1#19845
dd-octo-sts[bot] wants to merge 1 commit into
mainfrom
upgrade-latest-openai-version

Conversation

@dd-octo-sts

@dd-octo-sts dd-octo-sts Bot commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Update openai lockfiles and dependency package lockfiles.
This performs the following updates:

  1. Some openai lockfiles use openai latest. This will update openai and dependencies.
  2. Some openai lockfiles use a pinned (non-latest) version of openai, but require the latest version of another package. This will update all such packages.

@dd-octo-sts dd-octo-sts Bot added the changelog/no-changelog A changelog entry is not required for this PR. label Aug 25, 2026
@dd-octo-sts
dd-octo-sts Bot requested review from a team as code owners August 25, 2026 00:21
@dd-octo-sts
dd-octo-sts Bot requested review from brettlangdon and wantsui August 25, 2026 00:21
@cit-pr-commenter-54b7da

Copy link
Copy Markdown

Codeowners resolved as

Resolved from the full PR diff against main using the target branch CODEOWNERS file.
CODEOWNERS team requests not listed below are not required by the current file set.

.riot/requirements/109d638.txt                                          @DataDog/apm-python
.riot/requirements/132e4bd.txt                                          @DataDog/apm-python
.riot/requirements/134082f.txt                                          @DataDog/apm-python
.riot/requirements/1458d7e.txt                                          @DataDog/apm-python
.riot/requirements/14aa6df.txt                                          @DataDog/apm-python
.riot/requirements/1547cc9.txt                                          @DataDog/apm-python
.riot/requirements/162cf2e.txt                                          @DataDog/apm-python
.riot/requirements/16a63d7.txt                                          @DataDog/apm-python
.riot/requirements/1882fe7.txt                                          @DataDog/apm-python
.riot/requirements/19be394.txt                                          @DataDog/apm-python
.riot/requirements/1b544ab.txt                                          @DataDog/apm-python
.riot/requirements/1d14cdc.txt                                          @DataDog/apm-python
.riot/requirements/35f0cba.txt                                          @DataDog/apm-python
.riot/requirements/41b0f95.txt                                          @DataDog/apm-python
.riot/requirements/51ae308.txt                                          @DataDog/apm-python
.riot/requirements/5301b11.txt                                          @DataDog/apm-python
.riot/requirements/663ca38.txt                                          @DataDog/apm-python
.riot/requirements/6d1e866.txt                                          @DataDog/apm-python
.riot/requirements/77994b3.txt                                          @DataDog/apm-python
.riot/requirements/95d28c3.txt                                          @DataDog/apm-python
.riot/requirements/a2b9112.txt                                          @DataDog/apm-python
.riot/requirements/a827c2f.txt                                          @DataDog/apm-python
.riot/requirements/a9f0bf3.txt                                          @DataDog/apm-python
.riot/requirements/bbcdb10.txt                                          @DataDog/apm-python
.riot/requirements/bd89eb3.txt                                          @DataDog/apm-python
.riot/requirements/ec404a0.txt                                          @DataDog/apm-python
scripts/integration_registry/registry.yaml                              @DataDog/apm-idm-python
supported_versions.json                                                 @DataDog/apm-core-python @DataDog/apm-idm-python

@cit-pr-commenter-54b7da

Copy link
Copy Markdown

Circular import analysis

⚠️ Existing circular imports

There are 3 circular imports that already exist on the base branch and have not been changed by this PR.

ddtrace.llmobs -> ddtrace.llmobs._evaluators -> ddtrace.llmobs._evaluators.format -> ddtrace.llmobs._experiment -> ddtrace.llmobs
ddtrace.errortracking._handled_exceptions.bytecode_injector -> ddtrace.errortracking._handled_exceptions.callbacks -> ddtrace.errortracking._handled_exceptions.collector -> ddtrace.errortracking._handled_exceptions.bytecode_reporting -> ddtrace.errortracking._handled_exceptions.bytecode_injector
ddtrace.appsec._asm_request_context -> ddtrace.appsec._iast._iast_request_context_base -> ddtrace.appsec._iast._iast_env -> ddtrace.appsec._iast.reporter -> ddtrace.appsec._exploit_prevention.stack_traces -> ddtrace.appsec._asm_request_context

@cit-pr-commenter-54b7da

Copy link
Copy Markdown

Dependency direction analysis

⚠️ Existing dependency direction violations

There are 250 dependency direction violations that already exist on the base branch and have not been changed by this PR.

Show existing violations (showing 5 of 250 highest severity)
ddtrace.internal.tracemethods -×-> ddtrace.trace  (internal-core -> product:tracing, score=135)
ddtrace.llmobs._integrations.claude_agent_sdk -×-> ddtrace.trace  (product:llmobs -> product:tracing, score=133)
ddtrace.llmobs._integrations.base -×-> ddtrace.trace  (product:llmobs -> product:tracing, score=133)
ddtrace.llmobs._evaluators.runner -×-> ddtrace.trace  (product:llmobs -> product:tracing, score=133)
ddtrace.internal.test_visibility.api -×-> ddtrace.trace  (product:ci_visibility -> product:tracing, score=133)

To see all violations, download the layers-base.json and layers-pr.json artifacts from this CI job and run:

uv run --script scripts/import-analysis/layers.py compare layers-base.json layers-pr.json

@chatgpt-codex-connector chatgpt-codex-connector 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9fb485b040

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

httpcore==1.0.9
httpx==0.28.1
httpcore2==2.12.0
httpx2==2.12.0

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Keep a compatible HTTPX module in OpenAI test environments

For the latest OpenAI environments on Python 3.10–3.13, this replaces the httpx distribution with httpx2, which exposes a separate httpx2 module rather than httpx. However, the suite runs the entire tests/contrib/openai directory and test_openai_appsec_llm_events.py unconditionally executes import httpx during collection, so these four environments fail with ModuleNotFoundError before testing OpenAI 3.3.1. The test dependencies and transport clients need to be adapted for the renamed module, or a compatible httpx dependency must remain installed.

Useful? React with 👍 / 👎.

@datadog-official

datadog-official Bot commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Pipelines  Tests

Unblock PR with BitsAI

⚠️ Warnings

🚦 8 Pipeline jobs failed

DataDog/apm-reliability/dd-trace-py | build linux serverless: [amd64, cp315-cp315, v113741238-d2b8243-manylinux2014_x86_64, 1] — 🔧 Needs a code fix, caused by this PR

View more details · View in GitLab

DataDog/apm-reliability/dd-trace-py | build linux serverless: [arm64, cp315-cp315, v113741357-d2b8243-manylinux2014_aarch64, 1] — 🔧 Needs a code fix, caused by this PR

View more details · View in GitLab

DataDog/apm-reliability/dd-trace-py | build linux: [amd64, cp315-cp315, v113741238-d2b8243-manylinux2014_x86_64] — 🔧 Needs a code fix, caused by this PR

View more details · View in GitLab

View all 8 failed jobs.

ℹ️ Info

No other issues found (see more)

🧪 All tests passed
❄️ No new flaky tests detected

Useful? React with 👍 / 👎

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

@pr-commenter

pr-commenter Bot commented Aug 25, 2026

Copy link
Copy Markdown

Benchmarks

Benchmark execution time: 2026-08-25 00:48:52

Comparing candidate commit 9fb485b in PR branch upgrade-latest-openai-version with baseline commit 16de34b in branch main.

📊 Benchmarking dashboard

Found 0 performance improvements and 8 performance regressions! Performance is the same for 578 metrics, 10 unstable metrics, 2 known flaky benchmarks, 16 flaky benchmarks without significant changes.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

  • 🟩 = significantly better candidate vs. baseline
  • 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

scenario:httppropagationinject-ids_only

  • 🟥 execution_time [+1.874µs; +2.012µs] or [+9.731%; +10.447%]

scenario:iastaspects-add_aspect

  • 🟥 execution_time [+13.724µs; +17.197µs] or [+13.408%; +16.801%]

scenario:iastaspects-join_aspect

  • 🟥 execution_time [+50.218µs; +54.408µs] or [+23.909%; +25.903%]

scenario:iastaspects-title_aspect

  • 🟥 execution_time [+66.421µs; +73.190µs] or [+24.758%; +27.281%]

scenario:iastaspectsospath-ospathbasename_aspect

  • 🟥 execution_time [+129.874µs; +136.248µs] or [+30.677%; +32.183%]

scenario:iastaspectssplit-rsplit_aspect

  • 🟥 execution_time [+17.776µs; +21.416µs] or [+12.303%; +14.823%]

scenario:telemetryaddmetric-1-count-metric-1-times

  • 🟥 execution_time [+395.545ns; +446.084ns] or [+14.513%; +16.367%]

scenario:tracer-small

  • 🟥 execution_time [+29.179µs; +31.603µs] or [+8.704%; +9.427%]

Unstable benchmarks

These benchmarks have a confidence interval too wide to call a change; treat them as noise rather than signal.

scenario:coreapiscenario-context_with_data_listeners

  • unstable execution_time [-769.793ns; +721.381ns] or [-6.932%; +6.496%]

scenario:coreapiscenario-core_dispatch_1_listener

  • unstable execution_time [-35.108ns; +31.408ns] or [-5.741%; +5.136%]

scenario:coreapiscenario-core_dispatch_50_listeners

  • unstable execution_time [-1636.725ns; +1700.760ns] or [-9.560%; +9.934%]

scenario:coreapiscenario-core_dispatch_exception_listeners

  • unstable execution_time [-1362.368ns; +1103.377ns] or [-10.515%; +8.516%]

scenario:coreapiscenario-core_dispatch_listeners

  • unstable execution_time [-346.506ns; +311.702ns] or [-9.377%; +8.435%]

scenario:coreapiscenario-core_dispatch_no_args_listeners

  • unstable execution_time [-252.767ns; +254.174ns] or [-8.700%; +8.748%]

scenario:coreapiscenario-core_dispatch_with_results_1_listener

  • unstable execution_time [-68.795ns; +76.997ns] or [-6.119%; +6.848%]

scenario:coreapiscenario-core_dispatch_with_results_50_listeners

  • unstable execution_time [-3889.008ns; +4108.547ns] or [-9.553%; +10.093%]

scenario:coreapiscenario-core_dispatch_with_results_listeners

  • unstable execution_time [-805.859ns; +709.507ns] or [-10.043%; +8.842%]

scenario:packagesupdateimporteddependencies-import_many_stdlib_cached

  • unstable execution_time [-55.645µs; +62.110µs] or [-8.928%; +9.965%]

Known flaky benchmarks

These benchmarks are marked as flaky and will not trigger a failure. Modify FLAKY_BENCHMARKS_REGEX to control which benchmarks are marked as flaky.

scenario:iastaspects-ljust_noaspect

  • 🟥 execution_time [+46.223µs; +51.918µs] or [+15.564%; +17.481%]

scenario:span-start

  • 🟥 execution_time [+1.655ms; +1.797ms] or [+11.105%; +12.062%]

Known flaky benchmarks without significant changes:

  • scenario:errortrackingflasksqli-baseline
  • scenario:flasksimple-iast-get
  • scenario:iastaspects-casefold_aspect
  • scenario:iastaspects-casefold_noaspect
  • scenario:iastaspects-index_aspect
  • scenario:iastaspects-lower_aspect
  • scenario:iastaspects-replace_aspect
  • scenario:iastaspects-swapcase_aspect
  • scenario:iastaspects-title_noaspect
  • scenario:iastaspects-translate_aspect
  • scenario:iastaspects-translate_noaspect
  • scenario:iastaspects-upper_noaspect
  • scenario:packagespackageforrootmodulemapping-cache_off
  • scenario:packagespackageforrootmodulemapping-cache_on
  • scenario:sethttpmeta-all-enabled
  • scenario:telemetryaddmetric-record-100-metrics

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog/no-changelog A changelog entry is not required for this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant