-
Notifications
You must be signed in to change notification settings - Fork 4
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
[SDTEST-1129] Internal: decouple patcher from tracing, update ruby 3.4 compatibility #252
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.
LGTM 👍🏼
If you have time, maybe it makes sense to give a bit love to the untyped RBS returns.
|
||
def on_patch_error: (untyped e) -> untyped | ||
|
||
def default_tags: () -> untyped |
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.
I know that it might be cumbersome to fill in, but maybe we can shape it a bit? Like if it's Array, we can state it?
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.
Hopefully, while building auto instrumentation feature I will have a chance to rethink all of it and remove this all. Generally, all this stuff was created for APM use case and most of it isn't required for this more focused library and narrower use case.
…fix is relased by maintainers
What does this PR do?
Migrates patcher code from Datadog::Tracing::Contrib to Datadog::CI::Contrib
Motivation
Reduce coupling with private tracing details. Move all contrib/integrations code to CI to be able to develop independent auto-instrumentation feature.
How to test the change?
It works if unit tests still pass