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 #182

Merged
merged 345 commits into from
Jan 16, 2020
Merged

prepare 4.11.0 release #182

merged 345 commits into from
Jan 16, 2020

Conversation

eli-darkly
Copy link
Contributor

[4.11.0] - 2020-01-16

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)

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.

eli-darkly and others added 25 commits November 11, 2019 19:39
…d-methods

improve LdValue helper methods and tests
…other fixes

This reverts commit 5b6fd8e, reversing
changes made to 2f4e781.
fix NPE when serializing a user that wasn't created through the builder
* fix summary event output bug (2 entries for same flag) due to String ==

* sort private attrs list for test determinacy

* add full test coverage for event output formatting

* comment

* clarify order of operations
* add CircleCI Windows job, simplify CI config

* CI fix

* CI fixes

* use --no-daemon on Windows
don't let user fall outside of last bucket in rollout
add unit tests for basic bucketing logic
@eli-darkly eli-darkly requested a review from bwoskow-ld January 16, 2020 03:16
@eli-darkly eli-darkly merged commit 5bbaa7b into master Jan 16, 2020
@eli-darkly eli-darkly deleted the release-4.11.0 branch January 16, 2020 19:36
LaunchDarklyCI pushed a commit that referenced this pull request Jan 30, 2020
(2 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