5.6.1

[5.6.1] - 2020-01-06

Fixed:

• In rare circumstances (depending on the exact data in the flag configuration, the flag's salt value, and the user properties), a percentage rollout could fail and return a default value, logging the error "Data inconsistency in feature flag ... variation/rollout object with no variation or rollout". This would happen if the user's hashed value fell exactly at the end of the last "bucket" (the last variation defined in the rollout). This has been fixed so that the user will get the last variation.

5.6.0

[5.6.0] - 2019-08-20

Added:

• Added support for upcoming LaunchDarkly experimentation features. See LDClient.track().

5.5.12

[5.5.12] - 2019-08-05

Fixed:

• Under conditions where analytics events are being generated at an extremely high rate (for instance, if an application is evaluating a flag repeatedly in a tight loop on many threads), it was possible for the internal event processing logic to fall behind on processing the events, causing them to use more and more memory. The logic has been changed to drop events if necessary so that besides the existing limit on the number of events waiting to be sent to LaunchDarkly (config.capacity), the same limit also applies on the number of events that are waiting to be processed by the worker thread that decides whether or not to send them to LaunchDarkly. If that limit is exceeded, this warning message will be logged once: "Events are being produced faster than they can be processed; some events will be dropped". Under normal conditions this should never happen; this change is meant to avoid a concurrency bottleneck in applications that are already so busy that thread starvation is likely.

5.5.11

[5.5.11] - 2019-07-24

Fixed:

• FileDataSource was using YAML.load, which has a known security vulnerability. This has been changed to use YAML.safe_load, which will refuse to parse any files that contain the ! directives used in this type of attack. This issue does not affect any applications that do not use FileDataSource (which is meant for testing purposes, not production use). (#139)

5.5.10

[5.5.10] - 2019-07-24

This release was an error; it is identical to 5.5.9.

5.5.9

[5.5.9] - 2019-07-23

Fixed:

• Due to the gem name no longer being the same as the require name, Bundler autoloading was no longer working in versions 5.5.7 and 5.5.8 of the SDK. This has been fixed. (Thanks, tonyta!)

5.5.8

[5.5.8] - 2019-07-11

Fixed:

• In streaming mode, depending on the Ruby version, calling close on the client could cause a misleading warning message in the log, such as Unexpected error from event source: #<IOError: stream closed in another thread>. (#135)

5.5.7

[5.5.7] - 2019-05-13

Changed:

• Changed the gem name from ldclient-rb to launchdarkly-server-sdk.

There are no other changes in this release. Substituting ldclient-rb version 5.5.6 with launchdarkly-server-sdk version 5.5.7 will not affect functionality.

5.5.6

[5.5.6] - 2019-05-08

Fixed:

• CI tests now include Ruby 2.6.x.
• Running the SDK unit tests is now simpler, as the database integrations can be skipped. See CONTRIBUTING.md.

Note on future releases

The LaunchDarkly SDK repositories are being renamed for consistency. This repository is now ruby-server-sdk rather than ruby-client.

The gem name will also change. In the 5.5.6 release, it is still ldclient-rb; in all future releases, it will be launchdarkly-server-sdk. No further updates to the ldclient-rb gem will be published after this release.

5.5.5

[5.5.5] - 2019-03-28

Fixed:

• Setting user attributes to non-string values when a string was expected would cause analytics events not to be processed. Also, in the case of the secondary attribute, this could cause evaluations to fail for a flag with a percentage rollout. The SDK will now convert attribute values to strings as needed. (#131)