1.4.9

Full Changelog: 1.4.8...1.4.9

• No code changes, testing release flow for Harness Code

1.4.8

What's Changed

• techdebt: [FFM-12573]: Migrate build & release pipeline to Harness Code by @andybharness in #57

Full Changelog: 1.4.7...1.4.8

1.4.7

What's Changed

• maint: document initialized function by @conormurray95 in #55
• fix: [FFM-12713]: Limit number of targets in single payload by @andybharness in #56

Full Changelog: 1.4.6...1.4.7

1.4.6

What's Changed

• feat: [FFM-12281]: thread safety fixes by @conormurray95 in #54
• feat: [FFM-12277]: add initialised method by @conormurray95 in #53

Full Changelog: 1.4.5...1.4.6

1.4.5

What's Changed

• FFM-12192 Following from 1.4.4: Resolves an issue where Segmentation faults can occur on Ruby 3.4 and above by @erdirowlands in #52

Full Changelog: 1.4.4...1.4.5

1.4.4

What's Changed

• FFM-12192 Following from 1.4.3, we are still investigating an edge case in the SDK, where segmentation faults can occur when the SDK aggregates and sends metrics at the end of an interval:

  • Replaces concurrent-ruby/ConcurrentMap with our own thread safe hash implementation.
  • Fixed race condition if the optional timeout_ms argument is provided to wait_for_initialization and the SDK times out and initializes at the same time which could cause undefined behaviour for the lifetime of the SDK.

• FFM-12192 Also fixes some behaviour around default variations being returned:

  • Default variations are returned immediately:
    • if the SDK is not initialized or still initializing. This avoids potentially incomplete evaluations caused by partial cache data.
    • if a flag cannot be found and logs a warning.
    • If a requested variation does not match the flag type, the SDK now returns the default variation and logs a warning.

Full Changelog: 1.4.3...1.4.4

by @erdirowlands in #51

1.4.3

What's Changed

• FFM-12192 Following from 1.4.2, we are still investigating an edge case in the SDK, where very large projects can generate invalid metric events shortly after the SDK has initialised. This patch includes possible fixes for this issue. by @erdirowlands in #50

Full Changelog: 1.4.2...1.4.3

1.4.2

What's Changed

• FFM-12192 Following from 1.4.1, we are still investigating an edge case in the SDK, where very large projects can generate invalid metric events shortly after the SDK has initialised. This patch includes possible fixes for this issue. by @erdirowlands in #48

Full Changelog: 1.4.1...1.4.2

1.4.1

What's Changed

• FFM-12192 Skips processing invalid metrics if they are detected. We are currently investigating an edge case in the SDK, where very large projects can generate invalid metric events shortly after the SDK has initialised. This patch release ensures these invalid metrics events are skipped, and a warning is logged if the SDK encounters them. The impact is flag evaluation metrics will not include any events that have been skipped. by @erdirowlands in #47

Full Changelog: 1.4.0...1.4.1

1.4.0

What's Changed

Enhancements

• FFM-12088 Adds an optional timeout parameter for wait_for_initialization, see docs for usage by @erdirowlands in #44

Bug Fixes

The SDK now retries on HTTP code 0 which can be returned by the underlying typhoeus library for uncategorised errors by @erdirowlands in #44

Full Changelog: 1.3.2...1.4.0