-
Notifications
You must be signed in to change notification settings - Fork 173
fix(go/adbc/driver/internal/driverbase): Ensure to propagate the traceParent from the driver/database to connection #2951
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(go/adbc/driver/internal/driverbase): Ensure to propagate the traceParent from the driver/database to connection #2951
Conversation
…eParent from the driver/database to connection
|
@zeroshade / @lidavidm / @CurtHagenlocher |
zeroshade
left a comment
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.
Sounds good. Is there any way we can add a test for this at all?
Sure. I'll add a test. |
@zeroshade - I augmented an existing test |
|
Looks good to me! Thanks! |
|
@zeroshade - Any hints on how I can get the Python tests to run without errors? I don't seem to be able to re-run an individual step in this repository. |
|
ah. Matt this is the flake I mentioned the other day that I think is somewhere in arrow-go :) I kicked the jobs |
|
I'll try to look into the flake next week unless you're able to track it down lol |
|
@zeroshade / @lidavidm - Would you be able to merge this change when you have a chance? Thanks. |
This fix ensures the traceParent option is propagated from the Driver.Open to Database.Connect.