-
Notifications
You must be signed in to change notification settings - Fork 581
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
xray client: return an error if the HTTP request failed #5718
xray client: return an error if the HTTP request failed #5718
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This needs a changelog entry
I added a changelog entry, I hope that fits the current style. If not, I would appreciate suggestions, thanks! |
Co-authored-by: Damien Mathieu <42@dmathieu.com>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #5718 +/- ##
=====================================
Coverage 66.8% 66.8%
=====================================
Files 206 206
Lines 13207 13211 +4
=====================================
+ Hits 8827 8833 +6
+ Misses 4112 4111 -1
+ Partials 268 267 -1
|
cc @wangzlei as the soon to be owner of this instrumentation. |
c18e842
to
5e6df79
Compare
I reworked the error messages and added test cases / assertions. Some edge cases might be hard to test / not worth the effort like creating http requests. I hope you can find some time to review the changes or to comment if there is a need for changes. 🙏 |
Your PR now does more than just checking for non-200 HTTP status code. |
Thanks for the feedback. Following you gave a thumbs up on my comment above, I thought that would be appropriate.
Sorry for my confusion. |
My comment was about assertion of errors in tests. |
Rolled back in a moment, thanks. |
652be7c
to
82112a5
Compare
Sorry for the change, the old way of dealing with response bodies was restored. |
Hey 👋 Any chance to get this merged and released realistically in foreseeable future? |
This needs a second review from a @open-telemetry/go-approvers |
Anything I can do from my side to speed things up? It's already 3 month in review. |
Sorry. We don't have any codeowners for the component, so reviews and such are likely to be much slower. |
Thanks for the quick response. |
No description provided.