-
Notifications
You must be signed in to change notification settings - Fork 628
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 httpx version #1460
Fix httpx version #1460
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.
Can we leave #1459 open until we actually fix the instrumentation to work with that version?
@lzchen @ocelotl this is the 2nd time a version change like this has bit me, the first one being changed FastAPI requirements. I think that these need to be highlighted much more explicitly in new releases of the otel instrumentation since there is no other way to notify downstream users. In my case, I am using httpx 0.23.3 and requests were being instrumented ok, but then this version changed and now httpx is silently uninstrumented. I don't configure instrumentation dependencies explicitly as I instead pull in everything via the Could we get some better messaging around when these version requirements change between releases? I'm not sure what the right process is but silently failing can be very frustrating as often you don't realize it until you go and look for the data and it's not there. |
I added more color to a first-class issue report at #1745 |
Fixes #1459