Bumps dd-trace to the version 1.x, specifically 1.5.0.
Motivation
The need to use the new version of dd-trace and #64.
Testing Guidelines
Updated integration tests snapshots, also updated the integration tests to use the new API of dd-trace.
Additional Notes
The new version of dd-trace used, warns an error for the environment logger, which is handled in the integration tests.
It's worth mentioning that this only happens when using the writer SyncWriter in the configuration. It seems that it's expected in the future to use the TraceWriter, which doesn't cause to log a warning, but is not yet ready for use. https://github.com/DataDog/dd-trace-rb/issues/2312 which will be fixed in https://github.com/DataDog/dd-trace-rb/pull/2313
The package size is significantly increased compared to previous releases. This is due the bump on the dd-trace gem and multiple debase-ruby_source_core.
What does this PR do?
Bumps
dd-trace
to the version1.x
, specifically1.5.0
.Motivation
The need to use the new version of
dd-trace
and #64.Testing Guidelines
Updated integration tests snapshots, also updated the integration tests to use the new API of
dd-trace
.Additional Notes
The new version of
dd-trace
used, warns an error for the environment logger, which is handled in the integration tests. It's worth mentioning that this only happens when using the writerSyncWriter
in the configuration. It seems that it's expected in the future to use theTraceWriter
, which doesn't cause to log a warning, but is not yet ready for use. https://github.com/DataDog/dd-trace-rb/issues/2312 which will be fixed in https://github.com/DataDog/dd-trace-rb/pull/2313The package size is significantly increased compared to previous releases. This is due the bump on the
dd-trace
gem and multipledebase-ruby_source_core
.Types of changes
Check all that apply