Skip to content

Conversation

@mwisnicki
Copy link
Contributor

@mwisnicki mwisnicki commented Jun 23, 2025

DDEntryPoint activates created spans so DDSpan should too.

Activation binds span to current thread via ThreadLocal so it will become incorrect when IO/Fiber switches threads but at least it's an improvement and consistent with root spans.

Ideally there would be a Span option to disable activation entirely like this: #1187

Activation binds span to current thread via ThreadLocal so it will become incorrect
when IO/Fiber switches threads but at least it's an improvement and consistent with
root spans.

Ideally there would be a Span option to disable activation entirely.
@mergify mergify bot added the datadog label Jun 23, 2025
}
.flatTap(span =>
Resource.make(Sync[F].delay(tracer.activateSpan(span)))(s => Sync[F].delay(s.close()))
)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copied from

.flatTap(span =>
Resource.make(Sync[F].delay(tracer.activateSpan(span)))(s => Sync[F].delay(s.close()))
)

@mwisnicki
Copy link
Contributor Author

As per #1187 (comment) I now think that the right thing to do here is to never activate span since it is likely useless unless used as in #1189

@mwisnicki
Copy link
Contributor Author

Obsoleted by #1191

@mwisnicki mwisnicki closed this Jun 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants