<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<br>
<br>
<div class="moz-cite-prefix">On 24/10/2025 18:40, Wesley Hill wrote:<br>
</div>
<blockquote type="cite" cite="mid:CALz0bqnGpPapW9mYENNhXEZ0sMjOyMSfyotYdMR3UGRQdO55pA@mail.gmail.com">
<div dir="ltr">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Thanks
for writing up your experiences. What pain points would have<br>
remain if somehow OpenTelemetry could use ScopedValues?</blockquote>
<div><br>
</div>
<div>Ignoring that OTel Context propagation pain point, there
was the one other pain point related to Configuration:</div>
<div>
<ul>
<li>There's no accessor with which to get the timeout
configured on a JDK's Configuration object, and</li>
<li>Configuration.withTimeout does not allow passing null to
clear an already-set timeout.</li>
</ul>
So we would still need our own copy of the Configuration class
to manage the fact that we want to know the timeout to set the
Deadline on our Context, and we don't want to pass the timeout
down to StructuredTaskScope since we're managing cancellation
our way.</div>
<br>
</div>
</blockquote>
Could you expand a bit on how this arises? There is no timeout by
default so something (the composite object?) must be calling
withTimeout to set a timeout, then something else is looking to
remove it (or set it to Duration.ofDays(Long.MAX_VALUE), which is
effectively the same thing). If I read your first mail correctly
then the telemetry Context is self destructing object and the
Configuration is being used to carry the Context deadline through to
the Context, is that right?<br>
<br>
-Alan<br>
</body>
</html>