Skip to content

chore(deps): bump dd-smoke-tests/openfeature/src/test/resources/ffe-system-test-data from b42c4a1 to a596df7#11862

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/submodules/dd-smoke-tests/openfeature/src/test/resources/ffe-system-test-data-a596df7
Open

chore(deps): bump dd-smoke-tests/openfeature/src/test/resources/ffe-system-test-data from b42c4a1 to a596df7#11862
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/submodules/dd-smoke-tests/openfeature/src/test/resources/ffe-system-test-data-a596df7

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 6, 2026

Copy link
Copy Markdown
Contributor

Bumps dd-smoke-tests/openfeature/src/test/resources/ffe-system-test-data from b42c4a1 to a596df7.

Commits
  • a596df7 Merge pull request #17 from DataDog/leo.romanovsky/regex-shard-bound-fixtures
  • ce45493 Add regex and shard-bound fixtures
  • 6c7f63b Merge pull request #16 from DataDog/leo.romanovsky/malformed-split-shards-fix...
  • cf7d7d5 Add missing split shards fixture
  • d9d8020 Merge pull request #15 from DataDog/leo.romanovsky/date-window-assignment-rea...
  • e4803e3 Fix temporal allocation reasons
  • 95ff628 Fix date-window assignment reasons
  • 57e98f5 Merge pull request #14 from DataDog/leo.romanovsky/add-regex-evaluation-cases
  • 6db17e8 Add regex evaluation edge cases
  • 1db25ec Merge pull request #11 from DataDog/leo.romanovsky/ffe-malformed-config-cases
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

…ystem-test-data

Bumps [dd-smoke-tests/openfeature/src/test/resources/ffe-system-test-data](https://github.com/DataDog/ffe-system-test-data) from `b42c4a1` to `a596df7`.
- [Commits](DataDog/ffe-system-test-data@b42c4a1...a596df7)

---
updated-dependencies:
- dependency-name: dd-smoke-tests/openfeature/src/test/resources/ffe-system-test-data
  dependency-version: a596df75dca040c46078b768cd2536c67691523c
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot requested a review from a team as a code owner July 6, 2026 06:03
@dependabot dependabot Bot removed the request for review from a team July 6, 2026 06:03
@dependabot dependabot Bot added the submodules label Jul 6, 2026
@dependabot dependabot Bot requested review from dd-oleksii and leoromanovsky July 6, 2026 06:03
@dd-octo-sts

dd-octo-sts Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

PR Blocked - Invalid Label

The pull request introduced unexpected labels:

  • dependencies
  • submodules

This PR is blocked until:

  1. The invalid labels are deleted, and
  2. A maintainer deletes this comment to unblock the PR

Note: Simply removing labels from the pull request is not enough - a maintainer must delete this comment then remove the label to remove the block.

@dd-octo-sts

dd-octo-sts Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

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.

@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: 6b86e93b4d

ℹ️ 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".

@@ -1 +1 @@
Subproject commit b42c4a104ea70695c8fc3516780951f7434b7906
Subproject commit a596df75dca040c46078b768cd2536c67691523c

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 Align OpenFeature evaluator with bumped fixtures

This submodule revision adds/changes smoke-test fixtures that the current Java evaluator does not satisfy. For example, the updated temporal fixtures now expect reason: DEFAULT, while DDEvaluator.resolveVariant still returns STATIC for active allocations with no rules or shards (products/feature-flagging/feature-flagging-api/src/main/java/datadog/trace/api/openfeature/DDEvaluator.java lines 398-401), and the new malformed/unknown-operator fixtures expect default results even though the deserializer drops those flags and evaluate reports FLAG_NOT_FOUND (lines 101-103). Since OpenFeatureProviderSmokeTest asserts responseBody.reason == testCase.result.reason, the bumped smoke tests will fail until the evaluator/deserializer semantics are updated or these incompatible fixtures are excluded.

Useful? React with 👍 / 👎.

@@ -1 +1 @@
Subproject commit b42c4a104ea70695c8fc3516780951f7434b7906
Subproject commit a596df75dca040c46078b768cd2536c67691523c

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 Skip malformed allocations when collecting exposures

This revision's ufc-config.json includes malformed-allocations-flag where allocations is the string "this-is-not-a-list", but OpenFeatureProviderSmokeTest.buildLoggedAllocations iterates every raw definition.allocations value and immediately reads allocation.key/allocation.doLog (OpenFeatureProviderSmokeTest.groovy lines 207-210). In this bumped config the @Shared loggedAllocations initializer will encounter that string and throw a missing-property error before the smoke tests can even evaluate the cases, so the helper needs to ignore non-list allocations (or otherwise tolerate malformed flags) independently of evaluator fixes.

Useful? React with 👍 / 👎.

@@ -1 +1 @@
Subproject commit b42c4a104ea70695c8fc3516780951f7434b7906
Subproject commit a596df75dca040c46078b768cd2536c67691523c

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Load canonical fixtures with the tolerant parser

The bumped ufc-config.json now intentionally contains malformed flags (for example a string-valued allocations and an out-of-range totalShards), but DDEvaluatorTest.loadCanonicalConfiguration still parses the whole file with a plain Moshi CONFIG_ADAPTER instead of the tolerant UniversalFlagConfigDeserializer used by remote config. When testEvaluateCanonicalFixture runs against this revision, that parser will throw while loading the config before any evaluator assertions run, so the canonical fixture tests need to use the same per-flag-tolerant deserializer or skip malformed fixtures deliberately.

Useful? React with 👍 / 👎.

@dd-octo-sts

dd-octo-sts Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

🟡 Java Benchmark SLOs — Performance SLO warning (near threshold)

Suite Status
Startup 🟡 warning

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.94 s 14.02 s [-1.3%; +0.2%] (no difference)
startup:insecure-bank:tracing:Agent 12.86 s 13.04 s [-2.0%; -0.8%] (maybe better)
startup:petclinic:appsec:Agent 17.49 s 17.19 s [+0.9%; +2.7%] (maybe worse)
startup:petclinic:iast:Agent 17.03 s 17.56 s [-7.3%; +1.3%] (no difference)
startup:petclinic:profiling:Agent 17.32 s 17.36 s [-1.1%; +0.7%] (no difference)
startup:petclinic:sca:Agent 17.60 s 17.45 s [+0.2%; +1.5%] (maybe worse)
startup:petclinic:tracing:Agent 16.21 s 16.63 s [-6.8%; +1.6%] (no difference)

Commit: 6b86e93b · 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.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant