Gen Xu

I have encountered similar issue. Not only batch processor but also the hostmetrics receiver/scrapehelper seesm to have memory leak issue too. I am using hostmetrics with 0.1 seconds to exaggerate...

> Could you show your config file of collector? @gen-xu @fatsheep9146 we had some secrets in config but the following should reproduce the unbounded increasing of memory usage. ```yaml extensions:...

Any news about this? it would also be nice to have async tracer as well so we can do something like this ```python async with tracer.start_span_async("span"): pass ```

@TBBle yes if we have `AsyncSpanProcessor` then we might need `start_span_async`, but there are some other places I see a need with `start_span_async`: `opentelemetry.sdk.trace.Span` has a `_lock` attribute, while in...

@gshpychka Thanks for the link, didn't know there was a benchmark page available. I think the numbers I gave were not accurate, which are based on the viztracer library I...

This is a major breaking change afaik as old protobuf library version won't be able to use newer generated protobuf code, and it would force user to upgrade newer protobuf...

I have created a work around for this https://github.com/open-telemetry/opentelemetry-python/pull/2954 Not sure if we want to accept PR since I would also agree if anyone think this is an issue of...

@LucioFranco yes I agree it goes against naming convention. But sometime I think there are needs for that. For example XML, GPIO are very commonly used abbreviations together as all...

> @gen-xu I can not accept the PR: with this change, we generally convert any type of exception to the `Exception`. This is a serious API change that can create...

+1 on this, and any status update on this? it looks like there was a PR open from 2+ years ago? sometimes if I want to pretty print something, default...