Skip to content
This repository has been archived by the owner on May 30, 2024. It is now read-only.

prepare 4.11.0 release #181

Closed
wants to merge 358 commits into from
Closed

prepare 4.11.0 release #181

wants to merge 358 commits into from

Conversation

LaunchDarklyCI
Copy link
Contributor

[4.11.0] - 2020-01-15

Added:

  • When an EvaluationReason indicates that flag evaluation failed due to an unexpected exception (getKind() is ERROR, and EvaluationReason.Error.getErrorKind() is EXCEPTION), you can now examine the underlying exception via EvaluationReason.Error.getException(). (#180)
  • It is now possible to specify an infinite cache TTL for persistent feature stores by setting the TTL to a negative number, in which case the persistent store will never be read unless the application restarts. Use this mode with caution as described in the comment for FeatureStoreCacheConfig.getCacheTime().

Fixed:

  • The SDK now specifies a uniquely identifiable request header when sending events to LaunchDarkly to ensure that events are only processed once, even if the SDK sends them two times due to a failed initial attempt.

pkaeding and others added 30 commits November 15, 2018 16:16
…ation-for-java-android-sdks

fix fossa integration
fix build script to ensure all of our packages are correctly included
add feature store support classes and use them in Redis
eli-darkly and others added 24 commits December 13, 2019 13:33
don't let user fall outside of last bucket in rollout
add unit tests for basic bucketing logic
(4.x - #1) start renaming FeatureStore & UpdateProcessor to DataStore & DataSource
…kage

(4.x - #2) move Redis and FileData stuff into new integrations subpackage
@eli-darkly
Copy link
Contributor

Closing this because we need to back out a couple of changes that aren't ready yet.

@eli-darkly eli-darkly closed this Jan 16, 2020
@eli-darkly eli-darkly deleted the release-4.11.0 branch January 16, 2020 03:04
LaunchDarklyCI pushed a commit that referenced this pull request Jan 30, 2020
(1 of 2) allow each component to describe its own configuration for diagnostics
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants