Aaron Abbott

There are two separate concepts here 1. Setting the span in OpenTelemetry's current implicit context. Doing this causes any new spans to automatically become a child, without having to pass...

I'm guessing that PyInstaller is the issue, does it support entry points from dists you install? If this continue to be an issue, we should consider using the contextvars implementation...

Alternatively, it would be really handy if it turned the message into a git commit along the PR branch to avoid force pushing altogether. For folks using Github pull requests,...

Unfortunately not right now. I'll leave this open as a feature request but we aren't willing to accept a contribution for this right now

Looking at the new cardinality limits in the spec, specifically for synchronous instruments [it says](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/sdk.md#synchronous-instrument-cardinality-limits) > Views of synchronous instruments with cumulative aggregation temporality MUST continue to export the all...

Thanks for reporting. There is definitely a bug here but I'm not sure the best fix it. We are actually wrapping Prometheus client with a [custom collector](https://github.com/prometheus/client_python#custom-collectors) to avoid reimplementing...

@soundofspace > (as far as I understand prometheus also supports missing labels). I don't think the official prometheus client does. It requires specifying all label names at instrument creation and...

Ok, I think we will have to move away from using the prometheus client. I don't see a way to prevent it from generating UNIT, HELP, or TYPE for each...

This sounds like a bug for sure. @dhausauer-flx if you know a fix, would you mind submitting a PR? Otherwise if someone can provide a minimal repro (I understand it's...

If you check the original #62 you'll find some workarounds. I think we need some consensus from the project maintainers if we want to go ahead with this feature request...