RUMM-15 Gitlab CI setup#2
Merged
Merged
Conversation
xgouchet
force-pushed
the
xgouchet/RUMM-15_ci
branch
2 times, most recently
from
November 12, 2019 11:49
31cf267 to
dba73ee
Compare
xgouchet
force-pushed
the
xgouchet/RUMM-15_ci
branch
from
November 12, 2019 12:43
dba73ee to
e7d7a37
Compare
priyanshi-gupta
added a commit
to priyanshi-gupta/dd-sdk-android
that referenced
this pull request
Apr 20, 2021
This was referenced Jan 22, 2026
typotter
added a commit
that referenced
this pull request
Jan 22, 2026
Implements persistence and network transport for evaluation events. Storage layer (EvaluationEventRecordWriter): - Implements EvaluationEventWriter interface from PR #2 - Serializes FlagEvaluation events to JSON - Persists to SDK Core storage as RawBatchEvent - Thread-safe with synchronized writes Network layer (EvaluationsRequestFactory): - Creates HTTP requests to /api/v2/flagevaluations endpoint - Builds BatchedFlagEvaluations payload per EVALLOG.1 specification - Wraps individual FlagEvaluation events with top-level context: - Service metadata (service, version, env) - Device info (name, type, brand, model) - OS info (name, version) - RUM context (application.id, view.url) - Handles malformed events gracefully (skip and log) - Standard EVP headers (API key, origin, origin version, request ID) EVALLOG.1 compliance: - Endpoint: /api/v2/flagevaluations - Content-Type: application/json - Payload: {"context": {...}, "flagEvaluations": [...]} Depends on BatchedFlagEvaluations model from PR #1. Uses EvaluationEventWriter interface from PR #2.
This was referenced Jan 22, 2026
typotter
added a commit
that referenced
this pull request
Jan 22, 2026
Implements persistence and network transport for evaluation events. Storage layer (EvaluationEventRecordWriter): - Implements EvaluationEventWriter interface from PR #2 - Serializes FlagEvaluation events to JSON - Persists to SDK Core storage as RawBatchEvent - Thread-safe with synchronized writes Network layer (EvaluationsRequestFactory): - Creates HTTP requests to /api/v2/flagevaluations endpoint - Builds BatchedFlagEvaluations payload per EVALLOG.1 specification - Wraps individual FlagEvaluation events with top-level context: - Service metadata (service, version, env) - Device info (name, type, brand, model) - OS info (name, version) - RUM context (application.id, view.url) - Handles malformed events gracefully (skip and log) - Standard EVP headers (API key, origin, origin version, request ID) EVALLOG.1 compliance: - Endpoint: /api/v2/flagevaluations - Content-Type: application/json - Payload: {"context": {...}, "flagEvaluations": [...]} Depends on BatchedFlagEvaluations model from PR #1. Uses EvaluationEventWriter interface from PR #2.
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.