Skip to content
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 DataDog trace exporter #400

Merged
merged 3 commits into from
Apr 5, 2021
Merged

Conversation

owais
Copy link
Contributor

@owais owais commented Apr 3, 2021

Description

Fixed DataDog trace exporter

ddtrace package introduced some breaking changes that break the
DataDog trace exporter. This commit downgrades the dependency to last
know working version to fix the exporter.

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Checklist:

See contributing.md for styleguide, changelog guidelines, and more.

  • Followed the style guidelines of this project
  • Changelogs have been updated
  • Unit tests have been added
  • Documentation has been updated

@owais owais requested review from a team, toumorokoshi and hectorhdzg and removed request for a team April 3, 2021 23:26
`ddtrace` package introduced some breaking changes that break the
DataDog trace exporter. This commit downgrades the dependency to last
know working version to fix the exporter.
@ericmustin
Copy link
Contributor

@owais thanks for the ping here. Afaik, nothing wrong with keeping things pinned for now like you’ve done, but I’ll sync with @majorgreys this week on how we can address long term in dd-trace-py. Will followup when I have more.

Copy link
Member

@toumorokoshi toumorokoshi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minor nit about the changelog, otherwise LGTM!

I think regardless of how ddtrace chooses to handle it, we should get this merged in so we can keep CI working and users unbroken.

CHANGELOG.md Outdated
@@ -7,6 +7,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
## [Unreleased](https://github.com/open-telemetry/opentelemetry-python-contrib/compare/v0.19b0...HEAD)

### Changed
- Downgrade DataDog exporter's `ddtrace` dependency so the exporter continues to work.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be more accurate to say that the version range has been restricted? We've never prescribed a specific version.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. Updated.

@owais
Copy link
Contributor Author

owais commented Apr 4, 2021

@ericmustin IMO direct dependencies like this should always specify a fixed version instead of an open range. My recommendation would be to keep the dependency pinned and have the maintainer of opentelemetry-exporter-datadog update it to newer versions as they see fit.

Copy link
Member

@toumorokoshi toumorokoshi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

@lzchen lzchen merged commit 41b5f23 into open-telemetry:main Apr 5, 2021
@owais owais deleted the ddtrace-exporter branch April 5, 2021 16:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants