Skip to content
This repository has been archived by the owner on May 23, 2024. It is now read-only.

Do not strip leading zeros from trace IDs #472

Merged
merged 4 commits into from
Nov 15, 2019

Conversation

yurishkuro
Copy link
Member

Resolves #471

Yuri Shkuro added 2 commits November 14, 2019 21:07
Signed-off-by: Yuri Shkuro <ys@uber.com>
Signed-off-by: Yuri Shkuro <ys@uber.com>
@yurishkuro
Copy link
Member Author

I was afraid of this, crossdock fails with:

[trace] go→ (s1name=nodejs s2name=go s2transport=http s3name=nodejs s3transport=http sampled=true) ⇒ Trace ID mismatch in S3(nodejs): expected f4e83e1f67b3c15, received 0f4e83e1f67b3c15

need to fix the test driver to perform comparisons based on full length

Signed-off-by: Yuri Shkuro <ys@uber.com>
@codecov
Copy link

codecov bot commented Nov 15, 2019

Codecov Report

Merging #472 into master will increase coverage by 0.02%.
The diff coverage is 90%.

Impacted file tree graph

@@            Coverage Diff            @@
##           master    #472      +/-   ##
=========================================
+ Coverage   88.08%   88.1%   +0.02%     
=========================================
  Files          59      59              
  Lines        3500    3507       +7     
=========================================
+ Hits         3083    3090       +7     
  Misses        305     305              
  Partials      112     112
Impacted Files Coverage Δ
span_context.go 93.46% <100%> (ø) ⬆️
crossdock/client/trace.go 69.3% <87.5%> (+2.28%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a015c34...e63bbc2. Read the comment docs.

Signed-off-by: Yuri Shkuro <ys@uber.com>
@yurishkuro yurishkuro merged commit 3585cc5 into jaegertracing:master Nov 15, 2019
@yurishkuro yurishkuro deleted the fix-471 branch November 15, 2019 17:30
lukedirtwalker added a commit to lukedirtwalker/jaeger-client-go that referenced this pull request Sep 11, 2020
The wire encoding of the TraceID uses zero prefixes (jaegertracing#472).
The JaegerUI also uses zero prefixes (since 1.16).
So it makes sense that the Stringer of the TraceID also does this.

Resolves jaegertracing#532

Signed-off-by: Lukas Vogel <vogel@anapaya.net>
yurishkuro pushed a commit that referenced this pull request Sep 12, 2020
* TraceID.String prefix with zeroes

The wire encoding of the TraceID uses zero prefixes (#472).
The JaegerUI also uses zero prefixes (since 1.16).
So it makes sense that the Stringer of the TraceID also does this.

Resolves #532

Signed-off-by: Lukas Vogel <vogel@anapaya.net>

* SpanID.String prefix with zeroes

Also test parsing back works.

Signed-off-by: Lukas Vogel <vogel@anapaya.net>

* fix tests?

how do I run this thing locally?

Signed-off-by: Lukas Vogel <vogel@anapaya.net>

* fix tests!

Signed-off-by: Lukas Vogel <vogel@anapaya.net>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Do not strip leading zeros from trace IDs
3 participants