From 4361c320372e6fdc035577b07f979cccaf447a06 Mon Sep 17 00:00:00 2001 From: Charles de Beauchesne Date: Tue, 27 Oct 2026 12:12:53 +0100 Subject: [PATCH 1/2] Load the dd-openfeature SDK of the same build for java dev Java dev only loaded the dd-java-agent snapshot, so weblogs and the parametric app used the latest released dd-openfeature from Maven. Since dd-trace-java#12844, a dev agent does not work with a released SDK, and the parametric FFE tests fail with PROVIDER_NOT_READY. dd-trace-java publishes dd-openfeature.jar next to dd-java-agent.jar: load it too, and keep the released one if it's missing. Co-Authored-By: Claude Opus 5.5 --- utils/scripts/load-binary.sh | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/utils/scripts/load-binary.sh b/utils/scripts/load-binary.sh index 378da8b92ea..5f66d47829f 100755 --- a/utils/scripts/load-binary.sh +++ b/utils/scripts/load-binary.sh @@ -206,6 +206,16 @@ elif [ "$TARGET" = "java" ] || [ "$TARGET" = "java_lambda" ]; then curl --fail --location --silent --show-error --output dd-java-agent.jar "https://s3.us-east-1.amazonaws.com/dd-trace-java-builds/${LIBRARY_TARGET_BRANCH}/dd-java-agent.jar" + if [ "$TARGET" = "java" ]; then + # the dd-openfeature SDK of the same build: the released one, used by default, may not work with a dev agent. + # Not for java_lambda: its runtime image has no maven to install it, and its weblog does not use it. + # Builds older than dd-trace-java#12844 did not publish it: the released one is used then + if ! curl --fail --location --silent --show-error --output dd-openfeature.jar "https://s3.us-east-1.amazonaws.com/dd-trace-java-builds/${LIBRARY_TARGET_BRANCH}/dd-openfeature.jar"; then + rm -f dd-openfeature.jar + echo "No dd-openfeature.jar for ${LIBRARY_TARGET_BRANCH}, the released dd-openfeature will be used" + fi + fi + elif [ "$TARGET" = "dotnet" ]; then assert_version_is_dev From 4db052452fc1af60caa44060783a6b547cbf91cb Mon Sep 17 00:00:00 2001 From: Charles de Beauchesne Date: Tue, 27 Oct 2026 14:33:59 +0100 Subject: [PATCH 2/2] Fail when the dd-openfeature SDK can't be loaded, with retries Falling back to the released SDK hid every download failure, not only a missing jar, and the released SDK does not work with a dev agent. Co-Authored-By: Claude Opus 5.5 --- utils/scripts/load-binary.sh | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/utils/scripts/load-binary.sh b/utils/scripts/load-binary.sh index 5f66d47829f..6f04e57fbd1 100755 --- a/utils/scripts/load-binary.sh +++ b/utils/scripts/load-binary.sh @@ -208,12 +208,8 @@ elif [ "$TARGET" = "java" ] || [ "$TARGET" = "java_lambda" ]; then if [ "$TARGET" = "java" ]; then # the dd-openfeature SDK of the same build: the released one, used by default, may not work with a dev agent. - # Not for java_lambda: its runtime image has no maven to install it, and its weblog does not use it. - # Builds older than dd-trace-java#12844 did not publish it: the released one is used then - if ! curl --fail --location --silent --show-error --output dd-openfeature.jar "https://s3.us-east-1.amazonaws.com/dd-trace-java-builds/${LIBRARY_TARGET_BRANCH}/dd-openfeature.jar"; then - rm -f dd-openfeature.jar - echo "No dd-openfeature.jar for ${LIBRARY_TARGET_BRANCH}, the released dd-openfeature will be used" - fi + # Not for java_lambda: its runtime image has no maven to install it, and its weblog does not use it + curl --fail --retry 3 --location --silent --show-error --output dd-openfeature.jar "https://s3.us-east-1.amazonaws.com/dd-trace-java-builds/${LIBRARY_TARGET_BRANCH}/dd-openfeature.jar" fi elif [ "$TARGET" = "dotnet" ]; then