Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Separate context propagation (OTEP 66) #769
This PR is absolutely massive. Sorry about that but there was no real great way to split it up and still have it build/pass tests
Which problem is this PR solving?
Short description of the changes
Propagators (core and jaeger)
@@ Coverage Diff @@ ## master #769 +/- ## ========================================== - Coverage 92.93% 92.39% -0.55% ========================================== Files 233 239 +6 Lines 10545 12621 +2076 Branches 1028 1128 +100 ========================================== + Hits 9800 11661 +1861 - Misses 745 960 +215
In order to keep PR short (off the top of head):
I agree except that noop implementations won't ever be in the API in this case. Context is meant to be a standalone concept that the api and sdk both consume.