Robert Pająk
Robert Pająk
The Go SIG decided that the Go Logs SDK does not have to be an exception. I change the PR so that it only clarifies the specification.
OTel Go implementation is compliant with the baggage specification. See https://www.w3.org/TR/baggage/#value > The percent code point (U+0025) MUST be percent-encoded Actually, it looks like there is a bug in OTel...
`gray_key=version%3Dv2` and `gray_key=version=v2` values are equivalent. The Go implementation avoids percent encoding when it is not necessary. Nothing requires to pass the exact same header value during propagation.
Do we have some benchmarks that would demonstrate the overhead of the added randomness support? Can we add `benchstat` results?
> because in that repo all the component owners are added to @open-telemetry/java-contrib-triagers (e.g. so that they can label issues), which then makes them repo "collaborators". Maybe we could do...
During the **Project triage - EU-friendly** we discussed that probably it would be better to create a new Code Owner role in https://github.com/open-telemetry/community/blob/main/guides/contributor/membership.md and that the these teams will have...
@dmathieu, PTAL
FYI @codeboten
> I guess you can just use the new link, which would be something like `https://issues.oss-fuzz.com/issues?q=title:opentelemetry is:open&s=issue_id:desc` This is what I am using. However, - the docs should be updated...