Robert Pająk

@hjweddie Can you please sign the CLA?

Moved to next milestone as we have a workaround. I will try to solve this when working on https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/issues/915 I want to create to create API that could be used...

@pjanotti PTAL. Feel free to add edits and merge 😉

@rodrigc Here is a list of all reports: https://pkg.go.dev/vuln/list. I think that https://pkg.go.dev/vuln/GO-2022-1059 is a good candidate. You can have a "success" testdata with the latest `golang.org/x/text/language` and a "failing"...

How about adding a `OTEL_FAIL_FAST` env var to control this behaviour (default for SDK: `false`, supported values: `true`, `false`)? Side note: I assume that auto-instrumentation could have a different default...

I think that "debug mode" != "fail fast mode". Should we rename the issue to "fail fast mode"? The "fail fast mode" may be also beneficial in production to get...

@reyang 👍 Side note. Right now the spec does not allow fail fast when parsing numeric and enum env vars...

> But let's not have the discussion on Distribution here, the focus should be around clarifying "Auto-Instrumentation" Here you are: https://github.com/open-telemetry/opentelemetry-specification/issues/2873

I would stand that it is simply ["automatic-instrumentation"](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/glossary.md#automatic-instrumentation) Take notice that for Python auto-instrumentation you do not need to write code as you can use env vars to configure stuff...

I see your concern... But right now I have no good answer (nor opinion) for it 😢 > My question is, how do we call the piece of software that...