Skip to content

Conversation

@hoolioh
Copy link
Contributor

@hoolioh hoolioh commented Nov 7, 2025

What does this PR do?

Rename datadog-profiling crates according to the new naming convention.

Motivation

Prepare datadog-profiling to be published.

Copy link
Contributor

@morrisonlevi morrisonlevi left a comment

Choose a reason for hiding this comment

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

Some small comments that may or may not to be resolved, but overall it looks good.

default = ["ddcommon-ffi"]
cbindgen = ["build_common/cbindgen", "libdd-common-ffi/cbindgen"]
ddtelemetry-ffi = ["dep:libdd-telemetry-ffi"]
libdd-telemetry-ffi = ["dep:libdd-telemetry-ffi"] # package_ffi_on_windows needs it
Copy link
Contributor

Choose a reason for hiding this comment

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

Was this intentionally dropped?

Copy link
Contributor

Choose a reason for hiding this comment

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

This is weird, it was needed by the gitlab workflow when I renamed libdd-telemetry-ffi because windows build were unable to find the ddtelemetry-ffi feature and I duplicated it.
But now it runs without problems, so idk what have changed there... I'm taking a look.

Copy link
Contributor

Choose a reason for hiding this comment

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

Ok, mystery solved, @hoolioh fixed it 🎉

Copy link
Contributor Author

@hoolioh hoolioh Nov 11, 2025

Choose a reason for hiding this comment

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

We kind of stepped in each other toes. We changed the feature name to the new name due to the windows build was failing and then I realized that it was a mistake and fix the windows build script itself

assert_eq!(internal["execution_trace_enabled"], "false");
assert_eq!(internal["extra object"], json!({"key": [1, 2, true]}));
assert!(internal["libdatadog_version"].is_string());
assert!(!internal["libdatadog_version"].as_str().unwrap().is_empty());
Copy link
Contributor

Choose a reason for hiding this comment

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

Not necessarily a blocker, but we talked about using either version, whether the profiling or profiling-ffi version as they should be the same. This tests that it's not empty, which isn't the same.

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 I remember we solved that in the original PR but I didn't port the change to this branch. I'll port the changes here. The solution was to use the ffi package version.

Base automatically changed from julio/versioning/crashtracker to main November 11, 2025 00:41
@dd-mergequeue dd-mergequeue bot requested review from a team as code owners November 11, 2025 00:41
@hoolioh
Copy link
Contributor Author

hoolioh commented Nov 11, 2025

/merge

@dd-devflow-routing-codex
Copy link

dd-devflow-routing-codex bot commented Nov 11, 2025

View all feedbacks in Devflow UI.

2025-11-11 12:59:01 UTC ℹ️ Start processing command /merge


2025-11-11 12:59:05 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in main is approximately 34m (p90).


2025-11-11 13:27:42 UTC ℹ️ MergeQueue: This merge request was merged

@dd-mergequeue dd-mergequeue bot merged commit 7978fce into main Nov 11, 2025
37 checks passed
@dd-mergequeue dd-mergequeue bot deleted the julio/versioning/profiling branch November 11, 2025 13:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci-build mergequeue-status: done profiling Relates to the profiling* modules.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants