This repository was archived by the owner on May 30, 2024. It is now read-only.
prepare 3.0.3 release #123
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fix error in javadoc code sample
# Conflicts: # CHANGELOG.md # README.md # gradle.properties
# Conflicts: # src/main/java/com/launchdarkly/client/Clause.java # src/test/java/com/launchdarkly/client/FeatureFlagTest.java
add more flag evaluation unit tests
treat unsupported operators as a non-match, don't throw NPE
fix Redis optimistic locking logic to retry updates as needed
…evel reduce "same or lower version" log level to debug
pkaeding
approved these changes
Mar 26, 2018
bwoskow-ld
added a commit
that referenced
this pull request
May 1, 2019
…s-clarification extract gradle properties clarification to separate PR
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[3.0.3] - 2018-03-26
Fixed
NullPointerExceptionwhen trying to evaluate a flag rule that contained an unknown operator type. This could happen if you started using some recently added feature flag functionality in the LaunchDarkly application but had not yet upgraded the SDK to a version that supports that feature. In this case, it should now simply treat that rule as a non-match.Changed
WARNlevel toDEBUG. It can happen frequently in normal operation when the client is in streaming mode, and is not a cause for concern.