New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix opentracing.propagation.InvalidCarrierException: carrier not a collection #1720
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1720 +/- ##
==========================================
- Coverage 60.98% 60.82% -0.16%
==========================================
Files 167 167
Lines 12104 11958 -146
==========================================
- Hits 7382 7274 -108
+ Misses 4722 4684 -38
Continue to review full report at Codecov.
|
I think maybe |
The failure on CI does not seem to be related to this modification? |
That's right, I think that particular test is flaky on github CI environment, let me trigger a re-run |
Hello @wei840222, Thanks for updating this PR. There are currently no PEP 8 issues detected in this PR. Cheers! 🍻 Comment last updated at 2021-07-13 12:10:58 UTC |
…llection (#1720) * fix opentracing.propagation.InvalidCarrierException: carrier not a collection * Update jaeger.py * update injected headers back to origin header * Update jaeger.py
issue: #1591
When open the jaeger tracing like guide: https://docs.bentoml.org/en/stable/guides/tracing.html.
It will raise an exception on runtime and all api request become s to 500.
log:
and found inject function in https://github.com/jaegertracing/jaeger-client-python/blob/master/jaeger_client/codecs.py#L57 only accept dict type, and seems request header not need to pass to the span.
so, I follow the opentracing example on github https://github.com/opentracing/opentracing-python#outbound-request only pass a empty dict to it.