Yusuke Tsutsumi

Yeah, this may be difficult. An audit report would be cool: I would imagine you could feed in a data structure to store such merge information alongside the object you...

Hey @azmeuk! This is a really interesting problem, and I think it's pretty obvious where a three-way merge would be useful. I would love to support some way to do...

I'd be up for adding functionality into jsonschema-extractor to extract docstring data. I like the example of: ``` @attr.s class Foo: x = attr.ib(doc="this is a variable") ```

Hi, another opentelemetry-python contributor chiming in, thanks @Oberon00! > Why do the instrumentations check? Would you not just have the tracer check the context and return a non-reporting span? I...

> > I haven't seen examples of these expensive computations yet > > You have to look at everything the instrumentation does for each span. E.g. the sum of all...

> @toumorokoshi Your link is actually perfect to illustrate why we additionally could use the "surpress_instrumentation" context variable: In https://github.com/open-telemetry/opentelemetry-python/blob/v0.6.0/ext/opentelemetry-ext-wsgi/src/opentelemetry/ext/wsgi/__init__.py#L121, attributes are collected to be passed to start_span (so the...

@pauldraper will a PR be filed on this? I like this approach and would love to see it in the spec so I can implement it.

@jmacd @yurishkuro I'd like to do whatever I can to help move this forward. I'm itching to do some other OT stuff but don't want to leave work unfinished. Would...

> @toumorokoshi I like the overall direction, but my concern is with the handling of what you called "MAYBE" state. Specifically, per https://github.com/open-telemetry/oteps/pull/115/files#r446273010, I would not be able to implement...

@yurishkuro thanks for the thorough reply! I believe the Jaeger behavior as you described it is pretty much how OpenTelemetry works today: - effective no-op spans: write short-circuit, but a...