Weights missing when fetched from Redis

[crx]

When an app using Split initially loads, it loads the weights for alternatives from the configuration. These weights are correctly preserved in memory for use by the weighted algorithm.

However, if you're debugging and you call Split::Experiment.all, the experiment objects you get are loaded from Redis, and since Redis doesn't store the weights, all the weights are 1.

I can patch this but I'm wondering what you think the correct behavior is. Should the database store the weights so they can be fetched? Should they just be re-fetched from the configuration?

[phoet]

i think that it would be good for consistency to store all experiment related stuff in redis.

[andrew]

I agree, it makes sense to keep everything around, I suspect there is a subtle, potential issue we should check for, that the weights must be the same for every time the experiment is called.

I bet right now you could use different weights for the same experiment in different places right now, which if we store in a db could cause some strangeness for people.

[phoet]

@andrew i guess that using different weights would also cause strangeness for people 😄

[phoet]

@crx do you have some working code, that we can merge?

[andrew]

I'm closing out some of these old issues, if this is still a problem for you please comment and I'll reopen it.