-
Notifications
You must be signed in to change notification settings - Fork 16
EnvoyCarrier v2 #43
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
EnvoyCarrier v2 #43
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…inary (carrier format)
…inary (carrier format)
PTAL. With the new encoding and your prior example values, I have the base64 value hard-coded in the new carrier_test.cc. |
} | ||
|
||
// Test extraction of a well-known input, for validation with other libraries. | ||
const char same_data64[] = "EigJOjioEaYHBgcRNmifUO7/xlgYASISCgdjaGVja2VkEgdiYWdnYWdl"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As seen here.
throw error("incorrect trace_id"); | ||
} | ||
if (same_basic.basic_ctx().sampled() != true) { | ||
throw error("incorrect trace_id"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Invalid error message
throw error("incorrect trace_id"); | ||
} | ||
if (same_basic.basic_ctx().span_id() != 6397081719746291766L) { | ||
throw error("incorrect trace_id"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Invalid error message
No description provided.