-
Notifications
You must be signed in to change notification settings - Fork 484
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
Fix span links for leading 0s trace ID #539
Fix span links for leading 0s trace ID #539
Conversation
Signed-off-by: Everett Ross <[email protected]>
Codecov Report
@@ Coverage Diff @@
## master #539 +/- ##
==========================================
- Coverage 92.97% 92.95% -0.03%
==========================================
Files 197 197
Lines 4840 4840
Branches 1174 1174
==========================================
- Hits 4500 4499 -1
- Misses 300 301 +1
Partials 40 40
Continue to review full report at Codecov.
|
@@ -208,7 +208,7 @@ export class UnconnectedSearchResults extends React.PureComponent<SearchResultsP | |||
linkTo={getLocation( | |||
trace.traceID, | |||
{ fromSearch: searchUrl }, | |||
spanLinks && spanLinks[trace.traceID] | |||
spanLinks && (spanLinks[trace.traceID] || spanLinks[trace.traceID.replace(/^0*/, '')]) |
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.
I suggest adding a unit test for this use case.
Fix lookback test issue with dst Signed-off-by: Everett Ross <[email protected]>
* Fix span links for leading 0s trace ID * Add tests for deep linking leading 0s Fix lookback test issue with dst Signed-off-by: Everett Ross <[email protected]> Signed-off-by: vvvprabhakar <[email protected]>
Which problem is this PR solving?
?span=${id}@${traceID}
fetches a trace such that:the deep linking would not be passed on.
Short description of the changes
trace.traceID
with leading 0s stripped out iftrace.traceID
is not present inspanLinks