Paul "TBBle" Hampson

I've just checked, and with my [buildkit WCOW hacks branch](https://github.com/TBBle/buildkit/tree/hacks_ahoy)@320c037420b2406f7034962d575057e38cbe0a27 (see https://github.com/moby/buildkit/issues/616) the current state of this PR seems to be doing the right thing, copying data into local mounts...

That looks right to me. I haven't gotten around to testing it though.

~~So I'm not sure why, but it _looks_ like if I don't provide the `OTEL_X_EXPORTER` env-vars to the project, I don't get any errors, so I assume it's used the...

Looking at the code while I was implementing a custom distro package, I've just noticed that `"none"` option for the `OTEL_X_EXPORTER` env-vars _is_ supported, it's just handled directly in the...

@gen-xu What do you have in mind for `start_span_async` to actually do? I don't think `start_span` does anything that would need to have an async version (although I guess a...

The things protected by `Span._lock` (AFAICT) would not make sense to protect with an `asyncio.Lock` because there's nothing that would `await`, so there's no contention possible. So what you're actually...

I'm not sure if it should be a separate ticket, but working through how to deliver observable instruments using an async co-routine might be interesting. I haven't really done this...

At least for anyio, I thought it was already being used in the SDK for something, but I just looked and it's not; I must have been thinking of a...

With Helm v2, you could use `--force` to turn the upgrade from PATCH into DELETE+PUT, to work around this sort of thing. With Helm v3, that is not (currently) possible,...

I assume this is about Jaeger, since Jaeger Operator already supported this feature when the ticket was opened, per https://www.jaegertracing.io/docs/1.13/operator/#auto-injecting-jaeger-agent-sidecars.