- Notifications
You must be signed in to change notification settings - Fork 231
opentelemetry bridge #1411
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
opentelemetry bridge #1411
Conversation
Didn't actually do the testing I mentioned, but tuples are safer than mutating in place.
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.
Looks great! It would be interesting to know if this has any negative effects on performance. And if it does, I wonder if using a list of tuples instead of a tuple of tuples would help, as we wouldn't be constantly recreating the outer container.
Co-authored-by: Benjamin Wohlwend <bw@piquadrat.ch>
Also fix up some embarrassing mistakes from the first pass
Because I added opentelemetry to reqs-base.txt and it requires the contextvars backport, this test now fails on py3.6, and isn't necessary for newer versions. I think that's acceptable, considering py3.6 is EOL anyway.
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.
Some minor comments, other than that LGTM!
Check for opentelemetry to make sure we don't have failures on that matrix
Related issues
Closes #1362