Conflict between cbstreams and LD Java SDK version 6.1.0+

SMSMichael commented 10 months ago

LaunchDarkly introduced a feature with the 6.1.0 release of their Java SDK:

Support for Payload Filtering in streaming and polling modes. Payload Filtering is a beta feature that allows SDKs to download a subset of environment data, rather than full environments. Please contact your account executive for more information. (from https://github.com/launchdarkly/java-server-sdk/releases/tag/6.1.0)

While I'm assuming this change won't impact the majority of users, one of our applications uses cbstreams and it appears that this functionality is conflicting with the way that cbstreams manages java streams. Currently we are unable to use cbstreams while the current version of the LaunchDarklySDK module (using the 6.2.1 Java SDK) installed.

We're seeing an issue centered around a line of code that looks like this:

myResults = StreamBuilder
            .new( myArray )
            .map( invokeComponentMethod )
            .parallel()
            .collect()
        >

downgrading the LaunchDarkly SDK to v6.0.6 resolves this issue in the short term.

SMSMichael commented 10 months ago

File diffs between LaunchDarkly Java SDK 6.0.6 and 6.1.0 (when issue was introduced) can be found here: https://github.com/launchdarkly/java-server-sdk/compare/6.0.6...6.1.0

SMSMichael commented 8 months ago

Good news - it seems like the latest v6 SDK (6.3.0) has resolved the issue as far as we can tell. We will be monitoring for the next week or so and then I plan on closing out this issue.

SMSMichael commented 7 months ago

Confirming that we're not seeing the same issues with the 6.3.0 Java SDK, so I'm going to close this issue.

coldbox-modules / LaunchDarklySDK

Conflict between cbstreams and LD Java SDK version 6.1.0+ #7