feat: implement (de)serialization of binary trace context as utils #812
Conversation
This file contains 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
googlebot
added
the
cla: yes
ofrobots
approved these changes
Jul 18, 2018
src/util.ts
Outdated
| // 18 spanID field ID (1) | ||
| // 19->26 spanID value (traceContext.spanID) | ||
| // 27 options field ID (2) | ||
| // 28 options value (traceContext.options) |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
kjin
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
These functions will be used by gRPC tracing to (de)serialize binary trace context.
Because JS doesn't support the full range of 64-bit numbers, I've added a dependency on
hex2decwhich allows us to convert from arbitrary-length hex to decimal strings and vice-versa.