Releases: sixpack/sixpack
2.5.0
2.4.1
Release version 2.4.1
2.4.0
Release version 2.4.0
2.3.1
bump version
2.1.0
-
Fix restructured text issues in readme. [Jose Diaz-Gonzalez]
-
Add release script. [Jose Diaz-Gonzalez]
-
Add gunicorn and gevent. [Jose Diaz-Gonzalez]
These don't need to be pegged to a specific version, and are confirmed working with gunicorn 17.5 through 19.4.1.
-
Cast the environment variable to an integer. [Dan Alloway]
-
Various improvements to README.rst. [John Bacon]
Consistency improvements throughout the README.
2.0.4
-
Add a config value to disable csrf. [Thomas Meire]
-
Allow traffic fraction to change in mid-flight. [nickveenhof]
-
Fix readme heading for 2.0.1. [Jose Diaz-Gonzalez]
-
Fix early bailout in existing_alternative for excluded clients. [Steve
Webster]Also added an additional assert to the excluded client test that verifies excluded clients have no existing alternative even after a call to
Experiment.get_alternative
. -
[TRAFFIC] Fix over-recording. [zackkitzmiller]
-
Remove round from choose alternative. [chaaaarlie]
Rounding the random number generated at choose_alternative is excluding users who happen to get a random number greater or equal to 0.990000.
-
Added unit tests. [Philipp Jardas]
Redis database is now flushed after every test.
-
Do not check traffic fraction for update on every participation.
[Philipp Jardas]If a participation is requested without a traffic fraction argument, the traffic fraction is no longer assumed to be 1. This caused requests to always fail for experiments with a traffic fraction lower than 1 without explicit argument.
Further, the server no longer defaults the request parameter "traffic_fraction" to 1 but simply leaves it at None. It's up to the model to default this value to 1 only when creating an new experiment.
-
Catch ValueError during g_stat calculation. [Jose Diaz-Gonzalez]
There can be cases where the conversions for a given alternative are zero, resulting in a math domain error when taking the log of the value.
-
Discard conversions from excluded clients when traffic_fraction < 1.
[Thomas Meire]When traffic_fraction is < 1, some clients get the control alternative.
The participations of these excluded clients are not recorded to redis.
When there is a conversion request for an excluded client, the conversion
is not discarded and recorded to redis. When there are a couple of these
conversions by excluded clients, the number of completed conversions
becomes bigger than the number of participants, which should never be
possible. The computation of the confidence_interval relies on this
assumption and fails when the completed_count becomes bigger than
participant_count.The solution is to discard the conversions of excluded clients as well.
-
Fixing participating typo. [nickveenhof]
-
Bump fakeredis version to v0.4.0 for bitcount implementation. [Thomas
Meire] -
Display the number of clients that were excluded from the experiment.
[Thomas Meire] -
Add sixpack-java to list of clients. [Stephen D'Amico]
2.0.3
- [BUG] Fix broken config in some python versions
- [ENHANCEMENT] Add max redis connections config option
2.0.2
- [BUG] Fix broken experiments when a winner is set
2.0.1
- [FEATURE] New 'failing experiments' section in the dashboard
- [ENHANCEMENT] Better error handling
- [BUG] Remove infinite load for failing tests
2.0.0
- [FEATURE] Include new deterministic alternative choice algorithm
- [BUG] Several bug fixes
- [REMOVE] Whiplash/Multi-armed bandit has been removed