Fix OTLP gRPC metadata key normalization - #46
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Normalize OTLP/gRPC metadata keys to lowercase before constructing trace,
metrics, and log exporters.
grpcio rejects HTTP-style uppercase metadata keys such as
Authorization,causing exports to fail locally before any request reaches the backend.
Changes
Validation
tests/test_sdk_initialization.py: 38 passed.git diff --checkpassed.Post-merge
Create and push immutable fork tag
fr-v0.52.6.35. Ocelle must vendorfrom that tag rather than from a dirty working tree.