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

[PROF-6838] Upgrade to libdatadog 1.0.1.1.0 #2530

Merged
merged 1 commit into from
Jan 10, 2023

Conversation

ivoanjo
Copy link
Member

@ivoanjo ivoanjo commented Jan 6, 2023

What does this PR do?:

Upgrade dd-trace-rb to use the latest libdatadog release (1.0.1.1.0).

This libdatadog release includes:

Motivation:

Keep up with latest improvements and features being added to libdatadog.

Additional Notes:

I've skipped packaging the libdatadog 1.0.0 release, and we're going straight to 1.0.1.

I'm opening this PR as a draft because libdatadog 1.0.1.1.0 has not yet been published to rubygems (hence our CI failing with this PR). Once I've published it, I'll re-trigger CI and remove the draft label with no further changes. Update: Published, and dropped draft label.

How to test the change?:

The changes in this PR are already covered by the existing tests.

**What does this PR do?**:

Upgrade dd-trace-rb to use the latest libdatadog release (1.0.1.1.0).

This libdatadog release includes:

* A number of API renames (documented in
  <DataDog/libdatadog#73>)
* The addition of `endpoint_counts`, which we don't use yet, but that
  needed a few additional changes to API calls and specs.

**Motivation**:

Keep up with latest improvements and features being added to libdatadog.

**Additional Notes**:

I've skipped packaging the libdatadog 1.0.0 release, and we're going
straight to 1.0.1.

**How to test the change?**:

The changes in this PR are already covered by the existing tests.
@github-actions github-actions bot added the profiling Involves Datadog profiling label Jan 6, 2023
@ivoanjo ivoanjo changed the title Upgrade to libdatadog 1.0.1.1.0 [PROF-6838] Upgrade to libdatadog 1.0.1.1.0 Jan 6, 2023
ivoanjo added a commit to DataDog/libdatadog that referenced this pull request Jan 6, 2023
**What does this PR do?**:

Package libdatadog 1.0.1 for Ruby.

**Motivation**:

Use latest libdatadog version from Ruby.

**Additional Notes**:

The 1.0.0 release was never packaged, and I don't think it's worth
doing so just for completeness. (The binaries are still up on GitHub,
so this decision can be revisited if ever we change our minds).

I'm following along the checklist at
<https://github.com/DataDog/libdatadog/blob/main/ruby/README.md#releasing-a-new-version-to-rubygemsorg>

**How to test the change?**:

I have an open draft PR to integrate this release into the Ruby
profiler: DataDog/dd-trace-rb#2530 .
The downstream Ruby integration does not pick up new releases
automatically.

To test this locally, you'll need to download package the gem
manually, and then install it and you'll be able to run the
dd-trace-rb test suite using the draft branch above.
ivoanjo added a commit to DataDog/libdatadog that referenced this pull request Jan 6, 2023
**What does this PR do?**:

Package libdatadog 1.0.1 for Ruby.

**Motivation**:

Use latest libdatadog version from Ruby.

**Additional Notes**:

The 1.0.0 release was never packaged, and I don't think it's worth
doing so just for completeness. (The binaries are still up on GitHub,
so this decision can be revisited if ever we change our minds).

I'm following along the checklist at
<https://github.com/DataDog/libdatadog/blob/main/ruby/README.md#releasing-a-new-version-to-rubygemsorg>

**How to test the change?**:

I have an open draft PR to integrate this release into the Ruby
profiler: DataDog/dd-trace-rb#2530 .
The downstream Ruby integration does not pick up new releases
automatically.

To test this locally, you'll need to download package the gem
manually, and then install it and you'll be able to run the
dd-trace-rb test suite using the draft branch above.
@codecov-commenter
Copy link

Codecov Report

Merging #2530 (e030ed9) into master (194230e) will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2530      +/-   ##
==========================================
+ Coverage   98.31%   98.32%   +0.01%     
==========================================
  Files        1124     1124              
  Lines       60657    60660       +3     
==========================================
+ Hits        59635    59645      +10     
+ Misses       1022     1015       -7     
Impacted Files Coverage Δ
spec/datadog/profiling/http_transport_spec.rb 100.00% <ø> (ø)
lib/datadog/core/diagnostics/environment_logger.rb 99.21% <0.00%> (+0.78%) ⬆️
...filing/collectors/cpu_and_wall_time_worker_spec.rb 94.73% <0.00%> (+2.34%) ⬆️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@ivoanjo ivoanjo marked this pull request as ready for review January 6, 2023 15:02
@ivoanjo ivoanjo requested a review from a team January 6, 2023 15:02
@ivoanjo
Copy link
Member Author

ivoanjo commented Jan 6, 2023

Marked PR as ready for review :)

@ivoanjo ivoanjo merged commit cf56509 into master Jan 10, 2023
@ivoanjo ivoanjo deleted the ivoanjo/prof-6838-libdatadog-1.0 branch January 10, 2023 08:39
@github-actions github-actions bot added this to the 1.9.0 milestone Jan 10, 2023
@TonyCTHsu TonyCTHsu mentioned this pull request Jan 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
profiling Involves Datadog profiling
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants