Add initial_reconnect_delay option to config which controls the initial delay for reconnecting the streaming connection.
CI builds now include a cross-platform test suite implemented in https://github.com/launchdarkly/sdk-test-harness. This covers many test cases that are also implemented in unit tests, but may be extended in the future to ensure consistent behavior across SDKs in other areas.
Fixed:
The HTTP_PROXY/HTTPS_PROXY environment variables are now correctly applied for all requests to LaunchDarkly. Previously, this setting worked for streaming flag requests, but did not work for analytics event delivery (or flag polling), causing the latter to be attempted without using the proxy.
Rules targeting secondary attribute on user will now reference the correct value.
all_flags_state will return invalid flag state if the store hasn't initialized properly.
When using all_flags_state to produce bootstrap data for the JavaScript SDK, the Ruby SDK was not returning the correct metadata for evaluations that involved an experiment. As a result, the analytics events produced by the JavaScript SDK did not correctly reflect experimentation results.
The info level message logged when using DynamoDB now correctly identifies the feature store description. (#195)
Changed:
Providing a configuration hash when instantiating a persistent store is now optional.
[6.3.2] - 2022-03-18
Added:
initial_reconnect_delayoption to config which controls the initial delay for reconnecting the streaming connection.Fixed:
HTTP_PROXY/HTTPS_PROXYenvironment variables are now correctly applied for all requests to LaunchDarkly. Previously, this setting worked for streaming flag requests, but did not work for analytics event delivery (or flag polling), causing the latter to be attempted without using the proxy.secondaryattribute on user will now reference the correct value.all_flags_statewill return invalid flag state if the store hasn't initialized properly.all_flags_stateto produce bootstrap data for the JavaScript SDK, the Ruby SDK was not returning the correct metadata for evaluations that involved an experiment. As a result, the analytics events produced by the JavaScript SDK did not correctly reflect experimentation results.Changed: