Skip to content

Fix Rollout Bucketer.bucket call & Decision Service logic #71

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

oakbani
Copy link
Contributor

@oakbani oakbani commented Oct 27, 2017

✏️ Bucketer.bucket call arguments fixed and unit tests cases updated to ensure right number of params are passed
✏️ Revision of logic in Decision Service getVariationForFeatureExperiment
✏️ Refactoring of new Decision Service logic

@optibot
Copy link

optibot commented Oct 27, 2017

Can one of the admins verify this patch?

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.0009%) to 99.793% when pulling 967311f on msohailhussain:RolloutBucketingID-Fix&DecisionServiceLogic into 986565a on optimizely:master.

@oakbani
Copy link
Contributor Author

oakbani commented Oct 30, 2017

📝 [OASIS-1962] also addressed in this PR

@msohailhussain
Copy link
Contributor

@wangjoshuah Can you please review

@wangjoshuah
Copy link

build


feature_flag_key = feature_flag['key']
variation = get_variation_for_feature_rollout(feature_flag, user_id, attributes)
if variation
@config.logger.log(
Logger::INFO,
"User '#{user_id}' is in the rollout for feature flag '#{feature_flag_key}'."
"User '#{user_id}' is bucketed into a rollout for feature flag '#{feature_flag_key}'."

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

describe the actual rule the user was bucketed into by logging the audience name as the rule name.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You probably meant to have audience name logged inside the get variation for feature rollout and not at this place. I have put it where you have done in the java sdk

…llout

🖊️ Refactored get_audience_conditions_from_id in project config
🖊️ edited affected test cases
@coveralls
Copy link

Coverage Status

Coverage increased (+0.0004%) to 99.794% when pulling 8912794 on msohailhussain:RolloutBucketingID-Fix&DecisionServiceLogic into 986565a on optimizely:master.

@msohailhussain
Copy link
Contributor

@wangjoshuah Is there anyone else want to review this code?

@wangjoshuah
Copy link

@alda-optimizely you've also worked on this SDK before. Do you want to take a look at the PR?

@wangjoshuah
Copy link

build

4 similar comments
@wangjoshuah
Copy link

build

@wangjoshuah
Copy link

build

@wangjoshuah
Copy link

build

@wangjoshuah
Copy link

build

@mikeproeng37 mikeproeng37 merged commit ef897e2 into optimizely:master Nov 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants