-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Disable process scraper for any non Linux/Windows OS #1328
Disable process scraper for any non Linux/Windows OS #1328
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1328 +/- ##
==========================================
+ Coverage 89.67% 89.69% +0.01%
==========================================
Files 215 214 -1
Lines 15124 15126 +2
==========================================
+ Hits 13563 13567 +4
+ Misses 1138 1137 -1
+ Partials 423 422 -1
Continue to review full report at Codecov.
|
dc34ed7
to
6829281
Compare
This is the highest I can possibly get coverage for this PR since coverage reports are Linux only |
Please rebase |
I closed this by mistake |
6829281
to
55169b7
Compare
The build checks don't seem to be getting triggered, do I need to recreate this PR since it was closed? |
…still read the response body. (open-telemetry#1328) * chore(zipkin-exporter): relay on the status code for the request but still read the response body. * fix(zipkin-exporter): fix tests. * chore(zipkin-exporter): adds changelog. * chore: 202 -> http.StatusAccepted Co-authored-by: Chris Bandy <bandy.chris@gmail.com> * chore: 202 -> http.StatusAccepted Co-authored-by: Anthony Mirabella <a9@aneurysm9.com> Co-authored-by: Chris Bandy <bandy.chris@gmail.com> Co-authored-by: Anthony Mirabella <a9@aneurysm9.com> Co-authored-by: Tyler Yahn <MrAlias@users.noreply.github.com>
Much of the process scraper functionality is not supported on non Linux/Windows OSs, or is implemented poorly, e.g. this was taking about 15s to complete on my Macbook. Have opted to explicitly disable the scraper on any other OS.
Also fixed issue where an error wasn't returned on initialization in one case and added a test for this.
Fixes #958