Skip to content

fix(bucketer): Don't log invalid variation ID warning when bucketed into traffic allocation range with empty string entityId #549

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

Merged
merged 1 commit into from
Aug 10, 2020

Conversation

mjc1283
Copy link
Contributor

@mjc1283 mjc1283 commented Aug 10, 2020

Summary

Fix an issue introduced in #515. When bucket returns empty string, we shouldn't log a warning about invalid variation ID. Empty string is a valid value for the entityId property of traffic allocation range objects. There is no invalid variation ID in this situation.

Test plan

Manually tested with A/B tests and rollouts. Added new unit test.

Issues

OASIS-6890

…nto a traffic allocation range with empty string entityId
Copy link
Contributor

@mikeproeng37 mikeproeng37 left a comment

Choose a reason for hiding this comment

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

lgtm

@coveralls
Copy link

Coverage Status

Coverage increased (+0.004%) to 96.774% when pulling f503d74 on mcarroll/OASIS-6890 into 9cea0b6 on master.

@mjc1283 mjc1283 merged commit aeb389d into master Aug 10, 2020
@mjc1283 mjc1283 deleted the mcarroll/OASIS-6890 branch August 10, 2020 18:41
mjc1283 added a commit that referenced this pull request Aug 10, 2020
…nto a traffic allocation range with empty string entityId (#549)

Summary:

Fix an issue introduced in #515. When bucket returns empty string, we shouldn't log a warning about invalid variation ID. Empty string is a valid value for the entityId property of traffic allocation range objects. There is no invalid variation ID in this situation.

Test plan:

Manually tested with A/B tests and rollouts. Added new unit test.

Issues:

OASIS-6890
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.

3 participants