shutdown tried to join on a phantom thread. The exception was caught and logged, but this cleans it up
0.12.1
Event timestamp was incorrectly statically set. So every event from the python SDK had the same timestamp. This fixes that bug
0.12.0
Adds `get_client_initialize_response(StatsigUser)`. This can be used to generate the initialize response for a given user to be used in a client SDK. If you compute this using the python server SDK, you can bootstrap a statsig client SDK with the result and remove a network round trip to statsig
Also ID list updates to improve reliability and monitoring
0.11.0
Adds event_queue_size parameter to StatsigOptions to make the number of events to batch before flushing to Statsig configurable. Defaults to 500 as before.
Also, internally, wraps, catches, and logs exceptions to statsig via ErrorBoundary so we can debug errors
0.10.3
Rather than logging as exception, log internal SDK messages as warn
0.10.2
We were logging the wrong secondary_exposure array on statsig::layer_exposure