-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
try to fix tracing #9625
try to fix tracing #9625
Conversation
/werft run 👍 started the job as gitpod-build-at-mess-with-tracing.1 |
@@ -28,7 +28,8 @@ export namespace TraceContext { | |||
if (!!parentCtx?.span) { | |||
const ctx = parentCtx?.span?.context(); | |||
if (ctx && !!ctx.toTraceId() && !!ctx.toSpanId()) { | |||
options.references = [opentracing.followsFrom(ctx)]; | |||
// options.references = [opentracing.followsFrom(ctx)]; | |||
options.childOf = ctx; |
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.
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.
@geropl, is this still an issue?
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.
No, I think we should leave it as-is. The problems we faced were mostly solved by Mad's attempts to find dangling spans that were not finish()
ed. 👍
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Closing, because I'm out of ideas on this. |
follow-up to #9281