Describe the bug
During the lifetime of my application, everything is working properly.
Once I closed it, I have a "warning" in the collector:

warn zapgrpc/zapgrpc.go:191 [transport] transport: http2Server.HandleStreams failed to read frame: read tcp [::1]:4317->[::1]:64933: wsarecv: Une connexion existante a dû être fermée par l’hôte distant. {"grpc_log": true}

"Une co

Bug Report

If you use the B3 propagator with e.g. the Grpc.Core instrumentation then it fails to connect the parent spans to the new server spans because gRPC headers are always lower case.

The issue is that the B3 propagator does not store the headers as lower case and then this line in the Grpc.Core instrumentation does not do case-insensitive comparison: https://github.com/open-telemetry/

Consolidating thread on all open plugin requests.

All issues need help if you'd like to contribute to the project 😃

The documentation on writing a plugin can be found here.

• Umami DavidWells/analytics#149
• Firebase DavidWells/analytics#133
• Plausible

• This only affects the JavaScript OpenTel

For some uses cases it would be useful to have an option in the gr_satellites command line tool that skips the demodulator and sends the input the directly to the deframer.

There are many places to add tests with ”gtest_add_tests“, But gtest_add_tests is a new feature of Cmake 3.9 version, When I try to compile with 3.8.5, it doesn't compile the test code anyway, this confused me for a while.

Added in open-telemetry/opentelemetry-specification#1130

We were early adopters of some of these limits, but they are not formalized in the spec and we should update.

as mentioned in the UPDATING file, there are some domains in the list that represent the same domain but differ by a commonly confused character (like dashes, em dashes, and en dashes). Theres also a few that look like two characters smushed together (I think there's one like that for fi in a couple places). These are likely due to copy-paste errors or from parsing the PDF, however I want to be