Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Updates the keying mechanism for evaluation metrics to use a concatenated string format: "#{feature_name}\0#{variation_identifier}". This string combines the feature_name and variation_identifier separated by a null character (\0). This change replaces the previous approach of keying on the MetricsEvent class, which has now been deleted.
Why
We see an edge case occurring during the iteration of evaluation metrics when aggregating and sending data. Specifically, the keys seem to reference other objects in memory, and seg faults. Although Ruby permits using class objects as keys, the evaluation cache uses a hash with string keys and does not suffer from the same problem, so the intent is standardise on string keys to see if we can fix this edge case.
Testing