Releases: harness/ff-python-server-sdk
Releases · harness/ff-python-server-sdk
1.1.12
What's Changed
- FFM-7880 - If an error occurs when processing a new stream event, the SDK will now log that error correctly instead of potentially logging a blank string by @erdirowlands in #63
Full Changelog: 1.1.11...1.1.12
1.1.11
What's Changed
- FFM-6410 - The SDK will now evaluate a flag with multiple and/or nested prerequisites correctly by @erdirowlands in #62
Full Changelog: 1.1.10...1.1.11
1.1.10
What's Changed
- FFM-7360 - The SDK will now log an error if an evaluation fails and the default variation is returned by @erdirowlands in #58
Full Changelog: 1.1.9...1.1.10
1.1.9
What's Changed
- FFM-6932 - SDK seems to disconnect from the relay proxy by @andybharness in #57
New Contributors
- @andybharness made their first contribution in #57
Full Changelog: 1.1.8...1.1.9
1.1.8
What's Changed
- [FFM-6549]: Add
wait_for_initializationto the client API which can be called to block the thread until all groups and flags have been retrieved and loaded into cache. - [FFM-6549]: Add
is_initializedto the client API which can be called at any time to check if the initial retrieval and caching of groups and flags has been completed.
Notes
- For example usage of the above see: wait_for_initialization.py
Full Changelog: 1.1.7...1.1.8
1.1.7
Bugfix:
[FFM-5991]:
- Adding Targets to Group based on conditions: the
inoperator is now case-sensitive in the SDK.
Important: Please read before upgrading to this release:
- if you are targeting any Groups using the
inoperator, please ensure that your Target condition takes into account the case sensitivity of the operator.
1.1.6
Bugfix:
[FFM-5995]: Target Attribute values which were not strings would result in a 500 error from the metric service.
1.1.5
Bugfix:
- [FFM-5995]:
- All unique Targets would not get registered during a metrics interval
- The first metrics posting after Client initialisation could result in a 400 error
1.1.4
1.1.3
What's Changed
- FFM-4813 - Fix logic for target group clauses where OR's where being treated as AND's by @stephenmcconkey in #43
Full Changelog: 1.1.2...1.1.3